Priced in days, published in full
We price the work in days rather than as a lump, because a day is something you can see, question — and reduce by doing some of it yourself.
What you pay
1 · Exploration call — free
Thirty minutes. Your most-asked questions, what your systems are, and what you're paying to connect them. We do the arithmetic on the call and tell you honestly whether it pays back. No obligation, nothing to prepare.
2 · Workshop — 1–2 days
With your team: the source map, who-sees-what, your acceptance questions verbatim, and the register of every automation you already have with what each one costs. You keep every output whatever you decide — and the fee is credited in full against the implementation.
3 · Implementation — typically 8–20 days
The environment, the curation, the connections, the first services built on top, and acceptance against your own questions. Quoted as a number of days at the workshop, and then it doesn't move.
4 · Monthly service — small, on purpose
Deliberately less than the subscriptions it replaces. Continued access to everything we build for every client: new connectors, new capability, security updates, and the quality loop.
5 · Support days, when you want them
Bought in blocks and used as you like — another connection, another service, a hand with something. Blocks rather than a retainer, so you can always see what's left.
6 · Training & hackathon days
Teaching your people to build things themselves — and a facilitated day where your team builds the things they've wanted for months. The fastest way to make any of this feel like yours.
The monthly fee is not rent
Your environment is yours. It runs in your own cloud account for roughly £15–£60 a month, and it keeps running whether you speak to us again or not.
The monthly fee is separate: it's how you keep receiving what we build for everybody — new connectors, new capability, security updates, the quality loop. Stop paying it and nothing breaks; you just stop getting the new things.
That's a promise with an obligation attached, and we'd rather write it down: if there's nothing new in a quarter, we haven't earned it.
Where you'll sit, and how to pay less
The day count scales with the estate, not the ambition — how many systems need connecting, how much knowledge needs sorting out, how many visibility boundaries there are.
And if you've got someone in-house who can do part of it, do part of it. We'll tell you which parts and hand you the runbook:
| The work | Could your own person do it? |
|---|---|
| Cloud project setup and deployment | Yes — it's documented |
| Connecting a system that has an API and a credential | Yes |
| Converting and curating the documents | Yes — but it's more work than people expect |
| Designing who-sees-what | Partly — we'd want to review it |
| Building services in the console afterwards | Yes. That's the whole point |
| Governance, signed scopes, write agreements | No. This is the part that shouldn't be improvised |
A client with a capable developer might take eight days instead of fifteen. We'd rather do the eight days that need us than pad out fifteen — it's better work, and you'll tell someone.
The honest comparison
| £29–£99/mo AI tools | Copilot / Gemini | Zapier & the connector stack | Us | |
|---|---|---|---|---|
| Who sorts out the documents first | You | Nobody | — | We do, with you |
| Reaches the systems work happens in | No | Within the suite | Yes | Yes |
| What the wiring costs as you grow | — | Per seat | Per task, forever | Your infrastructure — pennies |
| Who owns the connections | — | Microsoft/Google | The vendor | You do |
| Building the next thing | Wait for the roadmap | Wait for the roadmap | Another zap, another fee | Describe it; a human approves it |
| When an answer is wrong | You debug it | Shrug | — | Cited source → ten-minute fix |
| Someone to call | — | — | — | Yes. Us. |
The software layer is genuinely cheap now — we're honest about that. What you're paying us for is the two days that make it worth asking, the connections set up properly, the scope we sign our name to, and the loop that keeps it right.
What we don't charge for
Your staff. There's no per-seat fee and there never will be: add your whole team and it doesn't change what you pay us. Charging by the head would make it expensive to let people in, and people using it is the entire point — it's also exactly the pricing model of the software we're arguing you should stop renting.
The exploration call, proposals, and scoping. If the numbers say this doesn't pay back for you, we'll tell you on the first call and leave you the map we made. If the workshop tells us your documents need six months of tidying before any of this makes sense, we'll say that too.
Start with your own numbers
Work out what you're spending on connective software and manual work before you talk to us. Five minutes, in your browser, no email required.
What's it costing you? Book 30 minutes