The Idea Validation Scorecard: A Checklist for Solopreneurs

Print this. Bookmark this. Run every idea through it.

If your idea cannot clear this checklist, building it is a bet, not a decision. The checklist takes 20 minutes. Skipping it costs months.

This is the Idea Validation Scorecard — five categories, 15 checkpoints, and a scoring model that gives you a go, wait, or kill recommendation based on evidence rather than enthusiasm.

How the Scorecard Works

The Idea Validation Scorecard runs your idea through five categories: problem clarity, market demand, competitive landscape, willingness to pay, and founder-market fit.

Each category contains three checkpoints. Each checkpoint is worth one point. You score it only if you can honestly confirm it — not if it sounds plausible, not if your gut says yes.

Total possible score: 15.

A high score does not mean the idea will succeed. It means you have gathered enough evidence to start testing — which is different from building.

For the full explanation behind each criterion, read the complete idea evaluation guide.

Does the Problem You Are Solving Actually Exist?

Problem validation answers one question: is this a real frustration that real people experience in their actual lives, or is it a problem you invented because you would find the product interesting? In CB Insights’ post-mortem analysis of failed startups, “no market need” ranked as the leading cause of failure — cited by founders who admitted they assumed demand existed and never checked. Almost none of them ran a problem validation step before building.

Score one point for each checkpoint you can confirm with actual evidence.

Checkpoint 1: You can name the specific person who has this problem.

Not a demographic segment. A person. “Freelance UX designers who work with two to four clients simultaneously and lose billable hours switching between invoicing tools” is a person. “People who want to be more organized” is not.

If you cannot name this person with that level of specificity, you are solving a hypothetical problem. Hypothetical problems produce hypothetical demand.

Checkpoint 2: You have heard this person describe the problem in their own words.

Not inferred. Not assumed. Heard. This means you have read their Reddit posts, their Indie Hackers threads, their replies to Twitter polls about the thing you want to fix — or you have spoken with them directly.

Their exact language is evidence. Imagining what they must feel is not.

Checkpoint 3: The problem is active, not aspirational.

An active problem is one they are dealing with right now — costing them time, money, or stress this week. An aspirational problem is something they would like to improve eventually, when they get around to it.

Active problems get solved. Aspirational problems get bookmarked.

Category score: __ / 3

Are People Already Looking for a Solution?

Market demand exists when people are actively seeking what you plan to build — not when they agree the problem is real. Acknowledgment is passive and does not predict purchase behavior. The demand signals that matter are keyword search volume, competitor product reviews, community discussions about unmet needs, and evidence of spending on imperfect substitutes.

Checkpoint 1: You have found search volume for the problem, not just the product category.

Search the words people use when they are frustrated, not the product label you have invented. “How to stop losing track of freelance invoices” carries more intent signal than “AI invoice management for freelancers.” If you find no search volume for the problem as people actually describe it, the market may not know it needs a solution.

Free tools that give you directional signal: Google Search autocomplete, Ahrefs Free, Ubersuggest, AnswerThePublic.

Checkpoint 2: You have found at least one community where people complain about this problem without being prompted.

Reddit threads. Facebook groups. Slack communities. Indie Hackers. The test is unprompted — people talking about the problem in their own space, not in response to your survey. If you can find three separate threads where different people describe the same problem in similar language, that is a demand signal worth noting.

Checkpoint 3: People are already paying for an imperfect solution.

This is the strongest demand signal of the three. If your target customer is currently paying for a spreadsheet template, a generalist tool that sort of works, or a freelancer to do something manually — they have already demonstrated willingness to spend on this problem. You are not creating demand. You are taking it.

Category score: __ / 3

Still not sure whether your idea is worth pursuing? The Should I Build This decision framework runs five demand signals and three killer questions in one structured pass. Takes 15 minutes. No signup required.

Does the Competitive Landscape Leave Room for You?

