Startup Idea Checklist: 12 Questions to Ask Before You Build Anything

I know what you're thinking. "Another checklist?" Stay with me. This one's different because each question has a right answer range, and I'll tell you exactly what the red flags look like. No theory, no MBA jargon — just 12 questions that'll save you from building something nobody wants.

I'm also going to be honest about something: I stole this framework from my own mistakes. Each question represents a lesson I learned the hard way — by ignoring it.

The market questions

Question 1: How painful is the problem you're solving?

This is the single most important question. Everything else is secondary. If the problem isn't painful enough, nothing else matters — not your tech, not your marketing, not your pricing.

There's a spectrum here. On one end: "it would be nice if..." Those ideas almost always fail for solo founders because you need massive scale to monetize mild convenience. On the other end: "I'm losing money/time/sleep because of this." Those ideas sell themselves because the customer is already looking for a solution.

Red flag: When you describe the problem to someone and they say "huh, yeah I guess that's annoying." That's a nice-to-have. You want them to say "god yes, that drives me crazy."

Question 2: How many people have this problem?

A super painful problem for 500 people is a hobby project, not a business. You need enough people with the problem to sustain a company. For a solo founder with low costs, "enough" might be 10,000 potential customers willing to pay $10/month. For a VC-backed startup, you'd need millions.

Don't overthink the numbers. A rough estimate is fine. Check Google search volume for related terms. Look at subreddit subscriber counts. Check how many people follow relevant hashtags or influencers. You're not building a spreadsheet — you're getting a sense of whether the audience is "tiny niche" or "real market."

Red flag: You can't find more than a few hundred people discussing this problem anywhere online.

Question 3: How crowded is the market?

Competition is confusing because both extremes are bad. Zero competitors often means zero demand — people have needed this thing and nobody built it, which should make you very suspicious. But a market dominated by Google or Salesforce means you'll get crushed unless you're targeting a specific segment they're ignoring.

The sweet spot is "a few small competitors, none of them great." That tells you the demand is real, the market is proven, but there's room for someone to do it better. Basecamp entered a crowded project management market and won by being simpler than everyone else. They didn't need to be the biggest — they just needed to be different.

Red flag: The top 3 search results for your product category are all Fortune 500 companies. Or: there are literally zero competitors and you can't find anyone complaining about the problem.

Question 4: What makes yours different?

Let me guess: "better UX." That's what everyone says. And honestly, sometimes that is the differentiator — but it's a weak one because better UX is subjective and easy to copy.

Stronger differentiators: a different target audience (enterprise tools rebuilt for solo users), a unique data source, a specific geographic focus, a radically simpler approach (cutting features instead of adding them), or domain expertise that gives you insight competitors don't have.

If you can't articulate in one sentence why someone would pick you over the competition, you don't have a differentiator yet. That doesn't mean you should abandon the idea — it means you need to think harder about positioning before you build.

The money questions

Question 5: Would your target customers pay for this?

There's a painful truth that kills a lot of consumer ideas: many problems are real, but the people who have them won't pay to solve them. Think about how many apps you've tried, liked, and deleted when they asked you to pay $4.99/month.

B2B is generally easier to monetize because businesses treat software as a cost of doing business. A freelancer will pay $15/month for invoicing software because it directly saves them money. That same freelancer might not pay $5/month for a journaling app even if they love journaling.

The best signal: are people already paying for worse alternatives? If the market has established pricing (project management tools: $10-25/user/month; email marketing: $20-100/month; etc.), people will pay for yours too. If everything in the space is free and ad-supported, monetization will be an uphill battle.

Question 6: How will you make money?

This sounds obvious but a shocking number of founders launch without a clear answer. "We'll figure out monetization later" is how you end up with a popular free tool and no revenue.

Subscriptions work best when your product delivers ongoing value. One-time purchases work for discrete tools and downloads. Freemium works when the free version is genuinely useful and the paid version is dramatically better. Ads only work at massive scale — if you're not planning for 100K+ monthly users, ads won't pay your rent.

