Enterprise Sales | Startup School
- Aisha Washington
- 1 day ago
- 6 min read
Enterprise sales can appear forbidding to an early-stage founder. The process involves unfamiliar terminology, multiple decision-makers, lengthy reviews, and contracts that may stall even after a customer has agreed in principle. Yet Pete Koomen, a Y Combinator group partner, YC alumnus, and co-founder of Optimizely, argues that selling is not an innate talent reserved for charismatic professionals. It is a practical skill that founders can develop.
Drawing on lessons from Optimizely, Koomen maps the journey from identifying a plausible buyer to helping that customer achieve a successful rollout. His central message is especially relevant before product-market fit: founders should lead sales themselves. At that stage, the pitch still depends on product vision, technical credibility, rapid experimentation, and a direct feedback loop between customer conversations and product development.
Why Early Enterprise Sales Belongs to the Founder
Before a startup has found a repeatable market, its sales process is still a collection of hypotheses. The company does not yet know exactly which organizations feel the problem most acutely, which people will champion a solution, what they will pay, or which objections will repeatedly block a purchase.
A conventional sales hire may struggle in this environment because there is no established playbook to follow. Founders, by contrast, can revise the product, reinterpret feedback, change positioning, and make credible promises about the company’s direction. Technical founders also possess advantages that are easy to underestimate: they understand the problem deeply, can answer detailed questions, and often communicate genuine conviction that the product can work.
Koomen organizes founder-led selling into six connected stages: prospecting, outreach, qualification, pricing, closing, and implementation. Each stage produces information that should improve the next attempt.
Prospecting Begins With a Testable Customer Hypothesis
Prospecting is more than compiling a list of recognizable companies. It starts with a precise theory about who experiences the problem and why the startup is positioned to solve it.
Koomen illustrates this through Optimizely’s early premise. The team believed that marketers at small and midsize technology, media, and e-commerce businesses wanted to conduct website experiments but were constrained by tools that required programming. Optimizely proposed a way for those teams to run A/B tests without writing code.
A useful sales hypothesis identifies four elements: a group of companies, a specific person inside them, a meaningful obstacle, and the promised improvement. That level of clarity helps founders avoid pursuing every organization that could theoretically use the product.
Once the hypothesis is defined, founders can build a target account list using industry directories and relevant filters such as company size, technology stack, geography, or business model. The next task is to identify actual people rather than treating an organization as a faceless lead. Tools such as Apollo and LinkedIn Sales Navigator can help locate relevant roles and contact details, but the tool matters less than selecting someone close to the problem and capable of advancing a purchase.
Outreach Should Earn a Conversation
Inbound interest can be cultivated before a startup has a large marketing operation. Koomen recommends publishing technically credible material, offering a self-service demonstration where appropriate, and contributing useful expertise in communities where prospective customers already spend time. The purpose is to make the founder and company discoverable through genuine subject knowledge.
Industry conferences can also be valuable, particularly when meetings are arranged before the event. Warm introductions remain powerful because they transfer a degree of trust. When neither channel is available, thoughtful cold outreach can still succeed.
An effective cold email is brief, specific, and easy to act on. It should show why the recipient was chosen, connect the product to a recognizable business problem, and make one clear request. Heavy automation may increase message volume, but it can also erase the relevance that makes an unfamiliar recipient respond.
Founders must also learn that activity is not the same as progress. Some prospective users offer extensive feedback without having the need, budget, or influence required to become customers. Others may like a product personally even though adoption requires approval from senior leadership. Koomen advises concentrating on accounts where the problem is real, money is available, and someone can navigate the decision.
Qualification Is a Discovery Process
The first substantive call should not be dominated by a product presentation. Its primary purpose is to determine whether the prospect and the startup are a genuine match.
Founders frequently begin pitching too soon because explaining the product feels safer than asking probing questions. Koomen reframes sales as collaborative diagnosis rather than persuasion. A strong salesperson listens carefully enough to understand the customer’s current situation, the cost of leaving it unchanged, and the urgency attached to solving it.
Useful questions explore how the organization handles the problem today, who is affected, what has already been tried, and whether funding has been allocated. Founders should also understand who owns the decision and what event, deadline, or strategic priority might create urgency.
Disqualification is a productive outcome. Ending an unlikely opportunity protects time that can be invested in better prospects, while forcing a weak fit through the funnel often creates trouble later.
When qualification reveals a compelling need, the demo should extend the discovery conversation. Koomen suggests treating it like a carefully constructed story rather than a tour of every feature. The user is the protagonist, the existing workflow is the conflict, and the product enables a better outcome. Each screen or capability should have a reason to appear.
Personalization makes that story more believable. Using the prospect’s own context, data, terminology, or workflow allows the audience to picture adoption inside its organization. The strongest demos contain a memorable moment when the product resolves a difficult task with surprising ease. Success is not measured by how many features were shown, but by whether the buying team believes its problem can be solved.
Pricing Is an Experiment in Value
Early pricing rarely emerges from a perfect formula. Koomen encourages founders to learn about value by asking what the problem currently costs, how many employees maintain internal workarounds, what budget exists, and how much the company spends on competing approaches.
These questions anchor price in economic impact rather than development effort. They also reveal whether the supposed pain is important enough to command resources.
Publishing fixed prices too early can limit this learning. Before the startup understands customer segments and usage patterns, pricing conversations are experiments. Founders can test different structures and observe both willingness to pay and the objections each proposal produces.
A common early mistake is charging very little—or nothing—in exchange for feedback. That arrangement may attract friendly participants without proving that the product addresses a priority. A meaningful price creates a stronger test of demand and tends to produce more serious engagement from the customer.
Pricing does not need to become an endless intellectual exercise. A concise deck or one-page document can explain the commercial terms, product benefits, and expected value in a format the internal champion can circulate. The immediate goal is to keep learning while making the offer understandable.
Closing Continues After the Customer Says Yes
In enterprise sales, verbal agreement is the beginning of closing, not its conclusion. Larger organizations may require procurement approval, security assessment, privacy review, legal negotiation, and compliance sign-off. Smaller buyers can move faster, although their lawyers may still revise contractual language.
Founders should map this process before assuming a deal is complete. Koomen recommends asking who must approve the purchase, what documentation they require, and whether time-consuming steps—such as a security questionnaire—can begin immediately.
Simple legal documents can reduce friction, and established open-source templates may provide a practical starting point. Koomen also advises separating changing operational details, such as project timelines and implementation scope, from the core legal agreement where possible.
Throughout procurement, the internal champion is the startup’s most important ally. That person understands the organization, can reveal hidden objections, and can help coordinate stakeholders. Frequent communication makes it less likely that an apparently healthy deal will quietly lose momentum.
Implementation Is Part of the Product Promise
One of the most damaging founder errors is treating deployment as the customer’s responsibility. A company does not purchase software merely to possess it; it purchases an outcome. If the product is never adopted successfully, the original business problem remains unresolved.
Implementation planning should therefore begin during sales discovery. Founders need to ask what technical work, process change, training, data access, and executive support will be necessary. Marketing, engineering, security, and other relevant leaders may need to contribute before the contract is signed.
Koomen recommends turning deployment into a shared project with a written roadmap, named owners, explicit milestones, and recurring check-ins. The startup should treat the rollout as a high-priority internal initiative rather than handing over credentials and hoping for the best.
This approach improves the customer’s chance of realizing value and exposes product friction early. It also supports retention, references, expansion, and a more accurate implementation playbook for future accounts.
Learning Sales by Practicing It
Koomen’s framework presents enterprise sales as a disciplined sequence, but founders should not wait until every step is perfected. The skill develops through conversations, missed deals, pricing mistakes, difficult objections, and successful deployments.
Reading can accelerate that development; Koomen specifically recommends Peter Kazanjy’s Founding Sales, which is available online. Still, practice supplies the feedback that theory cannot. Each interaction helps a founder sharpen the target market, improve the story, recognize stronger buyers, and anticipate organizational barriers.
Over time, selling becomes less mysterious. It becomes another system the company can observe, test, and refine—and, for a founder who learns it well, a durable strategic advantage.
