← Founder launch guides

Customer research field guide

What to Ask Before You Build a Digital Product

7 min read

Before you choose a format, ask about the work a buyer is already trying to do. The point is not to collect compliments for an idea. It is to understand a current problem well enough to decide whether a small, paid solution is worth testing.

Conversation prompts

Ask for stories, not predictions

Use these prompts with people who are close to the work. Let the conversation follow their language and examples; the questions are a structure, not a script to force through.

01

Start with the last real attempt

Tell me about the last time you tried to solve this. What were you trying to get done, and what happened next?

02

Locate the costly part

Where did this create extra time, uncertainty, rework, missed momentum, or an out-of-pocket expense?

03

Learn the current workaround

What do you use now? What is useful about it, and where does it stop being enough?

04

Ask about the decision

What would make you choose a tool, template, or guide instead of continuing with the workaround?

05

Test the smallest outcome

If something helped with one part of this next week, which part would be most useful to have handled?

Interpret the evidence

Look for a painful paid problem

One conversation is rarely a product brief. Look across several conversations for the same trigger, tradeoff, and language. A promising problem is both concrete and consequential enough that a buyer already spends time, money, attention, or goodwill trying to manage it.

  • The buyer describes a recent, specific instance rather than a general preference.
  • The current workaround has a visible cost or recurring frustration.
  • The desired first result can be named without building a complete system.
  • You can imagine a bounded format that helps without relying on custom access to you.

Make the next decision

Choose a test, not a full build

When a pattern emerges, write a small offer that names the buyer, their trigger, the first useful output, and what is excluded. Then put that offer in front of more qualified people. The goal is to find out whether the problem, language, and format are understandable before you invest in a larger product.

For a practical next step, pair these conversations with the offer validation guide. It turns what you heard into a compact test with a defined review point.

View the 48-Hour Offer Validation Sprint