1.1 Lean Validation: Test Demand Before Building
Lean validation is the disciplined, low-cost test of whether real demand exists before substantial product, marketing, or operational investment. It asks whether real people will take a real action in response to a real offer—not whether they say the idea sounds good.
It sits before campaign metrics such as CTR, ROAS, conversion rate and cost per lead. Those metrics assess a running campaign; lean validation tests the underlying assumption: does a market want and pay for this?
Three Principles
- Reduce uncertainty, not eliminate it. No pre-build test guarantees success. Identify the riskiest assumption and obtain enough evidence to decide the next move.
- Test cheaply before building expensively. If a page or outreach test answers the same demand question as months of product work, run the test first.
- Seek direction, not certainty. A good test gives a justified next action—build, iterate, reposition, or stop.
| Path | Time | Cost | What is learned |
|---|---|---|---|
| Full build first | 6–18 months | ₹20 lakh–₹2 crore+ | whether demand exists, but after commitment is hard to reverse |
| Functional MVP first | 2–4 months | ₹2–20 lakh | whether a small working version has demand/value |
| Lean validation | 7–21 days | ₹0–₹10,000 | whether to build at all, and what to build |
CB Insights is cited as finding that around 40% of startups fail through no market need. Lean validation aims to expose that risk in days rather than after years of build cost.
Market research and lean validation are complementary but not interchangeable. Research records what people say, believe, or report; lean validation observes what they decide to do when presented with a real offer. Use the former to understand a market and explain a result; use the latter for the build/no-build decision.
Three Traps That Cause Build-first Behaviour
| Trap | Faulty reasoning | Correction |
|---|---|---|
| Certainty illusion | “We know customers have this problem.” | Pain observation does not prove willingness to pay or adopt. |
| Builder’s bias | “Let’s build and see.” | Building to learn is the costliest experiment; test the assumption first. |
| Speed fallacy | “Validation delays first-mover advantage.” | A 7-day test is faster than a 6-month build; market fit matters more than being first. |
Clairo's early assumptions illustrate the distinction: will sales reps trust a bot in Zoom/Meet; do they value the follow-up more than transcription or summaries; will they pay ₹999/month; and after how many meetings does willingness to pay appear? A page, targeted messages, and short calls can test these without code.
Clairo later reached 300 paying customers, about ₹14.2 lakh monthly revenue, and about 14% month-on-month growth—but those outcomes do not remove the need to test the original assumptions first.
Zoko, a D2C plant-based cosmetics brand with 6,200 customers and 72% subscription retention, used an Instagram test before manufacturing three collections. A ₹5,000–₹10,000 story-ad test drove about 200 visitors to a test page over seven days: “2X faster results” beat “no chemicals, no compromise,” establishing the primary message while plant-based claims remained secondary.
Four Validation-first Mental Shifts
- Opinion → evidence: instinct starts the question; observable behaviour supplies the answer.
- Expensive build → cheap test: prefer a test that yields the same learning at roughly 1% of the cost and 5% of the time.
- Certainty → direction: seek enough evidence for the next step, not an impossible guarantee.
- Launch day → signal day: do not let a months-later launch be the first moment demand is tested.
Exam tip: Market research records what people say; lean validation observes a decision or commitment. The latter is the appropriate tool for the build/no-build decision.
Key takeaways
- Validate real demand before committing to a product build.
- Test the riskiest assumption with the fastest, cheapest credible method.
- A validation path obtains the decisive learning at a fraction of build-first time and cost.
- Avoid certainty illusion, builder’s bias, and speed fallacy.
- Think evidence-first: move the first truth moment from launch day to signal day.
1.2 Smoke Tests: Create a Fake Door and Observe Behaviour
A smoke test presents an offer as if it exists, then measures what cold market participants actually do. It is a fake door: the product is unavailable, but the behaviour at the door supplies evidence. Clicks, sign-ups and payment attempts require more commitment than survey praise.
The fake door can take three concrete forms: a waitlist page for an unavailable product; a Buy Now button that leads to a “Coming Soon” page; or a pre-order form that asks for payment details before fulfilment exists. Each puts the respondent closer to a genuine economic decision than a survey does.
Three Smoke-test Formats
| Format | Question answered | Design | Best use |
|---|---|---|---|
| Landing-page test | Does this proposition/message generate demand? | one headline, one subheadline, one CTA; measure sign-ups/waitlist | default test for a new product, segment, or message |
| Pre-sales test | Will someone pay before the product exists? | pre-order, deposit link, or B2B letter of intent | payment intent and higher-consideration offers |
| Ad-creative test | Which message/hook resonates? | two or more ad variations; compare ad-level CTR | rapid B2C/D2C message testing; directional data can appear within 48 hours |
Match the format to the missing question. A wrong format may be executed well yet answer the wrong question.
A B2B pre-sales commitment can be a pre-order, deposit, or signed LOI; it is useful where a buyer cannot yet make payment but can place formal authority behind an intended purchase. Ad-creative tests require only a message and small traffic budget, making them the fastest route to directional B2C/D2C evidence.
Examples
- Clairo: founder sent three targeted LinkedIn DMs/day to sales leaders for two weeks (50+ prospects, zero ad spend). “Your follow-up is written before your sales meeting ends” produced 3.1× more sign-ups than “AI meeting recorder.” The market valued the outcome, not recording technology.
- Zoko: ₹3,000 Instagram Story test over four days, same visual and two claims. “2X faster results” generated 2.8× the swipe-up rate of “No chemicals and no harsh effects.” Use speed as the principal message.
Three Primary Signals and a Payment Signal
| Signal | Metric | Positive threshold | If weak |
|---|---|---|---|
| Traffic | CTR to the page | revise ad message, value proposition, or targeting | |
| Intent | landing-page CTA conversion/sign-up rate | improve page promise/CTA or audience alignment | |
| Quality | bounce rate | fix message–page–audience alignment | |
| Payment | pre-order, deposit, LOI, payment attempt | any genuine conversion is high-quality evidence | move to a commitment test if still unproven |
The first three signals must be positive together before declaring demand from a page test. One green and two red signals are not validation. A payment commitment, even at a low rate, is stronger than a much higher waitlist rate because it puts money or formal authority at risk: a payment conversion is more meaningful than a waitlist conversion.
The signals diagnose different parts of the journey:
- CTR asks whether the first message/offer earns attention from the intended audience.
- CTA conversion asks whether the page's promise creates concrete intent after visitors understand it.
- Bounce rate checks whether the page, message, and audience are coherently aligned rather than merely generating a click.
- Payment/LOI/deposit tests whether interest turns into an economic or formal commitment.
The evidence ladder is social engagement → email/waitlist → Buy Now/pre-order action → LOI/deposit → full payment. Do not treat an email as equivalent to a payment simply because the email count is larger.
Low-resource Routes
| Route | Budget | Speed/strength |
|---|---|---|
| No-code page + organic/community post | ₹0–₹500 | low cost; organic signal accumulates slowly |
| Paid ads + landing page | ₹3,000–₹10,000 | controllable volume; data may arrive in 48 hours |
| Forum/community seeding (Slack, Reddit, Discord, founder groups) | low | slower, but reveals why people respond or decline |
| Product Hunt waitlist | community effort over 2–4 weeks | large potential audience; strongest fit for product/tech audiences |
Carrd and Typedream permit no-code pages. Community seeding through relevant Slack, Reddit, Discord, or founder groups is slower but adds qualitative explanation of why people did or did not respond. Product Hunt requires – weeks of community build-up but can reach an existing high-consideration tech audience. The barrier is not money or technical skill; it is choosing to test before building.
Key takeaways
- A smoke test measures behaviour, not stated preference.
- Use landing pages for demand/message, pre-sales for payment, and creative tests for resonance.
- Read CTR, conversion and bounce together; do not celebrate a single green metric.
- Meaningful validation is possible at near-zero cost.
1.3 Landing-page Validation: Design for a Clean Signal
A validation page has one job: produce a clean demand signal. A false positive—declaring demand due to biased page design or traffic—is worse than no signal because it sends the team into a costly build with false confidence.
Causes of False Positives
- Incentivised sign-up: “Sign up to win a free starter kit” measures desire for the incentive, not the product.
- Warm traffic: friends and followers supply goodwill; use cold ICP traffic instead.
- Vague offer: no specific value, price, or commitment lets visitors sign up at no meaningful cost.
Five Mandatory Structural Elements
- Specific headline — state the concrete outcome; it should repel the wrong audience. Include price early if price filters are relevant.
- Subheadline — name who it is for and the primary outcome in plain language.
- Minimal social proof — one early-adopter testimonial or small trust cue; excessive proof can mask a weak proposition.
- One CTA — one commitment only. Two CTAs turn the test into a general web page and blur the result.
- No navigation/distractions — remove menus, footer links, blog links and escape routes.
The page should make a wrong visitor self-select out. For example, an outcome-led Clairo headline can be “Your CRM updates itself after every sales call,” with a plain-language subheadline for sales teams at –-person companies that lose follow-ups after meetings. A Zoko page can make a bounded outcome and relevant qualifier explicit: visible skin change in days and a chemical-free promise. If the headline/subheadline do not let a reader tell whether the offer is for them, the page is too broad; where price is a material filter, disclose it early rather than collecting unqualified sign-ups.
Traffic quality determines signal quality. Use cold outreach to ICP job titles, tightly targeted LinkedIn ads by role/company size, tightly targeted Meta ads by demographic/location, cold email, or relevant communities. Avoid friends, followers and broad interest targeting.
| Traffic source | Signal quality | Reason |
|---|---|---|
| Founder friends/followers/family | Invalid for demand validation | Sign-ups can express goodwill rather than customer intent. |
| LinkedIn ads or cold outreach by role/company size | Strong B2B option | Reaches cold people who match a defined ICP, such as sales directors at –-person firms. |
| Instagram/Facebook ads by age, gender, and location | Strong B2C option | Reaches a defined cold demographic, such as Zoko's women aged – in Tier-1 cities. |
| Community seeding / cold email | Useful when tightly matched | Can reveal both action and qualitative context; broad or known audiences still corrupt the signal. |
Cold traffic is valuable because the visitor is responding to the proposed problem–solution, not a relationship with the founder or brand.
Read the Three Signals Diagnostically
| Signal pattern | Diagnosis | Next action |
|---|---|---|
| All green | real demand signal | proceed to a commitment/pre-sales test |
| Traffic green; intent and quality red | ad works; page promise does not | rewrite proposition/headline/CTA; keep traffic source fixed |
| Traffic red | insufficient qualified interest | stop page optimisation; fix ad copy/targeting and rerun traffic test |
| Traffic and intent green; quality red | likely audience mismatch | check who arrived versus intended ICP; tighten targeting |
Change one variable at a time. If ad and page change together, a changed result cannot identify the cause.
Worked Cases
Clairo CRM integration: LinkedIn ads targeted sales directors at 10–100-person companies, ₹8,000 over 10 days; email-capture CTA. Outcome headline, “Your CRM updates itself after every sales call,” beat a feature headline. Results: CTR 3.8%, sign-up 22%, bounce 41%—all green. Decision: proceed to pre-sales; lead with the outcome.
Zoko 21-day Glow Challenge: Instagram ads, ₹5,000 for seven days, targeting women aged 24–34 in Tier-1 Indian cities. CTR 3.8% (green), sign-up 9% (red), bounce 71% (red). The ad attracted people but the page did not deliver the expected proposition. Fix the value proposition, not merely layout/images/button size.
The diagnostic is deliberately narrow: with traffic green and both intent/quality red, retain the traffic source and rewrite the headline, proposition, or CTA. If traffic is red, do not optimise the page yet—fix copy/targeting first. If traffic and intent are green but quality is red, inspect who arrived versus the intended ICP; high sign-up plus high bounce can indicate broad/wrong targeting rather than page-design failure.
Key takeaways
- Validation pages minimise alternate explanations for a positive result.
- Use one headline, subheadline, CTA, minimal proof, and no distraction.
- Cold, tight ICP traffic is evidence; warm-network traffic is not market validation.
- Diagnose the failed signal before changing anything.
- A high bounce rate following a strong CTR usually calls for proposition/audience diagnosis, not cosmetic page redesign.
1.4 Pre-sales Validation: Ask for Commitment Before Build
Pre-sales validation asks for money or a formal commitment before the product is ready. It supplies a different category of evidence from interest: payment is hard to fake.
Commitment Spectrum
| Strength | Action | What it proves / does not prove |
|---|---|---|
| 1. Weakest | social engagement | awareness, not demand |
| 2. | email/waitlist sign-up | curiosity; no evidence of payment |
| 3. | pre-order with payment on delivery | conditional purchase intent |
| 4. | deposit paid | strong commitment; real money at risk |
| 5. Strongest | full advance payment | highest pre-build demand evidence |
Pre-sales means reaching stage 3, 4 or 5, not stopping at email sign-ups. It still does not prove product-market fit: retention after use is also required.
Method Selection
| Context | Method | What it validates |
|---|---|---|
| B2B early/enterprise/high-consideration purchase | Letter of intent (LOI) | written intent from a real buyer/authority when payment needs procurement approval |
| B2B complex workflow | Paid pilot / proof of concept | willingness to pay and workflow fit; requires some usable product version |
| B2B with trust and access | Advance/founding payment | real money before the product/feature exists |
| B2C launch/subscription | Founding-member offer | willingness to pay at a specific discounted early price |
| B2C | Pre-order page | stronger full-price checkout commitment with later fulfilment |
| B2C community/volume | Crowdfunding or deposit | demand plus social proof/community conviction |
Method Details That Affect Signal Strength
| Method | Crucial design rule |
|---|---|
| B2B LOI | It is non-binding rather than a contract, but a named real budget holder/decision maker must sign an intent to purchase when ready. |
| Paid pilot/POC | Deliver a limited product/workflow engagement for a small fee—sometimes only a few thousand rupees. It proves payment and fit, but needs some usable MVP. |
| Advance/founding payment | Exchange advance/full payment for early access or a grandfather plan whose preferential price can remain even when later prices rise. |
| Founding-member offer | Restrict early slots (e.g., first or ) and typically discount – to compensate the buyer for pre-build risk. |
| Pre-order page | Capture checkout payment at full launch price and set a later fulfilment date, often – days. It is stronger than an incentivised discount offer. |
| Crowdfunding/deposit | A public Kickstarter/Indiegogo-style campaign can add social proof because backers share it; a private deposit reserves a place with partial payment. |
Offer Designs and Advance Thresholds
- Clairo: Team plan at ₹1,499/month for six months versus ₹2,499 normal price (40% founding discount). Offer first to sales directors who had already signalled interest. Set success in advance: five payments in 14 days → build CRM integration; two or fewer → diagnose price or ICP mismatch.
- Zoko: first 100 Glow Challenge kits at ₹699 versus ₹999, using Instagram Stories/WhatsApp, visible limit, and three-week delivery. Set success in advance: 25 paid orders in seven days → manufacturing confirmed; fewer than 10 → revise offer and survey non-buyers.
The discount compensates for pre-build risk; it is not proof by itself. Set the success threshold before launch to avoid moving goalposts after seeing results.
For Clairo, five payments establish real willingness to pay ₹1,499/month, trust before the feature exists, and budget authority; they do not establish product-market fit, which additionally requires retention. For Zoko, the first- cap represents a genuine manufacturing constraint as well as urgency; the ₹300 reduction is the buyer's pre-sales risk premium.
Treat a “No” as Structured Data
| Rejection | Diagnosis | Next move |
|---|---|---|
| “Too expensive” | price–value gap | test smaller/entry offer; ask acceptable price |
| “Not now” | timing mismatch | ask when/what trigger creates relevance; retain as future lead |
| “Missing feature X” | feature/fit gap | ask whether X would cause purchase today; separate real blocker from negotiation |
| “Need to think” | trust/confidence gap | ask what information is missing; provide it and set follow-up date |
| “Good, but not for us” | ICP mismatch | remove from pre-sales pipeline; refine targeting |
A structured no is more useful than a vague yes that becomes a no at payment time.
Key takeaways
- Payment/commitment is the strongest pre-build evidence of demand.
- Match LOI, paid pilot, advance payment, founding offer, pre-order or crowdfunding to the context.
- Define price, population, time limit and success threshold before the offer runs.
- Diagnose rejection type; a no tells the next experiment.
1.5 Surveys: Use Them to Explain Behaviour, Not Prove Demand
Surveys are valuable after a test, to explain why people converted or did not and to mine ICP language. They are unreliable for “does demand exist?” or “will people pay?” because they measure attitudinal data (what people say) rather than behavioural data (what people do).
| Attitudinal statement | Behavioural evidence |
|---|---|
| “I would definitely buy this.” | paid ₹699 before the product existed |
| “Price matters less than quality.” | bought the cheapest available option |
| “I always follow up after meetings.” | 72% of follow-ups are not sent in practice |
Five Biases and Fixes
| Bias | Distortion | Fix |
|---|---|---|
| Social desirability | respondents support the researcher or try to look good | use anonymous surveys and remove identity pressure |
| Hypothetical bias | people overstate future purchase/use/change | ask about past behaviour, not imagined future |
| Acquiescence | tendency to agree with positive/yes–no statements | use balanced, behaviour-based questions |
| Leading-question bias | wording implies the desired answer | use neutral phrasing; test wording outside the team |
| Researcher confirmation bias | designer writes/interprets questions to support the idea | have an uninvolved reviewer inspect survey before launch |
Core rewrite rule:
Replace “Would you…?” with “When did you last…?”
| Biased question | Behavioural rewrite |
|---|---|
| “Would you use an AI recorder that writes follow-ups?” | “Think about the last missed follow-up email. What happened?” |
| “How important is chemical-free skincare?” | “Tell me about the last skincare product you stopped using and why.” |
| “Would you pay ₹999/month to save 90 minutes/day?” | “What is the most you paid for a productivity tool in the last 12 months, and why?” |
When Surveys Belong
| Question | Correct tool |
|---|---|
| Does demand exist? | smoke test or pre-sales—not survey |
| Will they pay ₹999/month? | pre-sales—not hypothetical price survey |
| Why did a visitor not convert? | post-test survey |
| What words does the ICP use for the problem? | open-ended survey/language mining |
Six Survey-design Rules
- Use fewer than 8 questions; completion declines after about 5 and added questions degrade quality.
- Ask one concept per question; avoid double-barrelled questions such as “quality and price.”
- Prefer past behaviour to future intention.
- Use open questions for language; closed questions for frequency/magnitude.
- Never name the product/feature in the question; it creates leading bias.
- Test-read with three people outside the team before sending broadly; revise any question that causes hesitation or conflicting interpretation.
Five-question Diagnostic Templates
Clairo non-sign-up visitor:
- Last delayed/missed sales follow-up: what happened?
- In a typical week, how many post-meeting follow-ups does the team send?
- What tool/process was tried in the past year and what happened?
- Describe the ideal follow-up process in one sentence.
- What would stop adoption of a new follow-up tool even if it worked?
Zoko bounce visitor:
- Last skincare product bought and purchase reason?
- A skincare product that disappointed you: what happened?
- Search words/phrases used for new skincare?
- What creates hesitation with an unknown skincare brand?
- Last time you paid more than ₹600 for skincare: what made it worthwhile?
Key takeaways
- Surveys diagnose why and capture customer language; they do not validate demand or price.
- Counter social desirability, hypothetical, acquiescence, leading, and confirmation biases.
- Ask neutral, past-focused questions without naming the product.
- Keep surveys short, single-concept, and pre-tested on three independent readers.
1.6 Minimum Viable Product Validation: Know When to Build
An MVP (minimum viable product) is not simply a rough product with fewer features. It is the minimum experiment that produces the highest-quality learning needed for the next decision.
Validation MVP versus Functional MVP
| Type | Question | Typical tools | When used |
|---|---|---|---|
| Validation MVP | Does real demand exist and what should be built? | smoke tests, landing pages, pre-sales offers, interviews | before writing code/building operations |
| Functional MVP | Does the product actually deliver value? | smallest working version/pilot | only after validation signals are green |
A stripped-down product built too early is not automatically an MVP; it may merely be a smaller, still-unvalidated product. Functional MVP follows validation MVP.
Four Build Signals: All Must Be Green
| Signal | Green condition | If red |
|---|---|---|
| Demand | page test shows CTR , sign-up , bounce | redesign a targeted demand experiment |
| Commitment | at least one genuine pre-sales payment, deposit, or LOI from real ICP | only soft interest exists; run commitment test |
| ICP clarity | name company/person type, buyer role, trigger event, and budget authority | ICP is too broad/wrong; narrow segment |
| Constraint clarity | name one concrete adoption barrier (price, awareness, integration, etc.) | barrier is undefined; investigate with interviews/survey |
Decision rule: begin a functional MVP only when all four signals are green. Any red signal requires one more targeted experiment for that gap—not a broad restart and not a build based on optimism.
The fourth signal, constraint clarity, is deliberately not a demand metric. The team must be able to state one concrete adoption barrier—such as price, awareness, integration, or another specific obstacle. Without it, a team may incorrectly assume that a seemingly interested ICP will adopt automatically.
Select Method by the Missing Signal
| Missing signal | Method | Indicative budget | Time |
|---|---|---|---|
| Basic demand | smoke test/ad creative/fake LinkedIn post | ₹0–₹3,000 | 2–3 days |
| Message resonance | landing-page validation (Carrd/Typedream) | ₹1,000–₹5,000 | 3–5 days |
| Willingness to pay | pre-sales/founding-customer outreach | ₹0 | 5–7 days |
| Behavioural depth/constraint | 10 ICP interviews (Zoom/voice) | ₹0 | 1–2 weeks |
Match the tool to the missing signal, rather than selecting the method the team finds most comfortable.
Use the narrowest adequate method: a fake LinkedIn post with a Loom link can test basic demand in – days for ₹–₹; a Carrd/Typedream page can test message resonance in – days; a founding-customer DM campaign can test payment in – days; and about real-ICP Zoom/voice conversations can reveal behavioural depth or the adoption constraint. If all four signals are already green, stop validating that decision and build the functional MVP.
Budget Tiers
| Band | Available moves |
|---|---|
| ₹0 | organic LinkedIn/community post; DMs to 20 target customers; WhatsApp/Zoom interviews; Google Forms post-test survey |
| ₹500–₹2,000 micro budget | Carrd/Typeform-style page, one boosted Instagram post for 3 days, ₹1,000 domain, three Canva creative variants |
| ₹5,000 lean budget | five-day paid campaign with two ad sets, basic A/B testing, 100 cold LinkedIn DMs, WhatsApp broadcast to 200 contacts with founding offer |
A three-day experiment with a predeclared threshold is more useful than a three-week test with no decision criterion. Typical low-resource tactics include a free Google Form for post-test learning, a low-cost domain of roughly ₹ for credibility, three Canva free-tier creative variants, and a basic test platform such as VWO when a small paid campaign needs an A/B comparison.
Validation Experiment Card: Six Fields
| Field | What must be specified |
|---|---|
| 1. Hypothesis | ICP, pain, and observable action expected if demand is real |
| 2. Method | smoke test, landing page, pre-sales, or interview |
| 3. Traffic source | paid/organic channel, audience, and cost |
| 4. Success threshold | predeclared signal target, order count, or confirmed pain stories |
| 5. Time limit | hard deadline; no extensions/goalpost shifting |
| 6. Learning/decision | precise implication of positive and negative results |
Completed Clairo Card
- Hypothesis: sales directors on Zoom lose 60+ minutes/week on post-meeting work and will pay ₹999/month for AI-generated follow-up before CRM integration is built.
- Method: landing-page validation with “Your CRM updates itself after every sales call.”
- Traffic: ₹2,000 LinkedIn campaign to sales directors at Indian SaaS firms with 50–500 employees; 5 days, one ad set/creative.
- Success: CTR , sign-up , bounce ; all green.
- Time: 7 days total—5 campaign, 2 analysis.
- Learning: positive → founding-customer outreach; negative → test auto-follow-up proposition before changing other variables or retest a different ICP.
Completed Zoko Card
- Hypothesis: conscious women aged 24–34 in Tier-1 Indian cities, frustrated with chemical skincare, will pay ₹699 for a 21-day Glow Challenge kit before manufacturing.
- Method: founding-member pre-sales offer: ₹699 instead of ₹999 to first 100; Carrd pre-order page and payment link.
- Traffic: ₹1,500 Instagram Story ad to Delhi, Mumbai and Bengaluru plus WhatsApp broadcast to 200 community members.
- Success: 25 paid pre-orders in 7 days.
- Time: seven days from launch; manufacturing decision within 24 hours of analysis, no extension.
- Learning: positive → demand established at ₹699 and test ₹999 next; negative → survey non-buyers to diagnose rejection, proposition, or traffic quality.
Key takeaways
- Validation MVP produces demand learning; functional MVP delivers value after demand is proven.
- Build only after demand, commitment, ICP clarity and constraint clarity are all green.
- Select the experiment from the specific missing signal.
- Constraints are not blockers: nearly every validation route can run below ₹5,000 and within a week.
- Use the six-field experiment card to make hypotheses, thresholds and next decisions auditable.