← The session and what comes next
Your session Job Map.
Illustrative session deliverable · fictional company · all figures are estimates
Birch Studio's Job Map.
Prepared 8 September 2026 · AI With Hands Session
1. Buyer and goal
Priya, founder. UK agency, 35 people. Time back for existing clients. Daniel, operations lead, owns the weekly report.
2. Where the week goes
“Every proposal comes back to me.” 4 h/week.
“Friday's report is a pile of updates.” 3 h/week.
3. Jobs ranked by gain and effort
- Proposal drafts · Priya checks the result.
4 → 1.5 h/week, including review. Estimated return: 2.5 h/week.
- Weekly report drafts · Daniel checks the result.
3 → 0.5 h/week, including review. Estimated return: 2.5 h/week.
Both are small-effort, larger-gain candidates. Later: client onboarding, a larger build. Leave filing notes until these run. Keep price quotes with Priya until the rules are clear.
4. Tools, cost and setup
Existing document tool plus an AI drafting tool. Shared extra budget: £20/month. Report drafts add £0 beyond that.
Setup: one working day per job. Check permissions and inputs first. These are allowances, not vendor prices or a build quote.
5. Estimated hours back
2.5 + 2.5 = 5 h/week after review and corrections. Check against past work, then measure once running. Priya approves proposal scope, price and dates. Daniel checks report figures.
6. Four-day quick start
After the second meeting's live run. Ten minutes a day:
- Pick a past proposal and shareable notes.
- Mark price, scope, recipient and date checks.
- Draft with the approved tool. Don't send.
- Compare, record misses. Stop on a failed check.
Practice steps; a complete build is separate.
7. The monthly money line
5 h × £50 × 52 ÷ 12 = £1,083.33 potential monthly capacity.
Less £20 tools: £1,063.33/month, before session and build fees. This isn't cash saved or a payback forecast.
8. The next step
Read this map two days before the second 45-minute meeting. Try the first job with your engineer. Then choose: practise yourself or scope a build. No further work is booked automatically.
Use your browser's Print command for just the one-page map.
The working notes behind the map.
The AI With Hands Session gives you a Job Map: the jobs worth tackling, the first quick wins, what they might cost and a small plan to start. Your engineer prepares it from your interview and checks it before you try the first job together.
Illustrative session deliverable. Birch Studio and Priya are fictional. Every time, cost and benefit below is an example estimate, not a measured result or a quote for your business. Your map uses your examples and makes unknowns visible.
1. The person and the goal
Priya, founder of Birch Studio. Prepared 8 September 2026. A fictional UK agency with 35 people. Priya wants time back for existing clients. Daniel, the operations lead, owns the weekly report and would help run the first job.
2. Two pains, in their words
- “Every proposal comes back to me to turn the notes into something we can send.” Example baseline: four hours a week.
- “Friday's report is a pile of updates I have to put together.” Example baseline: three hours a week.
The first two candidates could return an estimated five hours a week after building, review and correction time. We'd check those assumptions against past work and measure again once they're running.
3. The jobs, ranked by gain and effort
| Effort | Larger expected gain | Smaller or uncertain gain |
|---|---|---|
| Small | First: proposal drafts. Second: weekly report drafts. | Filing notes: leave until the useful jobs run. |
| Larger | Next sprint candidate: client onboarding from signed scope to a checked welcome. | Changing price quotes: leave with Priya until the rules are clear. |
Proposals go first because there's a clear source, a repeatable output and a named reviewer. A price or date that isn't supported by the source stays open for Priya to decide.
4. What each quick win needs
| Quick win | What does it | Extra monthly tool budget | Setup estimate | Estimated hours back each week |
|---|---|---|---|---|
| Proposal drafts | Existing document tool and an AI drafting tool, with Priya approving scope | £20 allowance, subject to the chosen plan | One working day | 2.5, from 4 hours to 1.5 |
| Weekly report drafts | The same tools, using Daniel's checked figures | £0 extra beyond that shared allowance | One working day | 2.5, from 3 hours to 0.5 |
These are example allowances, not vendor prices. Check the tools, permissions and real inputs before agreeing a build. The remaining time includes review. Setup estimates are separate from the small practice steps below.
5. Your four-day quick start
These four days follow the live session. You receive the map two days before the second meeting, read it and bring your questions. You try the first job with your engineer in that meeting. Then practise the agreed steps yourself:
- Day 1, ten minutes: Priya picks another past proposal and the notes it came from. Remove anything that can't be shared.
- Day 2, ten minutes: Mark what must be right: price, scope, recipient and promised date.
- Day 3, ten minutes: Try a draft using the approved tool and the steps checked in the live session. Keep it beside the original. Don't send it.
- Day 4, ten minutes: Compare the draft with the checks agreed in the live session. Record what was wrong or missing and decide whether it is safe to keep practising.
This is practice after the checked first run. Stop if the result fails a check. A complete business job isn't built in forty minutes.
6. What could come after
Client onboarding. Turn the signed scope into a welcome draft, setup tasks and a record of who owns each one. The business goal is lower risk: fewer client starts with a missing required input or an unapproved promise. Track the share of client starts with either mistake, using past work for the baseline and the same checks after launch. Baseline: not measured. Time from signature to welcome is a useful second measure; speed alone does not prove a business gain. Daniel owns the examples; Priya approves commitments. It needs a separate build scope.
7. The monthly money line
For this example, value the five possible hours back at £50 an hour. Use 52 weeks divided by 12 months:
5 × £50 × 52 ÷ 12 = £1,083.33 of potential monthly capacity.
£1,083.33 − £20 extra tool cost = £1,063.33 per month, before session and build fees.
This isn't cash saved or a payback forecast. Salaries don't fall because a draft takes less time. What Priya does with the time, the actual review effort and the cost of building determine the value. The job cost calculator helps put your current work on the same basis.
8. The next step
Read the map before the second meeting. Run the first job with your engineer, inspect the result and choose whether to continue yourself or commission a build. If you continue yourself, start the four days of practice after that meeting, using only approved tools and data. Nothing in the map books further work or grants access.
The map chooses. The build plan specifies.
This is the buying and prioritising document from the £999 AI With Hands Session. The separate sample build plan shows the detailed checks, exceptions and handover for one job once you've chosen it. See what the session includes, use the complete free Job Picker, or join the session waitlist.