8. Idea Scoring

Scoring an idea will not tell you the future. It will tell you where your thinking is strong, where it is wishful, and what to test next.

The core idea-scoring question is: which assumptions are strong enough to keep exploring, and which weak scores must be tested before we spend more time, money, or reputation?

The point of a scorecard is not to produce a number that makes you feel confident. The point is to force sharper tradeoffs. If every idea scores high, you are being too generous. If the idea you love scores low, do not hide the result. Use it to decide whether to change the idea, narrow the customer, or stop.

How To Score An Idea

Use a 1 to 5 score for each dimension:

Score	Meaning
1	Mostly guesswork, weak evidence, or obvious risk.
2	Some signal, but still vague or unproven.
3	Plausible, with early evidence and a clear next test.
4	Strong evidence from real customer behavior.
5	Repeated evidence from several customers, plus willingness to act or pay.

Do not score from your opinion alone. Beside each score, write the evidence. A score without evidence is just a mood.

The Startup Idea Scorecard

Dimension	What a high score means
Pain score	The problem is frequent, costly, risky, or emotionally intense.
Urgency score	Customers have a reason to solve it soon, not someday.
Buyer clarity score	You know who uses, pays, approves, blocks, and gets blamed.
Market timing score	Something is changing that makes this a better time to enter.
Reachability score	You can reach the first twenty to fifty prospects without fantasy channels.
Founder fit score	You have domain knowledge, access, distribution, technical edge, or speed.
Revenue potential score	There is a believable path to pricing, repeat revenue, and expansion.
Defensibility score	If it works, something can compound beyond first-mover effort.
Speed-to-test score	You can test the riskiest assumption in days or weeks, not months.

The most important early scores are pain, buyer clarity, reachability, and speed-to-test. A huge market with a vague buyer is still dangerous. A technically exciting idea that takes six months before the first customer signal is expensive. A small but painful wedge with reachable buyers is often a better starting point.

Do Not Hide Behind The Total

Do not simply add the numbers and pick the highest total. Some weak scores are survivable. Some are fatal.

Fatal early weaknesses:

Pain is low.
Buyer is unclear.
Customers are unreachable.
The idea needs massive behavior change before any value appears.
You cannot test the core assumption quickly.
Trust requirements are high and you have no credibility path.

Survivable weaknesses:

The first market is small but expands logically.
Defensibility is unclear before you own the workflow.
Pricing is uncertain but customers already spend on workarounds.
The product is manual at first but can teach you what to automate.
Competition exists, but customers hate the current options.

For example, a services-led idea may score low on scalability but high on pain, buyer clarity, and speed-to-test. That can be a good learning path if you treat the service as discovery, not as the final product. A consumer idea may score high on excitement but low on reachability and monetization. That is a warning to test distribution before product depth.

Weighted Scoring By Stage

The same scorecard should be weighted differently depending on stage.

At idea stage, weight heavily:

Pain.
Buyer clarity.
Reachability.
Speed-to-test.
Founder fit.

At validation stage, weight heavily:

Willingness to act or pay.
Repeat usage.
Channel response.
Delivery feasibility.
Pricing evidence.

At seed-stage company building, weight heavily:

Retention.
Gross margin.
Expansion.
Sales repeatability.
Defensibility.

Do not demand seed-stage proof from a weekend idea. Also do not ignore business quality just because early interviews sound promising.

Red Flags

Red flags do not always mean “stop.” They mean “slow down and test this before you spend months building.”

Red flag	What it usually means	What to test
No clear buyer	The user may not control money.	Ask who approved the last similar purchase.
No urgent pain	The problem is interesting but not important.	Ask what happens if nothing changes for six months.
Users love it, buyers will not pay	Value is real but not owned by budget.	Interview the budget owner separately.
Requires behavior change	Adoption will be harder than product demos suggest.	Test the first habit change manually.
High support, low margin	The business may become custom services.	Track delivery time per customer.
Regulation-first idea without expertise	The risk is not only product; it is compliance and trust.	Speak to practitioners before writing code.
Marketplace with no liquidity plan	Both sides may wait for the other side.	Start with one constrained niche and one side with urgency.
Consumer app with no distribution edge	Product quality alone will not get attention.	Test acquisition before product depth.
AI wrapper with no workflow ownership	The feature may be copied or ignored.	Find the workflow, data, and outcome the AI changes.

