Did AI save any time?
The draft took two minutes. When was the work actually finished?
Fictional example · not George's experience
20 support replies · all accepted after any repairs
Where did the other 160 minutes go?
Minutes across 20 replies
- Drafting
- 40
- Review
- 100
- Repairs
- 60
Each draft took 2 minutes to create and 5 to review. Four rejected drafts each needed 15 more minutes of repair. Total: 40 + 100 + 60 = 200 minutes.
That is no time saving in this invented sample. A narrower task could do better; it needs its own comparison, including failures.
The full example and its assumptions
A team compares 20 support drafts. Manual work takes 10 minutes per accepted draft: 200 minutes. AI drafting takes 2 minutes per case, review takes 5 minutes each, and four rejected drafts require 15 minutes each to repair: 40 + 100 + 60 = 200 minutes. Faster drafting produced no total time saving in this sample.
Suppose API use costs $4 across the sample. That is an additional $0.20 per accepted draft, before staff costs, despite unchanged completion time. The team keeps approval with a named reviewer and tries a narrower category. This small experiment cannot establish performance on rare, costly mistakes.
Illustration only, not a business forecast or a recommendation for your finances.
Try this next
Try one narrow category, such as routine replies with an approved answer. Agree what a usable reply looks like, then count drafting, checking and fixing on both paths.
Try the fictional customer-reply example →Opens an editable fictional plan. No worksheet answers or personal data are transferred. Export and import a trial JSON record there; saving on your device is optional.
What counts as finished?
Pick a small job you know well enough to check: a support reply, a draft or a bug fix. Before choosing a model, describe what makes the result usable and who will approve it.
Time the way you do it now, including checks and corrections. Keep the cost and common mistakes. That gives you something fair to compare with the AI version.
Count the whole job
Give both approaches representative work. Keep the inputs, outputs and reasons for accepting or rejecting each result. Keep rejected outputs and retries in the count. A failed attempt still took time and money.
Count model spend, checking and repairs alongside completion time. Staff minutes and elapsed time can differ when people work in parallel, so label which you measured. Check costly edge cases separately from routine work.
Who checks it tomorrow?
Name the person responsible for approving changes, watching failures and maintaining a fallback. Decide what the system may do on its own and what requires a human decision. Test the fallback before depending on it.
Use Work Changed for the wider effect on your week, including work pushed into evenings. Keep that separate from a trial of one task. AI Workflow Cost lets you explore costs and keep an observed trial. For a cost per accepted result, use actual total cost and the number actually accepted; a bill alone cannot supply either a task comparison or its missing review time. Rerun the comparison when the model, price or failure pattern changes.
- A current process and a clear definition of finished
- Failures, checking and repairs in the count
- Someone responsible and a fallback you have tried
Choose a next step
Decision worksheet
Pick one thing to do next. Keep a short plan without filling in a form.
Add detailed notes
Add notes only if they help. Answers stay in this page's memory and are never uploaded or saved automatically.
What input produces what accepted output, and who judges it?
What changed in completion time, review time, cost and failure rate?
Which actions require approval, and who can stop the workflow?
Which failure or change in cost would make me run the comparison again?
From George's writing
What a 3-Person Team Actually Pays for AI: July 2026Originally published
George's July 2026 account shows reported spending and token/cache use for a three-person team. It helps explain the bill. It supplies no same-task manual baseline or measured checking and repair time, so those trial fields must stay unknown.
What this account does and does not show
What George reported
- Reported AI spending
- Reported token and cached-token totals
- A three-person team context
Questions it leaves open
- An exact reporting window and comparable task mix
- A manual baseline and acceptance criteria
- Accepted and rejected output counts
- Human review and rework minutes
- A changed decision established by a same-task comparison
These missing observations prevent a measured cost-per-accepted-result or time-saving conclusion. Do not use the bill to fill the workflow calculator's trial inputs. The August 13, 2026 delegation account is a separate personal account of a skill and judgment gap, rather than a dataset completing this trial.
Example-led guide · Updated
Work through the question
Worksheets and reflections
Work Changed
Compare your estimated weekly hours before and after AI. See the mix of production, checking, additional responsibilities and coordination without assuming time was saved.
Free tool · no email required →
AI Workflow Cost & Break-Even
Compare your actual run prices, human verification, rework and setup over a chosen horizon. Keep freed capacity separate from cash savings.
Free tool · no email required →
From the field
Personal accounts behind the questions. Each essay reflects when it was written.
My Coding Agent Shouldn't Have a Boss
Claude Code is one of the best products I use. That is exactly why realizing how little of it I controlled became uncomfortable.
Why this reading: Read this while deciding how much coordination a coding workflow actually needs, then test that arrangement on your own task.
The parts of AI I could no longer delegate
Then consider what a founder needs to understand before trusting work delegated to AI.
Why this reading: Use this account of a judgment and skill gap to identify who can check an output and when delegation should stop.
When to Build vs Buy in AI (My Edition)
Historical account — October 11, 2026: These are the two mistakes I described on April 7: building too much support surface and depending on an abandoned…
Why this reading: Use the author's build-or-buy account to list review, maintenance and fallback work before comparing purchase prices.