Customer discovery: write down what you believe, then go prove it wrong

Customer discovery means testing your beliefs about customers by talking to them before you build. How to write beliefs you can disprove and learn from each call.

Instant Expert EditorialPublished Updated 5 min read

Customer discovery is testing what you believe about your customers before you commit to building for them. Write down who you think has the problem, how they handle it today, who pays and how they buy. Then talk to people outside your company and see which beliefs survive.

The term comes from Steve Blank's customer development method, where customer discovery is the first step. Blank's shorthand is that there are no facts inside the building. In a post on founder beliefs, Blank describes discovery as using outside evidence to confirm, reject or change your hypotheses, starting with who the customers are, what they need and who pays.

A worked example: four beliefs you can check

Here is a made-up example. You want to build a tool that helps property management companies track whether their maintenance vendors have current insurance certificates. Your beliefs might be:

  • Property managers chase expired certificates by email and spreadsheet.
  • A missed certificate has caused real trouble, such as an uninsured vendor on site.
  • A property manager feels the pain, but a regional director or procurement lead approves new software.
  • Companies with a few hundred units or more care most.

Each line is a guess you can check by asking property managers, vendor approvers and contract signers what happened the last time a certificate expired.

1. Write down what you believe first

Blank warns about two failure modes. Teams with no stated beliefs collect feature requests with no way to choose between them. Teams with strong beliefs who never talk to customers settle arguments by who is loudest.

So write each belief as a statement someone could prove wrong. "Property managers hate compliance" can't be proven wrong (it may well be true, which doesn't help). "The last expired certificate was found by accident, after the vendor had already done work" can be.

2. Hear from everyone involved in the purchase

In business markets, the person who does the work, the person who picks a tool and the person who pays are often different people. Plan to hear from each. Interviewing B2B buying roles covers what to ask each one, and choosing a first customer segment helps you pick which kind of company to start with.

The finding customers guide lists places to look, and procurement professionals in property management shows the kinds of people who choose vendors in the example.

3. Ask about what already happened

GOV.UK's interview guidance says to focus on stories and real examples, not on how things should happen. "Tell me about the last vendor whose certificate expired. How did you find out?" gives you facts. "Would you use a tool that tracks certificates?" gives you politeness.

Keep solution talk for later (problem interviews versus solution interviews). For ready-made wording, use the 30-minute discovery script.

4. Count commitments, not compliments

Praise for your idea is weak evidence. Stronger evidence is something the person has done or will do: they built a spreadsheet to track this, paid for a partial fix, introduced you to the person who approves vendors, or agreed to a pilot. Blank writes that the best validation you can get is an order.

If nobody has tried to solve the problem and nobody will commit time or money, the problem may be real but not urgent enough to pay for.

5. Update your beliefs after each batch

After every few conversations, mark each belief supported, contradicted or still unclear, and note which conversation told you so. Then aim the next round's questions and invitations at what is still unclear. The interview analysis guide and the decision memo template help turn notes into a decision.

Discovery doesn't end at a set number of interviews. It ends when you can predict much of what the next person will say and you have enough evidence for your next decision: build, change the customer you target, or drop the idea. The interview count guide discusses how to judge that.

Getting your first conversations booked

Start with the belief you are least sure about and the role that can answer it. For the certificate tool, the shakiest belief is probably who approves new software, so the first round goes to regional directors and procurement leads, not property managers.

If your network doesn't reach those people, describe the role in a people search, such as "procurement leads at property management companies with a few hundred units or more who approve maintenance vendors," or paste the LinkedIn URLs of people you already have in mind. You review who it finds before anything is sent. Discovery needs back-and-forth, so ask for a call rather than a written answer: 30 minutes covers one story in depth. You set what each person receives, and our fee (20% of what you pay) is added on top, so a $100 offer costs you $125 (how it works). Sending places a hold on your card for the priciest person's price, fee included, and you're charged for each person only when they book; declines cost nothing. People have 7 days to pick a time and get up to two reminders.

Keep your note about their work, not your product, so payment buys their time rather than a polite answer. Plan the first round with the research plan guide.

One customer discovery loop

  1. 1

    Write beliefs

    List who has the problem, how they handle it, who pays and how they buy, as statements that could be wrong.

  2. 2

    Pick people

    Choose the roles that can confirm or contradict the belief you are least sure about.

  3. 3

    Ask about past events

    Rebuild the last time the problem happened instead of asking what they think of your idea.

  4. 4

    Update the list

    Mark each belief supported, contradicted or unclear, then change who you invite and what you ask.

Run the loop in small batches until your remaining beliefs are clear enough to make the next decision.