SHORT ANSWER
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.
Answered by Andrew Crossley, Fractional Chief Product Officer · Updated 2026-08-01
Product teams are getting smaller while output expectations rise. The PMs who thrive are the ones who moved up the judgement curve early.
For founders, this changes hiring maths: one strong product leader with AI tooling now covers ground that used to need two or three people.
Specs, release notes, research synthesis, competitor summaries, ticket drafting. These are now minutes of work, not days.
The scarce input is still real conversations. AI can summarise ten interviews; it cannot have the eleventh.
What to cut, what to sequence, what risk to accept, what to say no to when a large customer asks.
Designing evaluation sets and quality metrics for AI features is becoming a core product skill, not an engineering one.
FROM EXPERIENCE
The parts of my week that AI took over completely: first-draft specs, interview synthesis, competitive scans, prototype scaffolding. That is easily a day and a half a week reclaimed.
The parts it did not touch: deciding which of three initiatives to kill, sitting with a customer who was frustrated, and telling a stakeholder no with a reason they accepted.
Many entry-level roles defined by documentation and coordination are shrinking. The path in is now via evidence and shipped outcomes rather than process work.
Learn to build with AI tooling. You do not need to be an engineer, but you should be able to produce a working prototype.
Product judgement with AI-native execution — designing evaluations, owning metrics, and making cut decisions.
IN SHORT
What the role actually involves and how it differs from a classic PM.
Read moreContract, fractional and advisory engagements — current availability.
Read moreLong-form writing on AI product leadership and shipping MVPs.
Read moreA short call to work out whether the problem is strategy, scope or speed.
Work with AndrewTHE FRAMEWORK
MORE ANSWERS
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.
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.