This video argues that startup founders should view sales not as a persuasion technique, but as solving a customer's problem together. Good sales does not feel like forcing something on a customer. It is a process that leaves the customer thinking, "This person understood my situation and actually helped." It also stresses that founders should not hand early sales to an executive too quickly or avoid opportunities to understand deep customer problems merely because the work is labeled "consulting."
1. The Used-Car-Salesman Prejudice
Dalton and Michael begin by discussing common mistakes and misconceptions founders bring to startup sales. Rather than reciting a standard "Sales 101" lecture, they focus on the office-hours moments when a founder's story makes them drop their heads and sigh.
Michael admits that he initially disliked the concept of sales. The word conjured images of used-car dealers, insurance agents, and high-pressure timeshare salespeople pushing customers into a purchase.
"I was a founder who was not interested in the concept of sales. I pictured a used-car dealer, an insurance salesperson, or an aggressive timeshare rep. I thought, 'I never want to act that way. That is a bad thing.'"
Many founders accept that they must sell while still carrying that negative image deep inside. They consequently treat sales not as understanding customer needs, but as an uncomfortable yet unavoidable practice of persuasion and pressure.
The two say, however, that truly good sales does not feel like sales. Think of an excellent service provider. When a customer emails a problem, the provider responds quickly, understands the situation, and helps find the required solution. The provider is certainly making money and selling a product or service, but the customer does not feel merely "sold."
"Good sales is so good that it does not feel like sales."
"When you describe a problem, they respond, 'Yes, there is a problem. Let's fix it. Let's accomplish what you are trying to do.'"
"They are clearly making money from me and selling me a product. Yet I feel as though I have met someone who understands me—a partner I can work with."
Both customer and seller finish such an exchange feeling good. The customer solved a real problem, and the company was paid for doing so. This is the video's basic model of healthy sales. 🤝
2. Selling Something That Does Not Help the Customer
Dalton is especially uncomfortable when a founder has partly recognized the customer's real problem, decides it is too hard to solve, and then tries to force a different sale. Instead of addressing the customer's genuine difficulty, the founder proposes a feature or product that is easy to build or can generate quick payment.
"I have some idea what the customer's problem is, but it is too hard and I do not think I can solve it. Still, I have to sell them something."
That behavior begins to resemble handing over something of little value and taking the money rather than conducting an exchange. Dalton explains that a transaction should leave both parties better off. If only the company makes money and the customer gains nothing, it is difficult to call it a proper exchange.
"A transaction means that after goods or services are exchanged, both sides are better off."
"If you sold someone something that gave them no benefit and only made money, can we call that a transaction? We may need a different word."
Early founders often deliver long monologues to customers, listing features without listening sufficiently and pushing for a "yes." Many also mistake discounting for the strongest sales weapon.
Lowering the price does not suddenly make a customer want a product they never wanted. The video uses a burrito analogy.
"If you are trying to sell me a burrito I do not want, repeatedly lowering the price will not suddenly make me want to eat it."
"Continual discounts make it stranger. I start wondering, 'What is wrong with this burrito?'"
Discussing price before the customer understands the product's value reverses the proper order. The customer naturally wonders, "I do not even know why this helps me. Why are we talking about price?"
The two say the very purpose of a business should be helping people. If sales feels painful, the founder may secretly be seeking payment for the least possible effort instead of helping customers. By recalling and emulating their own best purchasing experiences, more founders can become good at sales than they expect.
3. Good Sales Means Listening Deeply and Solving the Problem
The best sales founders are not the people who talk the most, the two say. They listen well and empathize. Because they understand the customer's situation and solve the real problem, the experience feels like relief.
"The founders I know who are best at sales listen, do not talk much, have great empathy, and genuinely solve customer problems. To the customer, it feels like relief."
"Good sales is good problem-solving."
Founders solve countless problems inside their companies each week: employee productivity, product development, hiring, and operations. They usually ask, "How can I help this person?" They should not switch approaches in a customer meeting and think, "How can I get out of this conversation with money while helping as little as possible?"
Customers often cannot diagnose their own problems perfectly or request the correct solution. Even when they ask for X, Y, and Z, the founder must help determine whether those things will truly help the business. The person in the conversation may not fully understand their company's broader problem.
"The customer may say, 'I want to increase revenue. I am not sure how.'"
"A customer may ask you to do X, Y, and Z, while you know those things will not really help the company. Treat that as a problem-solving situation."
This is where the old advice to put yourself in the customer's shoes matters. Rather than nodding at it as a pleasant cliché, take it seriously as though you were hearing it for the first time.
"Receive the advice to put yourself in the customer's shoes as if you had truly never heard it before."
"Act like a method actor. Imagine that person walking into the meeting room."
Imagine what is piling up in the customer's inbox, what their boss tells them to worry about, and what pressure awaits in the next meeting. You must enter the reality of their business to judge where your product genuinely helps.
Michael asks founders, "What would you think about if you were the CEO of the company buying your product?" Many founders then reveal that they know little about the customer's business model, essential priorities, or the CEO's top three concerns.
"Tell me about the customer's business. You say your product will help it, yet many people know nothing about that business."
"Are you helping the customer, or are you pursuing your own goals while treating theirs as secondary?"
A founder can still achieve visible milestones such as seed funding, hiring, and a Series A with this attitude. But to win on a large scale and survive for a long time, they must wake up from treating customer success as incidental.
4. Copying a Bad Product or Underestimating Its Value
Founders also become confused when a company thrives despite having a product they personally find terrible. They begin to think, "Perhaps we should succeed by doing what they do."
"We used the product, and it was awful. We did not like it. But the company is doing well. Should we copy their approach?"
The two warn against judging a company's success from only the few steps visible in front of you. A product may look bad or be poorly designed while delivering some other vital customer value. In B2B software especially, a product users find inconvenient may still provide major savings, regulatory compliance, operational stability, or integration benefits at the company level.
"If a company is winning, you may not understand the value it creates for customers. Do not therefore declare that value to be zero."
"Dismissing an entire product because the design is bad is a common mistake."
Blindly copying a competitor is dangerous, but so is concluding, "That product is garbage—why is it winning?" simply because you do not understand it. The important work is to investigate what customer problem is actually being solved.
5. Why Founders Should Not Hand Off Sales Too Soon
Once a company grows slightly and closes a few deals, founders often decide it is time to hire a VP of Sales. They expect an experienced executive to build the team and grow revenue because sales is not their own specialty.
"We raised some money and sold a little. Isn't it time to hire a head of sales? I am only the founder; they can build the sales team and do everything."
The two respond somewhat cynically. A "VP of Sales" title does not mean someone can discover the sales motion from scratch in a startup where neither product nor market is settled. An executive from a large or already successful company may excel at operating a team, hiring, setting targets, and meeting quotas. Running an existing system and discovering how to sell from first principles are different capabilities.
"What they are actually good at is running a team, hiring people, and managing them."
"In a new startup without an established playbook, it is hard to assume those skills will transfer. More strongly: they generally do not."
Michael believes that many B2B companies eventually become enterprise companies serving large customers. CEO and founder involvement in this market is far greater than many expect. Huge contracts at a company such as Palantir do not come merely from junior salespeople processing website leads. CEO-level people create opportunities, open important relationships, hand work to a team, and return to fix matters when something goes wrong.
"I was amazed by how much founder- and CEO-level involvement and sponsorship went into those huge contracts."
"The CEO personally creates or discovers the opportunity, hands it to the team, and comes back to solve the problem when the deal becomes tangled."
The sales organization should therefore not be an independent machine separated from the founder. It should be designed to amplify the founder's relationship-building and problem-solving ability.
When a salesperson asks, "How can I personally meet this important CEO?" the question should change. That CEO may have little reason to meet a mid-level sales manager. Ask instead, "What can I do to help our CEO meet that CEO?"
"Why would an important CEO meet a mid-level salesperson? Even your company's CEO might struggle to get that meeting."
"Change the question: 'How can I help our CEO secure this meeting?'"
The advice that founders must sell does not mean closing a few early deals and handing everything over. As the company grows, founders must continue playing a central role in important customer relationships and complex transactions.
6. The Trap in "Consulting Is Bad"
The final topic is the startup maxim "Do not do consulting." When founders encounter customer-specific integrations, lengthy implementations, or unusual requirements, they often dismiss them at once: "That is consulting, so we should not do it." Michael says this is repeated as though it were self-evident and required no examination.
Dalton recounts an experience with Disney at his first startup. Disney wanted a white-label social network where park fans could communicate and share tips. Disney wanted complete control and had highly specific requirements. The contract might have been worth millions of dollars, but Dalton's team declined it.
"Disney wanted to outsource all of its R&D to us instead of letting our startup own a product."
"They wanted extremely customized, specialized software no one else would want. That is clearly a bad business."
The real lesson is not to build entirely unrelated features exactly as a large customer dictates. Work that cannot be reused for other customers, does not connect to product strategy, and merely substitutes for a customer's internal engineering team is dangerous.
It is also a serious mistake to stretch this principle into "Deep integration is consulting, so avoid it" or "Customer-specific work is not product." The two say there is a broad gray area between consulting and product, and each case must be judged on its merits.
"There is a great deal of gray between consulting and non-consulting. Do not instantly dismiss something because it is 'consulting'; evaluate each case with an open mind."
Michael takes a more aggressive position. For an early startup, nine times out of ten the work is not really consulting but an opportunity to learn a customer problem deeply and develop the product.
"Just do the consulting. Nine times out of ten, you will not truly be doing consulting."
"Especially early on, you are gaining an opportunity to learn the problem. That is uniquely valuable. Trust your ability to productize it over time."
He says deep integration can itself become a moat, a defense competitors cannot easily cross. A long sales cycle is not automatically a drawback either. Once enterprise customers integrate a system deeply, moving to another product becomes difficult. You cannot point out that companies take decades to escape systems such as SAP while also saying that you dislike long sales cycles and deep integration. Those are part of the game.
"Deep integrations are deep moats. Long sales cycles are moats too."
"You cannot ask why it takes someone so long to leave SAP while saying you dislike long sales cycles and deep integrations. That is part of the game."
Michael believes Palantir may have pulled ahead partly because many companies avoid this complex sales and implementation work. The definition of "consulting" can of course remain ambiguous. If a custom project can be built and operated in a few days at high margin, it may not be bad consulting at all.
The more important criteria are whether the work solves an important customer problem, can generalize to other customers and the product, and moves the company in an interesting, scalable direction.
"The problem is not whether it is consulting. The problem is ending up alone in a corner, making money without solving a particularly important problem."
"If the work does not lead to something more interesting and generalizable, that is the real issue."
7. Transactions Where the Customer and Company Both Win
The two close by reducing the video's message to two principles.
First, excellent sales should feel like problem-solving. Founders must build a business that continually solves customer problems; otherwise, they are unlikely to win.
Second, business and transactions must rest on an exchange that leaves both sides better off. Meeting the company's monthly growth target and increasing revenue does not necessarily mean the customer won. Customer success cannot be dismissed as a matter the customer must solve alone.
"Excellent sales feels like problem-solving. You must be in the business of solving customer problems. Otherwise you cannot win."
"Both sides should be better off when the transaction ends. Design it that way."
"Do not think, 'We hit our 15% monthly growth target, so we won.' You may not know whether the customer won too."
The sales capability founders need is not flashy rhetoric or a huge discount. It is the ability to understand the customer's reality deeply, listen well, identify the real problem, and build a solution in which customer and company win together. That is how great founders approach sales.