Indie Product Launch Checklist for Developers

Chapter 1 of 8 · 4 checks · 2 min

Validate the problem first

Before building more, check that a specific group of people has the problem badly enough to change what they do, and ideally to pay.

Show
  1. Name the specific people who have the problem and how they solve it todayMust

    Why it matters and how to check

    Paul Graham's essay on startup ideas argues that the best ideas come from problems you have yourself, and that a small group of people who want something urgently beats a large group who mildly like it. Write down exactly who your users are and what they do today instead of using your product: a spreadsheet, a competitor, a manual process or nothing.

    If they do nothing today, ask yourself honestly whether the problem is painful enough.

    Check it: you can name the user group in one sentence and describe their current workaround.

    Do

    • Write the user and their current workaround in one sentence

    Avoid

    • Describing your audience as "everyone"
  2. Talk to potential users before building moreMust

    Why it matters and how to check

    Have short conversations with people who fit your user description. Ask about the problem, not your solution: when did this last happen, what did you do, what did it cost you? Listen for strong frustration and money or time already being spent on workarounds.

    Compliments about your idea are not validation. Specific stories of pain are.

    Check it: you have spoken with several people from your target group and written down their own words about the problem.

    Do

    • Ask about the last time the problem happened

    Avoid

    • Asking "would you use this?" and counting yes answers
  3. Look for a real commitment, not just interestShould

    Why it matters and how to check

    A waitlist signup, a pre-order, a paid pilot, a letter of intent or someone giving you their time for testing are stronger signals than likes or polite praise. Ask for a small commitment and see who says yes.

    If nobody commits, change the problem, the audience or the offer before writing more code.

    Check it: at least a few people have made a real commitment, such as signing up with an email, pre-paying or agreeing to test.

    Do

    • Offer early access in exchange for a pre-order or feedback session

    Avoid

    • Treating social media likes as demand
  4. Check the alternatives and why yours is differentShould

    Why it matters and how to check

    Search for existing products, open source tools and common workarounds. Competition is often a good sign that a problem is real. What matters is a clear reason someone would choose yours: simpler, cheaper, built for a specific niche, or better at one thing.

    Check it: you can name the main alternatives and state in one sentence why your target users would pick yours.

    Do

    • Read reviews of competitors to find what users complain about

    Avoid

    • Assuming you have no competition