Skip to content
use case — one record

One record per client. The chat, the deal, the invoice and the booking.

liveMost tools make you carry the client around: a chat here, a spreadsheet there, an invoice in a third place. Here the record is one, and every module writes to it.This is how niiko runs its own sales: lead in WhatsApp, deal in the CRM, invoice in Kiipu, kickoff in Ciita.

Modules involved: Miira, CRM, Kiipu, Ciita

how it works

Step by step

  1. It starts in the chat

    Miira answers the lead and creates the contact with what it learned: name, need, budget, urgency.

    contact, without typing it
  2. It becomes a deal

    In the CRM the contact moves through your stages — with the tasks, notes and calls logged on the same record.

    one pipeline, real
  3. It becomes an invoice

    Kiipu issues the invoice from the deal and sends a link your client opens without an account: they transfer, upload the receipt, and someone on your team approves it before it counts. Reminders go out on their own.

    paid without chasing
  4. It becomes a date

    Ciita books the kickoff against your real availability — and the agent can offer those same slots inside the chat.

    calendar that fills itself
what you need

Before you start

  • A plan with the modules the story needs: Free brings the agent and the CRM; scheduling and invoicing come with the paid plans.
plans

Free includes Miira and the CRM. Scheduling, invoicing, deliveries, contracts, team and publishing are modules you pick on any paid plan; Deliver brings them all.

Modules involvedMiiraCRMKiipuCiita

See the plans →

What it does NOT do yet

Said plainly

  • It isn't an accounting system: Kiipu keeps a ledger and can sync with QuickBooks, but it doesn't replace your accountant.
  • The record follows the client, not other systems: importing from another CRM is by file, not by live sync.
start

Stop carrying the client around

Create the workspace and let the first lead write its own record.