If your product launched tomorrow —
how many real buyers
can you name?
Not people who said yes.
People who would pay.
Most founders cannot answer that question.
Not because they are wrong. Because they never checked.
This is how it happens.
“I know this will work.”
Built on personal conviction. No external evidence.
“They are doing well. So this should work for me.”
Copied the product. Not the context that made it work.
“My network said yes.”
They said yes because they know you. Not because they would pay.
“The problem exists. I have the solution.”
Logical on paper. Untested in behavior.
The money did not disappear at launch.
It disappeared the day the decision was made.
Same factory.
Same materials.
Same water.
Ethnographic research at Indian weddings. The real buyer was the host — not the guest. The host’s goal: Surprise the guest. One word changed the entire brief: SURPRISE.
Brief reframed. Not a hydration vessel — a surprise delivery mechanism. Every design decision traced to that one behavioral observation.
Three concepts tested: Rubik’s Cube, Honeycomb, Volleyball. Scored against 5 behavioral criteria. Volleyball won — the only one that created sustained social interaction.
Verdict: BUILD. No guest in Indian wedding history had ever taken an empty bottle home. Until this one.
profit increase
The LSAR Framework
Four phases. One purpose. Replace assumption with behavioral evidence — before capital moves. Full framework →
Listen
What are people actually doing — not saying.
Structure
Convert that behavior into one product direction.
Analyse
Three to five directions tested. One survives.
Resolve
Build. Refine. Stop.
Observe real users in real situations.
Not what they say. What they actually do.
Field research or desk research — no bias. Real behavior. Real context. Real frustrations. Zero predetermined conclusions. The researcher enters with zero assumptions and lets behavior speak.
- What they actually do, why they do it, what context surrounds the decision
- Opinion is not behavior. Stated preference is not demand.
- LSAR only works with real behavioral evidence
Outputs from Listen
- Real user profile — who they actually are
- Real problem — what actually frustrates them
- Real behavior — what they currently do
- Real context — when, where, and why
- Jobs to be done — what they are truly trying to achieve
Convert behavior into product direction.
The customer’s voice — not the founder’s vision.
Everything comes from behavioral evidence — not from what the founder originally wanted to build, not from competitors, not from internal team opinions.
- If this phase is wrong — everything downstream is wrong
- A weak foundation produces a product that solves the wrong problem
- For the wrong person. At the wrong price.
Outputs from Structure
- Validated problem statement — precise, evidenced
- Target audience — buyer and user identified
- Pricing direction — from behavioral signals
- Feature priority map — ranked by evidence
- Market positioning — from observed gaps
- Structured product brief
Test every direction against evidence.
One survives. The rest are eliminated.
3–5 product directions generated. Each evaluated against behavioral evidence criteria — not team preference, not founder instinct. Weak directions eliminated with documented reasons.
- No voting by preference. No “this one feels better.”
- No consensus without evidence
- The strongest behavioral evidence wins
Outputs from Analyse
- 3–5 validated directions with evidence scores
- Eliminated directions with documented reasons
- Demand validation — real willingness, not stated interest
- One recommended direction
- Risk assessment
One verdict: Build, Refine, or Stop.
When Build — execution begins in whatever form the product requires. Every execution step stays aligned with Listen, Structure, and Analyse. The decision comes first. Execution follows. Always.
- The moment execution drifts from evidence — the wrong product gets built
- Good execution on a wrong decision still fails. Every time.
- LSAR ensures the decision and execution stay aligned
Outputs from Resolve
- Final product direction — one, clear, evidenced
- Build / Refine / Stop verdict
- Decision rationale document
- Execution plan aligned with evidence
- Launch readiness in whatever form required
- Capital allocation guidance
Product Decision Strategist · India
He started as a product designer.
He became a strategist by doing.
Manufacturing foundation. DFMA. Plastics engineering. The training that teaches you what a wrong design costs before it reaches production.
Form. Function. User behavior. How products are designed to be wanted — not just manufactured.
His own business. His own capital. 50+ customers. He made product decisions every week — and felt every consequence in rupees and months.
He watched 40+ founders across 45+ products make the same mistake. Not a similar mistake. The exact same one. Every time. In every industry. The decision to build was made before the evidence existed.
FMCG · Packaging · Food · Agricultural Equipment · E-commerce · Digital · Service Design
He built the system to close that gap — so no founder has to discover the mistake after the investment is committed.
Who this is for.
If you are still in the window — this is exactly what that window is for.
Limited engagements.
Three engagements.
Every one begins with a conversation.
15 minutes. No forms. No commitment. Full details on the pricing page →
Test Your Product Clarity
Answer 4 questions to reveal the current risk profile of your product idea.
Common Questions
What is a Product Decision?
A Product Decision is the process of determining whether a product should be built, improved, launched, or stopped — based on behavioral evidence rather than assumptions. It happens before building begins — before tooling, development, or inventory.
What is a Product Decision Strategist?
A Product Decision Strategist ensures founders make the right product decisions before investing serious capital in a new product. L Saravanan, India’s Product Decision Strategist, applies the LSAR framework to give founders one clear direction before building begins.
Why do products fail even when built correctly?
Products fail when the wrong product is built — not because of poor execution. Most founders skip the Product Decision phase and move from idea to investment based on gut feeling or unverified opinions. Without behavioral evidence, even a perfectly built product ends up unsold.
What is the LSAR Framework?
LSAR stands for Listen, Structure, Analyse, Resolve — a 4-phase product decision system developed by L Saravanan. It replaces founder assumptions with behavioral evidence before any build decision is made.
When should a Product Decision be made?
Before investing capital in development, tooling, packaging, or inventory. The ideal time is when a founder has a product direction but has not yet started building. This prevents ₹10L–₹25L+ in losses and 6–12 months of wasted time.
How is this different from product consulting?
Product consulting gives opinions. The LSAR framework gives decisions — one specific product direction backed by behavioral evidence from real users, with a clear Build, Refine, or Stop verdict. No generic reports. No ambiguity.
Who should work with L Saravanan?
Founders and CEOs across India preparing to invest ₹10L–₹25L+ in a new product within the next 30–90 days. Founders whose product direction is still flexible and who need behavioral evidence before building begins.
What does a Decision Sprint deliver?
A validated Problem Statement, Target Customer Profile, Assumption Map, Behavioral Evidence Report, Eliminated Directions List, and next engagement recommendation — in 7 to 10 days for ₹25,000.
One decision made correctly saves everything that comes after.