SHORT ANSWER
Choose an AI product consultant when the uncertainty is the customer problem, scope, AI use case, evaluation, pricing or what should be built at all. Choose a developer when those decisions are validated and the bottleneck is implementation capacity. Early founders often need a product-led build that combines both: senior product judgement to cut the scope and enough engineering execution to ship the one journey that matters.
Answered by Andrew Crossley, AI Product Consultant & Product Partner · Updated 2026-08-22
Hiring implementation capacity before the product decision is clear can make the wrong scope more expensive rather than less risky.
Hiring a consultant when a strong specification already exists can create more analysis when what the team actually lacks is delivery capacity.
If the team cannot agree on the customer, job, scope, AI behaviour or success measure, the problem is product judgement. If those are clear and validated, the problem may simply be implementation capacity.
Customer conversations, a paid pilot, repeated use or another meaningful commitment signal makes it safer to invest in engineering. Without that evidence, product validation usually has the higher return.
A developer can implement an AI feature, but someone still needs to define acceptable output, failure handling, evaluation inputs, cost limits and the human path when the model is wrong.
A founder may need a short product audit, a product-led build, a dedicated engineer or ongoing fractional leadership. Buy the missing capability rather than assuming one job title solves every stage.
FROM EXPERIENCE
Before validation, the valuable work is narrowing the customer, testing willingness to pay and deciding the smallest product journey worth building. Extra engineering capacity cannot answer those questions.
Once that journey is validated and specified, the balance changes. If the remaining constraint is build speed, deeper engineering capacity is the right investment. The best early engagement often moves from product judgement into hands-on delivery rather than forcing a permanent choice between the two.
Some can. Andrew's AI app and MVP engagements combine product scoping with AI-assisted implementation for focused first products. For deeper specialist infrastructure or larger engineering programmes, dedicated engineers should be part of the delivery model.
When the customer, workflow, success criteria and technical requirements are already clear enough that implementation is genuinely the bottleneck. A validated specification with a capable internal product owner is a good example.
Start by making sure someone owns product decisions as well as implementation. A non-technical founder can build far more with AI tooling now, but data access, reliability, AI evaluation and production decisions still need accountable judgement.
IN SHORT
Turning LLMs, RAG and agents into products that hold up in production.
Read moreDone-for-you six-week build turning a founder idea into a launched AI app.
Read moreAI-accelerated MVP delivery, scoped to one journey that earns.
Read moreProve demand before you spend the build budget.
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. For a small company, internal operational work is often the easiest first use to measure because the baseline task already exists and the team can compare time, quality and cost before and after.
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 it deeply, and add another tool only when a specific recurring task justifies the subscription and context-switch cost.
For a UK founder, a focused commercial AI MVP with one core journey typically sits around £12,000–£25,000 in the pricing model used on this site. A prototype or narrow validation build can be roughly £3,000–£8,000. Multiple user roles, RAG or agentic workflows, several integrations, sensitive-data requirements or bespoke design can push the build above £25,000. Model and infrastructure running costs should be measured separately per successful customer task.