In India, add one more red flag: “Everyone says price is the only problem.” Sometimes that is true. Often it means the customer does not trust the value yet. Test whether they will pay for a smaller, concrete outcome instead of a broad promise.

Green Flags

Green flags are signals that customers are already behaving like a market exists.

Green flag	Why it matters
Customers already spend money	Budget exists, even if the current solution is bad.
Manual workaround exists	The pain is real enough that someone built a hack.
Pain appears in job descriptions	Companies are hiring people to solve the problem manually.
Buyers search for solutions	Demand may be reachable through intent-based channels.
Customer asks “when can I use it?”	The conversation moved from idea discussion to action.
Prospect introduces you to others	The problem is credible inside their network.
Budget exists	You can discuss price before product perfection.
Existing tools are hated	Switching may be possible if you reduce risk.
Customer has an urgent deadline	Timing can pull adoption forward.
A small manual version works	You can learn without building the full product.

The strongest green flag is not praise. It is movement: time, access, data, money, introduction, pilot, or workflow change.

Scoring Example

Suppose the idea is a tool for small accounting firms to manage client document collection before GST filing.

Possible scores:

Dimension	Score	Evidence
Pain	4	Three CAs described monthly WhatsApp chaos and missed documents.
Urgency	4	Filing deadlines create recurring pressure.
Buyer clarity	4	Firm owner or partner can approve.
Market timing	3	Digitization is increasing, but habits are still fragmented.
Reachability	4	Founder has access to CA networks in two cities.
Founder fit	3	Understands SMB finance but not CA operations deeply yet.
Revenue potential	3	Small monthly fee possible; need volume or expansion.
Defensibility	2	Workflow may be copied unless data and client network compound.
Speed-to-test	5	Can run manual document collection for five firms next week.

This is not a verdict. It says: test manual delivery, pricing, and retention before worrying too much about defensibility.

India Angle

For Indian startups, score reachability and trust separately. A market can be large but expensive to access. A buyer can have money but prefer vendors introduced through trusted networks. A category can look digital but still close through WhatsApp, phone calls, channel partners, accountants, agencies, doctors, school administrators, brokers, or local operators.

Also score payment behavior honestly. “They can afford it” is weaker than “they already pay Rs X per month for a worse workaround.” In many Indian markets, willingness to pay depends on cash flow timing, perceived risk, and whether the solution feels essential.

For Bharat or regional-language markets, add:

Onboarding difficulty.
Support burden.
Trust channel.
Payment collection method.
Device and connectivity reality.
Local language requirement.

These are not reasons to avoid the market. They are reasons to score reality honestly.

A Simple Scoring Ritual

Score the idea alone.
Add evidence beside every score.
Ask a co-founder, advisor, or operator to score it separately.
Compare only the differences.
Turn the lowest important score into a test.
Re-score after customer evidence, not after more thinking.

If pain is low, run more discovery. If buyer clarity is low, map the buying process. If reachability is low, test outbound or partnerships. If revenue potential is low, discuss price before building. If speed-to-test is low, narrow the wedge until the test becomes smaller.

Evidence-Based Scoring Rules

Use these rules to keep the scorecard honest:

A score of 1 or 2 means you have mostly opinions, not proof.
A score of 3 means you have some segment-specific evidence and know the next test.
A score of 4 means several qualified customers showed behavior, not only interest.
A score of 5 means repeated customer behavior includes payment, access, data sharing, internal introductions, workflow change, or urgent follow-up.
Never give a 4 or 5 without writing the evidence beside it.
Do not let one enthusiastic customer carry the entire score.
Do not average mixed segments together.

If two founders score the same idea differently, treat the disagreement as useful. The gap usually reveals hidden assumptions.

Minimum Evidence Thresholds

Before you commit real build time, set a threshold for the kind of evidence required. Different decisions need different proof.

Decision	Minimum evidence before deciding
Spend one weekend exploring	One clear customer segment, one painful story, and one reachable interview source.
Spend 2-4 weeks validating	10-15 qualified conversations, repeated problem language, and a named buyer or budget path.
Build an MVP	Strong workflow understanding, at least one behavior signal, and a narrow success metric.
Quit a job or go full-time	Personal runway plan, repeated customer pull, and a clear 60-90 day validation target.
Hire or raise money	Evidence that the problem, buyer, channel, and next milestone justify the added obligation.

