Your business, rented monthly
Or built once and owned
Your client work, your internal work and your content all sit inside software somebody else owns, billed per head, renewing whether you're using it or not. We build those three as systems on your own infrastructure, hand them over, and you keep them. You own them outright, and there's nothing to renew.
Book a callFor founder-led companies whose software bill grows every time they hire.
Build the parts you actually use
Own them outright
Before we build, we look at what your people actually use, so each one comes out shaped to your company rather than to a product team's guess. Most companies start with one and drop the generic tool it replaces, the one they're paying for by the head and using a tenth of. Everything below is running right now, photographed rather than drawn.
Your Team Garden
The kitchen of your operations, fed from where the work already gets shared. Your team works in it from a browser, and only you need Claude.
- Tasks arrive three ways: tag a message in Slack, add one on the dashboard, or forward an email.
- A library your team reads, which answers a question instead of handing back a list of links.
- Onboarding checklists for new staff, with steps that unlock each other as they're done.
Your Client Garden
Every client, from the first time you meet them to the day you hand the work over.
- Everyone you know moves through five stages, and each client gets a garden only they can see.
- The proposal, the agreement with its payment plan, their onboarding, the work running, then handover.
- Your people hold a seat in one garden at a time. They get the board and the library, never the money.
Your Training Garden
Every workshop you run, from the seat somebody buys to the transcript they read back afterwards.
- They agree to the proposal, the payment plan opens, and their first steps arrive before the first session does.
- Pre-reading, a quiz at each end of it so you can see what moved, and the assignment for the week in between.
- A live room of your own to run the sessions in, with the recording and the transcript kept afterwards.
The two builds above, pointed at a room of people you are teaching. Everybody sitting in it needs a browser and nothing else.
Book a free call
Three kinds of person,
and only one of them needs Claude
Access is built in three layers from the first migration, rather than bolted on when somebody asks.
Working with Claude directly. You change and extend the system yourself, or you ask us to. Nothing is locked away from you.
With Claude or without, your call person by person. They run their teams and see across the whole picture.
A browser, and that's it. They don't need an AI account or a licence, and there's no training day.
What it costs
Each build is priced for the company it is built for, starting at around five people. It rises with headcount, because a system for fifty is more work than one for five and worth more once it's running.
There's a second way to buy any of them, where we build it and hold it through the first twelve months and then maintain it for an annual figure. That version costs more, because it's the build plus a year of us.
Three things sit around the builds. A data pass before we start, so we build what your people actually use. Training on handover, so you can change it yourself. And the same pass again six months in, on the system you own by then.
You own the system, the data and the code. There's no licence and nothing to renew, and what it costs to run afterwards is your own infrastructure plus the Claude seats for you and any manager you want one for.
Own it, or keep renting it
We build it, test it with your team, hand it over, and we're out. One payment, and it never comes back.
Book a call