What is a Product Decision?
The process that determines whether a product becomes a business — or expensive inventory.
Book a Decision SessionA Product Decision is the process of choosing what product to build, improve, launch, price, position, or stop — based on behavioral evidence rather than assumptions. It answers whether a product should exist, whether real demand exists, who the exact buyer is, and what version deserves investment.
What is a Product Decision?
A Product Decision is not design. It is not consulting. It is not a market research report. It is the structured process of answering — before money is committed — whether a product should be built at all.
Every product that exists was the result of a decision. The question is whether that decision was made on evidence or assumption. Most founders make product decisions every day — informally, instinctively, and often incorrectly.
A formal Product Decision process answers questions like:
Without clear answers to these questions — backed by real behavioral evidence — a founder is not making a product decision. They are making a bet.
Why most Product Decisions fail
Most product decisions fail not because founders are unintelligent — but because they rely on the wrong sources of input.
01 — Gut Feeling
“I know this will work.” “I’ve seen this succeed before.” Gut feeling is valuable experience — but it is not behavioral evidence. Markets change. Users change. What worked five years ago may not work today.
02 — Copying Competitors
“Competitor X is doing well with this product.” Competitors have different cost structures, different customer bases, different distribution channels. Copying a product does not copy the conditions that made it succeed.
03 — Friends and Contacts
“My friends said they would use it.” People say yes to be polite. They say yes when asked by someone they know. Opinion is not demand. Purchase behavior is demand. These are completely different things.
04 — No Evidence at All
“The idea just feels right. Let’s start building.” This is the most expensive mistake. By the time the product is built, tooled, packaged, and launched — the money is already gone. Finding out demand does not exist at this stage costs ₹10L–₹25L and 6–12 months.
The result of a failed product decision:
- Unsold inventory
- Price confusion
- Wrong product built
- Weak differentiation
- Wasted marketing spend
- Scaling failure
- Good product. No sales.
- Capital goes to right product
- Clear price positioning
- Evidence-backed direction
- Real differentiation
- Marketing hits real demand
- Scalable foundation
- Product becomes a business
The real cost of skipping a Product Decision
The cost of skipping a Product Decision is not just financial. It is time, energy, team morale, and market opportunity — all lost.
A founder who invests ₹15L in a product that does not sell has not just lost ₹15L. They have lost the 8–12 months it took to build, the team that burned out building it, the market window that closed while they were busy, and the confidence to try again.
The cost of making a Product Decision is a fraction of this. A Decision Sprint costs ₹25,000 and takes 7–10 days. The cost of skipping it can be ₹15L, 12 months, and a product nobody buys.
Product decisions determine whether a product becomes inventory — or a business.
What a real Product Decision looks like
A real Product Decision is not a meeting. It is not a brainstorm. It is not a survey. It is a structured process built on behavioral evidence from real users in real situations.
It starts with one honest question: What existing behavior proves that this problem is real and painful enough to pay for?
If the answer is “people told me they like the idea” — that is not a Product Decision. That is an opinion collection exercise.
A real Product Decision involves:
| Element | What it means |
|---|---|
| Real user observation | Watching actual users in their real environment — not asking them what they think in a controlled setting |
| Behavioral evidence | What users actually do — not what they say they will do |
| Assumption elimination | Identifying every assumption the founder holds and testing each one against reality |
| Demand validation | Proving that real people will pay real money for this — not just say they will |
| Direction clarity | One clear product direction — not five possibilities — backed by evidence |
| Build / Refine / Stop | A clear verdict — the only acceptable output of a Product Decision process |
The LSAR Framework — a Product Decision system
The LSAR Framework is a 4-phase product decision system developed by L Saravanan. It is the structured process used to replace founder assumptions with behavioral evidence — before capital is committed to a new product.
LSAR stands for Listen, Structure, Analyse, Resolve. Each phase mirrors the natural sequence of any evidence-based decision: understand reality, define the problem, test the options, commit to one direction. Each phase builds on the previous — producing one clear, evidence-backed product direction at the end.
The LSAR Framework applies to any business making a product decision — from SaaS startups deciding which feature to build, to founders launching a new product line, to established businesses expanding their offering. The principles of behavioral evidence work across industries.
Product Decision vs Product Consulting
These are fundamentally different things. Understanding the difference saves founders from paying for the wrong kind of help.
| Factor | Product Consulting | Product Decision (LSAR) |
|---|---|---|
| Output | Recommendations and opinions | One clear verdict — Build, Refine, or Stop |
| Based on | Consultant’s experience and judgment | Behavioral evidence from real users |
| Research method | Interviews, desk research, surveys | Real user observation, ethnographic research |
| Deliverable | Report with multiple options | One product direction with evidence |
| Risk | Opinion-based — can be wrong | Evidence-based — grounded in reality |
| Accountability | Low — “we recommended, you decided” | High — one clear decision, one clear rationale |
Who needs a Product Decision?
Every founder making a significant product investment needs a Product Decision process. Specifically:
When to make a Product Decision
A Product Decision should be made before any capital is committed to a new product. The earlier it is made, the cheaper the process and the higher the impact.
| Stage | Cost of wrong decision | Cost of Product Decision |
|---|---|---|
| Idea stage — no investment yet | Low — just time | ₹25,000 · 7–10 days |
| Pre-launch — ₹10L planned | ₹10L + 6 months | ₹75,000–₹1,00,000 · 3–5 weeks |
| Pre-build — ₹25L planned | ₹25L + 12 months | ₹1,00,000–₹1,50,000 · 3–5 weeks |
| Post-launch — product not selling | Already lost. Further loss likely. | ₹75,000+ to diagnose and redirect |
The pattern is clear: the earlier a Product Decision is made, the cheaper and more impactful it is. Waiting until after launch to discover demand does not exist is the most expensive possible outcome.
Frequently Asked Questions
A Product Decision is the process of choosing what product to build, improve, launch, price, position, or stop — based on behavioral evidence rather than assumptions. It answers whether a product should exist, whether real demand exists, who the exact buyer is, and what version deserves investment. A Product Decision happens before capital is committed.
A Product Decision is important because it prevents founders from committing ₹10L–₹25L+ to the wrong product. Most product failures happen not because of poor execution but because the wrong product was built. A Product Decision based on behavioral evidence ensures capital goes to the right product — before it is too late.
Product validation typically means testing whether an idea works. A Product Decision is broader — it determines whether the product should exist, who it is for, what problem it solves, which version to build, and whether the investment is justified. A Product Decision uses behavioral evidence from real users — not surveys or opinions.
The LSAR Framework is a 4-phase product decision system developed by L Saravanan: Listen — understand real user behavior; Structure — define the problem with evidence; Analyse — validate demand and eliminate wrong directions; Resolve — one clear product direction. LSAR replaces assumptions with behavioral evidence before capital is committed.
When a Product Decision is skipped, founders typically build based on gut feeling or unverified opinions. The result is unsold inventory, price confusion, weak differentiation, and capital loss of ₹10L–₹25L or more. The product may be built perfectly — but nobody buys it because demand was never real.
A Product Decision Strategist is an expert who helps founders make the right product decisions before investing serious capital. L Saravanan is India’s Product Decision Strategist — with 18+ years of experience, 40+ founders served, and 45+ products guided using the LSAR framework.
Product consulting gives opinions. A Product Decision process gives a structured, evidence-based verdict — Build, Refine, or Stop. L Saravanan’s LSAR framework uses behavioral research, real user observation, assumption elimination, and demand validation to produce one clear decision — not a generic report.
Yes. The LSAR Framework applies to any business making a product decision — from SaaS startups deciding which feature to build, to D2C brands launching a new product line, to traditional businesses expanding their offering. The framework is built on behavioral evidence principles that work across industries.
Before any capital is committed to a new product — before development, tooling, packaging, inventory, or marketing investment. The ideal moment is when a founder has an idea or product direction but has not yet spent money on it. Making the decision at this stage costs a fraction of what it costs to undo a wrong investment.
One clear, evidence-backed product direction. Specifically: a validated problem statement, target customer profile, behavioral evidence report, eliminated wrong directions, demand validation results, and a Build/Refine/Stop recommendation. The engagement removes guesswork and replaces it with decisions backed by real user behavior.
Ready to make the right Product Decision?
Every engagement begins with a 15-minute session to assess your product, your stage, and whether this is the right fit. Limited engagements available.
Book a Decision Session Limited engagements.