I recently completed Daniel Pink’s MasterClass on Sales and Persuasion.
I selected it because sales is part of almost every founder’s work. We explain an idea to a customer, ask a team to support a new direction, discuss a proposal, or try to build confidence around a decision.
The course was not mainly about scripts or closing techniques. It was about understanding people, asking better questions, and making ideas easier to act on.
Customers already have information
There was a time when the salesperson usually knew much more than the customer. Today, most customers do their own research before a meeting. They compare suppliers, review specifications, speak to other users, and form an early opinion.
This is also true in technical businesses. A pharmaceutical company exploring serialization or Track & Trace can already find basic information about GS1 DataMatrix, aggregation, EPCIS, and regulatory requirements.
Repeating the same information does not create much value. The useful part is helping the customer understand what matters in their own situation.
The role of the seller has moved from providing information to creating clarity.
Which risk is being overlooked? Where could implementation fail? Which decision should be made first? How will production, quality, information technology, procurement, and management be affected?
A customer may have plenty of information and still need help making sense of it.
Find the real problem
One of the strongest ideas in the course was the difference between solving a problem and finding the right problem.
Customers often begin with a visible requirement. They may say they need a printer, software, integration, or a regulatory solution. The first request, however, may only be the surface of the issue.
A request for a printer may really be about poor code quality. A request for software may be about weak data control. A request for integration may be driven by production downtime, reconciliation problems, or concern about an audit.
Good sales conversations do not rush towards the product. They spend enough time understanding what is actually going wrong.
Questions worth asking
• What are we really trying to solve?
• Why does it matter now?
• What happens if nothing changes?
• Who will be affected by this decision?
• What concern has not yet been discussed?
The right question can sometimes create more value than a quick answer.
Understand the other side
Daniel Pink uses the word “attunement” for the ability to understand another person’s point of view. In practice, it means paying attention to what the other person is trying to achieve, what they are worried about, and what they may need to explain internally.
This matters in complex business decisions because each stakeholder sees the same project differently.
Production thinks about downtime. Quality thinks about validation and compliance. Information technology thinks about integration and security. Procurement thinks about pricing and terms. Management thinks about risk and continuity. Operators think about how the system will affect their daily work.
A single presentation cannot speak to all these concerns in the same way. Before explaining our solution, we need to understand what matters to the person sitting in front of us.
This does not mean agreeing with everyone. It means listening well enough to have a relevant conversation.
Keep the message clear
Keep the message clearTechnical companies often make selling harder than it needs to be. We are proud of our systems, specifications, integrations, and standards. These details matter, but too many details can hide the main point.
A customer may not need every technical detail at the start. They may first need a clear answer to a practical question: Will this solution work reliably in our environment, protect our operations, and help us meet our responsibilities?
The technical explanation should support the answer. It should not bury it.
Clarity does not make the subject less intelligent. It makes the decision easier to understand.
A pitch should start a conversation
Another useful lesson was that the purpose of a pitch is not always to get an immediate yes.
A good pitch creates interest. It gives the other person a reason to ask questions. It allows the solution to develop through discussion.
This is particularly true in business-to-business projects. The customer understands their operation. The solution provider understands the technology and implementation. The best outcome often appears when both sides work through the problem together.
The best pitch may not be the one with the most slides. It may be the one that starts the right conversation.
Rejection is also information
Sales, leadership, and entrepreneurship all involve rejection. Projects are delayed. Proposals are declined. Budgets change. Customers stop responding.
The course describes the ability to stay steady through this as “buoyancy.” I found the idea practical because it does not ask us to ignore rejection or remain positive without reason. It asks us to understand the setback properly.
A lost opportunity does not always mean the solution was wrong. The timing may have been wrong. The problem may not have been urgent. The right decision-maker may not have been involved. The value may not have been explained clearly enough.
Rejection should not always be treated as a final judgment. Sometimes it is useful information for the next attempt.
My main takeaway
My main takeawayMy main takeaway from the course was simple:
Good selling is not about pushing people towards our answer. It is about helping them reach a better answer.
That requires listening, curiosity, clarity, and patience. It also requires confidence without pressure and persistence without ignoring feedback.
Products matter. Technology matters. Pricing matters. But people still make the decisions.
The better we understand them, the better we can serve them. That is the part of sales and persuasion I will remember most from this course.