Context

Jen Abel, co-founder of Jellyfish and GM of enterprise sales at State Affairs, returns to Lenny's Podcast for a third conversation, this time walking through the entire enterprise sales cycle step by step using a hypothetical example: selling a $100K AI legal tool to SpaceX's legal department. Where most teams think of enterprise sales as five CRM pipeline stages (intro, demo, proposal, contracting, closed), Jen breaks it into roughly 15 distinct steps, arguing that treating the five-stage funnel as an actual sales process, rather than a forecasting tool, is the single biggest reason most founders and sellers underperform in the enterprise. For a PM, the episode is really a masterclass in structured discovery, information asymmetry, and stakeholder management, skills that map directly onto product discovery and cross-functional influence, not just closing deals.

The Big Idea

The standard five-stage CRM pipeline (intro, demo, proposal, contracting, closed) is a forecasting tool for weighting deal probability, not an actual playbook for running an enterprise deal, and the real cycle is closer to 15 distinct steps built around continuously extracting information ("alpha") from the buyer at every stage.

Jen estimates 90% of salespeople and founders run enterprise deals as if the five CRM stages were the process itself, jumping straight from an intro call to a demo. The sellers who win instead treat every touchpoint, including calls most people skip entirely (a pre-demo prep call, a post-demo debrief, a pre-pilot planning call), as an opportunity to gather more information than any competitor has, then use that information to make the product and the pitch feel purpose-built for that specific buyer.

Key Insights

Target only two people, using the pincer model

Jen argues there are exactly two viable entry points into an enterprise account: the top decision-maker (the executive who owns the budget) or their direct report, one level removed ("N-minus-one"). Going further down the org risks losing the message in a game of telephone and means learning about user-level value instead of the executive-level value that actually unlocks a six-figure budget decision. Her "pincer model" is to approach both simultaneously, ideally the founder reaching the executive directly while an account executive reaches the N-minus-one, so that whichever contact responds first can pull the other person in ("I heard that name before, I got that email too").

Sell the alpha, not the problem

• What: Jen distinguishes between naming a problem you solve and articulating the "alpha," the specific unfair advantage or new way of thinking about the business unit that an executive can personally stand behind and use to justify sponsoring a new vendor.
• Why it matters: every vendor pitching an executive claims to solve a problem, which makes problem-framing feel like a commodity. An executive bringing in a new tool is taking on real risk, so they need something bigger to defend to their own boss or board, not "we'll reduce the time spent on X."
• Example: the opening outreach has to fit two to three sentences and answer, specifically, what this executive uncovers or unlocks by bringing in a net-new tool, not a generic AI-mandate pitch.

The first call is for intelligence, not pitching

Jen runs the intro call as an informal, unscripted 30-minute conversation with no slides, no demo, and explicitly no recorder, because a recorded call makes people less open and less vulnerable. She always lets the buyer speak first ("would you like to go first?") so she can shape her framing around what they actually reveal, and she deliberately avoids anchoring the conversation toward her own product too early, since the goal is to keep pulling on threads (why does this need to change now, why not wait another year) until the buyer reveals their real internal priorities. All the information leverage a seller will ever get from a buyer comes from this first call. Once a deal starts to feel like a formal sales process, buyers become guarded.

Show only the 20% of the product that matters

When running the actual group demo, Jen's rule is that 80% of the value comes from 20% of the product, and that 20% should already be known from prior discovery calls with the buyer's team. Demoing the full product risks a stakeholder objecting to paying for capability they'd never use, which can unravel the entire narrative the seller spent weeks building. She also insists on co-authoring the demo agenda with the internal champion beforehand (a 15-minute pre-demo call to confirm exactly which features to show and what questions to plant), so the eventual group demo already reflects the specific priorities of the people in the room.

Healthy win rate is 25 to 35%, not higher

Jen states that a healthy enterprise win rate, from qualified opportunity to signed contract, runs between 25% and 35%. If a seller's win rate is meaningfully higher than that, she treats it as a sign the price is set too low, since a large portion of any real market genuinely isn't ready to buy yet (organizational immaturity, timing, budget cycles) and pricing to win nearly everyone means leaving money on the table with the buyers who would have paid more.

Mental Models & Frameworks

The real 15-step enterprise sales cycle

• 1. Landing the meeting: pincer outreach to the executive and N-minus-one with a two-to-three sentence alpha pitch.
• 2. Intro call: unscripted 30-minute discovery, no demo, no recorder, buyer talks first.
• 3. Follow-up intro call: a short pre-demo planning call with the champion to co-design what gets shown.
• 4. Prepping the pitch/framing the demo: aligning the narrative to what specific stakeholders in the room care about.
• 5. Running the demo: showing only the highest-value 20% of the product, reframed in the buyer's own language.
• 6. Post-demo debrief: calling the champion within minutes for a raw, unfiltered reaction.
• 7. Identifying the pilot process: defining who runs the pilot and what "success" means before it starts.
• 8. Prepping the pilot: reverse-engineering the signature timeline and assigning three to four specific named users and tasks.
• 9. Running the pilot: a tightly scoped two-to-three-day (or paid 30-day, for integration-heavy products) hands-on trial.
• 10. Post-pilot session: reviewing actual usage data against what was promised, using the champion to check on disengaged users.
• 11. Papering prep: documenting the agreed timeline and pricing in writing, sending a Word document (not a PDF) so buyers can redline.
• 12. Papering review: getting legal on a live call to resolve redlines faster than email back-and-forth.
• 13. Papering procurement process: working directly with procurement and legal leads to negotiate contract terms.
• 14. Signature: confirming the actual signatory in advance so delays get caught early.
• 15. Expansion planning: deciding, often with the founder involved for a company's first ten enterprise deals, what services or product expansion comes next.

