How it works

1 — The call (30 minutes, free)

What your staff ask over and over. What your systems are. What you pay to connect them, and what your team does by hand that they shouldn't.

We do the arithmetic on the call — including our own costs — and tell you whether it pays back. If it doesn't, we say so and leave you the map.

2 — The workshop (1–2 days, with your team)

We look at your actual folders together and agree who should see what. We harvest the questions your staff really ask, word for word — they become the test the whole project is measured against.

Then two things that surprise people:

• Which systems get connected, in what order — with a named person holding the credential for each. This conversation reliably uncovers a personal login carrying something load-bearing.
• The automations register — everything you already run: what it does, whose account, what it costs, when it last worked. One page, frequently the most valued thing we produce.

3 — The agreement (one page)

Plain language, a signed scope, and a day count. The technical appendix is the configuration we deploy — the contract and the running system are the same text, so they cannot drift apart.

4 — The build (typically 8–20 days)

• Merge — your three returns policies become one, with your decision on the differences.
• Transcribe — we sit with your most experienced people and write down what has only ever lived in their heads.
• Connect — the systems agreed at the workshop, set up once, with credentials in your own secure store.
• Build — the first services on top. Small, useful, chosen by you.

5 — Acceptance, then you take over

Your questions, from your own phones, each answer checked and each citation followed. Then a 30-minute weekly review for the first month.

And one more thing before we step back: your admin builds and publishes something themselves, with us in the room. Not us demonstrating — them doing it. An admin who has never done it once won't do it later, and the whole point is that you don't need us for the next thing.

6 — The part that isn't a stage

When an answer is wrong

It will happen. Every answer cites its source, so a wrong answer points at the exact document to fix — a document you own and can edit. No vendor queue, no retraining. That loop is what you're actually buying.

What your team gets, and what your admin runs

Your team gets your own site, at your own address: it opens on your headings, and from there they ask questions and get cited answers, read any approved document as a page, and see what's been built for them. What that looks like →

Your admin gets a separate space alongside it, built for non-technical people: documents, connections, users, who-sees-what, what's been built, and a full audit trail of every change and approval. Only the people you nominate can reach it.

How much of the first one your staff see is set per person, per area — as open or as narrow as you want it, changeable any afternoon.

Two things worth separating, because most suppliers blur them. Your environment is yours — about £15–£60 a month in your own cloud account, 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 everyone. Full pricing →