// roadmap
What’s live, what’s next, what’s further out.
This is the real state of the niiko platform, kept by hand from our own build log. It’s not a list of promises: no dates, on purpose — we publish what ships, when it ships. What you see marked live is running in production today, including on niiko’s own WhatsApp number.
// We ship in public on the studio changelog — vorluno.dev/changelog.
// now — in production
Running your business today.
Miira
liveAn AI agent that answers and qualifies every lead over WhatsApp — in real time, day or night.
CRM
liveEvery client, deal and conversation on one timeline that reflects reality — not one you feed.
Ciita
liveScheduling on your real availability: a booking page anyone opens without an account, and appointments the agent proposes from that same calendar.
Runs today, as an add-on to your plan.
Kiipu
liveCollections that don’t chase people — payment links, reminders that go out on their own, receipt photos read by AI, and a ledger that always balances.
The core runs in production. Per-workspace reminder times are not built yet.
Fiilz
liveThe work you deliver, project by project: pieces with their versions, an assigned approver, and the client approving or asking for changes on a screen of their own.
Running today. The client portal exists as a frame — its sections are being filled in.
Riinda
liveYour team, looking inward: what needs attention, who is carrying what, and who can take the next thing without being buried.
Iiko
livePublishing tied to proof: compose once, see it as it will look on X, LinkedIn and your site, sign it, and learn which post brought which client.
Runs today. GitHub traffic is the one stretch of the funnel that still says “no data”.
Niima
liveFrom the yes to the signature: proposals built from your own catalogue, accepted from the client’s phone, and the contract signed right there.
Proposals and contracts are one path, in one module — not two.
capability by capability
What each module actually does today.
A module is too coarse an answer to the question people bring here — «does it already do the thing I need?». So here they are one by one, with the same labels.
Every inbound lead answered and qualified
Over WhatsApp, in seconds, at any hour. The same agent qualifies Vorluno’s own leads.
Handoff to a person, mid-conversation
The moment someone steps in, the agent steps back — no double replies, no fighting over the thread.
The agent answers from what you taught it
Services, prices and policies you wrote down — not a prompt somebody tuned.
Saved views instead of static segments
A view is a live query, so an audience is never out of date.
A booking page anyone opens, no account
And the times the agent offers come from that same availability — they cannot contradict each other.
Reminders that go out on their own
On schedule, from a number of their own so your sales number stays clean.
A receipt photo, read and matched
The client uploads it, the system reads it and matches it, a person confirms.
Every movement in a ledger that balances
Double-entry by construction. Card numbers never touch our infrastructure.
From proposal to signature in one path
Built from your own catalogue, accepted from the client’s phone, signed right there.
The client approves the work on their own screen
Versions per piece and one named approver — no «final_v3_REAL».
Who on your team is carrying what
Read from the work already in niiko, so nobody has to keep a second board alive.
Erasure that reaches the backups
Each data subject gets their own key at creation; destroying it makes their data unreadable everywhere a copy exists.
Autonomy set per capability, with a cap on money
Every turn already resolves its policy and the screen shows it. Enforcement is behind a flag that is off — the gate does not refuse the action yet.
Your own reminder hours
The schedule runs; choosing the windows per workspace is not built yet.
The client portal, section by section
The frame exists and the decision already happens on the review screen. The rest of the sections are being filled in.
An accepted proposal opens the project
Declared as missing on purpose: there is no code doing this today.
A unified inbox you can open
The threading engine runs inside Miira today. There is no Inbox page — that is still ahead.
Knowledge linked to clients and deals
Designed, not built yet.
// next
Being built, and designed.
Miira outbound campaigns
in buildThe outbound side of Miira: reaching an audience, not just answering it. The foundation runs in production; the campaign wizard, the sequence engine and Meta template sync aren’t built yet.
In build — not available yet.
Inbox
partialWhatsApp and email in one thread, so nothing falls through the cracks. The threading engine runs inside Miira today.
A capability today, not a module you can buy — the threading engine runs inside Miira, and there is no Inbox page to open. A standalone unified inbox is still ahead.
Notes
soonKnowledge tied to the work — linked to clients and deals, not lost in a folder graveyard.
Designed; not built yet.
Last reviewed: 2026-09-21. This page is curated by hand from our internal build log — the date is a freshness signal, not a promise.
// See what shipped, dated, on the studio changelog: vorluno.dev/changelog. Or see the modules that are live.