Overview
Enterprise deals are won less by presenting more product than by orchestrating a buying process that feels uniquely designed for the customer. Using a hypothetical $100,000 sale to SpaceX’s legal team, Jen explains a roughly 15-step lifecycle beginning with outreach to the executive decision-maker and their direct report. The first call is treated as the highest-value discovery opportunity: no slides, demo, script, or recorder—just an informal conversation designed to uncover the organizational change the buyer wants and the executive advantage the product could create. A champion then helps co-author the demo, recruit the right stakeholders, expose internal objections, and define a tightly scoped pilot. The demo should concentrate on the 20% of the product delivering 80% of the relevant value, while the pilot should specify users, tasks, success criteria, and the path to purchase before access begins. Pricing, procurement, legal review, and signature are similarly project-managed rather than left to unfold passively. Healthy enterprise selling also requires restraint: disqualify immature buyers, preserve consistent pricing, and accept a qualified-opportunity win rate around 25–35%. The governing principle is to slow down enough to collect superior information, then use that information to accelerate a credible, customer-shaped decision.
Sections
Recommended Actions
Concrete practices for running an enterprise opportunity from outreach through signature.
- Write a two- or three-sentence outreach message that names the required organizational change and the executive advantage your product unlocks; have the founder contact the executive while the enterprise seller contacts the N-minus-one.
- Run the intro call without slides, a demo, or a recorder; let the buyer speak first and use the conversation to test urgency, maturity, desired change, and executive value.
- Schedule a champion preparation call before the group demo to map stakeholders, priorities, questions, risks, and the narrow product capabilities worth showing.
- Design the pilot around three or four power users, explicit tasks, individual onboarding, shared success criteria, and a pre-agreed purchasing timeline.
- Prepare procurement before momentum fades: identify legal, security, procurement, and signature owners; send editable contract paper; and resolve material redlines live where possible.
- Audit sales performance by examining time and conversations between intro and demo, whether each demo has an account-specific rationale, pilot conversion, and qualified-opportunity win rate.
Higher-Order Insights
Broader implications derived from the proposed sales system.
- Enterprise sales resembles product management: both require discovery, synthesis, stakeholder alignment, sequencing, and the removal of work from the customer’s plate.
- The seller’s defensible advantage is often accumulated customer-specific information rather than a universally superior pitch. Each additional conversation increases that advantage when it changes the narrative or next action.
- The CRM’s five stages describe forecast probability, not the customer journey. Treating them as the actual sales process erases the preparation, alignment, evaluation, and contracting work that determines the outcome.
- Natural improvisation becomes more valuable as contract size rises because enterprise buyers judge how well the seller understands their specific organization, not merely how consistently a standard script is delivered.
Failure Modes
Common ways enterprise opportunities lose value, momentum, or credibility.
- Entering through stakeholders below the executive or N-minus-one can distort the opportunity around user convenience rather than fundable executive value.
- Moving directly from an intro call to a generic demo sacrifices leverage, stakeholder alignment, and customer-specific intelligence.
- Showing the entire product can expose irrelevant functionality and cause buyers to discount the package as partially unusable.
- Starting a pilot without a defined purchase path can exhaust momentum months before the buyer is able to commit.
- Using a forward-deployed engineer to compensate for an unusable product can destroy the economics of a $100,000 deal.
- Starting implementation before procurement and signature creates payment and authorization exposure.
Important Tradeoffs
Explicit alternatives discussed in the interview and the conditions favoring each.
- Top-down selling reaches budget authority and executive priorities, whereas lower-level entry points tend to produce user-value feedback and message distortion.
- A lightweight pilot should run for two or three days without charge, while an integration-heavy evaluation should run for one or two months as a paid engagement credited toward the final contract.
- Cost-oriented products compete on acceptable adequacy for low-priority work, while high-value products address consequential risk or strategic outcomes and can command materially higher prices.
- Forward-deployed engineering is economically justified when it removes customer effort in a large, complex engagement, but becomes dangerous when required merely because a modestly priced product is difficult to use.