Two sales professionals discussing customer pain points in a glass-walled meeting room, illustrating sales as a learning tool.

Chapter 9. A sale is a learning machine

5 min read

Part 11 of 20 in How to Sell: The Key to Success

This chapter explores how sales can be a powerful tool for understanding customer pain points, not just generating revenue. It offers strategies for founders to learn from sales interactions to better meet customer needs.

Quick Summary

  • Revenue is important, but understanding customer pain is crucial for building the right product.
  • Rushing sales or offering discounts can result in missing valuable customer insights.
  • Asking specific questions helps uncover true customer needs and leads to delight.
  • Documenting customer feedback accurately is essential for product development.
  • Saying no to the wrong customers can strengthen trust with the right ones.

Founders say they want revenue. They do. They also need something revenue does not automatically bring: a description of the pain sharp enough to build against. A sale that you rush, discount, or hand to someone who cannot ask why, will give you the money and steal the lesson. You will then spend the money building the wrong relief.

Bettger’s question method was a learning method that happened to close. He found out what the other person wanted, and he helped them get it. The founder’s version has a second duty. Find out what they want, help them get it, and keep the words, so the next ten buyers meet a product that already understands them.

Delight is specific

You cannot delight a segment. You can delight a person who told you the true annoyance. Delight, in an early startup, is not a brand campaign. It is the moment a buyer thinks: they fixed the thing I actually said, not the thing in their roadmap. That moment produces the witness you need for Chapter 6. It also produces the only referral that works in a distrustful market, which is a buyer telling a peer, unprompted, that the Tuesday got shorter.

The questions that create delight are not clever. What did you do last Tuesday when this broke? Who felt it? What did it cost, in hours or in a scolding? What have you already tried? What would you not want us to change? What would make you look good to the person you report to? A founder who asks these and then builds the answer will outperform a founder who asks for feature requests. Feature requests are solutions. You are hunting the pain underneath them.

Write it down in their language

Memory flatters you. A note does not. After every conversation, four lines in the Customer Truth document.

  • Pain, in their sentence, not yours.
  • Workaround they use today.
  • Who else decides, and what that person fears.
  • What “delighted” would look like in a month, in their words.

Once a fortnight, read the document and ignore the deck. The repeated sentence is the company. If eight buyers mention the panic on the second of the month and none mention your favourite feature, the favourite feature is a hobby. Bettger kept records because he did not trust his impressions. You should not trust yours either. You are too close to the idea, and too eager for it to be right.

The sale that teaches you to say no

Learning cuts both ways. Some pain is real and not yours to solve. A buyer who wants a custom workflow for one branch, a price that only works if you acquire the customer for free, a use case that pulls you into a regulated mess you do not understand. Founder-led sales is also how you learn the customers you will not serve. A hired team, measured on bookings, will serve them anyway. You will feel busy and lose the plot.

Say no in the meeting, out loud, and write down why. The no is part of the product. It is also, strangely, part of the close with the right buyer. A founder who declines the wrong work is easier to trust with the right work.

Revenue is the test, not the teacher

Do charge. A free pilot teaches you what people will try, not what they will keep. Bettger did not improve his craft by giving policies away. Ask for money early enough that the buyer’s objections become serious. Then treat the rupee as a receipt for a lesson you have already written down. A company that has revenue and no Customer Truth document has a cash register and no memory. It will not delight anyone on purpose. It will occasionally delight someone by accident, and it will not know how to repeat it.

The purpose of a sale is not only the revenue. It is the pain, named clearly enough that you can remove it.

Practice. Open the Customer Truth document today, even if it has three entries. Highlight every phrase a buyer used that you have never used on your site. Put one of those phrases on the homepage this week. That is delight, starting at the sentence.

Frequently asked questions

Why is understanding customer pain important in sales?

Understanding customer pain helps build products that truly address customer needs, leading to better satisfaction and success.

What questions should founders ask to understand customer needs?

Questions should focus on specific situations, costs, existing solutions, and desired outcomes to uncover true customer needs.

How does documenting customer feedback help?

Documenting feedback ensures accurate understanding of customer needs, guiding product development and improving customer satisfaction.

Why should founders say no to some customers?

Saying no to unsuitable customers prevents wasted resources and builds trust with customers who align with the company's goals.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top