Back to blog
Business & Startups

From Idea to First Step: Defeating Business Paralysis

Ries's Lean Startup: market risk dominates technical risk for first-time founders. The first move is conversation, not building. Five tiny first steps that validate cheaply, why ADHD founders are especially prone to build-in-isolation failure, and three classic mistakes.

Samuel Culman9 December 20255 min read

The short answer: the first move is almost never building

Eric Ries's The Lean Startup (source) consolidated something most first-time founders need to hear: the riskiest part of a new business idea is not whether you can build the thing. It's whether anyone wants the thing you're going to build. The default founder script — "I'll build first and find users second" — runs the highest-risk step last. The correct sequence is to validate demand before writing code, signing a lease, or quitting a job. Most ideas die on this question and would have died cheaper if the founder had asked it first. The first move is not a build move; it's a conversation move.

Why "I just need to ship to find out" is partly wrong

Shipping does produce information, but most of the information you need is available earlier and cheaper. You can know whether someone has the problem, whether they're already paying to solve it, what they hate about current solutions, and whether they'd find your imagined solution preferable — without building anything. The build-to-learn argument is sound for technical risk (will it work?) but not for market risk (will anyone want it?). For first-time founders the market risk is usually the dominant one and the easier one to test cheaply.

The tiny first step — what it actually looks like

  • DM three potential customers and ask about the problem. Not your solution. The problem. How do they currently handle it, what do they wish was different, what would they pay to make it go away. Three conversations this week is a feasible first move; building a prototype is not.

  • Draft a one-page landing page for the imagined product. Title, problem statement, the headline solution, an email signup. Spend an hour on it. The landing page is for testing interest, not for converting customers; the metric is whether anyone signs up at all.

  • Put a "buy now" button on a thing that doesn't exist yet. Sometimes called the fake-door test. People click; you measure how many. Click-through-to-thanks-for-your-interest is enough to tell whether the imagined product has any pull. If nobody clicks, the time to find out is now.

  • Take pre-orders before the product exists. Highest-quality signal — people will sign up for free things they don't actually want; the same people pre-paying is a much narrower group. A few pre-orders are sufficient evidence; many is rare and tells you something.

  • Define the kill criteria before you start. What signal would convince you to walk away from this idea? If you can't write it down now, you won't be able to write it down later when sunk costs kick in. "If after 30 conversations and a landing-page test, no one has shown interest beyond polite curiosity, I will stop." Pre-decided kill criteria save founders from years of slow-bleed pursuits.

Why this pays double for ADHD founders

ADHD energy is well-suited to the conversation-and-test phase — variety, novelty, fast feedback loops, low ramp-up. The lethal failure mode for ADHD founders is the eight-month build-in-isolation phase where the brain has decided exactly what to build and is wired to ride the hyperfocus until something ships. The output is often technically impressive and commercially dead, because the building was disconnected from the customer signal. The first-move-is-conversation script avoids that trap; it converts the natural ADHD energy into the highest-leverage early activity. Many founders find this is the difference between a project that ships and one that ships into nobody.

Where it fails (and the repair)

  • Talking to friends instead of customers. Friends will validate anything. The conversations need to be with real prospective customers — even strangers — for the signal to be meaningful. Specific, named, in the actual segment you'd serve.

  • Asking about your solution instead of their problem. "Would you use a thing that does X?" is a hypothetical with politeness bias. "How do you currently handle Y?" is a behaviour question. Behaviour answers predict purchase; hypothetical answers don't.

  • Building anyway because the conversations are scary. If shipping a prototype feels easier than three conversations with strangers, the prototype is being used as procrastination. The discomfort of the conversations is the work; bypassing them is bypassing the validation phase entirely.

FAQ

What if my idea requires the product to exist before anyone can evaluate it?

Rare. Most products can be described well enough that prospective users can evaluate the value proposition without using it. If you genuinely believe yours can't, the cheaper test is a clickable mockup — a few screens that simulate the core experience — not the actual built product. Eric Ries calls these MVP variants; the goal is not the minimum buildable thing, it's the minimum thing that produces the signal.

How many conversations are enough?

Steve Blank's customer development guidance suggests roughly twenty conversations is where patterns become legible — earlier, individual answers dominate; later, you're confirming. For most ideas, ten serious conversations are already informative enough to know whether to continue. Three is too few; thirty is excessive at this stage. Aim for a dozen.

What if everyone says they're interested but no one buys?

That's the classic mismatch and the reason hypothetical-yes signal is weak. The fix is to move from words to commitment as early as possible — pre-orders, paid pilots, retainer agreements. The transition from "interesting" to "I'll pay" is the actual validation gate. If you can't cross it, the conversations were polite, not real demand.

Can I just hire a developer and skip the building question?

Sure, but it doesn't change the order. Hiring a developer to build something nobody wants is more expensive than building it yourself. The validation step is the same regardless of who's building. Don't spend money to skip a thinking step.

What's the absolute smallest first move I can make today?

Three messages today to three people in the segment you'd serve, asking how they handle the problem you think your idea solves. If you can't write the three messages — you don't know who would buy yet, and that's the actual first move. Define the segment before everything else.

Frequently asked questions

What if my idea requires the product to exist to be evaluated?
Rare. Most products can be described well enough for users to evaluate the value proposition without using them. If you genuinely believe yours can't, the cheaper test is a clickable mockup — screens simulating core experience — not a built product. Ries calls these MVP variants.
How many conversations are enough?
Steve Blank suggests ~20 conversations where patterns become legible. For most ideas, 10 serious conversations are informative enough. Three is too few; thirty is excessive at this stage. Aim for a dozen.
What if everyone says they're interested but no one buys?
Classic mismatch — why hypothetical-yes signal is weak. Fix: move from words to commitment early — pre-orders, paid pilots, retainer agreements. The transition from 'interesting' to 'I'll pay' is the actual validation gate.
Can I hire a developer and skip the building question?
Sure, but doesn't change the order. Hiring a developer to build something nobody wants is more expensive than building it yourself. Validation is the same regardless of who's building. Don't spend money to skip a thinking step.
What's the smallest first move today?
Three messages today to three people in the segment you'd serve, asking how they handle the problem your idea solves. If you can't write the three — you don't know who would buy yet, and that's the actual first move. Define the segment first.
Share:

Like what you're reading?

Try the platform built around the same ideas — 14 days free.

Start free trial

Read also