Business Backwards logo — a watercolor honeybee shaped like a backwards B and an infinity symbol
Business
Backwards
Guide

How to validate a business idea, problem first.

Do not build from assumption. Build from evidence. This guide gathers the Business Backwards validation principles and exercises into one practical sequence you can start this week.

Five steps to real evidence

  1. Step 1

    Start with the problem, not the solution

    Your experience is a clue, not a conclusion. Before testing a product, confirm the problem exists for people other than you — and describe it in their words.

    • Talk to five people who live the problem.
    • Write the problem in their words, not yours.
  2. Step 2

    Listen before you pitch

    Ego protects the idea. Humility protects the mission. Conversations are for learning, not convincing.

    • Schedule one customer conversation this week with no agenda except to listen.
    • Run 10 honest customer interviews — listen more than you talk — and tag the patterns.
  3. Step 3

    Study what already exists

    Competition is information, not a threat. Existing solutions teach you customer language, pricing, gaps and how the market moves.

    • Map three competitors.
    • Read 50 reviews and tag patterns.
    • Visit one community where your audience gathers.
  4. Step 4

    Run the smallest experiment that would change your mind

    Validation is not approval. It is information. A landing page, a waitlist or ten honest conversations are cheaper than a year of building something nobody wants.

    • Publish a single landing page with one promise and one clear call to action.
    • Open a waitlist that asks explicitly: “I'd pay $X for this.”
    • Pre-sell to 5 customers before writing any production code.
  5. Step 5

    Read the evidence honestly

    Page views are not buying intent, and friends' enthusiasm is not proof of demand. Look for strangers giving you money, time or attention.

    • Track conversion from landing page to email signup and note what works.
    • Decide in advance what result would make you stop, change course or continue.

Common mistakes

  • Treating friends' enthusiasm as proof of demand.
  • Validating the solution before the underlying problem.
  • Confusing page views with buying intent.
  • Building a landing page that's a brochure instead of a test.
  • Skipping validation because it feels slow or unglamorous.

Questions to ask yourself

  • What evidence would make me stop building?
  • What is the cheapest way to learn the next thing I need to know?
  • How many strangers (not friends) have given me money, time, or attention?
  • If only one of my assumptions is wrong, which one would hurt most?
  • What does “enough” validation look like before I commit to building?

Keep going