Sales as Product Design: How Founders Misread Customer Demand

Pain Is Not Demand

Entrepreneurship doctrine has long encouraged founders to search for severe, expensive or persistent customer pain. Find a sufficiently painful problem, the reasoning goes, and customers will welcome a remedy.

But customers tolerate an astonishing amount of inconvenience. They complain about outdated systems, inefficient processes, poor service and costly workarounds while continuing to live with all of them. As one of Rob Snyder’s mentors memorably put it, “Bitchin’ ain’t switchin’.”

A complaint may reveal dissatisfaction, but it doesn’t necessarily reveal intent. The more consequential signal is action: Has the customer made the issue a priority? Is someone responsible for addressing it? Has money, time or political capital been committed? Has the customer examined alternatives?

Instead of searching primarily for pain, founders should look for something “more like a project on their to-do list or a priority.” This reframes demand as movement rather than sentiment. A customer who dislikes a product but has no plans to replace it represents weak demand. Another who describes the problem less dramatically but has assembled a team, evaluated vendors and established a deadline may represent a genuine opportunity.

Why Customer Research Can Mislead

This distinction helps explain why apparently rigorous customer research sometimes produces weak businesses. Founders can spend months gathering feedback, testing concepts and collaborating with prospective customers while avoiding the one interaction that creates clarity: asking someone to buy.

The methods seem logical. The problem is that customers can participate generously in research without experiencing the urgency necessary to change their behavior. They may praise a concept because it sounds useful, agree to a pilot because the cost is low or offer feedback because they want to be helpful. None of those actions carries the meaning of a purchase. Customers are often polite, and their enthusiasm in an interview is a false positive.

Companies also tend to ask customers questions that confirm the company’s preferred story. Once a team has invested in a product, it becomes difficult to separate what the customer wants from what the company hopes the customer wants. “It’s extremely difficult for anyone in a company to think about ‘what the customer is buying’ without polluting their understanding with details about their product, vision, and what they want the customer to want,” Snyder observed. Founders can spend months “feeling productive doing customer research, experiments, and design partnerships” only to discover that few people will purchase what they have created.

Sales Is a Form of Product Design

The fastest way to uncover that difference is through selling, a discipline that many founders have been taught to postpone or distrust. Sales is frequently portrayed as persuasion: overcoming resistance, creating urgency and convincing reluctant people to purchase something. Under that definition, it can seem both distasteful and strategically inferior to product development or marketing.

“When you don’t understand sales, sales seems gross and scary,” Snyder said. “It feels pushy, like you’re greedily convincing someone to buy something they don’t want or need.” But effective selling begins with the assumption that persuasion has limits. Customers buy because they are already trying to accomplish something and require help. The salesperson’s role is to understand that objective, determine whether the product can help and make it easier for the customer to decide. “Most sales reps will tell you they’ve never convinced anybody of anything that person wasn’t already convinced of,” Snyder said.

Seen this way, sales is not an activity that follows product design. It’s part of product design. Every serious sales conversation reveals what customers are attempting, which alternatives they have considered and why those options remain inadequate. Founders who delay those conversations risk producing a polished answer to a question no buyer is urgently asking. “Sales is the most effective way for a founder to design something a potential customer will actually buy,” Snyder explained. When entrepreneurs wait too long to sell, they may learn that nobody wants the product.

Untangling What Customers Are Really Buying

Customers rarely present their intentions in clean, analytical language. They arrive at sales conversations carrying years of frustrations, partial solutions, and organizational constraints. Snyder calls the resulting complexity a “demand hairball.” His PULL framework is intended to untangle it. The founder identifies the Project on the customer’s to-do list, asks why it has become Unavoidable, examines the List of options already considered, and identifies the Limitations that make those options inadequate. Together, these questions expose the specific way the customer is stuck.

This process forces the conversation away from product features and toward the customer’s actual progress. It also helps founders distinguish curiosity from commitment. A potential buyer who cannot identify a project, an urgent reason to act, considered alternatives, or meaningful limitations may not yet represent demand. Using this demand as an organizing principle helps prioritize work: efforts that help customers complete an unavoidable project deserve attention, while work that merely satisfies an internal metric should face greater scrutiny. Poorly chosen targets, like measuring engineers by lines of code, can mislead the entire organization away from what customers are truly buying.