Pick a model before you build. It shapes everything — your feature set, your marketing, your pricing psychology.

The execution questions

Question 7: Can you build version one yourself?

If yes, you've just eliminated the biggest risk in early-stage startups: dependency. You can move fast, iterate based on feedback, and pivot without negotiating with a co-founder or paying a contractor.

If no, you have two options: learn enough to build a basic version (harder but better long-term), or find a technical co-founder (faster but you're now splitting equity and decisions). Paying a developer with savings is the worst option at this stage because you'll burn cash before validating anything.

Also consider no-code tools. If your idea is a marketplace, a directory, a booking system, or a content platform, you might be able to build an MVP with Bubble, Webflow, or Airtable without writing a line of code. It won't scale, but it'll let you test the idea.

Question 8: How long to build an MVP?

My rule of thumb: if your MVP takes more than 4 weeks to build, your scope is too big. Cut features. Then cut more. Then cut again until you can build it in 2 weeks.

Here's why this matters: every week you spend building is a week you're not learning from real users. The fastest path to product-market fit is: build the smallest possible thing, put it in front of real people, learn from their behavior, and iterate. Spending 6 months on a "perfect" v1 is the most expensive way to find out you built the wrong thing.

Dropbox's MVP was a 3-minute video showing how the product would work. Buffer's MVP was a single landing page with pricing. Both validated demand before writing serious code.

Question 9: How excited are you about this?

I'm putting this in execution because motivation is an execution problem. You can have perfect market fit and a great business model, but if you're bored by month three, you'll quit. And month three is usually the worst — the initial excitement has faded, traction is slow, and there are easier things to do with your evenings and weekends.

You don't need to be "passionate" in the Instagram-entrepreneur sense. But you should genuinely find the problem interesting. You should want to read about the industry on a Sunday morning. You should care about making your users' lives better, not just about making money.

Rate yourself honestly on a 1-10 scale. Below 6? Think hard about whether this is the right idea for you specifically, even if it's a good idea in general.

The financial questions

Question 10: How much can you invest upfront?

Good news: most software products can launch for under $100. Domain, hosting, maybe a few months of a tool subscription. If your idea requires $10K+ before it generates a single dollar, that's not necessarily a dealbreaker — but it dramatically raises the stakes.

The zero-budget path is real: free hosting (Netlify, Vercel, GitHub Pages), free tools (Firebase, Supabase), free marketing (SEO, social media, communities). It's slower, but it keeps you alive while you figure things out.

Question 11: Monthly marketing budget?

Here's an unpopular opinion: $0 marketing budget is actually fine for the first few months. SEO takes time but costs nothing. Community participation is free. Content marketing is free if you write it yourself. Building in public on Twitter is free.

Paid ads make sense later, once you know your conversion rate and customer lifetime value. Spending money on ads before you've nailed your messaging is like pouring water into a leaky bucket — expensive and demoralizing.

If you have $200-500/month for marketing, save it for month 3 or 4, after you've validated the idea organically. Then use it to amplify what's already working, not to test what might work.

Question 12: What's the one-sentence version?

Not technically a financial question, but it belongs at the end because it forces clarity. Can you describe your idea in one sentence that makes a stranger say "oh, I get it"?

If your explanation takes three paragraphs, your idea is too complex — either to build, to market, or to understand. Simplify until it fits in a tweet. "We help freelancers get paid faster." "A meal planner that learns your tastes." "Score your business idea in 2 minutes."

If you can't do this, don't start building.

Using this checklist

Don't just read this and nod along. Actually sit down with your idea and answer each question in writing. Be brutally honest — the only person you're hurting by being optimistic is yourself.

If you've got strong answers to questions 1, 2, 5, and 7 — painful problem, real audience, willingness to pay, and you can build it — you've got a solid foundation. Weaknesses in other areas are fixable.

If you're weak on 1 and 5 — mild problem and people won't pay — I'd think twice before building. Those are the hardest weaknesses to overcome because they're about the market, not about you.

And if you want a number instead of a gut feeling, well — that's why we built the tool. Same 12 questions, but the math is done for you.