Use this as a checklist for auditing your own sales motion: if a deal skips straight from step 2 (intro call) to step 5 (demo) without steps 3 and 4, that missing planning call is very likely where deals are being lost to a demo that doesn't land.

Alpha as the currency of enterprise trust

Throughout the cycle, "alpha" functions as Jen's term for asymmetric, hard-to-get information, both what the seller learns about the buyer's real priorities, and what the buyer gets that makes the product feel built specifically for them. Every step of the 15-step process (the pre-demo call, the post-demo debrief, the pre-pilot planning session) exists primarily to generate more alpha than a competitor has gathered, which is what lets a seller reframe a generic product into something that feels custom-built by the time the group demo happens.

Trade-offs & Nuance

Free short pilot versus paid extended pilot

For products that show value quickly, Jen prefers a free two-to-three-day pilot restricted to three or four actual end users (never the executive sponsor, who isn't the user), arguing this shortens the sales cycle by weeks compared to an open-ended trial. But for products requiring real data integration or configuration to demonstrate value, she recommends charging for a 30-to-60-day pilot and crediting that fee back if the deal closes, on the reasoning that willingness to pay for a pilot is itself a strong buying signal, and it's mostly compensating for the services work the integration requires anyway. The trade-off is cycle speed and seller control (short pilot) versus a more realistic proof of value plus a paid-pilot signal (long pilot), and the right choice depends on how integration-heavy the product genuinely is, not on seller preference.

Forward-deployed engineers as a signal, not a strategy

Jen is skeptical of using forward-deployed engineers (FDEs) as a default sales motion, distinguishing between an FDE deployed to accelerate and control an already-good rollout (fine) versus one deployed because the product is too hard to use without hand-holding (a bad sign). She notes the economics only work at Palantir's multi-million-dollar deal sizes; using an FDE-style motion on $100K deals breaks the unit economics the same way staffing a full-time engineer against one sales relationship would. The nuance: an FDE-style approach can be legitimate for land-and-expand strategies at higher price points, but it should be a deliberate pricing and business-model decision, not something a team backs into because the account management team quietly relabeled themselves.

Common Mistakes

Mistake: pitching before listening on the first call

Jumping into slides or a demo on the very first call sacrifices the single richest window a seller ever gets for learning the buyer's actual priorities, since buyers become measurably more guarded once a conversation starts to feel like a formal sales process. Jen's fix is structural: no demo, no slides, no recorder, and always let the buyer answer first so the seller can shape everything that follows around what was just said rather than a generic pitch.

Mistake: demoing the entire product

Showing every feature in a demo, rather than the specific 20% that maps to what discovery calls revealed matters to this buyer, invites stakeholders to object to paying for capability they won't use, which can unravel a carefully built narrative in real time during the room's biggest moment. The fix is deliberately narrow scoping, informed by the pre-demo planning call, not an impulse to showcase everything the product can do.

Mistake: blaming procurement for a stalled deal

Jen points out that "it's stuck in procurement" is frequently used, by both sellers and by buyers who don't want to deliver bad news directly, as a socially acceptable excuse rather than an accurate description of what's actually happening. Procurement's job is not to kill deals, it's to verify the purchase matches how the organization is required to buy; a genuinely stalled deal usually has a different underlying cause (a stakeholder who's gone quiet, unresolved doubt) that blaming procurement conveniently avoids surfacing.

Practical Application

Build a two-sentence alpha pitch and pincer outreach

For your next enterprise target account, identify the top decision-maker and their direct report (N-minus-one), then write outreach that fits two to three sentences and names a specific unfair advantage the executive unlocks, not a generic problem statement. Send to both simultaneously (founder or most senior available person to the executive, an account exec to the N-minus-one) so whichever responds first can pull the other in.

Redesign your intro call around discovery, not demo

• Do: run the next enterprise intro call with no slides and no demo prepared, and open by asking the buyer to describe their priorities first.
• Then: dig past the first surface-level answer with follow-up questions like "why does this need to change now, and not in a year," to reach the real internal pressure driving the initiative.
• Why it works: buyers give their most honest, least guarded information before a conversation feels like a sales process, and that information is what lets you tailor everything that follows.

Reverse-engineer the signature date before starting a pilot

Before putting any users into a pilot, get on a call with your champion to work backward from an assumed successful outcome: what date would you want signatures by, who needs to be looped in from procurement or security, and what would make hitting that date worth it for them. Running this planning conversation before the pilot starts, rather than after, keeps momentum from stalling once the pilot proves the product works.

Questions to Consider

• In our own enterprise sales or stakeholder-influence conversations, are we leading with a generic problem statement that every competitor could also claim, or with something specific enough that the decision-maker could defend it to their own boss?
• Do we have a structured post-demo debrief call with our internal champion within minutes of every demo, the way Jen describes, or are we assuming silence after a demo means things are fine?
• If our current enterprise win rate is well above 30 to 35%, could that mean our pricing is too low rather than that our sales process is working unusually well?

Bottom Line

Winning enterprise deals is less about a polished pitch and more about running a longer, more deliberate information-gathering process than any competitor bothers to run, structured across roughly 15 real steps rather than the five CRM stages most teams mistake for an actual playbook.

Notable Quotes

"The worst thing you can do in the sales process when you move into demo is just go into one straight demo with no product... you just lost the deal at that point." (Jen Abel)

"If your win rate is higher than [30 to 35%], your price is too low." (Jen Abel)