From the yes to the signature, without leaving the workspace.

Nothing of Niima is built yet — this is the design, published as it stands. The idea: the proposal, the signature and the portal the client logs into are the same record, so what was agreed and what is being charged can never drift apart.

Open workspace →

the idea

One record from the proposal to the invoice.

// Designed, not built. Every line below is a plan.

Proposals the client reads in the browser, not a PDF attached to an email thread
A signature on that same proposal, so the signed version is the version
A portal where the client sees what was agreed and what is being delivered
Money that starts from the signed contract — never re-typed from it

why it is not built yet

It was designed to sit on top of things that had to exist first.

The ledger came first

A signed contract that turns into money needs an auditable place for that money to live. That foundation is built and running under Kiipu — it was not going to be improvised underneath a proposal.

The client record came first

A proposal belongs to a client, and that client is the same one the CRM and the agent already work with. One record, not a copy per module.

The design is done and public

Requirements, flows and decisions are written. Publishing them as a plan — and saying plainly that there is no code — is the version of this page we can stand behind.

What it does NOT do yet

Read this before anything else on this page:

No code has been written. There is no Niima module in the product today.
What exists is the design — requirements, screens, flows and decisions, written and reviewed.
There is no public date. When there is one, it will be said here and not before.
Everything below is written as a plan, because that is what it is.

// what is real today

The modules underneath already run.

Miira qualifies WhatsApp leads and Kiipu collects on a double-entry ledger. Niima is designed to sit on top of both — that is why they came first.

See Kiipu →