Sales Playbook

SaaS Sales Playbook: The Close Is the Start, Not the Finish

Most SaaS sales playbooks end at closed-won.

But in a subscription business, most revenue comes after the first sale, through retention and expansion. A SaaS playbook needs post-close plays for the whole customer life.

A SaaS sales playbook is a documented set of plays for selling subscription software, and it must extend past the close into onboarding, retention, and expansion, because in a recurring-revenue model most revenue comes after the first sale, not from it.

A SaaS sales playbook built as a one-time-sale playbook makes a costly error: it ends at closed-won. The deal is won, the playbook stops, the rep moves to the next logo. In a subscription business that is the wrong place to stop, because the first sale is the smallest part of a customer’s value. Most SaaS revenue comes after the close, through the customer staying and growing, and a playbook that treats the close as the end has documented the cheapest, smallest slice of the work and left the most valuable plays, the ones that keep and expand customers, left unwritten. In SaaS, the close is not the finish. It is the start of the part where the real money is made.

A SaaS sales playbook is a documented set of plays for selling subscription software, and it must extend past the close into onboarding, retention, and expansion, because in a recurring-revenue model most revenue comes after the first sale, not from it. Build the playbook for the customer’s life, not the deal alone.

Why must a SaaS sales playbook extend past the close?

Because subscription economics put the majority of a customer’s value after the first sale, so a playbook that ends at the close ignores where the revenue is. Acquiring a SaaS customer costs money up front, the sales and marketing spend, and that cost only pays back over the months and years the customer stays and expands. Frederick Reichheld and Earl Sasser documented these retention economics at Bain decades ago: by their analysis a five percent improvement in customer retention raised profitability somewhere between 25 and 85 percent in net present value, depending on the industry, because keeping and growing a customer is far more valuable than the initial acquisition (Reichheld & Sasser, “Zero Defections,” HBR). The number has been argued about since, and it should be: it is a model, not a law. But the direction is not in dispute, and in subscription software the effect is sharper than in the services Reichheld studied, because the customer pays again every period rather than once.

Consider what acquisition buys. A new logo is not revenue; it is the right to bill a customer repeatedly, and a cost you have not yet earned back. The sales-and-marketing spend on that customer pays off only after a payback period, often a year or more, of subscription payments. Everything before payback is the company lending the customer money. Everything after is profit, and almost all of it sits past the close, in months the one-time-sale playbook does not cover. A playbook that ends at closed-won is a playbook that documents the lending and ignores the earning.

The market has noticed where the growth comes from. ChartMogul’s 2024 retention report, drawn from more than 2,500 SaaS businesses, found that “the median company with ≥100% NRR grew at 48% year-over-year,” more than twice as fast as companies below 100 percent net revenue retention, and that for companies at or above 100 percent, “expansion accounts for over half of their revenue” (ChartMogul, SaaS Retention: The New Normal). Among companies with $15 million to $30 million or more in ARR, expansion drove about 40 percent of growth in the first half of 2024, up from 30 percent in early 2021. The variable was not how many logos they signed but how much of the base they kept and grew. The money is migrating to the part of the customer life most playbooks never reach.

The practical consequence is that the most valuable plays in SaaS live after the close, and a one-time-sale playbook has none of them. The onboarding handoff that gets a customer to value before they churn, the retention play triggered by a health-score dip, the expansion play triggered by a usage threshold, these are where SaaS revenue is made or lost, and a playbook that stops at the close leaves every one of them undocumented and unrun.

SaaS customer value over time: the acquisition cost is paid up front and sits below the line until a payback period of roughly a year, after which subscription revenue earns it back and expansion compounds above the line, so most of a customer's value lands well after the close while a one-time-sale playbook covers only the early loss-making window.
Acquisition spends money up front; the customer only turns profitable past the payback period. Most of the value lands after the close, where a close-and-move-on playbook stops.

Is chasing new logos the wrong instinct?

Not wrong, incomplete, and it is worth being fair to the instinct before correcting it. The whole folklore of selling, from “always be closing” to the comp plan that pays out on the signed deal, points the rep’s attention at the new logo. There is a reason: the new logo is visible, it is celebrated, and it is the moment the contract is signed. You can hear it on the sales floor, where the bell rings for the signed logo and stays silent for the renewal.

