Get a client started
Turn the signed scope into a welcome draft and a checked task list.
For founder-run UK companies with 20–150 people.
Gone by Friday starts with one job.
AI With Hands Session
Two 45-minute meetings with an engineer. A ranked Job Map. A first job tried together.
A complete build is scoped separately.
No dates announced. Join to hear when bookings open.
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.
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.
Start with the notes from a discovery call. Finish with a proposal draft that keeps the agreed scope separate from the promises still waiting for your approval.
From the source, at 02:10
“Our welcome PDF still tells new customers to email the old address.”
The draft
Replace it with a one-page welcome document. Supply an editable version and a PDF. Use the client's approved wording. Website changes are excluded.
The decision you keep
Friday was requested, not agreed. Confirm the date before sending.
Fictional worked example.
Turn the signed scope into a welcome draft and a checked task list.
Reconcile the figures before writing the explanation.
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.

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.
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.
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.
You can start whether or not you already use AI.
You still approve proposals, chase updates or answer the difficult replies. Start with one repeat job you can hand over safely.
Your engineers are building the product. Your support, sales or operations team still does the repeat work by hand. Bring the job to us and share the session details with the founder who signs it off.

Matt Hertel. An engineer who has also run the company. Built and sold apps solo. Fractional CTO in startups. Every Sunday, one job start to finish, in No Manual Yet.
In Thursday complaint, Tuesday fix, I describe taking a reported problem through to a shipped fix.
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.
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.
I spent another week on LinkedIn watching people measure AI.
Get an email when session dates are available. Decide whether to book then.