Should I Build This? A Decision Framework for Solopreneurs

You have an idea. You are already naming it in your head.

Stop for a moment.

Before you open a design tool, register a domain, or sketch a single feature — answer this: is there actual evidence that this is worth building?

Not excitement. Not encouragement from people who care about you. Evidence.

This framework gives you a structured way to find out. You can run it in a few hours. No code, no ads, no landing page.

Most product failures do not happen at launch. They happen in the weeks before the first line of code is written — when the founder assumed there was a market without checking, when they confused enthusiasm for demand, when they asked the wrong people the wrong questions and got encouraging answers that meant nothing.

The “should I build this?” question is the one most solopreneurs rush past. The evaluation step feels slow and uncomfortable. The building step feels productive. So they build.

This framework has five demand signals to check, three questions that cut bad ideas quickly, a 48-hour pre-build test you can run with a browser and a notebook, and a decision model that gives you a clear go, wait, or kill answer.

What it does not do: it does not promise certainty. No framework does. What it does give you is a structured way to reduce the likelihood of building something the market never asked for.

That is worth a few hours of your time before you spend six months building.

What “Worth Building” Actually Means

The question is not “is this a good idea?” Good ideas fail all the time. The real question is whether this specific idea, in this specific market, with your specific resources and position, has enough real demand to justify the investment you are about to make.

Worth building means three things are true simultaneously:

1. Enough people have the problem and are actively searching for a solution
2. At least some of those people will pay money for a solution rather than cobble together a workaround
3. You can reach those people and deliver something good enough to compete with what already exists

An idea can be genuinely clever and still not be worth building — for you, right now. The framework below evaluates both dimensions: whether the market is real and whether your position in it is viable.

This is a different question from the full 10-point evaluation covered in the idea evaluation scorecard. That framework is for deep evaluation once you have decided an idea is worth investigating further. This framework is the earlier filter — the first pass that decides whether an idea deserves deeper investigation at all.

The Five Demand Signals That Tell You If an Idea Has Legs

These five signals are your first filter. They require research, not guessing. For each signal, note whether the evidence you find is strong, weak, or absent.

Signal 1: Search demand exists

People who have a problem they want to solve search for it. Run searches using the language your potential customer would use — not the language you use as a product builder. Look for forums, Reddit threads, YouTube videos, and blog posts discussing the problem in detail. If people are writing about the problem repeatedly in public, they are telling you the problem exists and matters to them.

You are not looking for exact keyword volumes at this stage. You are looking for evidence that the problem is discussed publicly and repeatedly.

Signal 2: People are already paying for partial solutions

Search for products that address this problem, even imperfectly. If people are paying monthly subscription fees or one-time purchase prices for a tool that only partially solves the problem, that is strong evidence of willingness to pay. If there are no paid products in the space at all, that is not evidence of opportunity — it is often evidence that the market is not large enough or not willing to pay for a solution.

Signal 3: Active communities exist around the problem

Reddit communities, Discord servers, Facebook groups, Slack groups, and forums built around a specific problem are evidence that the problem is real and recurring. Check the activity level: communities with daily posts and strong engagement are a stronger signal than passive communities with a few posts per week and low participation.

Signal 4: Negative reviews of existing products name the gap

Go to the reviews of the closest existing products. Sort by critical reviews. If the critical reviews consistently describe the same gap — something the product does not do, something it does badly, something users wish existed — that gap is where your product could live. This is a stronger demand signal than general market research because it comes from people who already proved willingness to pay by purchasing.

Signal 5: People have built workarounds

When people are solving a problem with spreadsheets, manual processes, or stitched-together tools, they have already proven that the problem is worth solving. They are investing time and effort. They are waiting for something better. Finding evidence of workarounds — in forum posts, job listings, or community discussions — is one of the clearest demand signals available.

Reading Your Signal Score

If three or more signals are present and strong, the idea has enough market evidence to investigate further. If fewer than three are present, or the signals you find are weak, you need to understand why before committing.

Download the Idea Validation Scorecard — evaluate your idea in 20 minutes, free

The Three Killer Questions That Cut Bad Ideas Fast

These questions surface problems that will sink a product regardless of how good the idea looks on paper.

Question 1: Are you solving the problem for a person who has it today, or for a version of yourself who had it years ago?

This is the most common pattern in failed solo products. A developer builds a tool she wished she had three years ago, not a tool people are currently struggling to find. A coach designs a program based on the transformation he went through, not the transformation his clients are currently seeking. The product is real. The market is the founder’s past self. The customers do not exist at scale.

Before you build, verify that the person who has this problem today is searchable, findable, and reachable. Can you name five places where they gather online? Can you describe what they complained about this week?

Question 2: Is this a one-time purchase or a recurring need?

A one-time purchase product requires a constant flow of new customers. A product addressing a recurring need can retain customers and build compounding revenue. For solopreneurs with limited time and marketing resources, recurring need problems are generally more forgiving — you spend less time on acquisition and more time on improvement.

Neither answer disqualifies the idea. But the answer changes what it takes to make the product financially sustainable, and you need to know that before you build.

Question 3: What will people do if this product does not exist?

If the answer is “they will keep using a specific workaround that costs them time and money,” that is a good sign. There is already a behavior you can replace. If the answer is “they will do nothing — they will live without it without any real cost,” that is a harder market. It means you need to not just compete but create demand. Creating demand from scratch is a much longer and more expensive process than capturing demand that already exists.

The three killer questions do not score your idea on a scale. They produce binary flags. One clear “no” in response to any of them is a signal to investigate further before committing. Two “no” answers is a strong case for a wait or kill verdict.