But the comp plan and the folklore were built for a one-time sale, and they mis-train a SaaS team. Jason Lemkin, who has watched more SaaS companies scale than almost anyone, has argued for years that lifetime value alone understates a happy customer, because that customer also throws off “second-order revenue”: the referrals, case studies, and expansions that a first-order CLTV calculation never captures, and that at scale come to rival the new-business line (Lemkin, SaaStr, on second-order revenue). A team that pours its best plays into the new logo and treats the rest as an afterthought is optimizing the smallest of three revenue streams and starving the two larger ones. The fix is not to stop closing. It is to write the post-close plays with the same care, and to measure whether they get run.

In SaaS the sale does not end at closed-won: a one-time-sale playbook goes prospect then close then stops, ending there; a SaaS playbook goes land, onboard, retain, then expand, because the close is the start of the customer's life and most SaaS revenue comes after it, so a SaaS playbook needs post-close plays of onboarding handoff, retention, and expansion triggers.
A one-time-sale playbook stops at the close. A SaaS playbook keeps going through land, onboard, retain, and expand, where the revenue is.

What plays does a SaaS sales playbook need?

The acquisition plays, plus the post-close plays that retention and expansion run on. A SaaS playbook keeps the standard land plays for winning the initial deal, but adds the plays a subscription business lives on. An onboarding-handoff play ensures the customer reaches value quickly and does not churn in the first weeks, the window where early churn is decided, and prevents the kind of rushed handoff we flagged as a source of revenue leakage. Retention plays tie to customer-health signals so a renewal risk triggers a defined response instead of a surprise. Expansion plays trigger on usage and outcomes, so a customer past a threshold gets the right expansion motion at the right moment. These post-close plays are the heart of a SaaS playbook, and a generic playbook focused on acquisition has none of them.

  • Land play. Win the initial deal. Necessary, and the smallest part of the customer’s value.
  • Onboarding-handoff play. Get the customer to value fast, so they do not churn early. The handoff is where retention starts.
  • Retention plays. Triggered by health signals, so renewal risk gets a defined response instead of a surprise.
  • Expansion plays. Triggered by usage and outcomes, so growth is a motion, not an accident.
Where a SaaS business's revenue grows: a bar chart where the new-logo sale is the smallest bar labeled the start, retention is a larger bar that keeps the base, and expansion is the largest bar that compounds growth, showing a playbook that ends at the new-logo sale captures the smallest bar and ignores the other two.
New logos are the smallest bar. Retention and expansion are where SaaS revenue compounds, and where the playbook must reach.

How do you build a sales play for account expansion in SaaS?

Start from a trigger, not a calendar. An expansion play is a defined response to a signal that a customer is ready to buy more: who acts, what they bring, who they talk to, and what they offer. It is the cheapest revenue in the business. KeyBanc’s 2018 private SaaS survey put the median cost of acquiring $1 of new-customer ARR at $1.32, of upsell ARR at $0.71, and of expansion ARR at $0.38, about 28 percent of the new-customer cost (KeyBanc survey, via Sage). Yet expansion is the play teams leave to whoever happens to notice, which is a little like a farmer who budgets every hour for clearing new fields and none for the harvest on the fields already planted.

Six parts make the play runnable, and each one closes a gap where expansion usually stalls.

  • The trigger. A specific, observable signal: active seats near the licensed count for a month, a second department logging in, a plan limit hit, or the outcome from the handoff’s success plan met. A vague “the account seems happy” fires never, or at random.
  • One owner. The account manager, the CSM, or the original AE, by name in the play. Expansion owned by “the account team” is owned by no one, and the trigger fires into silence.
  • Proof of the outcome. The result the customer bought for, in their numbers, pulled from the sales-to-customer-success handoff notes and the latest business review. An expansion pitch without proof asks for more money on faith.
  • The new buyer. The person who controls the budget for the next team or tier is often not your champion. The play names who to reach and asks the champion for the introduction.
  • One priced offer. Seats, a tier, or a module, with the price, so the buyer evaluates a decision rather than a conversation. The email that opens the conversation is a template too; trigger-matched versions are in cross-sell email templates.
  • The exit rule. If health signals are red (support escalations, falling usage, a lost champion), the expansion play stops and the account moves to a retention play. Pitching an upsell to an unhappy customer turns a renewal risk into a churn.
