SHORT ANSWER
AI reduces operating costs by removing repeated, rules-light manual work: support triage and first-draft responses, data entry and reconciliation, research and reporting, and QA. Realistic savings in a small company are 20-40% of the time spent on those specific tasks, not of total headcount cost. The saving is real only if the reclaimed hours are redeployed rather than absorbed.
Answered by Andrew Crossley, Fractional Chief Product Officer · Updated 2026-08-01
Cost pressure is the most common reason companies get serious about AI, and the most common place they overpromise to a board.
Task-level savings are measurable and defensible. Headcount-level claims usually are not.
Two weeks of task logging beats a workshop. Look for high-frequency, low-variance work with a reviewable output.
The top three tasks almost always account for most of the available saving.
Measure handling time before and after, plus the correction rate. Four weeks is enough to know.
Name what the reclaimed time is now spent on. Unassigned savings evaporate into the working week.
Model spend, tool subscriptions and review time all count. Net saving is the only number worth reporting.
FROM EXPERIENCE
Contact centre work taught me that cost per contact is driven by reason mix, not agent speed. The saving comes from removing the reasons customers contact you at all, and only then from handling the rest faster.
AI applies in exactly that order: use it to classify and quantify reasons, fix the top product defects, then automate the residual handling.
20-40% of the time spent on the targeted tasks. Company-wide double-digit cost reduction in year one is rare and usually overstated.
In small companies it usually means avoiding the next hire rather than cutting the current team.
Typically one to three months for operational automation, because build cost is low and the task volume is already known.
IN SHORT
Turning LLMs, RAG and agents into products that hold up in production.
Read moreContinuous discovery that tells you what to build next.
Read moreA short call to work out whether the problem is strategy, scope or speed.
Work with AndrewTHE FRAMEWORK
MORE ANSWERS
No, but it is removing a large part of what product managers used to spend their week doing. AI already writes specs, summarises research, drafts tickets, analyses feedback and builds prototypes. What it cannot do is decide what a company should refuse to build, hold accountability for a metric, or persuade a room. Roles weighted towards documentation are shrinking; roles weighted towards judgement are becoming more valuable.
Startups use AI in three places: inside the product as a feature that completes a user task, inside operations to remove repeated manual work, and inside go-to-market for research, content and support triage. The highest-return use in a small company is usually operational — it lowers headcount pressure immediately, with no dependency on customers changing their behaviour.
Founders need four categories, not forty tools: a frontier chat assistant for thinking and drafting, an AI-assisted build tool for prototypes and MVPs, a research and synthesis tool for customer and market work, and automation for repeated operational tasks. Pick one per category, use them daily for a month, and only add a fifth tool when a specific recurring task justifies it.
An AI application costs roughly £10,000–£30,000 to build as a focused MVP on hosted models, and £50,000–£150,000 for a production system with retrieval, evaluation and integrations. Running cost matters more than build cost: expect £0.01–£0.30 of model spend per task. If a customer generates a hundred tasks a month, price accordingly — AI products fail on unit economics more often than on build budgets.