How a project runs.
The same six steps every time. You see a demo every week, and nothing goes live until you’ve signed it off.
Six steps, start to finish.
What happens, how long it takes and what we’ll ask of you.
Discover
Half a day with the people doing the work. We measure the hours and check what data is involved.
- How long
- Half a day on site, with the report within a week
- From you
- An hour with each person who does the work
- You get
- A ranked list of automations and a fixed quote
Design
A one-page plan with a data-flow diagram, the risks and how to switch it off.
- How long
- A fixed quote within three working days
- From you
- One sign-off meeting
- You get
- Your sign-off before anything is built
Build
Built in your own accounts, with test data first and a demo every week.
- How long
- 14 days for a Starter, three to five weeks for a sprint
- From you
- Test data, and 30 minutes a week for a demo
- You get
- Working automations you can see early
Train
Hands-on training for the people who will use it, and a named champion on your team.
- How long
- Half a day, on site
- From you
- The people who’ll use it, and one champion
- You get
- A team that can run it without us
Hand over
A runbook, logins in your own vault, an owner for every automation and a before-and-after measure.
- How long
- The last day of the build
- From you
- A password vault we can add logins to
- You get
- Proof of the hours saved
Care
30 days of support included, then an optional monthly plan with monitoring and a report.
- How long
- 30 days included, then monthly if you want it
- From you
- Tell us when something in the business changes
- You get
- Someone local to call
A Starter, day by day.
The £2,450 Starter gets two automations live in 14 days, with your team trained to run them.
Day 1: kick-off and team workshop
Half a day on site. Your team learns what AI is good and bad at, and we confirm the two workflows and how we’ll measure them.
Days 2 to 9: build
Both workflows are built in your own accounts with test data. You see a working demo on day 5.
Days 10 to 12: test with real work
We run them alongside your team on real jobs, with a person checking every output.
Day 13: hand over and train
The people who’ll use it learn to run it, change it and switch it off. You get the runbook.
Day 14: live
It starts doing the work. We stay on call for 30 days.
Days 30 and 90: measure
We check the agreed number against where you started, and fix anything that falls short.
What we need from you.
A named contact
Someone who knows the work and can make decisions, for about an hour a week.
Access in your name
We build in your accounts. You own every login, and we use the least access we need.
Examples of the work
A handful of real emails, documents or spreadsheets, so we build for what actually arrives.
Time for the demos
30 minutes a week to see it working and tell us what’s wrong.
Website projects.
Two weeks for a refresh, four to six for a rebuild. Every site ships with an AI assistant and at least one enquiry automation.
Website check and kick-off
We run our checker on your current site and agree goals, pages and who owns the words.
Content and structure plan
A page-by-page plan, including the questions customers ask, written for people and for AI search.
Design
Two rounds of changes, on real content rather than placeholder text.
Build
The site, its AI assistant and at least one enquiry automation, connected to your CRM or inbox.
Checks before launch
Speed, accessibility, forms, redirects and structured data, all scored on our own checker.
Launch and training
We launch, then show you how to edit pages and read the enquiries.
Care
Your care plan starts: updates, backups, monitoring and a monthly report.
Start with a free check, or talk it through.
Ten questions give you a score and your top three opportunities. Or book 30 minutes with the person who would build it.