How to build a sales play for account expansion in SaaS, in six parts: a usage trigger such as seats near the licensed limit or a second team adopting, one named owner, proof of the outcome the customer bought for, the new buyer who controls the expansion budget, one priced offer, and an exit rule that moves a red-health account to a retention play; KeyBanc's survey put expansion ARR at $0.38 per dollar against $1.32 for new-customer ARR.
Six parts, and the trigger comes first. Expansion is the cheapest revenue in SaaS: KeyBanc put $1 of expansion ARR at $0.38 of sales and marketing cost, against $1.32 for a new customer.

A worked example makes the parts concrete. A customer bought 40 seats to cut onboarding time for its sales team. Six weeks after the handoff, 38 of the 40 seats are active and a customer-success manager sees logins from the account’s support team, which never bought. The trigger fires. The account manager owns it. She pulls the onboarding numbers from the last business review, asks the sales director (her champion) to introduce the head of support, and brings one offer: 25 seats for the support team at the existing rate. Had support tickets spiked that month, the exit rule would have sent the account to the retention play first. The trigger, the owner, and the exit rule are written once; the account manager fills in the rest from the account in front of her.

What does a SaaS sales playbook template look like?

A grid with one row per play and the same five columns on every row: the trigger, the owner, the first action, what done looks like, and the number that shows the play ran. The rows run the customer life in order, from land to renewal, because a SaaS sales playbook template that stops at the first row is the one-time-sale playbook this post argues against.

PlayTriggerOwnerFirst actionDone whenMeasured by
LandQualified opportunityAEDiscovery against the buyer’s success criteriaSigned, with a written success planWin rate; plays run per deal
Onboarding handoffClosed-wonAE to CSMHandoff call with the champion on the success planCustomer reaches first valueTime to first value
Adoption checkLow usage at day 30CSMUsage review with the championActive-seat target metActive seats against licensed
Renewal riskHealth score dropsCSMExecutive check-in and a recovery planHealth back to greenGross revenue retention
ExpansionUsage or outcome thresholdAMProof of outcome, then the new-buyer introductionPriced offer accepted or declinedExpansion ARR; net revenue retention
Renewal120 days before term endAMValue review against the success planRenewed on timeRenewal rate
A SaaS sales playbook template as a grid: six plays in customer-life order, land, onboarding handoff, adoption check, renewal risk, expansion, and renewal, each with the same five columns of trigger, owner, first action, done when, and measured by, with the five post-close plays highlighted as the part a one-time-sale playbook leaves out.
One row per play, the same five columns on every row. Five of the six rows sit after the close, which is the part a close-and-move-on playbook leaves blank.

Two rules keep the grid useful. The triggers and thresholds come from your own data, the usage level at which your customers expanded and the health signals that preceded your churn, not from someone else’s template. And the last column is not optional, because a play without a number is a play you cannot prove ran.

How do you make a SaaS sales playbook reps and CSMs run?

Build the post-close plays from your own retention and expansion wins, then surface them in the flow of work for the people who run them. The post-close plays only matter if the rep and the customer-success manager run them, so document how your best CSMs save renewals and trigger expansions, codify those as plays, and put them in the flow of work where the work happens, with the right play surfacing on the account at the moment it applies, the same sales process adoption discipline that governs any playbook. The b2b saas sales playbook spans acquisition and post-sale, which makes it a revenue enablement problem as much as a sales one: owning the behavior across the handoffs from sales to success, where SaaS revenue most often leaks.