How to Run a 48-Hour Pre-Build Test

Before committing to building, run this test. It takes roughly eight hours spread across two days and requires nothing more than a browser and a document to write in.

Hours 1 to 2: Map the competitive landscape

Find every product that addresses your problem space, even partially. List them. Note their pricing, their reviews, their positioning, and the language they use to describe the problem they solve. You are building a picture of what the market looks like from the outside and what position is unoccupied.

Hours 3 to 4: Read the community

Find two or three of the most active online communities around your problem space — Reddit is a good starting point, but also look for Discord servers, niche forums, and Facebook groups. Read the last month of posts. Do not post anything yourself yet. Note what people are struggling with, what words they use to describe the problem, what solutions they have tried and rejected. This is the research equivalent of standing outside a store and watching who goes in and what they say on the way out.

Hours 5 to 6: Find the gap in one sentence

Based on your competitive landscape and community research, write one sentence that describes the gap you see. Not the product you want to build — the gap in what currently exists. For example: “Current tools for X require Y, which people in this community consistently describe as a dealbreaker, but no product has removed it.” If you cannot write that sentence with specific evidence behind it, the idea is not specific enough to evaluate and you need more research.

Hours 7 to 8: Have one honest conversation

Find one person who matches your target customer profile. Not a friend. Not a family member. Someone who actually has the problem you are solving, and who you have identified through your community research. Ask them about the problem — not about your product. Ask what they currently do about it, what that costs them, and what is most frustrating about existing solutions. You are not pitching. You are listening.

One conversation will not validate your idea. But it will tell you whether you are solving a real problem for a real person or building for an imaginary market. The Mom Test by Rob Fitzpatrick (themomstest.com) remains the most practical guide to running these conversations without unconsciously leading the witness.

For more on building a minimum version of the product once you have passed this pre-build test, the MVP for solopreneurs guide covers what to build first and why smaller is almost always right.

The Go, Wait, or Kill Decision Model

After running the five-signal check, the three killer questions, and the 48-hour test, you have three possible verdicts.

Go

You have found three or more strong demand signals. Your killer question answers are clear — people with the problem exist today, the need recurs, and there is a specific behavior you can replace. Your 48-hour test has identified a concrete gap backed by real community evidence, and at least one conversation with a real potential customer has confirmed it. The risk is not zero — it never is — but you have enough evidence to move to the next phase: building a minimum version you can show to potential customers before you invest in a full build.

Going does not mean starting to build. It means you are ready to design a minimal proof that someone will pay. That is a different exercise.

Wait

You have mixed signals. Some demand evidence exists but it is weak or partial. The gap is real but not clearly defined. One or more of the killer questions raised issues you have not resolved. Waiting does not mean doing nothing — it means doing more research. Return with better answers before committing months to execution.

The most common “wait” scenario: you have demand signals but you cannot find a real person with the problem who is actively looking for a solution. That gap between “problem exists” and “people are searching for a solution” is worth understanding before you build.

Kill

The signals are absent. There is no evidence of people searching for a solution, no paid products in the space, no active community, and no gap in existing offerings. Or the killer questions revealed a structural problem: the market does not exist at scale, the problem is a one-time purchase in a small market, and people can live without your solution without any real friction. Kill the idea.

This is not failure. Killing a bad idea before you spend six months on it is one of the most valuable decisions a solopreneur can make. The cost of a kill verdict at this stage is a few hours of research. The cost of discovering the same thing after building is measured in months and money.

The value proposition canvas is a useful tool for documenting your go or wait verdict in a structured format — it forces you to articulate exactly what jobs your customer is trying to do and which gains or pains your product addresses.

Frequently Asked Questions

Should I build this product if I already have an audience?

Having an audience does not validate a product idea. An audience proves that people are interested in your content or your persona — not that they will pay for a specific product. The most reliable way to check: run a pre-launch list for the specific product and count how many people from your audience opt in. Per typical creator economy post-mortems on Indie Hackers (indiehackers.com), audience-to-buyer conversion rates for new digital products from content creators usually fall in the range of under 1 to 3 percent, sometimes lower. Your audience signal score still needs to pass the five-demand-signal check above.

How many demand signals do I need before I start building?

Three or more strong signals is a reasonable threshold for moving to the next phase. One or two weak signals is a wait verdict. The signals that carry the most weight are Signal 2 (paid solutions exist) and Signal 5 (workarounds exist), because both require people to invest money or time — a stronger commitment than just complaining about the problem online.

What if my idea has already been built by a competitor?

Existing competition is generally a good sign, not a bad one. It confirms the market exists and people pay for solutions. Your job is to find the gap — the thing existing products do badly or do not do at all — and build for that gap. The exception: if one dominant player owns the entire market with very high switching costs and no clear gap in reviews or community discussions, that is a harder environment for a solo founder with limited resources.

Is this framework only for SaaS products?

No. The five demand signals, three killer questions, and 48-hour test apply to any product a solopreneur might build: a course, a digital template, a membership, a consulting offer, or a software tool. The specific signals will look different for each — for a course, “paid solutions exist” means finding other courses that sell at your target price point — but the underlying logic is the same.

What comes after a go verdict?

A go verdict does not mean start building. It means you have enough evidence to design a minimum testable version — the smallest thing you can put in front of a potential customer to test whether they will pay. This is different from an MVP in the traditional sense. It is a pre-build demand test: a waitlist, a pre-sale offer, a landing page that captures real payment intent before you write a line of code.

Keep Reading

• How to Evaluate a Business Idea: A 10-Point Framework
• MVP for Solopreneurs: What to Build First and Why
• Value Proposition Canvas as an Evaluation Tool