What to Ask Your First Customers to Improve Your Offer

Talking with your first customers can reveal where an offer delivers on its promises, which parts cause difficulties, and which needs remain unmet. To gather useful information, ask about real experiences and listen without trying to defend the solution. The goal is not to gain approval, but to better understand the problem and decide what is worth testing.

Before the conversation: define what you need to find out

Choose one or two specific aspects you want to understand: for example, how they discovered the offer, what they expected to get from it, or when they encountered obstacles. Bring a brief guide, not a rigid script. That way, you can cover the same topics with different people while also following up on relevant details that come up during the conversation.

If possible, talk to people who have used the offer recently and can describe their experience. Explain that you want to learn, not sell them something or persuade them that they liked it. During the conversation, listen more than you talk and give the person room to think before responding.

Questions for exploring the customer experience

Start with a specific situation. Open-ended questions focused on past events tend to provide more context than asking for a general opinion or a prediction about what someone would do.

1. Understand the reason and expectations

• What was happening when you decided to look for a solution?
• What other options did you consider, or what were you doing before?
• What did you expect this offer to help you achieve?
• What influenced your decision to try it the most?

These answers help distinguish the need that led to the purchase from the explanation the company assumes motivated the customer.

2. Reconstruct actual use

• Tell me about the last time you used the offer. What happened, from the beginning?
• What were you trying to do, and what steps did you take?
• When did things go smoothly, and when did you have to stop?
• Did you ask for help or find another way to complete the task?

If a difficulty comes up, follow up with neutral questions: “Can you tell me a little more?”, “What did you do next?” or “What did you expect to happen?” Avoid suggesting in advance what the problem should be.

3. Identify value and friction

• What part did you find most useful? In what specific situation?
• Was there anything that surprised or confused you, or took longer than expected?
• What didn’t work the way you thought it would?
• What did you have to work out on your own?
• If you could change one thing about the experience, what would it be and why?

Ask for examples when the answer is broad. “I liked it” is an impression; knowing what task the person was able to complete and how they did it provides context for interpreting that impression.

4. Explore what is still missing

• What are you still doing outside this offer to solve the same problem?
• What have you tried before, and why did you stop or keep using it?
• Is there a related task that is still difficult?
• What would need to change for the experience to fit better into the way you work?

The alternatives and workarounds customers already use can point to needs the offer does not meet. That does not automatically mean a feature should be added: first, understand how often the need arises and how much it matters.

When analyzing responses: separate what was said from what was inferred

After each conversation, record these separately:

• Facts and examples: what the person did, when it happened, and what result they got.
• Quotes or exact wording: how they described their expectations, difficulties, or priorities.
• Interpretations and hypotheses: what the experience might indicate and what would be worth verifying.

This separation reduces the risk of turning a first impression into a conclusion. A preference expressed by one person may be a clue, but it does not by itself prove that all customers need the same change. Look for patterns across conversations, and also check whether differences depend on the customer type, context, or way the offer is used.

Choosing which change to test first

Before expanding customer acquisition, rank the problems you observed by asking three questions:

1. Does it recur? Did it come up in several conversations, or was it an isolated experience?
2. Does it matter? Does it prevent someone from completing an important task, reduce perceived value, or cause only a minor annoyance?
3. Can it be tested? What small change would help establish whether the solution improves the experience?

Frequency alone is not enough: an infrequent difficulty may matter in a specific context. Likewise, an appealing improvement idea is not proof that it will solve the problem. Assess the available evidence and note what you still do not know.

Close with a hypothesis and a small test

Turn the best-supported finding into a specific hypothesis: “We believe [customer type] has difficulty with [specific task] because of [observed reason]; we will test [limited change] and observe [signal of improvement].”

Test the change with a limited group or in one specific part of the experience before rolling it out more widely. Decide in advance what you will observe—for example, whether people complete the task with less confusion—and talk again with those who tried it. That way, early feedback becomes a learning cycle, not a list of requests to implement without question.