Step three
The build.
One job, fixed price, four weeks. We take the biggest aye from the look-round and build it properly into the tools you already use. You see it working every week, not at the end. When it's done, you own it.
What gets built
Anything on the capabilities page, scoped to one job. The usual first builds:
- The morning brief. Who's in today, who's new, who's back and what they said, who owes you. Read with the first brew.
- One place to ask. Bookings, accounts, email and the spreadsheet joined up so you can ask across all of them.
- The quote that writes itself. From a photo and three words, in your voice, before you've left the drive.
- The Friday chase. Unpaid invoices chased politely, with the invoice attached, after you've pressed go.
- A dashboard with a brain. The numbers that matter, where they came from, and a weekly note on what to do next.
How it runs
- Price agreed in writing before anything starts. If the scope changes, the change and the price get agreed before carrying on.
- Week one you see the first rough version. Every week after, a working update. No big reveal at the end.
- Built into your systems on accounts you own. You get the code, the prompts, the logins.
- Every build meets the five safety rules: least access, a person approving the steps that matter, a log of everything, your data in your systems, nothing trained on. If it can't, it doesn't get built.
- Handover is a session with the people who'll use it, not a PDF.
Already know what you need?
For larger businesses opening their own software and systems to AI, we build bespoke MCP servers and the governance around them, deployed in your own estate if that's where it needs to live. That's a different conversation and we're happy to have it at that level from the start. More on that here, or just get in touch.