SHORT ANSWER
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.
Answered by Andrew Crossley, Fractional Chief Product Officer · Updated 2026-08-01
Small teams have the most to gain and the least capacity to experiment badly. Choosing the wrong first AI project costs a quarter.
Investors now expect a coherent answer to how AI changes your cost base or your product. 'We use ChatGPT' is not one.
Support triage, sales research, onboarding data entry, QA. Fast payback, no customer-behaviour risk.
Pick a step users already find tedious and produce a reviewable draft rather than an automatic action.
Not tokens, not calls. Cost per task that a human accepted without rework is the honest unit.
Anything customer-visible, financial or contractual keeps review until the evaluation data justifies removing it.
FROM EXPERIENCE
Classifying inbound support messages by reason code, drafting a first response and routing the exceptions is a genuinely boring project with an immediate payback: faster response times and, more importantly, structured data on why customers contact you.
That reason-code data is the best product roadmap input most startups have and never collect.
Support and sales research automation. Days to implement, immediate time saved.
Not initially. Most first projects are prompt, retrieval and workflow design on hosted models.
Use business-tier APIs with no-training guarantees, redact identifiers, and write a one-page data policy before the first pilot.
IN SHORT
Turning LLMs, RAG and agents into products that hold up in production.
Read moreFive days to build your own AI-powered MVP, no engineering team.
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.
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.
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.