A competitive market is not a red flag — it is evidence that demand exists. The real risk is not too much competition but entering a crowded market with no clear reason to choose you over what already exists. The checkpoint here is not “is there competition?” It is “is there a specific gap or underserved segment that existing players are ignoring?”

Checkpoint 1: You can name at least three existing alternatives.

If you cannot find three, search harder. Customers always have alternatives: paid products, free tools, manual workarounds, or doing nothing. List all of them. If you genuinely cannot find three, the market may be underdeveloped — which is a separate risk you need to understand before building.

Checkpoint 2: You have found a specific complaint that existing alternatives share.

Go to G2, Capterra, or the relevant subreddit. Read the one-star and two-star reviews of the category leaders. If the same complaints surface repeatedly — “too complex for small teams,” “pricing is built for agencies,” “support disappears after the sale” — that is the gap. Your product should close that gap, not replicate what already exists.

Checkpoint 3: Your differentiation is specific, not a claim about quality or price.

“Better UX” is not differentiation. “Cheaper” is not differentiation unless you have a structural cost advantage you can sustain. Specific differentiation sounds like: “built only for freelancers who bill hourly, not project-based agencies” or “the only tool that integrates with Notion and does not require a separate dashboard.” Someone in your target segment should immediately understand why this is different from what they already use.

Category score: __ / 3

Would the Right Person Actually Pay for This?

Willingness to pay is not the same as interest. Someone can love your idea, share your landing page, and join your waitlist — and never open their wallet. The gap between interest and payment is where most solo product launches fail. Rob Fitzpatrick describes this in The Mom Test: polite enthusiasm is cheap, and “that sounds great” tells you nothing about actual buying behavior.

Checkpoint 1: You have found evidence of spending in this category.

This does not need to be evidence about your specific product. It needs to be evidence about the category. If people are paying for adjacent products, that validates category willingness to pay. If your only evidence is friends saying it sounds interesting, you have social support — not market evidence.

Checkpoint 2: You can name a price point without hedging.

Pick a number. Not a range. Not “it depends on the tier.” A real number you would quote to someone right now without apologizing for it. If you hesitate — if your instinct is to set the price lower than you think it is worth — that is worth investigating. Underpricing is often a confidence problem disguised as a positioning problem. If you cannot name a price, you have not thought through the value clearly enough.

Checkpoint 3: Someone has asked “when can I buy this?” or attempted to pay.

This is the hardest checkpoint and the most valuable one. An email waitlist with 200 signups tells you less than one person handing over $50 for early access. Pre-selling forces you to ask; an actual purchase attempt is unambiguous. If you have not run any version of a pre-sell or a direct “would you pay for this” conversation with a real payment option, score this checkpoint zero.

For the full methodology on testing willingness to pay without building anything, the Mom Test summary covers the specific question framing that separates genuine buying intent from supportive agreement. Rob Fitzpatrick’s original framework is documented at momtestbook.com for those who want the source material.

Category score: __ / 3

Do You Have the Right Fit to Build and Sell This Idea?

Founder-market fit is not about passion for the problem. It is about whether you have the access, credibility, or skills to build and sell this product to this audience in a realistic timeframe. Founders with deep domain expertise in their target market tend to make better product decisions earlier — they know what the buyer actually cares about before writing a line of code, which shortens the gap between first build and first revenue.

Checkpoint 1: You have direct access to your target customer.

Not through cold outreach. Through existing relationships, community membership, or professional context. If you have to build an audience before you can talk to anyone who might buy, your time-to-first-customer just got significantly longer. That is not disqualifying, but it needs to be factored into your plan and your runway calculation.

Checkpoint 2: You have domain credibility or technical capability in this space.

Domain credibility means you have worked in the industry, built something adjacent, or have a professional background your target customer would recognize. Technical capability means you can build a functional version without hiring. You do not need both — but you need one. If you have neither, your first step is not building the product. It is going to earn one of those credentials.

