The Founder's Pre-Build Checklist: 15 Questions Before You Code

You've validated your idea. You've talked to customers. You have signal. Now comes the decision: Should you actually build this?

This checklist answers that question.

These 15 questions separate founders who build products people want from founders who build products nobody needs.

Go through them honestly. If you can't answer "yes" to at least 12, don't build yet.

Section 1: Customer Validation (4 questions)

1. Have you talked to 10+ actual target customers?

Why it matters: If you've talked to fewer than 10 customers, you're still in "early learning" phase. Sample size of 3-4 feels like enough, but it isn't. It takes 10+ conversations to identify patterns vs. outliers.

How to validate:

• Document customer interviews (5-question minimum each)
• Include their name, company, job title, and problem statement
• Show me the conversation notes (not summaries—actual notes)

Red flag: You've talked to friends. You've talked to investors. But you haven't talked to 10 strangers who fit your customer profile.

Answer: Yes / No / Partial (how many?)

2. Do at least 7/10 customers acknowledge the problem exists (and it's urgent)?

Why it matters: Customers acknowledging a problem isn't the same as urgency. "Yeah, that's annoying" is different from "This costs me $10K/month."

Urgent problems get solved. Annoying problems get tolerated.

How to validate:

• In your customer interviews, ask: "How much time do you spend on this weekly?"
• Ask: "What's the cost of this problem currently?"
• Look for pain language: "Nightmare," "Waste," "Lose," "Frustrated"

Red flag: 3/10 customers say it's a problem. 7/10 say "Yeah it happens but not a big deal."

Answer: Yes / No / (Number who confirmed urgency?)

3. Have at least 3+ customers offered to pay or commit to a pilot?

Why it matters: This separates "interesting" from "buyable." Willingness to pay is the ultimate confirmation signal.

How to validate:

• Ask directly: "Would you pay for a solution?"
• If yes: "What's a fair price range?" (Listen; don't suggest)
• If yes to price: "Would you be willing to pilot it with us?"

Red flag: 0 customers offered to pay. They all say "I'd use it if it was free."

Answer: Yes / No / (How many committed?)

4. Can you articulate your target customer in one sentence?

Why it matters: If you can't define your customer, you don't know who to build for. "Everyone" is not a customer.

How to validate:

• Write: "My ideal customer is [job title] at [company type] earning [salary range] with [specific problem]"
• Example: "My ideal customer is a B2B SaaS founder (Series A funded) spending >$10K/month on customer retention who struggles with churn prediction."

Red flag: Your customer description is 3 sentences long and includes 5 different personas.

Answer: Yes / No

Section 2: Problem Understanding (3 questions)

5. Do you understand the complete problem (not just the symptom)?

Why it matters: Most founders understand the symptom. "Companies can't track expenses." But the real problem might be different: "Finance teams spend 15 hours/week reconciling expense reports creating resentment" or "We have no visibility into what teams actually spend."

Understanding the real problem changes what you build.

How to validate:

• Ask customers: "Why does this matter?" 5 times (like a child)
• Map the problem to 3 different people affected: decision maker, implementer, user
• Document what each person wishes would change

Red flag: You understand the symptom. But when asked "Why does that matter 3 levels deep?" you hit a wall.

Answer: Yes / No

6. Have you identified the economic value of solving this problem?

Why it matters: Some problems are real but solving them makes no economic sense. "Save 30 minutes/week of developer time" might not be worth a developer's overhead.

But "Reduce customer churn by 5%" is worth thousands.

How to validate:

• Ask customers: "What's the cost of this problem today?" ($ or hours)
• Calculate: "If we reduced this cost by 50%, what would that be worth?"
• Example: "Enterprise customer wastes 10 hours/week on manual reporting (engineer @ $150/hr = $1,500/week = $78K/year)"

Red flag: You can't quantify the value. The problem feels real but when you try to add numbers, the ROI is unclear.

Answer: Yes / No / (What's the estimated value?)

7. Have you mapped the customer's buying process?

Why it matters: Even if the problem is real and urgent, if the buying process is slow/complex, you won't make revenue.

Selling to enterprises takes 9 months. Selling to SMBs takes 4 weeks. Selling B2C takes 3 days. This matters.

How to validate:

• Ask: "How would a solution like this get bought at your company?"
• Ask: "Who would have to approve it?"
• Ask: "What's your typical buying process for tools?"

Red flag: "I don't know, probably marketing or the CEO. We don't really have a process."

Answer: Yes / No

Section 3: Market & Competition (3 questions)

8. Is this TAM (Total Addressable Market) at least $10M?

Why it matters: Building a business that serves a $1M market is possible (lifestyle business), but it's not a venture-backable business. If you want to raise capital or build something that compounds, TAM matters.

How to validate:

• Number of potential customers × average price they'd pay = TAM
• Example: "10K SMBs × $500/year = $5M TAM" (too small)
• Example: "100K B2B SaaS companies × $10K/year = $1B TAM" (good)

Red flag: TAM is $2M. You're trying to build a venture business in a shoebox market.

Answer: Yes / No / (What's the estimated TAM?)

9. Have you researched 3+ competitors and understand what you'll do differently?

Why it matters: If competitors don't exist, the market doesn't exist (or you haven't looked). If you can't articulate differentiation, you're building a commodity.

How to validate:

• List 3+ competitors (direct or adjacent)
• For each: "What's their main weakness?"
• For your idea: "How do we solve what they haven't?"
• Can you say this in 1 sentence? If not, you're not differentiated.

Red flag: "There are no competitors" or "Competitors exist but they're not as good" (vague).

Answer: Yes / No

10. Is the market growing or at least stable?

Why it matters: An awesome product in a dying market is still a dying business. "Fax machine software" was a real market once.

How to validate:

• Search: "Industry report for [category]"
• Look for: Market size 2019 vs. 2024. Growing or shrinking?
• Ask customers: "Is your company investing more or less in this area this year?"

Red flag: Your market is shrinking (e.g., building fax software in 2025).

Answer: Yes / No

Section 4: Business Model (3 questions)

11. Do you have a clear monetization model (not just "premium features")?

Why it matters: "We'll figure out pricing later" means you haven't thought about your customer's budget or your unit economics.

How to validate:

• Write down: "We charge $[price] per [unit] to [customer]"
• Example: "$50/month per user to SMB operations teams"
• Calculate: "If average customer has 5 users and stays 2 years, annual contract value = $6K"

Red flag: "We'll make money from ads" or "We're not sure yet, maybe subscription or one-time."

Answer: Yes / No / (What's the model?)

12. Have you validated pricing with customers (not internal guessing)?

Why it matters: Founders are terrible at guessing pricing. You'll either underprice (leaving money on the table) or overprice (selling nothing).

How to validate:

• Ask 5 customers: "What would you pay for this?"
• Use Van Westendorp Price Sensitivity approach: "At what price is this too cheap?" "At what price is this too expensive?"
• Ask: "Would you pay [X price]?" and listen for genuine interest vs. negotiation.

Red flag: "We think $X/month is fair" based on feature count or competitor pricing (not customer input).

Answer: Yes / No / (What's the validated price?)

13. Can you describe unit economics in rough terms?

Why it matters: If customer acquisition costs you $500 and they pay you $100/month, you need 5+ months to break even on acquisition. That's fine for venture scaling, but you need to know it.

How to validate:

• Estimate: "To acquire 1 customer, we'll spend $[X] on marketing and sales"
• Estimate: "Average customer pays $[X] per year"
• Calculate: "Payback period = acquisition cost ÷ annual revenue"
• If payback > 12 months, you need really high retention or funding to scale

Red flag: "I don't know our CAC or LTV. We'll figure it out after launch."

Answer: Yes / No / (Rough numbers?)

Section 5: Founder Readiness (2 questions)

14. Do you have unfair advantage (expertise, network, or timing)?

Why it matters: The market is competitive. If you have no edge, you'll lose to founders who do.

How to validate:

• Do you have 5+ years in this industry?
• Do you have network of 50+ people who know you in this space?
• Did you identify this problem before competitors?
• Do you have technical/domain expertise competitors lack?

Red flag: "I'm entering a new market because I'm good at building things."

Answer: Yes / No / (What's your edge?)

15. Are you committed to this for 3+ years?

Why it matters: Real products take time. If you're hoping to get rich in 12 months, you're going to make bad decisions.

How to validate:

• Honestly answer: "If this takes 3 years before I see real traction, will I keep going?"
• If the answer is "Maybe" or "Only if it's working by Month 18," you're not ready.

Red flag: You're running away from a corporate job, not running toward a problem you're obsessed with.

Answer: Yes / No

Scoring Your Checklist

Count your "Yes" answers:

How This Connects to Your Validation Framework

This checklist is the final gate before building. It's the bridge between general idea validation → and execution.

You've confirmed the problem is real. You've confirmed customers care. This checklist confirms you're ready to build without major risks.

Common Mistakes Founders Make

Mistake #1: Rushing to build before answering these questions.

• Result: You build product nobody wants. You waste 6 months.
• Fix: Spend 2 weeks on this checklist. It saves 6 months later.

Mistake #2: Answering questions based on what you hope is true, not what you know is true.

• Result: You have false confidence. You start coding. You hit walls.
• Fix: Be brutally honest. If you can't verify it, mark it as "No" or "Partial."

Mistake #3: Treating this checklist as a one-time gate.

• Result: You answer all 15, score 13/15, and build.
• Fix: Revisit this checklist monthly as you build. As you learn more, answers might change.

If You Score Low: What to Do

If you score 10 or below, don't build yet. Instead:

Week 1: Do 10 more customer conversations. Focus on questions 1-7 (customer validation).

Week 2: Research competitors more deeply (question 9).

Week 3: Revisit pricing and unit economics (questions 11-12).

Week 4: Re-score yourself.

If you still score <10, seriously consider: Is this the right problem? Or should I look for a different angle in the same space?

The best founders kill ideas before investing time. Do that here.

The Paradox

The founders who score highest on this checklist build products faster because they have fewer surprises.

Fewer surprises = faster iteration = faster to product-market fit.

Don't skip this.

Ready to Build?

If you score 12+, you have validated signal. You know your customer, your problem, and your differentiation.

Start building.

And as you do, circle back to idea validation → to lock in your positioning and messaging.

Ready to validate comprehensively before building? Use Edmired to run through the complete validation framework and build with confidence, not guesses. Join the beta.