docs / from-proposal-to-signature
From the yes to the signature
Niima is one path, not two tools. The proposal is built from the same catalogue the agent quotes from, and the contract is signed on the same record — so what was agreed and what gets charged cannot drift apart.
before you start
What this guide covers.
// Contracts are not a separate module. They are the second half of this one.
This guide takes a deal from a proposal to a signed contract without leaving niiko and without printing anything. The split between 'proposal software' and 'signature software' is an artifact of how those tools were sold; your client should never experience it.
step one
Build it from your own catalogue.
// The same catalogue the agent quotes from — so a price never contradicts itself.
Proposal lines come from your catalogue: your services, your prices. This is the same source the WhatsApp agent uses when it quotes, which is what prevents the most embarrassing failure in this whole flow — an agent quoting one number and the proposal saying another.
- Sections you write once and reuse across proposals
- Lines you add or drop until it fits the budget
- Prices that come from the catalogue, not from memory
step two
Let the client decide from their phone.
// A link they open, read and answer — accept or decline, right there.
The client gets a link, reads the proposal on their phone and accepts or declines on the spot. No account, no PDF attachment, no thread of 'did you get my email'. The decision lands on the record.
step three
Send the contract for signature.
// Your own templates, and the signers you name.
Contracts come from your own templates, with the signers you name. Because it happens on the same record as the accepted proposal, what was agreed and what is being signed are the same thing rather than two documents somebody has to reconcile.
step four
Sign in the browser.
// They read it, type their name and sign. No printer, no photo of a page.
The signing ceremony happens in the browser: the signer reads the document, types their name and signs. What was signed stays attached to the deal — not in an inbox, not on somebody's desktop.
What this guide doesn’t cover
Running in production: proposals with catalogue lines, the client's public decision, contracts from templates and the in-browser signing ceremony. What is not built yet:
- An accepted proposal does not open the project in Fiilz on its own yet — you open it.
- Contracts are not a separate module: they are the second half of this one, on the same record.
Last updated: 2026-09-02.