A tool is not yet a system
I've described elsewhere why a dozen AI tools bought side by side rarely add up to a whole: each has its own memory, its own rules, and what one learns never reaches the next. The alternative isn't a bigger toolbox, but a shared foundation — and many surfaces on top of it.
I want to show two of them concretely here: ZenBI and ZenSales. They look very different — one answers business questions, the other turns a sales conversation into a clean CRM entry. But they stand on the same backbone. That's exactly what makes the difference.
The shared foundation
Beneath both lies what our operating-system idea is about: a shared memory, a shared knowledge graph, shared governance. What the system learns about a company — its vocabulary, its customers, its quirks — doesn't live separately in each application, but once, shared.
That sounds technical, but it has a very practical consequence: a new surface doesn't have to get to know the company from scratch. It docks onto a foundation that already knows what's going on. That's why the second application becomes useful faster than the first — and the third benefits from what the first two learned.
ZenBI — ask your business in your own language
Most companies sit on more data than they use — spread across systems, locked in dashboards someone had to build first. Whoever has a question needs either SQL skills or an appointment with the BI department.
ZenBI flips that around. You ask in natural language — the way you'd ask a colleague: "How did margins develop last quarter, by region?" ZenBI understands the context and the business logic, pulls the relevant data together, and picks the right visualization itself. No SQL, no dashboard-building.
The point isn't only the natural language — plenty can do that part. The point is that ZenBI sits on the shared memory. It knows what "margin" means in this company, because the foundation knows. An answer without that context is a calculator; an answer with it is a judgement.
ZenSales — when your voice becomes the CRM
The other surface sits at the opposite end of the day: after the customer meeting, in the car, when the details are still fresh and the discipline to type them neatly into the CRM is at its lowest.
ZenSales is a voice-to-CRM for the German Mittelstand. You speak what happened — and out of it comes a structured contact entry, with the right fields, and on request a suggestion for the next step. GDPR-compliant, eligible for funding, a native app in the App Store. Not a form you fill out in the evening, but a sentence you speak on the move.
Here too the value lies in the foundation: what ZenSales records about a contact isn't trapped on an island. It belongs to the same memory the rest of the system draws on — controlled and traceable.
Why this is more than two apps
You could see ZenBI and ZenSales as two separate products. That would be the toolbox view. The operating-system view is a different one: they are two faces of the same system.
What ZenBI learns about the business and what ZenSales records about customers flow into the same backbone. A sales question in ZenBI may know what was discussed in the field — controlled, in the same system, under the same governance. That's the compounding interest separate apps never reach: each surface makes the others smarter, instead of fragmenting the picture further.
Step by step, not all at once
That explicitly does not mean adopting everything at once. On the contrary — the path is exactly the one I described for adopting AI: start with one tangible process, prove the value, and then dock the next surface onto the same foundation.
Maybe a company starts with ZenSales, because clean contact management is an immediate relief. Maybe with ZenBI, because someone can finally answer the margin question without building a dashboard. The order follows the business, not the product catalogue. All that matters is that each step sits on the same foundation — otherwise you're collecting islands again.
What remains
You recognise an operating system not by how many programs it has, but by the fact that they work together without each reinventing the wheel. ZenBI and ZenSales are two such programs: very different in what they do, identical in what they stand on.
That's the real thought behind our product picture. Not a suite of interchangeable apps, but one system with many surfaces — one that gets smarter with each of them, instead of more cluttered.