The handoff deserves a hard look, because it is the most under-documented moment in the whole saas sales process and the one where the early-churn window opens. The rep who won the deal carries context the customer-success manager does not: what the buyer was promised, which stakeholder championed it, what success was supposed to look like. When that context does not transfer, the customer lands cold, value arrives late, and the renewal is at risk before anyone has done anything wrong. A good post-close play makes the transfer a defined step with an owner, not an email and a hope. Measure adherence on the post-close plays as seriously as on the acquisition ones, because in a subscription business the post-close plays carry the larger number, and what goes unmeasured in the post-sale motion is exactly where avoidable churn lives.

What we recommend

Build your SaaS sales playbook for the customer’s life, not the deal, because in a subscription business the close is the start of the value, not the end of it. Keep the land plays, but add the post-close plays SaaS revenue runs on: an onboarding handoff that gets the customer to value before they churn, retention plays triggered by health signals, and expansion plays triggered by usage. Build those plays from your own retention and expansion wins rather than from a generic saas sales playbook template, surface them in the flow of work for the reps and CSMs who run them, and measure adherence on them as seriously as on acquisition. The reason this beats the usual close-and-move-on playbook is that it documents where SaaS revenue is, which is mostly after the first sale. A playbook that ends at closed-won has captured the smallest slice of the business. The SaaS playbook that wins keeps going to where the revenue compounds.

From here: the buying-group plays in the B2B sales playbook, the handoff losses in revenue leakage, the cross-functional scope in revenue enablement, and the adoption underneath in sales process adoption.

Frequently asked questions

What is a SaaS sales playbook?+
A SaaS sales playbook is a documented set of plays for selling subscription software. Unlike a one-time-sale playbook that ends at closed-won, a SaaS playbook has to keep going past the close, into onboarding, retention, and expansion, because in a recurring-revenue model the first sale is the smallest part of a customer's value. Most of the revenue comes after the close, so the playbook covers the whole customer life rather than the deal alone.
How is a SaaS sales playbook different?+
It does not stop at the close. In a one-time sale, the playbook ends when the deal is won. In SaaS, the close is the start of the customer's life, and the larger revenue, renewal and expansion, comes later. So a SaaS playbook adds post-close plays: a clean onboarding handoff so the customer reaches value, retention plays to keep them, and expansion plays triggered by usage. A playbook that ends at closed-won captures the smallest slice of SaaS revenue.
What should a SaaS sales playbook include?+
The standard acquisition plays plus the post-close plays SaaS lives on: a land play to win the initial deal, an onboarding-handoff play so the customer reaches value quickly and does not churn early, retention plays tied to health signals, and expansion plays triggered by usage and outcomes. The recurring-revenue model means retention and expansion drive growth, so a SaaS playbook that documents only acquisition has documented the smallest part of the job.
Why does the SaaS sales playbook extend past the close?+
Because subscription economics put most of a customer's value after the first sale. Acquiring a customer costs money up front and only pays back over the months and years they stay and grow, so retention and expansion, not the initial close, drive a SaaS business. A playbook that ends at closed-won ignores where the revenue is and leaves the most valuable plays, the ones that keep and grow customers, undocumented and unrun.
How do you build a sales play for account expansion in SaaS?+
Define the trigger that opens the play (seat use near the licensed limit, a second team adopting, a plan limit hit, a goal from the handoff met), name one owner, gather proof of the outcome the customer bought for, map the new buyer who controls the expansion budget, make one specific priced offer, and set an exit rule that hands the account to a retention play if health is red. Then measure whether the play ran each time the trigger fired. Expansion is cheap revenue: KeyBanc's SaaS survey put the cost of $1 of expansion ARR at $0.38 against $1.32 for new-customer ARR.
What does a SaaS sales playbook template look like?+
A table with one row per play (land, onboarding handoff, adoption check, renewal risk, expansion, renewal) and the same columns on every row: the trigger that starts it, the owner, the first action, what done looks like, and the number that shows it ran. Filling it from your own retention and expansion wins beats copying a generic template, because the triggers and thresholds are specific to your product.

What 2026 sales teams actually run.

The State of Sales Enablement, free.

Ready to see it on your own deals? Book a demo

Supered Launch Week runs Nov 2 to 6, then Demo Day goes live Tue Nov 10, 11 AM ET.Register free