This protects founders from overcommitting too early. A promising idea deserves testing. It does not automatically deserve payroll, a large build, or investor promises.

Behavior Signals Ranked

When scoring, rank customer behavior from weak to strong:

Signal	Strength	What it really means
Compliment	Weak	The person is being polite or conceptually interested.
Complaint	Weak to medium	The pain exists, but may not be urgent or paid.
Specific story	Medium	The customer has lived the problem recently.
Workaround	Stronger	The pain is costly enough to create action.
Internal introduction	Stronger	The problem may matter beyond one person.
Data or workflow access	Strong	The customer is investing trust and time.
Paid pilot or deposit	Very strong	The buyer is taking commercial risk.
Repeat usage or renewal	Strongest	The solution is becoming part of work.

Do not treat all “positive feedback” equally. A founder can collect 50 compliments and still have no startup. Ten specific customer stories plus three workflow-access commitments are usually more valuable.

Segment Split Scoring

If the same idea has mixed feedback, split the segment before you average the score. Averages hide truth.

Example:

Segment	Pain	Buyer clarity	Reachability	Notes
Solo consultants	3	4	5	Easy to reach, but lower willingness to pay.
20-100 person agencies	4	4	3	Stronger pain, founder network needed.
Large enterprises	5	2	1	Pain is high, but access and procurement are hard.

This changes the decision. The large-enterprise segment may look attractive on pain, but it may be a poor first wedge. The agency segment may be the better starting point because pain and access are both workable.

For Indian markets, segment by operating reality, not only industry:

Owner-led vs professionally managed.
Tier-1 vs tier-2/3 city.
Digital-native vs WhatsApp/spreadsheet-led.
Cash-flow-constrained vs budgeted.
Regulated vs informal.
English-first vs regional-language-first.

One “SMB” score is usually fake. The best ideas become clearer when the segment becomes uncomfortable specific.

Weighted Idea Scorecard

For the earliest stage, use weights. Some dimensions matter more before you build.

Dimension	Weight	Why
Pain	20%	Weak pain makes everything harder.
Buyer clarity	15%	No buyer means no revenue path.
Reachability	15%	You need access before you need scale.
Speed-to-test	15%	Fast learning preserves time and cash.
Founder fit	10%	Advantage compounds through learning.
Revenue potential	10%	Pain must become a viable business.
Urgency	10%	Urgency turns interest into action.
Defensibility	5%	Often unclear early, but worth noting.

This weighting deliberately favors near-term learning. A venture-scale idea with low reachability and slow testing may still be interesting, but it is expensive. A narrow idea with sharp pain and easy access may be a better starting wedge.

Score Interpretation Patterns

The shape of the score matters more than the total.

Pattern	What it means	Founder move
High pain, low buyer clarity	Users hurt, but revenue path is unclear.	Map buyer, approver, blocker, and budget owner.
High pain, low reachability	The problem may be real but inaccessible.	Find a channel, partner, community, or narrower segment.
High reachability, low pain	You can contact people, but they may not care.	Change problem or ask about current workarounds.
High founder fit, low market timing	You know the market, but now may not be urgent.	Look for a trigger: regulation, platform shift, cost pressure, growth.
High excitement, low speed-to-test	The idea may be too broad or technical-first.	Shrink the wedge until a 7-day test exists.
High revenue potential, low trust	Buyer may pay, but credibility is missing.	Start with proof, reference, service layer, or lower-risk workflow.

This prevents a common founder error: using one strong dimension to hide a weak one. A huge market does not fix weak reachability. Founder passion does not fix buyer confusion. A strong technical demo does not fix low urgency.

Scorecard Review Questions

After scoring, ask these questions before choosing a next step:

Which score is based mostly on guesswork?
Which score would change the decision if it dropped by two points?
Which score can be improved with one week of customer work?
Which score depends on a segment that is too broad?
Which score is inflated by founder excitement?
Which score is hiding an India-specific risk such as trust, payment, support, language, procurement, or channel?

The next test should attack the weakest important score, not the easiest score to improve.

Turn Low Scores Into Tests

Every weak score should become an experiment.

