The 5-Step Business Idea Validation Checklist (Before You Write a Single Line of Code)

Most first-time founders make the same mistake: they fall in love with an idea, spend three months building it, then discover nobody wants to pay for it. The product is polished. The landing page is beautiful. The features are exactly what they imagined.

And nobody buys.

The reason isn't bad execution. It's bad sequencing. They validated after building instead of before.

This checklist exists to break that pattern. Five concrete steps you can complete before a single line of code is written. Each one produces real signal — not encouraging nods, not survey responses, not "I'd definitely use that." Real signal.

Work through these in order. Do not skip to step 3 because you already did step 1 in your head. "In your head" doesn't count.

---

Step 1: Define Who Would Pay — Not Who Would "Use" It

This is the step almost everyone skips because it feels obvious. It isn't.

"Who is this for?" has a precise answer: the specific person who will hand over money. Not the person who would find it useful. Not the person who might recommend it to someone else. The person who opens their wallet.

These are often different people, and building for the wrong one kills companies.

Here's the diagnostic: can you name your customer in one sentence with enough specificity that a stranger could find 10 real examples of that person within 30 minutes?

Weak: "Freelancers who struggle with client management." Strong: "Independent UX designers with 2–5 clients, billing $5k–$15k/month, who use Notion and have no dedicated invoicing tool."

The strong version is findable. You can search LinkedIn for them. You can find communities they post in. You can name three specific people who match right now.

If you can't describe your payer that precisely, you haven't done step 1. The rest of the checklist doesn't work until this is done — because every subsequent step depends on talking to the right people, not a generic "target market."

Do this now: write one sentence describing your buyer. Include their role, their context, their approximate scale, and what they're currently doing (or failing to do) about the problem. If it takes more than one sentence, keep cutting until it fits.

---

Step 2: State the Problem in One Sentence They Would Use Themselves

You think you're solving a problem. Your customer might describe that same problem completely differently — or not recognize your description at all.

This matters because it determines whether your cold outreach, landing page, and sales copy land or bounce off. If you describe the problem using your vocabulary instead of theirs, you'll get blank looks and polite non-responses.

The test: if you sent your problem statement to 10 people who have the problem, would they immediately say "yes, that's exactly it" — or would they say "sort of, but it's more like..."?

Here's the format: "I help [specific person] who [specific problem in their exact words] so they can [specific outcome]."

To write this accurately, you can't rely on what you assume. You have to go read what they actually write. Find Reddit threads where they vent. Find LinkedIn posts where they describe the frustration. Find reviews of competitor tools that mention the pain. Extract their exact phrasing.

Your version: "I help freelancers who struggle with getting paid on time." Their version: "I help freelancers who lose 10+ hours chasing invoices every month and have written off $2k+ in the last year."

Their version is specific. It has numbers. It's something they would recognize as describing their life.

Do not proceed to step 3 until you can state the problem using language your customer would actually use.

---

Step 3: Find 10 Real People Who Match Your ICP and Talk to Them

Not a survey. Not a landing page. Not a "would you use this?" poll.

Actual conversations. Async or live — doesn't matter. What matters is that these are real humans who fit your payer profile from Step 1, and that you're asking about their reality, not pitching your solution.

Here's where to find them:

• LinkedIn: search by title + industry + company size. Filter to 2nd-degree connections first.
• Reddit: find subreddits where they complain about the problem. Look for recent threads, DM the people who described the pain most specifically.
• Slack communities and Discord servers specific to their industry or role.
• Twitter/X: search for people describing the problem, not discussing solutions.

Your outreach message is 3–4 sentences. It's about the problem, not your product:

"I'm researching how [role] handles [problem area]. Does [specific friction point] actually come up for you — or have you mostly figured it out? Even a one-line reply helps."

That's it. No Calendly link. No product mention. No pitch.

What you're testing: is the problem real enough that strangers take 90 seconds to respond to a cold message about it? If yes — that's signal. If no — either the problem isn't painful enough, you're reaching the wrong people, or your message doesn't land.

Target: 10 responses. Out of 30–40 outreach attempts, that's realistic at 25–35% response rate if the problem is real and your message is focused.

---

Step 4: Build the Ugliest Possible Version — a Landing Page, Not Code

You do not need a product yet. You need a testable claim.

A landing page is not a product. It's a hypothesis. It says: "I believe this specific person has this specific problem, and I have a way to solve it. Here's the value proposition. Here's what you get. Here's the price. Is this for you?"

The ugliest possible version has three sections:

