Make the next buyer decision clear
A promising enterprise conversation can stall between the obvious milestones. The demo happened, but nobody checked the executive’s reaction. The pilot worked, but its users cannot approve the purchase. The proposal arrived, but nobody knows which internal process it must enter.
Jen Abel’s conversation with Lenny exposes the work inside those gaps: the preparation, smaller conversations and internal coordination that make a complex purchase possible. Her distinction between pipeline categories and the actual buying process is the foundation for this playbook.
Watch Jen explain it at 1:03:00 →
The Revenue Puzzles application is to give that work a clear operating structure. Every meaningful move should answer four questions:
| Question | What the team needs |
|---|---|
| What must the buyer decide? | A specific decision or uncertainty to resolve |
| What will help them decide? | Relevant evidence, a conversation or a working document |
| Who owns the next action? | A named person on our side and, where applicable, theirs |
| What allows us to advance? | Observable buyer evidence, with a date |
Use this for complex B2B SaaS, consulting and hybrid sales where the purchase involves several people, meaningful implementation work or material business change. The episode focuses on six-figure enterprise deals; buying complexity determines how much of this process your account needs.
The 15 deal moves below are Revenue Puzzles’ adaptation of the conversation, including a post-signature expansion move. They are a working sequence you can revisit, combine and run in parallel. The five operating sections then add CRM mapping, templates, agent responsibilities and a management cadence.
“Slow down to go fast.”
In practice, spend the extra fifteen minutes understanding a stakeholder before committing the whole buying group to the wrong evaluation.
Enter through executive value
Jen’s starting point is the senior executive responsible for the outcome, or the person one reporting level below them. She describes coordinated outreach to both levels as a pincer approach: the founder engages the executive while the sales lead engages their direct report.
Source: Jen Abel on Lenny’s Podcast, 09:30–18:30 →
Run the move
Start with the change this business unit is trying to make. Translate your offer into an outcome the executive could explain to their own leadership.
Jen uses alpha to describe the distinctive advantage a buyer gains. For this playbook, make that advantage concrete: something the team could do, decide or deliver that its current approach makes difficult.
| Offer | Executive relevance to investigate |
|---|---|
| AI account research software | Enter a new segment with enough account intelligence to focus the sales team |
| CRM and RevOps implementation | Make a growing pipeline manageable as ownership moves from the founder to the team |
| Consulting and implementation support | Launch a commercial initiative with defined ownership, delivery capacity and measurable progress |
These are Revenue Puzzles examples. Validate the business outcome and your ability to deliver it before using one in outreach.
Write two or three sentences connecting an observed trigger, a relevant outcome and a small next step. Coordinate account outreach so the founder and seller share context.
Discover the change the buyer needs
Jen recommends an informal first conversation, with the buyer speaking first and the seller adapting their explanation to what they hear. She deliberately keeps slides and the demo out of that opening discussion.
Source: Jen Abel on Lenny’s Podcast, 18:30–29:30 →
Run the move
Use roughly thirty minutes as a starting format. Explain why you reached out, invite the buyer to describe their situation, then explore what needs to change.
Questions to work from
- What does your team need to achieve over the next two quarters?
- Where does the current way of working make that difficult?
- What has made this a priority now?
- What have you already tried?
- How would you know that the change had worked?
- Who else would need to support it?
Follow the answers. If the buyer mentions a new market, explore the commercial implications. If they mention an internal mandate, ask how it translates into their team’s responsibilities.
Then explain the part of your offer that is relevant. Be specific about its limits and the assumptions you still need to test.
Jen advises keeping a recorder out of this first call to encourage openness. The Revenue Puzzles application is to agree the format explicitly, respect the buyer’s preference and document agreed facts afterwards. Keep AI capture out of conversations where it would reduce trust.
Build the plan with an internal champion
Before a group demo, Jen returns to the person she has built a relationship with. That smaller conversation helps her understand the organisation and shape the next meeting together.
Source: Jen Abel on Lenny’s Podcast, 30:00–33:30 →
Run the move
Ask for a short planning conversation. Work through who should attend, what each person needs to understand and which questions are likely to decide whether the initiative advances.
A useful internal champion helps the buying process move. Look for actions:
- They explain the organisation’s priorities and decision process.
- They introduce relevant people.
- They correct your interpretation.
- They help define the evaluation.
- They share concerns while you can still address them.
Treat championship as something to establish through behaviour. A friendly first contact may grow into that role.
Prepare the demo around the buying group
Jen sometimes adds a smaller pre-demo with another stakeholder to gather context before the full group meets. She also asks the internal partner what matters to each attendee and what a successful demo should accomplish.
Source: Jen Abel on Lenny’s Podcast, 33:30–40:00 →
Run the move
Prepare a short brief for the meeting.
| Person or role | What to establish before the session |
|---|---|
| Executive sponsor | Business outcome, internal priority and decision they need to make |
| Operational owner | How the process would work and who would own it |
| Users | Tasks they need to complete and practical constraints |
| Technical or security evaluator | Feasibility questions, dependencies and required evidence |
| Potential sceptic | Their concern and what could reasonably resolve it |
Add a separate conversation where it will close a material gap. Use your champion to coordinate access.
Choose the use cases, sequence and proof points. Write down what you are leaving for a later session so a useful detour does not consume the meeting.
Demonstrate the relevant outcome
Jen recommends showing the part of the product that matters to the buyer’s priorities. Her warning is that a broad feature tour can weaken the relevance created in earlier conversations.
Source: Jen Abel on Lenny’s Podcast, 38:30–46:30 →
Run the move
Open with the business situation you have understood. Credit the people who helped you prepare, and invite new attendees to correct or add to that context.
Then demonstrate a small number of relevant workflows. Connect each one to the outcome the team described.
| Time | Purpose |
|---|---|
| 0–10 min | Confirm the business context and hear from new participants |
| 10–30 min | Demonstrate two or three relevant workflows or deliverables |
| 30–45 min | Explore practical questions, dependencies and objections |
| 45–60 min | Agree what remains to be proven and the next decision |
Adjust this Revenue Puzzles agenda to the account. The calendar allocation should follow the evaluation.
For services: show the client what they would receive, how it would be used and what input delivery needs from them. Make the proposed outcome tangible before expanding the scope.
Debrief while the reaction is fresh
Jen recommends a prompt conversation with the internal champion after the demo to hear their candid reaction and identify people who need further attention.
Source: Jen Abel on Lenny’s Podcast, 46:30–48:30 →
Run the move
Arrange the debrief in advance where possible. Keep it short enough that it actually happens.
Ask
- Which part landed best?
- Who still has a concern?
- What did we misunderstand?
- Is there someone we should speak with before the team decides?
- What would help you organise the next step?
Turn each concern into a specific action: clarify a requirement, show a workflow, involve an expert or change the proposed scope.
Align price and the route to a decision
Jen places substantive pricing discussions after the demo and before the pilot, working with the champion on the internal business case. She also recommends understanding what a successful pilot would need to trigger before it begins.
Sources: 54:00–58:00 and 1:01:30–1:02:30 →
Run the move
Discuss the proposed scope, commercial model and likely investment before either team commits substantial evaluation effort. If price determines basic feasibility earlier, give a useful range with its assumptions.
Work through four questions:
- Can the sponsor support the investment for the outcome being discussed?
- Which budget would fund it, and who can approve that budget?
- What evidence would justify the purchase?
- If the evidence is positive, when could the organisation decide and implement?
Give the champion a concise business case they can use internally. Separate subscription, implementation, services and usage charges where applicable. Define what could change the final price.
When price is challenged, identify the reason: budget availability, scope, value, timing or comparison with an alternative. Explore a smaller scope, staged rollout or different term where those changes make business sense.
Design the proof before opening access
Jen distinguishes a short evaluation that can demonstrate value with little setup from a longer pilot requiring customer data, configuration or integration. She recommends defining tasks and success criteria with the buyer.
Source: Jen Abel on Lenny’s Podcast, 49:00–54:30 →
Run the move
Choose the smallest evaluation that can answer the buyer’s actual question.
| Evaluation | Best fit | Define before starting |
|---|---|---|
| Short product evaluation | Value is visible with limited setup and representative data | Named users, specific tasks, success criteria and a review date |
| Integrated pilot | Value depends on customer systems, data or configuration | Scope, delivery effort, responsibilities, access requirements, fee and acceptance criteria |
| Paid discovery or diagnostic | A services buyer needs a better-defined problem or implementation scope | Standalone deliverables, client inputs, decision to be enabled and the next commercial option |
Jen suggests two or three days for a lightweight product evaluation and charging for a longer, more involved pilot, potentially crediting that fee against the eventual purchase. Treat those as options appropriate to the work. A task that needs a full operating cycle cannot be meaningfully validated in an arbitrary three-day window.
Agree who will participate, what they will do, how success will be assessed and who will make the next decision. Book the results meeting before access opens.
For paid work, document the scope and authorisation for that engagement. Keep its deliverables and fees distinct from the later purchase.
Run a focused pilot
Jen recommends a small group of relevant users, deliberate onboarding and explicit tasks. In the episode’s lightweight example, she suggests three or four people.
Sources: 52:00–53:30 and 58:30–59:30 →
Run the move
Choose participants who represent the work you need to validate. Keep the executive sponsor connected to the outcome while the appropriate users perform the tasks.
Onboard each participant for their role. Make the first task obvious, provide support and collect the evidence you agreed to assess.
For each task, record:
- Whether the participant completed it.
- The result produced.
- Time or effort, where relevant to the business case.
- Quality and acceptance against the agreed criteria.
- Blockers, assistance required and unresolved dependencies.
Discuss evaluation activity transparently with the participants. Usage data can help explain an experience; ask the person what happened before drawing a conclusion.
AI product adaptation
- Output quality
- Relevant failure cases
- Required human review
- Operating cost, where it affects the decision
Services adaptation
- Test a contained deliverable or workflow
- With the people who would actually use it
- Record client input and delivery effort required
Turn the results into a decision
Jen’s post-pilot discussion brings user feedback together with what happened during the evaluation. The aim is to understand the experience clearly enough to decide what should follow.
Source: Jen Abel on Lenny’s Podcast, 1:04:30–1:07:30 →
Run the move
Review the pilot against the criteria agreed before it started.
| Result | Next action |
|---|---|
| Criteria met, purchase path confirmed | Agree scope and proceed with the required approvals |
| Criteria partly met, specific fix available | Define the fix, owner, additional test and decision date |
| Evidence inconclusive | Decide whether a bounded further test is worth the effort |
| Value shown, timing or readiness changed | Record the dependency and agree a reactivation trigger |
| Required value not demonstrated | Close the evaluation and document what was learned |
Ask the operational owner and sponsor whether the results support the business outcome. User satisfaction is one input; implementation readiness and the investment decision also need owners.
Prepare the purchase
Jen recommends equipping the champion with a forwardable summary of the agreement and a clear route into procurement. She also advises asking which party’s contract format will work best and providing an editable document for review.
Source: Jen Abel on Lenny’s Podcast, 1:11:30–1:14:30 →
Run the move
Turn the evaluation into a concise purchase brief:
- Business outcome and agreed scope.
- Evidence supporting the decision.
- Investment, term and relevant conditions.
- Implementation needs and proposed timing.
- Executive sponsor and budget owner.
- Approval steps, owners and outstanding questions.
- Target signature date and the business reason for it.
Ask whether the buyer expects your agreement, their agreement or a specific procurement package. Provide an editable version in the format their reviewers use.
Discover these requirements earlier and activate the relevant work as soon as the buyer permits. Procurement, security and legal may need to start before the pilot is complete.
For the detailed closing motion, continue with the Deal Signature Playbook.
Resolve the contract questions
Jen recommends a live discussion when substantial contract changes would otherwise create repeated back-and-forth, with appropriate legal support involved.
Source: Jen Abel on Lenny’s Podcast, 1:14:30–1:16:30 →
Run the move
Keep one agreed working version and an issue list. Route each question to someone authorised to resolve it.
| Issue type | Likely owner on your side |
|---|---|
| Price, scope, term and rollout | Commercial lead |
| Delivery responsibilities and acceptance | Delivery / implementation lead |
| Data access and technical commitments | Technical / security lead |
| Contract wording and allocation of legal risk | Legal counsel |
Agree what can be resolved asynchronously and what deserves a focused call. Bring the people needed to make decisions.
Coordinate the approval work
Jen treats procurement as part of the route to a completed purchase and payment. She also points out that vague references to procurement can conceal a lack of internal commitment.
Source: Jen Abel on Lenny’s Podcast, 1:13:00–1:16:30 →
Run the move
Maintain a separate status for each relevant approval.
| Workstream | Evidence of completion |
|---|---|
| Business approval | Accountable sponsor confirms scope and priority |
| Budget | Authorised owner confirms the funding path |
| Technical and security review | Required reviewers confirm acceptance or documented conditions |
| Legal | Required contract review completed |
| Procurement and vendor setup | Buyer confirms the purchasing requirements are met |
| Signature routing | Final document, authorised signers and routing process confirmed |
Give every open item an owner and date. Run independent reviews in parallel where the buyer’s process allows.
If an item stalls, ask for the precise dependency: an unanswered question, missing document, unavailable reviewer or changed business priority.
Confirm the signature and handoff
Jen’s final signing advice is to identify the actual signatory before routing the agreement. That person can differ from the executive sponsor.
Source: Jen Abel on Lenny’s Podcast, 1:16:30–1:17:30 →
Run the move
Confirm the final version, authorised signers, routing order and any required purchase reference. Keep the champion informed about the next action.
Record Closed Won when the purchase meets your documented acceptance and booking rules. Keep signature, implementation start, invoicing and payment as distinct events.
Hand delivery a concise record of:
- The business outcome the customer bought.
- Scope, exclusions and contractual commitments.
- Pilot findings and unresolved limitations.
- Stakeholders and their responsibilities.
- Implementation dependencies.
- First value milestone and its owner.
- Commercial terms relevant to delivery and renewal.
Earn the next expansion
After the signature, Jen discusses expansion through additional product value and, where appropriate, services. She also highlights the founder’s role in learning from early enterprise customers.
Source: Jen Abel on Lenny’s Podcast, 1:18:00–1:20:00 →
Run the move
Start with the outcome already sold. Agree a review point when the customer should have enough experience to assess progress.
Capture adjacent needs without letting them silently expand the current commitment.
| Expansion direction | Evidence to look for |
|---|---|
| More users or teams | Existing users achieve value that another group recognises |
| Additional use cases | A related problem has a clear owner and business case |
| Additional markets | The approach works locally and can be adapted elsewhere |
| Implementation or advisory services | The customer needs defined expertise to realise more value |
| Ongoing operating support | The process needs an accountable owner and continued execution |
Treat a new purchase as a new commercial decision. Confirm its value, scope, sponsor, budget and delivery capacity.
The Offer Architecture Playbook explains how to connect the starting engagement, first win and follow-on offer.
Map the moves into your CRM
The smaller conversations belong inside a manageable pipeline. Jen makes this distinction explicitly in the episode; the mapping below follows the existing Revenue Puzzles CRM playbook.
Episode source: 1:03:00–1:04:30 →
Keep the established stage structure
| SaaS stage | Work this playbook helps organise |
|---|---|
| Discovery | Understand the business situation and establish a credible buying process |
| Solution fit | Align stakeholders, shape the demo and confirm relevant capabilities |
| Business case | Establish expected value, commercial feasibility and evidence from evaluation |
| Decision | Confirm the preferred approach, decision process and required approvals |
| Commercial | Finalise terms, complete the applicable reviews and obtain acceptance |
| Services stage | Work this playbook helps organise |
|---|---|
| Discovery | Understand the problem, desired outcome and timing |
| Qualified initiative | Confirm the project, sponsor, priority and plausible budget |
| Scope / design | Define deliverables, method, responsibilities and dependencies |
| Proposal | Review the scoped offer and investment with the buyer |
| Negotiation | Resolve commercial, contractual and purchasing questions |
| Contract / SOW | Complete approval and acceptance of the final commitment |
A pilot may sit across solution fit, business case and decision. A services diagnostic may be a separately contracted first purchase. The buyer’s commitments determine the stage; the deal moves organise the work within it.
Keep initial outreach at the account and lead level. Create an opportunity once fit, commercial relevance, a plausible buying process and a mutually agreed next step are established.
Capture evidence progressively
| Point in the process | Additional information to establish |
|---|---|
| Discovery | Desired change, business impact, timing, owner and next step |
| Before the group session | Champion evidence, sponsor, stakeholder map and demo brief |
| Before the pilot | Success criteria, participants, commercial assumptions and decision path |
| Before contracting | Agreed scope, budget path, approval owners and target dates |
| Before closing | Final acceptance evidence, actual signer and delivery handoff |
Across every active deal, maintain the last meaningful buyer action, next buyer commitment, owner, due date and source of the evidence.
For a HubSpot implementation, organise the account around the Company, the people around associated Contacts and the purchase around the Deal. Use associated notes and tasks for the work. Add custom fields progressively where the team needs structured reporting.
An unanswered email is a seller activity. An introduction to the budget owner is buyer progress.
Keep four working documents
These templates are Revenue Puzzles additions built to put the episode’s ideas into daily use. Keep them short, linked to the account and updated as the buyer’s understanding changes.
A · Account and buying-group brief
| Field | Working entry |
|---|---|
| Account and initiative | Company / specific purchase being explored |
| Desired change | Buyer’s words, with source and date |
| Why now | Trigger, consequence and timing |
| Executive value hypothesis | Distinctive outcome; confirmed or still to test |
| Internal champion | Name / concrete actions taken |
| Executive sponsor and budget owner | Names / access / confirmation still needed |
| Other stakeholders | Person / role / concern / next conversation |
| Current approach and alternatives | Incumbent / internal build / other vendor / continuing as today |
| Next buyer commitment | Action / owner / date |
Keep public research, seller interpretation and buyer-confirmed information distinguishable. A hypothesis becomes confirmed when the buyer supports it with evidence.
B · Demo or solution-workshop brief
| Field | Working entry |
|---|---|
| Decision the session should enable | What the buyer should be able to decide afterwards |
| Audience | Attendees and the questions they need answered |
| Opening context | A short account-specific explanation |
| Use case 1 | Business outcome / workflow / proof |
| Use case 2 | Business outcome / workflow / proof |
| Known limitations | Dependencies, gaps and assumptions to explain |
| Questions to resolve | Who can answer each question |
| Follow-through | Proposed next decision / champion debrief |
C · Pilot charter and results
| Field | Working entry |
|---|---|
| Decision to enable | What purchase or implementation decision follows |
| Participants and sponsor | Users / operational owner / sponsor |
| Tasks | The specific work each user will perform |
| Baseline | Current result and source, where measurable |
| Success criteria | Measure / threshold / assessor |
| Scope and dependencies | Data / access / setup / customer input / exclusions |
| Timing | Ready-to-start conditions / start / finish / review |
| Commercial terms | Fee / scope / any explicitly agreed credit |
| Results | Actual evidence against each criterion |
| Decision | Proceed / defined retest / defer / stop |
Agree the criteria together. Set thresholds appropriate to the task and establish who can assess them. If there is no reliable baseline, say so and choose a test that can still support the decision.
D · Mutual action plan and internal decision brief
A mutual action plan records the steps both sides have agreed to take. Keep the buyer’s own activities visible.
| Milestone | Buyer owner | Our owner | Date | Completion evidence |
|---|---|---|---|---|
| Confirm evaluation result | — | — | — | Accepted result |
| Approve business case and scope | — | — | — | Decision recorded |
| Complete technical / security review | — | — | — | Required acceptance |
| Resolve contract questions | — | — | — | Approved version |
| Complete procurement requirements | — | — | — | Buyer confirmation |
| Execute agreement | — | — | — | Accepted agreement |
| Begin implementation | — | — | — | Ready-to-start conditions met |
| Review first value milestone | — | — | — | Outcome reviewed |
Remove irrelevant rows and add the buyer’s actual dependencies. Some milestones can proceed together.
We are evaluating [supplier / scope] to help [team] achieve [business outcome].
The evaluation established [results and evidence]. The remaining conditions are [open items].
The proposed investment is [amount, term and included scope]. [Budget owner] is responsible for confirming funding.
We are targeting [implementation date] because [business reason]. To support that timing, the remaining decisions are [decision / owner / date].
The approval we are requesting now is [specific approval]. Supporting materials: [business case / evaluation results / proposed agreement].
Use this summary only once the champion has checked that it accurately represents the internal position.
Give humans and agents clear jobs
This operating model is a Revenue Puzzles extension. Jen emphasises the human skill involved in enterprise sales and cautions against generic AI-generated outreach. Her comments reinforce the need to preserve judgment and a personal voice.
Sources: 45:30–46:30 and 1:22:30–1:23:30 →
One deal owner. Clear supporting roles.
| Work | Human responsibility | Useful agent contribution |
|---|---|---|
| Account research | Choose the account and judge relevance | Gather current information with sources; flag uncertain identities |
| Outreach | Decide the angle and write the message in their own voice | Assemble relevant facts and check claims |
| Discovery | Build trust, listen and interpret | Organise approved notes after the conversation |
| Stakeholder planning | Understand influence and coordinate access | Maintain the role map and surface missing evidence |
| Demo preparation | Choose the narrative and proof | Assemble the brief and identify unresolved requirements |
| Pilot | Agree success and handle buyer feedback | Summarise authorised results and flag incomplete tests |
| CRM and coordination | Confirm commitments and own the next action | Prepare record updates, track dates and highlight contradictions |
| Negotiation and signature | Make commercial decisions and obtain approvals | Maintain issue lists, document versions and open actions |
| Expansion | Judge customer value and the next opportunity | Bring usage, delivery and feedback evidence into the review |
Give the agent a usable deal context
Maintain an account context containing the current offer, relevant product or service limits, approved proof points, stakeholder map, latest buyer evidence and the four working documents.
Every important assertion should have a source and a date. Distinguish a public fact, a buyer statement, a seller interpretation and an unresolved question.
Review the current deal using the approved account notes, stakeholder map, evaluation results and mutual action plan.
Return: the latest confirmed buyer action; the next buyer commitment and date; missing or conflicting evidence; and the three most useful actions for the deal owner.
Cite the source and date for each factual finding. Label assumptions and unknowns explicitly. If you recommend changing the stage or close date, explain which evidence supports that recommendation and leave the decision to the owner.
Start with review and drafting support. Broader autonomy should follow a defined scope, reliable inputs and an accountable owner, consistent with the Revenue Puzzles agent operating model.
Inspect evidence every week
Use the review to decide where the team’s next effort will change the outcome.
Ask the deal owner
- What is the buyer trying to change?
- Which buyer action shows this is still a priority?
- Who is actively helping inside the account?
- Whose agreement is still missing?
- What has the evaluation proved, and what remains uncertain?
- What must the buyer do next, by when?
- What threatens the current timeline?
- What should we do, change or stop this week?
Finish with a decision: continue, resolve a named gap, change scope, move the expected date or close the current opportunity and agree a future trigger.
Track a small set of useful measures
| Measure | Definition for this playbook |
|---|---|
| Deals with a current buyer commitment | Active opportunities with a buyer-confirmed next action, owner and a due date of today or later ÷ all active opportunities |
| Days since meaningful buyer action | Days since an introduction, decision, completed test, approval or other substantive buyer milestone |
| Evaluation decision rate | Completed evaluations with an explicit proceed, retest, defer or stop decision ÷ completed evaluations |
| Stage conversion and time | Progression and time spent within comparable deal cohorts |
| Close-date slippage | Opportunities whose expected close date moved later during the review period, measured consistently |
| Qualified opportunity win rate | Won opportunities ÷ all opportunities in the same qualified-entry cohort, assessed once outcomes have sufficiently matured |
For win-rate reporting, show the cohort’s open opportunities and no-decision losses. A closed-outcome win rate can be useful too; label that different denominator explicitly. Separate materially different segments, deal sizes and sales motions before comparing them.
How to use Jen’s benchmarks
Jen describes an enterprise qualified-opportunity win rate of roughly 25–35% in the conversation and discusses pricing, qualification and maturity as factors. These are practitioner observations from her experience.
Source: Jen Abel on Lenny’s Podcast, 1:07:30–1:11:30 →
Use that discussion to ask better questions about your own economics. A higher win rate alone is insufficient evidence to change pricing. Likewise, pilot length and approval time depend on the work, customer and buying process.
Build your baseline from consistently defined data and completed cohorts. For late-stage inspection, use the existing 16-point Deal Signature Score; keep its checklist separate from any forecast probability.
Put it to work this week
Start with three active opportunities at different points in the process. Use live work to find what the team needs.
Add agent support to a bounded task such as assembling research, reviewing missing evidence or preparing CRM updates. Expand once the owner can reliably check its work.
After the first month, review whether the team has clearer buyer commitments, fewer avoidable evaluation extensions and better visibility into approval dependencies. Use the findings to refine the process.
Every active deal should have a clear answer to four questions: what the buyer wants to achieve, what they have confirmed, what must happen next and who owns it.
Sources, credits and interpretation
Start with Jen and Lenny
The primary source for this playbook is Jen Abel’s conversation with Lenny Rachitsky on Lenny’s Podcast, published 23 August 2026.
- Watch the full episode on YouTube.
- Read the official episode page: How to close $100K+ enterprise deals, step by step.
- Follow Jen Abel on LinkedIn and X.
- Explore JJELLYFISH, which Jen co-founded.
- Read and subscribe to Lenny’s Newsletter, and learn more about Lenny’s work.
The YouTube title may differ from the title on the episode page. Both links identify the same conversation.
What this adaptation adds
Jen’s guidance supplies the central sales ideas: executive relevance, informal discovery, preparation with an internal champion, focused demos, pilot design, pricing conversations and coordination through contracting.
Revenue Puzzles adds the editorial structure, buyer-evidence gates, SaaS and services applications, CRM mapping, four working documents, human and agent responsibilities, metric definitions and rollout cadence. Example messages and templates are original Revenue Puzzles copy. The short quotation above is attributed directly to Jen.
Credit identifies the source of the ideas. It does not imply that Jen Abel, Lenny Rachitsky or their organisations reviewed or endorsed this page.
Read the numbers in context
The episode includes experience-based observations about deal sizes, win rates, pilot lengths and sales cycles. The examples are useful prompts for designing a motion; they do not establish universal thresholds or guarantee an outcome.
This playbook focuses on the operating principles and identifies its own recommendations separately. The timestamps point to the relevant discussions so you can hear Jen’s reasoning and nuance in full.