Weak score	Test
Pain	Interview five people about the last real occurrence and current workaround.
Urgency	Ask what happens if nothing changes for six months and whether a deadline exists.
Buyer clarity	Speak separately to the user, budget owner, and blocker.
Reachability	Build a list of 50 prospects and send 20 specific outreach messages.
Founder fit	Ask an industry operator to review your assumptions and introspect your access.
Revenue potential	Ask about current spend, approval thresholds, and paid pilot conditions.
Defensibility	Map what could compound: data, workflow, distribution, brand, network, integrations.
Speed-to-test	Narrow the customer or promise until a 7-day test is possible.

Scoring is useful only if it changes what you do next.

Portfolio View For Founders With Many Ideas

If you have too many ideas, put them into three buckets:

Bucket	Meaning	Action
Active	Strong enough to test now.	Run a focused sprint.
Parked	Interesting but missing access, timing, or evidence.	Keep notes; revisit monthly.
Killed	Repeated evidence shows weak pain, buyer, access, or fit.	Archive the learning and move on.

Most founders keep too many ideas in the active bucket. That feels open-minded, but it weakens execution. A good active bucket usually has one primary idea and at most one backup experiment.

Scoring Calibration Workshop

Scorecards are useful only when founders score evidence consistently. Before using scores to choose an idea, calibrate the team.

Use one idea and ask each founder to score privately:

Dimension	Founder A	Founder B	Founder C	Evidence gap
Pain
Urgency
Buyer clarity
Market timing
Reachability
Founder fit
Revenue potential
Defensibility
Speed-to-test

Then discuss only the dimensions where scores differ by two or more points. Do not debate taste. Ask, “What evidence are you using?”

Common calibration problems:

One founder scores market size; another scores entry wedge.
One founder scores technology excitement; another scores customer pain.
One founder has customer context the others have not heard.
One founder is optimistic because they want to build.
One founder is pessimistic because they dislike selling into the segment.

The scorecard should surface these differences early, before they become co-founder conflict.

Evidence Tags

Beside every score, add one tag:

Tag	Meaning
`Guess`	We believe this but have no direct evidence.
`Story`	A customer described the problem.
`Behavior`	A customer showed a workaround, spent time, or took action.
`Buyer`	We spoke to someone with budget or authority.
`Paid`	Someone paid, signed, deposited, or agreed to commercial terms.

Do not compare a Guess 5 with a Paid 4 as if they are equal. A lower score with stronger evidence may be safer than a high score built on imagination.

Re-Scoring Cadence

Re-score ideas only after new evidence:

5 qualified interviews.
A channel test.
A pricing conversation.
A paid or manual pilot.
A competitor/customer review mining session.
A buyer map conversation.

Do not re-score because the team had a more exciting brainstorming session. Scores should move when reality moves.

Weighted Scorecard

Not every dimension deserves equal weight at every stage. Early founders often overweight market size and underweight reachability. That creates impressive ideas that cannot get first customers.

Use different weights by stage:

Dimension	Pre-idea	Validation	First customers
Pain	20%	20%	15%
Urgency	15%	20%	20%
Buyer clarity	10%	15%	20%
Reachability	20%	15%	15%
Founder fit	20%	10%	10%
Revenue potential	5%	10%	10%
Defensibility	5%	5%	5%
Speed-to-test	5%	5%	5%

At the pre-idea stage, reachability and founder fit matter a lot because you need to learn quickly. At validation, urgency and buyer clarity matter more. At first customers, buyer clarity becomes central because revenue requires authority, process, and trust.

Do not let a huge market hide weak access. A small reachable wedge beats a large abstract market in the first month.

Score Interpretation

After scoring, interpret the pattern instead of only the total.

Pattern	Interpretation	Next move
High pain, low buyer clarity	Users hurt, but payment path is unclear.	Run buyer discovery.
High market, low reachability	Attractive category, weak entry.	Test channels before product.
High founder fit, low urgency	You understand the domain, but timing may be weak.	Look for triggers or adjacent pain.
High urgency, low trust	Customer needs help, but may not trust a startup.	Start with service, proof, or lower-risk workflow.
High score, mostly guesses	Excitement without evidence.	Run interviews before choosing.
Medium score, strong paid evidence	Less glamorous but real.	Consider focusing here.

The best scorecard does not choose for you. It tells you what conversation to have next.

The Red Team Round

Before committing to an idea, run a red team round. One founder or advisor argues against the idea using evidence, not cynicism.

