Connect it once.
Build on it forever.
One cloud environment your business owns. Your systems connect to it, your knowledge lives in it, and everything your team needs gets built on top — without buying anything else.
What your people actually open
Your own site, at your own address, signed into with the work account they already have. It opens on your headings — the things your team actually does, in your words — and from there they can:
Ask
Questions in plain language, answered with the company document cited underneath. If we can't answer from your documents, we say so rather than inventing one.
Read
Every approved document as a proper page, grouped and searchable. For the times someone wants to read the handbook rather than interrogate it — new starters, mostly.
See what's built
The Monday report, the stock summary, whatever your team has had built — filed under the heading it belongs to, not in a drawer nobody opens.
Alongside it, and separate from it, sits your admin space: who's in, who sees what, what's connected, whether the last sync worked, and a record of every change. Only the people you choose can reach it.
How open it is, is your call. Access is set per person, per area, and every heading says who it's for. Some businesses put everything in front of everyone; some keep supplier pricing to three people. Both are the same product, and you can change your mind on a Tuesday afternoon.
The one part that isn't adjustable is the oversight — who has access, what was indexed, what changed, whether the sync ran. Those screens are in every deployment and can't be switched off, including by us. That's what makes everything else safe to leave flexible.
What's inside it
What gets built on it
| When someone says… | What gets built |
|---|---|
| “Nobody can find anything” | Cited answers from your own documents |
| “Where's that order? Have we got any?” | Live lookups against the systems that know |
| “I type the same reply every week” | A draft into your own inbox, for you to send |
| “Someone rebuilds that report every month” | It assembles itself |
| “These two systems disagree” | A report showing where, and who owns fixing it |
| “Karen copies it across on Fridays” | A scheduled job, replacing a subscription |
| “We can't change anything without a developer” | Your own people build it, and you approve it |
We don't sell a catalogue of automations, because we'd be guessing at what your business needs. We build the first few with you and leave you able to build the rest.
Indexed, or connected — they're different
Some things belong in the knowledge base: policies, procedures, product data. They change slowly and belong in cited answers.
Others should never be copied anywhere — stock levels, order status, what a customer is owed. Those are read live, at the moment somebody asks, and never stored. A six-hour-old stock answer is worse than no answer.
The full distinction, and why it matters for your mailbox →
The rule that makes it safe
Everything measurable is calculated. The AI writes prose, classifies, and works out what you meant — it never produces a number anything depends on.
A price, a stock figure, a total: those are computed and cited. That boundary is why this is safe to point at regulated work, and it's enforced in the code rather than promised in a policy.
Your systems stay yours
Connecting a system is not a step towards replacing it. Your webshop stays your webshop, the accounts package keeps doing the accounts, and the spreadsheet Sandra owns is still Sandra's. Your existing automations keep running too — we won't switch off something that works.
And if you leave: documented offboarding, your data back, the environment deleted, confirmed in writing.
Bring the list of things you'd have built by now
The ones that needed a developer, another subscription, or the person who's always busy.
Start with the numbers Book a call