Introduction
A surprising number of AI projects begin with "We should probably add AI." Very few begin with "Our users have a problem that AI solves."
The second approach is the correct one. AI should solve a problem. Not satisfy a trend.
This framework helps you decide whether AI adds value to your product, or whether it adds complexity, cost and risk while the underlying problem stays exactly where it was.
What it solves
What AI solves well
-
Open-ended language work
Summarising, drafting, translating, paraphrasing, classifying free-text input, work that used to require a person and now can be acceptable with a model in seconds.
-
Pattern matching at scale
Routing tickets, suggesting next steps, prioritising lists, detecting anomalies. When the input is structured and the patterns are messy, models often outperform rule-based systems.
-
Generating drafts that humans review
Email replies, first-cut content, suggested code, candidate matches. The product still has the human in the loop, but the time-to-first-version drops by 80% or more.
-
Personalising at scale
Recommendations, tailored content, individualised onboarding. AI shines when the input is rich and there is enough usage to learn from.
-
Voice and vision tasks
Transcription, image labelling, OCR, document extraction. Tasks that used to need bespoke pipelines now run on commodity APIs.
What it does not solve
What AI does not solve
-
An unclear product
If the product does not yet solve a customer problem, AI will not rescue it. AI added to an unclear product is an unclear product with a higher hosting bill.
-
Missing distribution
A clever AI feature with no distribution still has no users. AI is not a substitute for the marketing, sales and product work that gets a product in front of people.
-
Bad data hygiene
AI is sensitive to data quality. If the product's data is incomplete, inconsistent or untrusted, the model output will look impressive on stage and embarrass you in production.
-
Operational maturity
AI features come with monitoring, rate limits, retries, fallbacks and prompt versioning. If the basic product does not have monitoring, AI is the wrong place to start.
-
Pricing that does not account for variable cost
AI inference costs scale per user, per call, per token. A flat-rate product with AI features can quietly turn unit economics negative without anybody noticing.
Decision tree
Six questions before you add AI
Run every proposed AI feature through these questions. The 'no's keep you from shipping AI that does not earn its complexity.
- Question 01
What user problem are we solving?
No → Find the problem before designing the feature. A solution looking for a problem is the most expensive way to discover that the problem was elsewhere.Yes → Confirm the problem in one sentence, named by a real customer in a real situation. - Question 02
Would this problem still exist without AI?
No → Skip it. If the problem disappears once you change a process, a price or a setting, AI is solving a self-inflicted issue.Yes → Confirm the problem persists across customers, not just one loud user. - Question 03
Can simpler automation solve it?
No → Use the simpler automation. Rules, scripts and integrations are cheaper, more predictable and easier to debug than a model.Yes → Confirm AI is the simplest tool that works, not the most impressive one available. - Question 04
Will users notice the difference?
No → Skip the feature. If users cannot tell whether AI is involved, the AI is not the source of the value.Yes → Define how they will notice. Faster, better, cheaper, different, pick one and make it measurable. - Question 05
Can we explain the value in one sentence?
No → Sharpen the value statement first. If you cannot explain it, customers will not understand it, and support will not be able to defend it.Yes → Test the sentence on three customers. If they nod, build. If they ask follow-up questions, sharpen. - Question 06
Will AI improve the product or only the pitch deck?
No → Save the spend. AI as a marketing feature lives until the next funding round and dies the moment unit economics arrive.Yes → Build it. Track adoption, cost and customer outcomes, and be willing to remove the feature if any of those slips.
Common mistakes
Five common mistakes founders make
- 01
AI before product-market fit
Adding AI to a product that has not yet found fit is taking a bet on the wrong variable. Find the fit first, then ask where AI sharpens it. The other order produces clever features for nobody.
- 02
AI without customer demand
Engineers ask for AI; designers ask for AI; investors ask for AI. Customers rarely ask for AI by name, they ask for outcomes. Build to the outcome, not to the keyword.
- 03
AI because competitors use it
Competitor moves are signals, not strategies. Their AI feature solves their problem. Your AI feature should solve yours. Copy the discipline, not the feature list.
- 04
AI as a marketing feature
An AI feature you cannot defend to a customer is an AI feature you cannot maintain. Marketing-driven AI ages badly, and accelerates churn when the gap between the pitch and the experience becomes visible.
- 05
AI without operational planning
Models drift, providers raise prices, prompts break, costs scale unpredictably. AI features need monitoring, fallbacks and an owner. Shipping AI without an operational plan is shipping technical debt with a marketing team.
Alternatives
Practical alternatives to AI
Four options that often deliver the same customer outcome with less complexity, cost and risk.
-
Better defaults and rules
Many 'we need AI' problems are actually 'we need better defaults' problems. A handful of rules and sensible defaults often delivers most of the perceived value of a model at a fraction of the cost.
-
Templates and structured workflows
Templates give users a starting point without the unpredictability of generated output. They are easier to maintain, easier to support and easier for customers to trust.
-
A human in the loop
For low-volume, high-stakes work, a human reviewer is faster to set up and more reliable than an AI system. Automate later, once you understand the rules the human applies.
-
Narrow AI in one specific place
If AI does belong in the product, start with one specific workflow rather than a horizontal capability. Narrow wins are easier to ship, measure and improve.
Ronald's rule of thumb
If removing AI does not reduce customer value, do not add AI.
Use the same test as for any other feature: take it out and see what changes. If the customer is unaffected, the AI is decoration. Decoration is fine, but it should not be billed as infrastructure, and it should not be defended as strategy.
, Ronald · YourStartup.Expert
Summary
Summary
AI is useful almost everywhere and misapplied almost everywhere. The decision to add it should start from a customer problem, not from a category trend. The six questions above eliminate the wrong reasons first: no clear problem, no need for AI, a simpler tool exists, users cannot tell the difference, value cannot be explained, or the value is marketing rather than product.
When AI passes all six, build it deliberately, with monitoring, an owner and a willingness to remove it if it stops earning its cost. That last willingness is what separates AI in a product from AI in a slide deck.
Common questions
Adding AI to a product, answered.
The questions founders ask before they commit to AI features.
- Should every startup use AI?
- No. AI belongs in products where it solves a specific customer problem better, faster, cheaper or differently than the alternative. Most startups have a few places where AI fits and many places where it does not. Adding AI everywhere is the same mistake as adding any other technology everywhere, it dilutes focus, complicates the stack and confuses the customer.
- When does AI create value?
- When the task is open-ended language work, pattern matching at scale, personalisation, voice or vision processing, or generating drafts that humans review. Value appears when AI shortens the path between a user's intent and their outcome, and when the cost of inference fits comfortably inside the unit economics. If either of those is missing, AI is decoration rather than value.
- What are alternatives to AI?
- Better defaults, rule-based systems, templates, structured workflows and a human in the loop. Many problems framed as 'we need AI' resolve once you list the actual decisions the user is trying to make. Simple systems with good defaults frequently outperform AI features in customer-perceived value while being easier to maintain, support and price.
- Is AI expensive to maintain?
- Often yes. AI features carry inference costs that scale with usage, vendor lock-in to a specific model family, prompt and parameter changes that break when the model updates, and a need for monitoring, fallback paths and rate limiting. The build cost of an AI feature is rarely the largest line. The recurring operational cost is.
- How do I validate an AI idea?
- Build the smallest possible version against real customer input, manually if necessary. If the output produces measurable customer value (faster, better, cheaper outcomes), invest further. If the output is interesting but not used, kill it. AI validation looks like product validation: real customers, real workflows, real outcomes. Anything else is a demo.