Ask:

Why might this problem be less urgent than we think?
Who benefits from the current messy process?
Why have existing tools not solved it?
What will make customers delay purchase?
What trust proof will be required?
What makes distribution harder than it looks?
What would make this a services business instead of a product company?
Which assumption, if false, kills the idea?

Then write the top three objections and the test for each.

Objection	Why it matters	Evidence needed	Test

This protects the team from scoring optimism. A good idea should survive skeptical inspection, or become sharper because of it.

Score-To-Sprint Conversion

Do not leave the scorecard as a document. Convert it into a sprint.

Weakest score	Sprint design
Pain	Interview 10 qualified customers about recent incidents.
Urgency	Identify triggers, deadlines, penalties, and moments of action.
Buyer clarity	Speak to budget owners and map approval paths.
Reachability	Test 3 channels with 30 targeted outreaches each.
Founder fit	Spend time in the workflow, shadow operators, or bring in an insider.
Revenue potential	Ask pricing, current spend, and willingness for a paid pilot.
Defensibility	Study switching costs, data loops, workflow depth, and expansion paths.
Speed-to-test	Narrow the promise until a seven-day test is possible.

Every scoring session should end with calendar blocks. If the scorecard does not change the next week of work, it is theatre.

India Reality Adjustment

For Indian founders, a raw idea score can be misleading unless you adjust for trust, distribution, collection, and service intensity. A problem can score high on pain and still become a hard business because the customer is difficult to reach, hard to onboard, slow to pay, or dependent on local service.

Add these adjustment questions after the normal score:

Adjustment	Strong signal	Weak signal
Trust path	Customer can trust you through domain proof, references, brand, compliance, data handling, or visible ROI.	Customer must trust an unknown startup with sensitive work immediately.
Payment path	Buyer has a known budget, current spend, clear approval, or owner-led decision.	Everyone likes it but nobody knows who pays.
Collection path	Payment can be collected reliably through subscription, prepaid, invoice, wallet, channel, or contract.	Collections require repeated chasing and custom negotiation.
Onboarding burden	Customer can start with a narrow artifact, one workflow, or a guided setup.	Every customer needs heavy migration, training, or process redesign.
Support burden	Support load decreases with product maturity.	The business stays dependent on manual support forever.
Distribution fit	You can reach buyers through a channel you understand.	The only plan is “performance marketing” or “go viral.”
Language/context fit	Product matches the customer’s language, device, workflow, and skill level.	Product assumes behavior copied from a different market.

Use the adjustment like a penalty, not a separate brainstorm. If an idea scores 8/10 but has no trust path, no buyer path, and high support burden, treat it as a 5 until proven otherwise.

Score By Segment, Not By Market

Do not score “AI for accounting.” Score:

Two-partner CA firms serving 100-300 SMB clients.
D2C brands with monthly GST reconciliation issues.
Multi-outlet restaurants handling aggregator payouts.
Exporters managing invoice, shipping, and compliance documents.
Funded startups with finance teams but messy internal approval flows.

The same idea can be excellent for one segment and weak for another. Segment-level scoring prevents the founder from killing a good wedge because the broad category looks messy, or pursuing a broad category because one small segment looked excited.

The Minimum Score To Continue

A simple rule:

Continue only if pain, buyer clarity, and reachability are all at least acceptable.
Narrow if pain is strong but buyer or reachability is weak.
Pause if founder advantage is weak and the market requires trust.
Stop if the only high score is market size.

Market size is an amplifier. It should not be the foundation. A huge market with no wedge is just a large place to get lost.

Founder Portfolio View

When founders have many ideas, they often compare them as if all ideas deserve equal emotional attention. They do not. Treat ideas like a portfolio and decide which ones deserve testing, parking, or killing.

Bucket	Meaning	Founder action
Active test	Strong enough to spend this week on evidence	Calendar customer calls, channel tests, or paid/manual proof
Watchlist	Interesting but missing access, timing, or founder fit	Save notes, revisit after new evidence or network access
Partner idea	Strong problem but weak personal advantage	Look for co-founder, advisor, operator, or acquisition angle
Services first	Problem is real but product path is unclear	Test paid service or audit with strict productization notes
Kill	Mostly market size, trend, or founder curiosity	Archive and stop consuming attention

