The client record
Every proposal hangs off the client the CRM already knows — the same one Miira opened when they first wrote.
One workspace, eight modules
live — in productionThe proposal is built from your own catalogue and your client reads it on their phone. When they accept, the contract goes out for signature on that same record — so what was agreed and what gets charged can’t drift apart.
A proposal built from the catalogue with two line items and a total, accepted from the client’s phone and signed.
The quote went out as a PDF. The client asked for two changes over WhatsApp, so you sent a second PDF. The contract is a document someone printed, signed, photographed at an angle and sent back. When the invoice comes, nobody is sure which of the three versions is the one that counts.
Every line below is running in production today.
Proposal and contract are one route inside Niima — splitting them would make you reconnect by hand what is a single journey.
Every proposal hangs off the client the CRM already knows — the same one Miira opened when they first wrote.
The proposal is built from the same catalogue the WhatsApp agent quotes from. One list of prices, not two that drift.
A signed contract can be set to invoice, on the same double-entry ledger Kiipu collects against.
Quoting and signing is one of the six modules you choose: one with Answer, three with Collect, and all six come with Deliver. If you already have a plan, swap it in once a month or add it as an extra.
See pricing →What is running today, and what is not:
Fiilz takes it from there: the pieces, their versions, and the client approving what you deliver — on the same client record.