Know which job to give AI first.
The AI With Hands Session turns your week into a ranked Job Map and a first job tried together. You can use the map yourself or have us build what comes next.
Gone by Friday is the aim: a useful job off your plate. The session is the first paid step. A complete build is scoped separately.
Start with the AI With Hands Session.
An engineer studies how the job runs today, prepares your ranked Job Map and tries the first job with you.
£999
Two 45-minute meetings with an engineer. A ranked Job Map. A first job tried together.
A complete build is scoped separately.
Session bookings aren't open yet. We'll email when dates are available. There's no opening date to announce yet.
Find the hours, or get your money back.
If we can't find 5 hours a week you could get back, you get a full refund. This covers the opportunities we identify together. It isn't a promise of savings before a job is built and measured.
Your £999 session fee is credited against a later One Build, sprint or monthly service. You can also keep the map and do the next step yourself.
Your week, in your words.
A 45-minute interview with an engineer. Show where the work piles up. Bring the person who does the job if that's someone on your team. We ask the questions.
We make your Job Map.
We rank the jobs, check the figures and name the first quick win. You get the map two days before the second meeting, with tool costs, estimated hours back and a four-day start.
Run the first job together.
A second 45-minute meeting. Try the first job live, inspect the result and decide what happens next. You leave with the map and a clear choice: do it yourself or have us build it.
See the session Job Map, including the ranked jobs and the money line.
You bring the work. We move it forward.
You show the work.
For the session, bring your week and examples you can share. Set aside two 45-minute meetings and time to read your map. You approve the goal and any access.
We do the building.
Your engineer prepares the map and leads the live run. If you choose a build, we set it up, test it against past work and fix the misses. You don't need to learn to build it.
Your team keeps control.
A named person checks the result where a mistake matters. Your team keeps the instructions and a readable log. The check should help them approve the work without doing it all again.
From the first example to the handover.
Pick the job that repeats.
Show us the work and a result you'd accept. Your engineer writes down where the job starts and ends, then checks the exceptions with the person who does it.
Check it against real work.
Your engineer builds and tests against past examples, including the awkward ones. You agree what a good result looks like. We fix the misses before the team relies on it.
Leave a job someone can run.
Your engineer hands over the instructions, a readable log and a way to stop and recover. Your team owns the final decisions. Reviewing the result shouldn't mean rewriting it.
Read the sample build plan to inspect the boundaries, check sheet and stop rules together.
A good first job has a clear finish.
It repeats often enough to matter. Past examples show what good looks like. Someone owns the result and can approve access. The Job Picker helps you choose.
Work with changing rules, no reliable source or no available owner needs sorting first. We agree what stays with a person. We also agree what to leave alone.
Your job's data and access.
Use the signup form for contact details. Don't paste client records, passwords or confidential examples into it. The website's privacy notice explains how signup details and site measurement are handled.
Before you share job material, we agree with you what can be used, which tools will receive it, who gets access, where copies will be held and when they'll be removed. The first session interview is recorded to prepare your map; agree that recording and its storage before it starts. If the material can't be shared, start with redacted examples.
You approve the access needed for the job. Permission to read a document doesn't grant permission to send it. Your team names the final approver and keeps a way to stop the job. These choices belong in your written scope before live work begins.
One document. Ready to give away.
Our publishing tool turns written material into a branded PDF and matching page preview. It checks the design rules before exporting.
This is the actual Job Picker output from a run on 8 September. AI assistance started the job; fixed tools rendered the files. We still check the wording and layout before publishing.
Inspect the input, finished pages and run record →
Real internal work. No client result or time saving claimed.
After the session, you choose.
Keep the map and take the next step yourself, or ask us to build it. There is no automatic next purchase.
What would a later build cost?
One Build costs £3,500. It takes a quick win from your map and gets it running in a week. The 30-Day Hands-On Sprint costs £20,000 for a larger job. Your £999 session fee counts towards either. You choose after the session; there's no automatic next purchase.
The first three sprints have a £10,000 founding offer in exchange for a written case study and three introductions. Payment is £5,000 at the start and £5,000 when the agreed business measure improves. We confirm eligibility and the written terms before any payment.
The sprint includes watching the work with your team, checking past examples and running beside a person before the job goes live. Your engineer comes to your office. Set aside two founder hours each week. It includes four hours of founder coaching, four weekly 45-minute team sessions, the playbook and 60 days of support.
For the sprint, the promise is a job running by day 30 or we keep working free until it is, provided the founder gives those two hours a week and the team shows up. The written scope sets the job, access, dates and support arrangements before you commit.
The practical questions.
What am I joining the waitlist for?
The £999 AI With Hands Session: two 45-minute meetings with an engineer, your Job Map prepared between them and a live run of the first job. We'll email when dates are available. There's no announced opening date and joining takes no payment.
What if you can't find enough time to get back?
If we can't find 5 hours a week you could get back, you get a full refund. This covers the opportunities we identify together. It isn't a promise of savings before a job is built and measured.
Can my department lead work with you?
Yes. A department lead can bring the job and own its day-to-day result. The founder approves the spend and access. For a later sprint, the founder also commits two hours a week; it isn't something they delegate and disappear from.
Do I have to build it myself?
No. Your engineer prepares the map and leads the first live run. You can use the map yourself or commission us to build the chosen job. The free guides explain the method; reading them isn't homework for buying the session.
Do we need another tool?
We start with the tools you already pay for. We check what they can do and what access the job needs before agreeing the work. Any extra cost needs your agreement.
Will it send things without us?
The human check is part of the job. For work such as a proposal or a client reply, the reviewer checks the exact draft before it goes out. If the draft changes, it needs another check.
What do I need to bring?
Your week, a recurring job and examples you're allowed to share. Your engineer leads two 45-minute meetings and prepares the map between them. Leave time to read it before the live run. A later sprint asks for two founder hours each week and the team's attendance.
What happens after I join the waitlist?
You get a confirmation email now. We'll email again when session dates are available, so you can decide whether to book. Joining doesn't reserve a date, take payment or subscribe you to the newsletter. Reply to leave the list.
What if the result is wrong?
The job stops at its check. Your engineer investigates and fixes build failures during the agreed delivery and support period. Your reviewer decides whether the corrected result is right. The sample build plan shows the checks and stop rules.
What gets handed over?
The agreed job, instructions to run it, a readable record of actions and the checks a person owns. Access, ownership and any ongoing support are written into the scope before work begins.
See a job before choosing one.
The worked examples are open to read. Each shows the sources, a draft and the checks.