Use this table after every scoring session:

Idea	Current bucket	Evidence needed to move up	Kill condition	Next review
	Active / watchlist / partner / services / kill

This protects the founder from carrying twenty half-alive ideas. Unmade decisions have a cost. They dilute sales calls, product energy, hiring narrative, and fundraising story.

Evidence Grading

Give every idea an evidence grade. The score says how attractive the idea looks. The grade says how much reality has touched it.

Grade	Evidence level	Example
D	Founder opinion	”I think this is painful.”
C	Customer stories	10 target users describe the pain with recent examples.
B	Behavior	Customers share workflow artifacts, introduce colleagues, or change process.
A	Commercial intent	Buyer discusses budget, paid pilot, contract, procurement, or deposit.
A+	Repeatable proof	Multiple similar customers pay, use, return, or expand.

Do not let a D-grade idea with a high score beat a B-grade idea with a medium score. The job of early startup work is not to protect exciting ideas. It is to upgrade evidence.

Upgrade Path

Move one grade at a time:

Current grade	Upgrade test
D to C	Talk to 10 people in one narrow segment.
C to B	Ask for artifacts, workflow walkthroughs, referrals, or implementation effort.
B to A	Ask for paid pilot, deposit, invoice, procurement step, or budget-owner meeting.
A to A+	Repeat the commercial proof with similar customers without heroic founder effort.

If an idea cannot move from D to C quickly, the founder may not have enough access. If it cannot move from B to A, the pain may not be commercial. If it cannot move from A to A+, the business may depend on one-off trust, custom work, or a narrow opportunity.

Opportunity Cost Check

Before choosing an idea, ask what it will prevent you from doing.

Cost	Question
Time	Will this consume the next 6 to 18 months of founder attention?
Reputation	Will this position you with a customer segment you want to serve for years?
Hiring	Can you attract the people this idea needs?
Capital	Does the idea need money before proof, and can you access that money?
Family/personal	Does the required travel, stress, uncertainty, or cash risk fit your life?
Strategic	Does this idea build an advantage even if the first version changes?

Some ideas are attractive but wrong for the founder’s life, network, or ambition. That is not weakness. It is strategy.

Score Drift Review

Scores should change as evidence changes. If your scorecard never moves, you are probably using it to justify a decision you already made.

Run a score drift review every week during idea search:

Review question	What to look for
Which score changed?	Pain, buyer clarity, reachability, urgency, distribution, founder advantage, willingness to pay.
What evidence caused the change?	Call note, artifact, pilot response, referral, data access, quote, budget conversation, rejection.
Did the score change because of evidence or mood?	A good call can inflate the idea. A bad call can deflate it too much.
Is the score changing for the segment or only one person?	One sharp customer can teach you, but should not define the whole market.
Which low score is still being ignored?	Founders often avoid the weakest part of the idea.
What test would change the score next week?	A score without a next test is just commentary.

Keep a simple log:

Date	Score before	New evidence	Score after	Decision
Week 1	Buyer clarity 2/5	Five users liked it, but none owned budget.	2/5	Find budget owner.
Week 2	Buyer clarity 2/5	Two founders said ops head can recommend but founder approves.	3/5	Interview founders.
Week 3	Willingness to pay 2/5	One paid manual audit, one refused price, one asked for ROI proof.	3/5	Run paid pilot with narrow promise.

This prevents a common founder error: treating old excitement as current evidence. Your scorecard should age. If the idea is real, new evidence will make it sharper. If the idea is weak, new evidence will expose where it is weak.

Score-To-Decision Rule

The scorecard is not the decision. It is an input into the next move.

Use this conversion:

Score pattern	Evidence grade	Decision
High score, low evidence	Attractive hypothesis.	Do not build yet. Upgrade evidence first.
Medium score, fast evidence improvement	Promising wedge.	Keep testing and narrow the segment.
Medium score, no evidence movement	Stalled idea.	Change source, segment, or kill/park.
Low score, strong founder access	Possible hidden opportunity.	Run one tight sprint before rejecting.
High pain, unclear buyer	Discovery needed.	Map budget owner and approval path.
Clear buyer, low urgency	Nice-to-have risk.	Test trigger, deadline, and ROI.
Strong score from one customer	Custom project risk.	Find three similar customers before building.
Strong score across five customers	Real signal.	Move toward prototype, concierge test, or paid pilot.