Checkpoint 3: Your estimated time to first revenue is six months or less.

Not time to product completion. Time to revenue. If you have to ship twelve months of product before you can charge anyone, your personal runway becomes a hard constraint. Shorter paths exist for almost every idea: pre-selling, a service version of the product, a done-for-you implementation. If none of those are available to you, understand specifically why before committing.

The Value Proposition Canvas evaluation is a useful complement here — it surfaces the jobs-to-be-done that your target customer cares most about, which directly informs whether your fit is strong enough to execute.

Category score: __ / 3

How Do You Interpret Your Total Score?

Add up your five category scores.

12–15 (Go): You have enough evidence to move to a demand test. Put up a landing page, run a pre-sell, or set up a waitlist with a concrete offer. The next step is an MVP demand test — not building the full product.

8–11 (Wait and investigate): Look at which categories you scored one or zero in. Those are not random weaknesses. They are the specific assumptions your idea rests on that you have not tested. Set a two-week research deadline for each gap. Re-score when you have answers. If the score does not move, the assumption may be untestable — which is a signal worth taking seriously.

5–7 (Reshape): The idea has at least one foundational problem. This does not mean the general space is wrong — it may mean your specific take on it is. Use your lowest scores to challenge the core premise. Who else might have this problem? What would the solution look like if it targeted a narrower segment? What version of this idea could you build in six weeks instead of six months?

0–4 (Kill): This version of the idea has too many unknowns to invest in. Kill it. That is not failure — that is what the scorecard is for. Bring your next idea through the same process.

Frequently Asked Questions

What is an idea validation checklist for solopreneurs?

An idea validation checklist is a structured tool that evaluates a business idea across five categories — problem clarity, market demand, competitive landscape, willingness to pay, and founder-market fit — before you commit to building it. Each category contains concrete checkpoints that require real evidence rather than intuition, producing a score that recommends go, wait, or kill.

How long does it take to complete the idea validation scorecard?

The scoring itself takes about 20 minutes if you have already done basic research. If you have not yet investigated demand signals, competitive alternatives, or willingness to pay, budget one to two hours to gather the evidence first. Running the scorecard without evidence defeats the purpose — the checkpoints require real observations, not informed guesses.

Can I use this scorecard to compare two or more ideas?

Yes, and this is one of the most valuable uses. Run each idea through all five categories independently and compare both the total scores and the pattern of scores. Two ideas can produce the same total for very different reasons — one might score high on demand but low on founder fit, while the other reverses that. The pattern tells you as much as the number.

What should I do if my idea scores below 8?

Treat the score as a diagnostic. Look at which specific checkpoints you scored zero on — those are the assumptions your idea is resting on that you have not verified. Ask: can I reshape the idea so those assumptions no longer apply? Can I research those gaps in the next two weeks? If you cannot find a version of the idea that scores well after honest investigation, move on. The next idea benefits from the same process.

Is this checklist the same as the lean canvas?

No. The lean canvas (developed by Ash Maurya, available at leanstack.com) is a business model document that maps your value proposition, customer segments, revenue streams, and cost structure. The Idea Validation Scorecard evaluates whether the core problem-solution premise is worth pursuing before you design a business model. Use this scorecard first. If the idea clears the gate, fill out the lean canvas as your next step.

Take the Idea Evaluation Further

This scorecard gives you a snapshot. It tells you whether you have enough evidence to proceed — but it does not tell you how to gather that evidence if you scored low, or how to run a demand test once you score high.

The next two reads:

How Much Validation Is Enough? — The three evidence levels that tell you when to stop researching and start testing.

MVP for Solopreneurs — The minimum thing you need to put in front of real buyers before writing a line of code.

Keep Reading

• How to Evaluate a Business Idea (The Complete Framework)
• Should I Build This? A Decision Framework for Solopreneurs
• How Much Validation Is Enough?