You can audit us before you meet us.

Small and mid-sized businesses do not run on one system. They run on WhatsApp Web for talking, a spreadsheet for the pipeline, email for chasing invoices and a document nobody updates — and the real cost is not the tools, it is the invisible work of keeping them in sync by hand, plus the leads and promises that fall through the gaps between them.

niiko is one workspace where every module shares one client record, from the first WhatsApp message to the last invoice. The wedge is the agent: it answers and qualifies every inbound lead in seconds, day or night, and the record it creates is already a client in the CRM with the whole conversation attached. Each additional module is worth more because the record is already there — which is the part a competitor cannot copy by shipping a similar feature.

We are building it in a market we understand from the inside: Latin America, where WhatsApp is not a channel but the channel, and where the alternative to niiko is usually not a competitor — it is a spreadsheet.

The longer version of this argument →

The agent that qualifies leads for niiko's own customers is the same agent that qualifies Vorluno's. We are the first user of every module we sell, which means a defect reaches us before it reaches anyone else — and it is why the changelog reads like a log rather than a brochure.

Several decisions were made before there was a single byte of customer data because they cannot be retrofitted: per-tenant isolation enforced by the database rather than by remembering a filter, a per-subject encryption key so the right to erasure works even in backups, a double-entry ledger for every movement of money, card data that never touches our infrastructure, and a schema catalogue so no event can quietly change shape. Those are the questions a procurement team asks the day a real customer shows up, and they are answered.

What that costs is speed on the first day. What it buys is not having a quarter of remediation between a serious customer and a signature.

Revenue, retention, pipeline and burn are not published here, and that is a decision rather than an omission. A financial figure printed on a static page is a figure that ages on its own — correct the week it is written, misleading three months later, and nobody remembers to come back. We would rather hand you current numbers in a conversation, with the context that makes them mean something, than leave a stale one in public.

Ask, and you get the full picture under an NDA: monthly recurring revenue and its build, retention by cohort, customer acquisition cost and payback, burn and runway, the pipeline as it stands, and the concentration risk that comes with being early. Including the parts that do not flatter us — a studio that publishes its own audit findings is not going to start editing at the point where it matters most.

And one thing you will never get from us: a projection presented as a fact.