Set hard rules before you start:

No idea moves to build mode until at least one customer has made a costly commitment.
No idea gets killed after one bad call unless the call reveals a fatal assumption.
No idea stays active for more than two weeks without a specific risk being tested.
No idea wins because the total score looks good while one fatal score is weak.
No idea gets compared across segments without segment-specific scoring.

For Indian founders, this discipline matters because many markets contain real pain but messy payment behavior. A high pain score does not automatically mean software revenue. The decision rule forces you to ask: who pays, why now, through which channel, and with what proof?

Idea Scorecard Decision Meeting

A scorecard is useful only if it changes what the founder does next. Many teams score an idea, feel temporarily clear, and then continue exactly as before. Treat the scorecard as a decision meeting, not a document.

Run this meeting when:

you are choosing between multiple ideas
you have finished a discovery sprint
a co-founder wants to start building
an investor, advisor, or customer has made the idea feel more exciting than the evidence supports
you are about to spend money on product, hiring, content, or paid acquisition

The goal is not to prove that the idea is brilliant. The goal is to decide whether the next seven days deserve founder attention.

Pre-Work

Before the meeting, prepare one page:

the exact customer segment being scored
the latest scorecard
the top five evidence notes
the weakest assumption
the strongest customer quote or behavior
the next test you would run if the idea survives
the condition under which you will kill or park the idea

Do not bring a market-size deck. Do not bring product mockups unless customers have already reacted to them. Bring evidence.

Decision Agenda

Step	Question	Output
Segment lock	Which exact customer are we scoring?	One segment, not “SMBs” or “founders”
Evidence review	What did customers actually do or say?	Evidence notes, tagged as weak, medium, or strong
Fatal score check	Is any dimension too weak to ignore?	List of blockers
India reality check	What will be harder in India than in a spreadsheet?	Trust, payment, support, channel, or compliance risks
Decision	Continue, narrow, park, kill, services-first, or partner-needed?	One written decision
Next test	What is the smallest test that can change our mind?	Owner, deadline, and kill condition

Keep the meeting under 45 minutes. If it takes longer, the team is usually debating taste instead of evidence.

Decision Options

Decision	Use When	Next Action
Continue	Pain, urgency, reachability, and founder fit are all credible.	Run the next validation sprint.
Narrow	One segment scores much better than the broad market.	Rewrite the idea for that segment only.
Park	The idea is interesting, but timing, access, or conviction is weak.	Store the memo and review later.
Kill	The pain is weak, the buyer is unclear, or evidence is mostly polite feedback.	Stop active work.
Services-first	Customers have pain, but product risk is high.	Solve manually for 3 to 5 customers before building.
Partner-needed	Demand exists, but distribution or compliance access is missing.	Find a channel, domain, or implementation partner before product work.

The most useful decision is often “narrow.” A broad idea such as “AI for finance teams” may be average. “AI reconciliation assistant for D2C brands doing marketplace payouts across Amazon, Flipkart, Shopify, Razorpay, and cash-on-delivery returns” may be worth testing.

India-Specific Checks

Before saying yes to an idea in India, ask:

Trust path: Why would this customer trust a new company with this problem?
Payment path: Will they pay upfront, monthly, annually, usage-based, or after results?
Collection path: Who follows up when invoices are delayed?
Support burden: Will adoption require founder-led onboarding, WhatsApp support, training, or on-site work?
Channel access: Can you reach buyers directly, or will you need accountants, agencies, consultants, system integrators, banks, communities, or marketplaces?
Compliance drag: Does GST, data residency, sector regulation, procurement, or vendor approval slow the sales cycle?

None of these automatically kill an idea. They make the operating model visible. A good idea with a hidden support or collections burden can become a bad startup.

Decision Memo

End the meeting with a short memo. This memo is more valuable than a beautiful pitch deck because it records how the team thinks.

Field	Answer
Idea	What are we testing?
Segment	Who exactly has the problem?
Current decision	Continue, narrow, park, kill, services-first, or partner-needed
Score shape	Which dimensions are strong and weak?
Evidence grade	What proof do we have?
Weakest assumption	What could make this idea collapse?
Next seven-day test	What will we do next?
Owner	Who is responsible?
Kill condition	What result will make us stop?
Review date	When will we decide again?