Pete Kuman’s talk walks early‑stage founders through a practical, step‑by‑step sales process for winning their first enterprise customers. He argues that technical founders are uniquely qualified to sell because they possess deep problem expertise and genuine conviction, and that selling is a learnable skill rather than a dark art. The process begins with forming a clear sales hypothesis, then prospecting for companies and individuals that match it—using tools like BuiltWith, Apollo, or LinkedIn Sales Navigator and prioritizing warm introductions over cold blasts. Outreach should aim to generate inbound interest (content, demos, forum participation) and, when cold emailing is necessary, keep messages short, personalized, and something you’d be excited to receive. Qualification calls focus on discovering the prospect’s problem, budget, and decision‑making authority—not pitching. A successful demo tells a personalized story that shows how the product solves the prospect’s specific pain points, rather than touring features. Pricing is treated as an experiment: ask cost‑impact questions first, start with a number that feels slightly uncomfortable, and learn from the prospect’s reaction. Closing requires understanding the prospect’s procurement process early, keeping legal documents simple, and leveraging your champion to move things forward. Finally, implementation follows the signed deal, turning the prospect into an active user. Throughout, the emphasis is on listening, experimentation, and treating sales as a collaborative problem‑solving activity.
1. Pete Kuman is a group partner at YC and a YC Alum.
2. He was co‑founder and CTO of Optimizely in the winter 2010 batch.
3. The talk walks step by step through the process of closing your first Enterprise customers.
4. The sales funnel steps covered are prospecting, outreach, qualification, pricing, closing, and implementation.
5. Prospecting means finding potential customers and producing a list of companies and specific humans who might need and buy the product.
6. A sales hypothesis states: customer X has problem Y and our product will help them solve it.
7. At Optimizely the initial hypothesis was that marketers at small and medium tech, media, and e‑commerce companies wanted to run A/B tests on their websites but could not because off‑the‑shelf tools required coding.
8. Optimizely would enable them to run A/B tests without writing code.
9. One way to identify likely companies is to buy industry lists and filter them with criteria.
10. Optimizely used Builtwith to check whether prospects used analytics tools and JavaScript frameworks as signals of sophistication.
11. After obtaining a company list, the next step is to find the right humans at those companies and their contact information.
12. Tools such as Apollo and LinkedIn Sales Navigator are used by founders to get lead contact details.
13. Outreach aims to schedule a meeting with a prospect.
14. The easiest way to get a meeting is to get the prospect to reach out to you.
15. Generating inbound demand can be done by launching early and often, creating technical content, building self‑served demos, and participating in online forums.
16. If customers gather at industry conferences, founders should attend and obtain attendee lists ahead of time to set up meetings.
17. When contacting a specific prospect, first try to find a warm introduction via shared connections on LinkedIn.
18. Cold emails should be written by hand, be short and to the point, make the ask clear, and explain why you are reaching out to each recipient.
19. A rule of thumb for cold emails is to only send emails that you yourself would be excited to receive.
20. An anti‑pattern seen among YC founders is talking to anyone who will take their call, which selects for people easiest to talk to rather than those who will be great customers.
21. Talking to easy‑to‑talk‑to customers can create the illusion of progress while providing useless or counterproductive feedback.
22. Trying to sell enterprise software to startups is a waste of time if the problem only appears when companies become large (e.g., an HR information system).
23. Selling bottom‑up with a product that requires top‑down adoption (e.g., hospital software) is ineffective if you only talk to individual contributors.
24. For products needing organization‑wide coordination, you must talk to senior leaders such as a CIO or CFO to close a deal.
25. On the first call, the goal is to qualify the prospect by determining whether they have the problem, budget, and decision‑making authority, and to schedule a follow‑up call for a product demo.
26. Founders often mistakenly dive into their pitch on the first call instead of asking questions.
27. Effective sales involve listening and asking questions to understand the prospect’s problem, budget, buying process, and decision makers.
28. Questions to ask include: what made you take this call, how long have you had the problem, how bad is it, who else is affected, how do you quantify impact, why haven’t you solved it, what is your budget, how does your organization buy software, who makes the buying decision, and who else must weigh in.
29. If the prospect does not have the problem, budget, or authority, ending the call saves time for both parties.
30. When the prospect does have a solvable problem, the next step is a product demo.
31. The purpose of a demo is to convince the audience that you can help them solve their problem, not to show off the product.
32. A helpful demo approach is to think of it as a movie script: start with a recap of the user and their problem, then tell a story showing exactly how the user solves the problem with your product.
33. Demo features should each have a clear reason for being included; the demo should feel like a good story with a flow and one or more “magic moments” that surprise the audience.
34. Great demos are personalized, using information gathered on the first call such as the prospect’s logo, website, customer names, and team member names.
35. An example from Optimizely’s early days: they built a feature to demo the product directly on the customer’s website instead of a dummy site, which impressed marketers.
36. After a successful demo, the next step is to discuss pricing.
37. There is no simple formula for pricing; you can make the job easier by asking earlier questions such as: how much is this problem costing your company, how many people maintain your in‑house solution, what is your budget for solving it, and how much are you spending on a competitor.
38. Treat each pricing conversation as an experiment: test a price point and learn from the prospect’s reaction.
39. In Optimizely’s early days they offered published self‑serve pricing for a basic version and an Enterprise plan that required a sales conversation, without publishing Enterprise pricing to retain flexibility.
40. A common pricing mistake is charging too little or offering the product for free in exchange for feedback.
41. When a customer truly wants your product, a high price does not scare them away; higher prices can help identify customers who desperately need a solution.
42. Important pricing conversations often happen without you present; you can help your champion by providing slides or a one‑pager that explains your pricing, product overview, and benefits.
43. In the beginning, pick a price that makes you a little uncomfortable and observe the prospect’s reaction; it is okay to let them negotiate you down.
44. Closing a deal is not a single conversation; it includes all steps from the prospect’s decision to buy until they actually purchase, such as security, privacy, legal reviews, and compliance signoff.
45. A frequent founder mistake at closing is being surprised that a deal thought done is not actually done and may take weeks or months or fall through.
46. To avoid surprise, ask the prospect upfront how they buy software and who needs to sign off.
47. Move through procurement quickly by asking explicitly if steps like security questionnaires can be started early and executed in parallel.
48. Keep legal documents simple; use open‑source templates from YC’s Common Paper, keep timelines and scope out of the legal contract, and place them in an order form or shared project‑tracking document.
49. Your prospect who becomes your champion is your biggest ally; stay in constant communication and ask them for help when something gets stuck.
50. After obtaining a signature, the next phase is implementation, during which the customer starts using the product.