Market research for a new product: test the problem first, the market size last

Research a new product in order: reframe the idea as a problem, use internal data, interview buyers, test the concept and commitment, then size the market.

Instant Expert EditorialPublished Updated 5 min read

Market research for a new product should estimate market size last. Answer four questions in order: does a specific group of people have the problem, does your idea make sense to them, will they act when asked to pay or commit, and are there enough of them. Most wasted effort comes from starting with a big market-size figure. The order holds whether you call it new product research, product market research or concept validation.

This page is for a business that already has customers. If you have none yet, market research to start a business covers that situation.

The running example: an ordering add-on for restaurants

Here is a made-up example used throughout the page. Your company sells point-of-sale software to independent restaurants. Several customers have asked whether you could help with ordering supplies, and the team is excited about an inventory and ordering add-on. (Someone has already suggested a name for it.)

The request is a good lead, but it is a solution the team has already pictured. That makes it easy to research whether customers like the idea instead of how ordering works today and what it costs them.

1. Turn the product idea back into a problem

The UK government's guidance on the discovery phase says a team handed a predefined solution should reframe it as a problem to be solved, and consider how much the problem currently costs. Its example: "we need to build an interactive map" becomes "how can we make it easier for people to find their nearest contact centre?"

Here, "build inventory ordering" becomes: "How do restaurant managers decide what to order each week, who does it, and what does getting it wrong cost them in waste, stockouts and time?" Evidence can answer that, and it leaves room for an answer that is not your add-on.

The same guidance says stopping at the end of discovery is not a failure if research shows that is the best choice. Decide before you start which finding would make you stop.

2. Collect what your company already knows

Before recruiting anyone:

  • Requests and support tickets. Who asked for ordering help, and what were they trying to do? How to test a feature request covers reading these without taking the requested feature literally.
  • Sales notes and lost deals. Did any prospect choose a competitor because it handled ordering?
  • Usage data. Do customers export sales data to a spreadsheet at the end of the week? That can point to a workaround.

Existing customers are a biased sample. They chose your current product, and people with the problem who never became customers are missing from these records.

3. Interview buyers, users and non-customers about the last order

Talk to the people who do the ordering and the people who would approve paying for a tool. In a small restaurant they may be the same person; in a group of restaurants they often are not. How to interview B2B buyers, users and champions covers the difference.

Ask about the last order, not your idea:

Walk me through last week's produce order. Who decided the quantities, what did they look at, and what went wrong?

Include a few restaurants that do not use your software, and at least one person from the supply side, such as a restaurant procurement lead, who can explain how suppliers take orders and what they expect. Keep problem conversations separate from any where you show the concept; problem interviews vs. solution interviews explains why mixing them muddies both.

4. Test whether the concept makes sense, not whether people like it

Next, show people a short description or rough prototype. Nielsen Norman Group describes concept testing as sharing an approximation of a product that captures its core value, to see whether it meets the target audience's needs. The same article separates what people say from what they do, and notes the two are often quite different.

Look for understanding and fit. Can the manager explain back what the add-on does? Where would it fit in their week? What would they stop doing? Polite interest is common and tells you little.

5. Ask people to act

Stated interest is weak evidence. Ask for a commitment:

  • Offer a paid pilot to a few customers at a real price.
  • Have your sales team mention the add-on in renewal conversations and record who asks for a quote.
  • Put a clearly labelled "coming soon, join the pilot" option in your product and count sign-ups from the people who fit.

How to research willingness to pay covers setting up these tests and reading the results.

6. Size the opportunity last, from the bottom up

Now estimate size, starting with your own customers: how many fit the profile, what share of those in the pilot converted, and what they would pay. If you plan to sell beyond your base, use public business counts to estimate how many similar restaurants exist in the markets you serve.

Write each step of the estimate next to its evidence, and label guesses as guesses.

Write down the decision

End with a short memo: the problem you found, how common it seems, what the concept and commitment tests showed, and the decision. Turning customer interviews into a testable product decision has a format.

If you need to hear from people outside your customer base, such as restaurants on a competitor's software or suppliers, Instant Expert can find people who match a description you write. You review them, it sends your invitations and you pay only for calls that get booked. The directory pages for restaurant procurement professionals and restaurant finance professionals are one place to start for this example.

Research a new product in this order

  1. 1

    Reframe as a problem

    Turn the product idea into a question about what people do today and what it costs them.

  2. 2

    Use internal evidence

    Review requests, support tickets, lost deals and usage data you already have.

  3. 3

    Interview the right people

    Talk to users, approvers, non-customers and the supply side about recent events.

  4. 4

    Test the concept

    Check that people understand the idea and can say where it fits in their work.

  5. 5

    Ask for commitment

    Offer a paid pilot or quote and record who acts, then estimate size from the bottom up.

Each step answers a question that makes the next one worth asking; sizing comes last.