Why your first AI project should save hours, not transform the business
It usually starts in a board meeting. The CEO asks, “What’s our AI strategy?” The room fills with urgency. A transformation plan gets commissioned, consultants get brought in, and workshops fill the calendar.
Eighteen months on, the only deliverable is a slide deck. The consultants are still billing. No one can point to a single hour saved or a customer actually helped. I’ve watched ambition outpace outcomes when the goal is too broad and the outcomes too vague. Transformation is a worthy long-term aim, but as a first project, it almost always disappoints. The bar for success gets lost somewhere between talk of an AI-enabled future and nothing you can measure.
There’s a better way. I start by picking a single workflow and focusing on saving real hours. I measure the result inside eight weeks, then take that number straight to the board.
Why transformation programmes fail as a first project.
Transformation projects fail because the metrics are vague. “Improved customer experience.” “Faster decisions.” “AI-augmented productivity.” None of those survive a serious commercial review. None of them help leadership decide whether to fund the next AI project or walk away.
Eighteen months on, the only deliverable is a slide deck. The consultants are still billing. No one can point to a single hour saved or a customer actually helped. The pattern is consistent: ambition outpaces outcomes when the goal is too broad and the outcomes too vague.
Transformation is a worthy long-term aim. It is a poor first goal.
Evidence does the work no slide deck can.
I’ve spent over a decade running experimentation programmes. At RNLI, I helped lift donation journey conversion by 28 percent. That single number convinced a sceptical board to fund the full CRO programme. Evidence did the work that no slide deck could.
Moving from experimentation to AI, the same discipline applies: design the test, measure the gap, score the result, and decide whether to scale. The context is new, but the underlying approach hasn’t changed.
This is why hours saved is the right first metric for AI. It’s the experimentation playbook applied to a new tool. Define the baseline, run the trial, score the outcome, and expand from evidence.
A number you can take straight to a finance director.
Every business already understands time. When AI gives hours back to a workflow, you have a number you can take straight to a finance director. The baseline is clear. The improvement is clear. Both get measured the same way.
Hours saved is different from the vague metrics that sink transformation projects. The baseline is measurable, because everyone knows how long the task took before. The impact is testable, because shadowing the workflow for two weeks gives you the number. The result compounds, because those hours come back into the business to be redeployed.
If you can’t show hours saved on a first project, you’re not ready for a bigger one.
Five criteria. Miss any one and the work gets harder to defend.
- Weekly frequency. If the task only runs once a quarter, you won’t learn fast enough to fix the AI’s mistakes before the next cycle comes round.
- High reversibility. Mistakes should cost a rework, not a refund. Internal tasks with human review before anything leaves the building are safer than customer-facing ones.
- Low judgement load. The right answer shouldn’t depend on context only insiders know. AI is good at patterns. People are good at judgement.
- Clear baseline. You should be able to measure how long the task takes today without commissioning a workshop. If you need a project plan just to estimate the baseline, the workflow is too tangled.
- One owner. One person accountable for the outcome. Cross-functional projects multiply meetings and dilute responsibility. Save those for later.
Candidates that meet all five
- Weekly summary emails drafted from meeting transcripts.
- First-draft proposals built from a standard template.
- Ticket triage routed into a fixed set of categories.
- Expense receipts coded against the accounting chart.
Candidates to skip on a first project
- Customer-facing chatbots — judgement load and reversibility risk.
- Forecasting and planning — judgement load too high.
- Sales discovery — frequency too low.
The shortlist is always shorter than boards expect. That’s the point. Smaller firms without a dedicated data team can’t afford to overshoot on the first project.
A schedule that fits inside a single quarter.
This schedule fits inside a quarter and gives the business a defensible result by the end of it.
- Week 0. Define the workflow on a single page. Log the baseline with a stopwatch, not a guess. Choose your tool.
- Weeks 1–2. Set up. Pilot with one user.
- Weeks 3–6. Run live. Measure time on every run. Track quality escapes — the moments the AI got it wrong and a human had to step in.
- Week 7. Score the workflow against six dimensions: adoption, time saved, quality, risk, defensibility, gap-to-target.
- Week 8. Decide. Scale, iterate, or kill.
Budget: one person’s two hours per week, plus tool costs. Usually £200–£500 per month, all in. If your first AI project needs a procurement review, it’s too big.
The deliverable is a single, defensible sentence:
This workflow now takes X hours per week, down from Y, with a quality score of Z.
That sentence earns permission for the next project. Without it, the second project stands on the same shaky ground as the first.
Scaling is more workflows, not bigger projects.
Scaling isn’t about bigger projects. It’s about more workflows, each one run with the same discipline.
After two or three completed first projects, I’ve seen businesses gain something new. A scorecard of real numbers, not forecasts. A team that has learned, in context, what AI can and can’t do. Permission from leadership to invest more, earned by evidence rather than promised on a slide.
That’s what an AI strategy looks like in practice. Small projects shipped on schedule. Scored against a consistent rubric. Stacked into something that compounds.
Transformation, if it happens at all, is the sum of twenty completed first projects. It doesn’t get bolted on. The firms that lead in AI by 2027 will be the ones with the most workflows shipped and the cleanest numbers to show for them.
The only AI strategy that survives a finance meeting.
The most defensible AI leader in any industry next year will be the one whose team has shipped the most workflows and is ready to do it again next quarter.
Ship your first AI project by the end of this quarter. Measure it. Show the number. Earn permission for the next one by doing this one well.
The AI Opportunity Roadmap is how I work alongside firms doing exactly this: a 3–4 week engagement to pick the first workflow, score it, and ship it.
Frequently asked questions
00 entries-
Q.01
What should my first AI project be?
A single workflow that runs weekly, has high reversibility, low judgement load, a clear baseline, and one accountable owner. Strong candidates: weekly summary emails drafted from meeting transcripts, first-draft proposals built from a standard template, ticket triage routed into fixed categories, expense receipts coded against the accounting chart. The shortlist is always shorter than boards expect. That’s the point. Smaller firms without a dedicated data team can’t afford to overshoot on the first project.
-
Q.02
Why is “hours saved” the right metric for a first AI project?
Hours saved is the only AI metric that survives a finance meeting. Every business already understands time. The baseline is measurable, because everyone knows how long the task took before. The improvement is testable, because shadowing the workflow for two weeks gives you the number. The result compounds, because those hours come back into the business to be redeployed. “Improved customer experience”, “faster decisions”, “AI-augmented productivity” do not pass a serious commercial review.
-
Q.03
How long should a first AI project take?
Eight weeks, inside a single quarter. Week 0: define the workflow on a single page, log the baseline with a stopwatch, not a guess. Weeks 1–2: set up, pilot with one user. Weeks 3–6: run live, measure time on every run, track quality escapes. Week 7: score against six dimensions. Adoption, time saved, quality, risk, defensibility, gap-to-target. Week 8: decide. Scale, iterate, or kill.
-
Q.04
How much does a first AI project cost?
One person’s two hours per week, plus tool costs of £200–£500 per month, all in. If your first AI project needs a procurement review, it’s too big. The low cost is part of the discipline. It keeps the bar for evidence high and the blast radius low. The result earns permission for the next project rather than risking the whole programme.
-
Q.05
What kinds of AI projects should I avoid as a first project?
Skip customer-facing chatbots: judgement load is high, reversibility low. Skip forecasting and planning: judgement load is too high. Skip sales discovery: frequency is too low to learn from. Skip anything that needs a workshop just to estimate the baseline. That’s the workflow telling you it is too tangled for a first project. Mistakes on a first AI project should cost a rework, not a refund.
-
Q.06
What are the five criteria for a good first AI project?
A good first AI project meets all five criteria. Weekly frequency, so you learn fast enough to fix mistakes before the next cycle. High reversibility, so mistakes cost a rework, not a refund. Low judgement load, because AI is good at patterns and people are good at judgement. A clear baseline, measurable today without a workshop. One accountable owner, because cross-functional projects multiply meetings and dilute responsibility. Miss any one and the work gets much harder to defend.
-
Q.07
What’s wrong with an AI transformation programme as a first project?
Transformation programmes fail as first projects because the metrics are vague and the bar for success gets lost. The pattern repeats. A CEO asks “what’s our AI strategy?”. Consultants get brought in. Workshops fill the calendar. Eighteen months later, the only deliverable is a slide deck. No hours saved. No customer actually helped. Transformation is a worthy long-term aim but a poor first goal. It’s the sum of twenty completed first projects, not something you bolt on at the start.
-
Q.08
How do I scale from a first AI project to an AI strategy?
Scaling means more workflows, each run with the same eight-week discipline. Not bigger projects. After two or three completed first projects, a business gains three things: a scorecard of real numbers rather than forecasts, a team that has learned in context what AI can and can’t do, and permission from leadership earned by evidence rather than promised on a slide. The firms that lead in AI by 2027 will be the ones with the most workflows shipped and the cleanest numbers to show for them.