1. Headline: the outcome you deliver. Not "introducing X" — what they get.
2. Three bullets: what it does, who it's for, how it works at the highest level.
3. CTA: "Join the waitlist" or "Get early access" — a form that captures an email and intent.

Build time: 90 minutes maximum. Use Carrd, a free Framer template, or a plain HTML page. The quality of the design is irrelevant at this stage. The quality of the claim is everything.

Or skip the 90 minutes entirely. Launchmap builds your landing page in 60 seconds — enter your idea and it generates a live page with your headline, copy, and CTA already written. Free tier includes the full landing page. Start at launchmap.madethis.app.

The landing page's one job: make a claim specific enough that someone reading it immediately knows whether it's for them or not. If a stranger has to think for more than 10 seconds about whether they're the target user, the page is failing.

Send the link to the 10 people from Step 3 who confirmed the problem is real. Ask for an honest reaction, not a compliment.

---

Step 5: Ask for Money Before You Build — Pre-Sell or Die

This is the step most founders skip because it feels too early, too aggressive, or somehow unfair. It isn't any of these things. It's the only step that actually validates your idea.

Everything before this step is research. Good research — essential research — but still research. The only validation that matters is a stranger paying you money for something that doesn't fully exist yet.

Here's the exact ask:

"Based on our conversation and what you saw on the page — I'm offering founding member pricing to the first 10 people who commit before I build the full product. [Price] secures your spot and locks in [specific benefit]. Interested?"

This doesn't have to be a large amount. Even $1 or $29 is a different category of signal than "this looks interesting." Payment requires intent. It converts enthusiasm into evidence.

How to accept money before you build:

• Stripe payment link (takes 5 minutes to set up)
• "Send me $X via Venmo/PayPal and I'll send you the founding member agreement"
• A simple invoice with net-30 terms (B2B context)

Decision threshold:

• 3+ pre-sales: you have validated demand. Build the smallest version that delivers on the promise.
• 1–2 pre-sales: pivot the message or the audience. One more round.
• 0 pre-sales: the problem isn't urgent enough, the price is wrong, or the audience is wrong. Don't build — iterate on steps 1–4.

Zero pre-sales after two full rounds isn't failure. It's the cheapest learning you'll ever buy.

---

The Complete Validation Checklist

Use this as a quick reference before you write your first line of code:

• I can name my payer in one sentence with enough specificity to find 10 examples in 30 minutes
• I've described the problem using language my customer actually uses (sourced from their posts, reviews, or conversations — not my assumptions)
• I've had real conversations with at least 10 people who match my ICP
• At least 3 of those conversations confirmed the problem is real and urgent
• I've built a landing page with a specific claim (90 minutes or less)
• I've sent the landing page to people who confirmed the problem and asked for honest reactions
• I've made a pre-sell ask to at least 5 people who confirmed interest
• At least 1 person has paid me (or made a near-commitment: invoice requested, deposit sent, verbal commit on record)
• I can state what I'm building in one sentence, for whom, at what price, and why they'd choose it over doing nothing

If any of these boxes are unchecked, you're not done validating. That's not a failure — it's exactly where you should be at this stage.

---

Why This Order Matters

These steps are in a specific sequence for a reason. Each one is a prerequisite for the next:

• You can't do Step 2 without Step 1 — you don't know whose vocabulary to use.
• You can't do Step 3 without Step 2 — you'll ask the wrong questions.
• You can't do Step 4 without Step 3 — you'll build a page for a problem you've only assumed is real.
• You can't do Step 5 without Step 4 — you have nothing to point people to.

Skipping steps doesn't make the process faster. It makes it slower, because you end up backtracking when reality catches up with your assumptions.

The founders who move fastest through this checklist are the ones who do each step completely before moving to the next one.

---

Skip the Groundwork, Not the Validation

The research, the landing page, and the first-draft outreach copy — that's the part Launchmap handles automatically. You enter your idea and get:

• A live landing page with your headline and CTA already written
• A list of your first customer targets by name and role
• Outreach copy drafted and ready to send
• A reality score that flags weak assumptions before you spend time on them

The conversations and the pre-sell ask — those still have to be you. But everything else compresses from days to minutes.

Start free at launchmap.madethis.app →

Free tier includes your full business map, reality score, and landing page. No credit card required.

---

Validation is not a phase you complete before the real work begins. It is the real work — at least until someone pays you. Do these five steps in order, don't skip the pre-sell ask, and you'll know whether to build within a week.

Most founders take six months to learn what this checklist tells you in five conversations.