The approval stops living in someone’s chat.

Every piece with its versions stacked, an approver who knows it’s theirs, and a client who says yes — or asks for changes — on a screen of their own. No account to create, no workspace to learn.

Open workspace →

the day it goes wrong

Which version did they actually approve?

The file went out as an attachment. The changes came back as two voice notes and a screenshot. Three weeks later nobody can say which version the client said yes to, whether that round was already billed, or who was supposed to answer. The file is somewhere. The decision isn’t anywhere.

what it does

The work and its decision, in the same place.

// Every line below is running in production today.

Projects with their own sections — the work organised the way you deliver it, not the way a folder tree forces you to
Pieces that stack their versions: a file you upload, or a Figma link
An assigned approver per piece, so “who signs off on this” stops being a question
The client approves or asks for changes on a screen of their own, reached by a link — no account of yours
Feedback as threads anchored to the piece, which get resolved — not messages that scroll away
Milestones that group pieces: when the last one is approved, the milestone closes

what it’s wired to

An approval is a trigger, not an ending.

// Nothing below is re-typed anywhere — it is the same record moving on.

The client record

Every project hangs off the client the CRM already knows — the same one Miira opened when they first wrote.

The money

A closed milestone says there is something to bill, on the same double-entry ledger as every other cent in Kiipu.

Your client’s own door

They come in through their own link and see only what’s theirs. Your workspace stays yours.

which plan

Fiilz ships with Scale.

The plans split by which stretch of the funnel they close end to end — Starter answers, Growth gets paid, Scale delivers. Fiilz is the delivering half of Scale, next to Niima’s proposals and contracts.

See pricing →

What it does NOT do yet

What is running today, and what is not:

Running in production: projects, sections, pieces with their versions, assigned approvers, the client’s approval screen, feedback threads and milestones.
The client portal exists as a frame — its sections are still being filled in. Today your client decides on the review screen their link opens, not from a portal home.
A closed milestone reports that there is something to bill. Issuing that invoice automatically is a setting with no screen yet, so today a person creates it.
An accepted proposal does not open the project on its own yet — you create the project.
There is no “see it as the client sees it” preview for your own team.

// the other half

Delivering is half the job. Quoting is the other.

Niima turns the yes into a numbered proposal and a signed contract — same workspace, same client record, nothing printed.

See Niima →