The Enterprise Land-and-Expand Reboot — 60-Min Training

The two reboot options on the table

Every enterprise sales org running this play eventually faces the same fork, and the 60-minute Training exists to force a decision rather than let each rep improvise. Option A is the big-land model: sell the platform up front, five teams, six workflows, full security review, the largest contract Procurement will approve. Option B is the engineered small-land model: sell one team, one workflow, one measurable outcome, and treat the remaining 60-80% of account potential as a mapped expansion thesis you execute over the following 18 months.

The big-land model is seductive because it front-loads bookings and it flatters the quarterly number. An account executive comped on total contract value will always drift toward it. The failure pattern is consistent: the deal takes an extra 60-90 days to close because every additional team drags its own stakeholder and its own security questionnaire into the cycle. The buyer signs a contract sized for an organization-wide deployment, then discovers 60 days later that only one of the five teams has the bandwidth to implement. The bill is real, the value is not, and the renewal turns into a knife-fight over shelfware. Net revenue retention craters before a single expansion conversation happens.

The small-land model deliberately gives up near-term contract value in exchange for two things: speed to first value and a clean expansion runway. If the mapped account potential is $500K across four teams, the land is $100K-$200K covering one team. That is small enough to deploy without a heavy Procurement gauntlet, large enough that the executive sponsor cares whether it works, and structured so that the next three teams are already named in your account plan before the ink dries.

The trade-off is genuine and the Training should say so plainly. Option A produces a bigger Q3 number and a worse Q3-next-year number. Option B produces a smaller booking, a longer path to the same total dollars, and dramatically better retention economics. Neither is free. What makes Option B the default in this Reboot is that expansion revenue carries almost no acquisition cost — the relationship, the security review, the procurement paper, and the integration work are already paid for. A dollar of expansion is worth roughly the same revenue as a dollar of new logo at a fraction of the cost to acquire it.

There is also a hybrid worth naming: the phased land, where the paper covers the full multi-team scope but the commercial terms ramp — team one pays from month one, team two from month seven, team three from month thirteen. This gets the customer's budget certainty and your contracted expansion into a single signature. It only works when the sponsor has real authority across all three teams and when your implementation capacity is genuinely proven. Used carelessly, it is a big land wearing a small land's clothing, and it fails the same way.

How to decide between them

The decision is not a matter of taste. Run every open opportunity through the same four gates in deal review, and the answer falls out.

Gate one — can the buyer name the next team? Ask the sponsor directly: "After this team is live and working, which group gets it next, and who runs that group?" If they can name the team and the leader, you have a real expansion thesis and a small land is safe. If they cannot, you sold a pilot, and no contract structure will save it.

Gate two — what is the honest time-to-value? If your implementation team says the first user gets real output in 60-90 days, land small. If the answer is 180 days for any configuration, you are either over-scoping or your product needs services that the land cannot carry. Push scope into the expansion roadmap.

Gate three — does the deal trigger heavyweight Procurement? Many enterprises have a dollar threshold or a data-classification threshold above which a full vendor security review, legal redlines, and a committee approval kick in. Landing just under that line is legitimate deal design, not gaming — it buys you 45-90 days of calendar and lets the expansion ride the precedent your land established.

Gate four — is the sponsor willing to sign a success contract? Hesitation here is the single most reliable red flag in the play. A sponsor who will not commit to three named outcomes and four calendar holds is not a sponsor; they are a well-disposed bystander. If gate four fails, shrink the land further or slow the deal.

Two additional decision inputs matter enough to state explicitly. First, implementation capacity: if your services or customer success team is running above roughly 80% utilization, a big land will queue behind other deployments and the time-to-value gate fails regardless of what the contract says. Second, the buyer's fiscal calendar: landing three to four months before their fiscal year start gives you a live deployment with real numbers exactly when next year's budget is being written, which is the highest-leverage moment for an expansion ask.

Concrete numbers behind each option

The 60-minute Training earns its slot only if the room leaves knowing the arithmetic. Work a single cohort out loud on the whiteboard.

The small-land cohort. Fifty customers, average land of $200K, $10M in cohort annual recurring revenue. Gross revenue retention of 95% means you lose $500K to churn and downgrade in year two — that is the leaky-bucket floor, and it is non-negotiable. Below 95% GRR, stop the expansion program and fix retention first, because expansion into a leaking base is arithmetic you cannot win. Expansion engine: five triggers fired per account per year, roughly 40% converting to a closed expansion, average expansion of $60K-$70K. That produces approximately $2.5M of net expansion, or 25 points. Year-two ARR lands at roughly $12.0M against a $10M base — 120% net revenue retention, the widely cited best-in-class bar for books in the $25K-$500K ACV range.

The big-land cohort. Same fifty customers, average land of $350K, $17.5M cohort ARR. Bookings look 75% better on day one. But the failure modes compound: deals close 60-90 days later, so a meaningful share slip out of the fiscal year entirely. Deployment stalls on the teams that never had capacity, so gross retention runs closer to 85-88% — call it $2.2M lost. Expansion is structurally harder because you already sold the obvious adjacent teams, so net expansion runs 5-10 points instead of 25. Year-two ARR lands near $18M on a $17.5M base — roughly 103% NRR. The big-land cohort is larger in absolute dollars in year one and is worth substantially less per dollar of ARR, because the growth multiple the market pays is driven by retention, not by initial deal size.

The four numbers every rep must know cold. Gross revenue retention target 95% or better. Net revenue retention target 120%, with 100% acceptable and 110% respectable. Trigger conversion — the share of fired expansion triggers that close within 60 days — target 40%, and treat anything under 25% as evidence that the AE-to-CSM handoff is broken rather than that the triggers are wrong. Time-to-first-expansion — target 180 days from land, treat 270 days as an at-risk flag, and escalate anything past 365.

Discount arithmetic on multi-year. The ceiling in this play is 10% off for a two-year commitment and 15% off for three years, and never before month nine of the land. Before month nine you genuinely do not know whether the land is real or a churning pilot, and a discount locked against a bad deployment buys you a discounted churn. The trade is straightforward: you are giving up roughly one month of revenue per year of term in exchange for removing a renewal event, a competitive re-evaluation, and a budget cycle from the equation. That trade is good when the 90-day gate came in green and at least one expansion trigger has already converted. It is bad in every other case.

Payback economics. New-logo acquisition in enterprise software commonly runs a 24-30 month CAC payback. Expansion revenue into an existing account carries no new security review, no new procurement cycle, no new integration build, and typically a fraction of the selling time — payback in the 12-14 month range is realistic. That gap is the entire financial argument for the Reboot, and it is worth writing on the board in two colors.

Implementation details and sequencing

The play fails in execution far more often than in strategy, so sequence it precisely.

At signature — the 90-Day Land-Success Contract. This is not a legal instrument; it is a mutual accountability pact signed in the same meeting as the order form, by the AE, the CSM, and the executive sponsor. It contains exactly three quantified outcomes chosen by the sponsor, not lifted from a CSM template — for example, "cut average handle time by 20%," "reduce lead-to-MQL latency from 48 hours to 4," or "eliminate 40 hours per month of manual data entry for the sales operations team." Each outcome gets a named owner, and that owner should be a mid-level manager who touches the work daily, not the sponsor. The contract carries four calendar holds booked live in the meeting: week-two kickoff, day-30 health check, day-60 outcome review, day-90 QBR and expansion conversation. Store it as a custom object in the CRM linked to the opportunity, with automated reminders at day 30, 60, and 75.

Day 60 — the color gate. Green means the outcomes are tracking and the day-90 QBR becomes an expansion conversation. Yellow triggers a save-the-land intervention: the CSM manager joins, scope gets re-cut, and the timeline resets rather than drifts. Red escalates to leadership on both sides within five business days. The gate exists so that bad lands surface at day 60 when they are fixable, not at day 300 when they are a renewal problem.

Days 1-90 — the expansion sprint. Run a 15-minute weekly standup between AE, CSM, and the sponsor's named owner. Days 1-30 are adoption: get the three contracted outcomes instrumented and moving. Days 31-60 are value articulation: co-author a one-page ROI summary with the sponsor, in their numbers and their language, because that page becomes the internal document that sells the expansion when you are not in the room. Days 61-90 are the expansion proposal: present a tiered menu — more seats, an adjacent module, a premium support tier — then narrow to a single recommended option with a 30-day decision window at the QBR.

Ongoing — the expansion trigger taxonomy. Anniversary-driven outreach is the weakest possible trigger, because 90 days before renewal the buyer's next-year budget is already locked and you are negotiating against sunk cost. Replace it with five signals wired into the CRM, each auto-assigning a joint AE-plus-CSM task with a pre-written three-slide deck, sample email, and call script, actioned within five business days:

• Usage trigger — seat utilization crosses 80% for two consecutive months, or a power user emerges. Script: "Your team is at 84% active, which is top-decile for our base. Who else in the department would benefit, and can we get 20 minutes next week to scope it?"
• Team-growth trigger — the sponsor names an adjacent team in a one-on-one or QBR, or headcount in the land department grows 20%+. Script: "You mentioned the support team is hitting the same problem — we solved that for a similar team in six weeks. Worth 30 minutes before your quarterly planning locks?"
• Exec-change trigger — a new VP, CRO, or CIO joins in the buyer's org. Reach out within seven days, before their vendor review starts: "Your predecessor sponsored our deployment in revenue operations; here's where the numbers landed. I'd like 20 minutes to show you where we could go next."
• Integration trigger — the buyer adopts an adjacent tool in your stack, which creates a concrete, technical reason to expand rather than a commercial one.
• Anniversary trigger — fires at day 270, not 60 days from renewal, so the conversation lands while budget is still flexible.

Roles and the shared number. The CSM owns the 90-Day Land-Success Contract. The AE owns the trigger taxonomy and the commercial conversation. Both carry the same compensation-relevant metric: dollar net revenue retention on the cohort they landed. Splitting the number is what breaks the handoff — when the AE is paid on new bookings alone and the CSM on adoption alone, nobody owns the expansion, and trigger conversion collapses into the sub-25% range.

Comp and CRM changes required. This Reboot does not survive an unchanged compensation plan. At minimum, add a cohort-NRR accelerator or a retention modifier so the rep who lands $150K that becomes $400K out-earns the rep who lands $250K that renews flat. On the systems side you need three objects: the Land-Success Contract as a custom object linked to the opportunity, a trigger object with type, fire date, owner pair, and outcome, and a cohort report that rolls land ACV, 90-day score, fired-trigger count, and projected 18-month NRR into one view.

The 60-minute run of show

Timebox the Training so it installs a play rather than delivering a lecture. Five minutes to frame: "we close the same logo three times — land, second-team expand, multi-year renewal," and "every land is graded on NRR 12 months out, so a $50K land that becomes $200K beats a $120K land that renews flat." Fifteen minutes on small-land sizing and the success contract, working two live open deals from the room rather than slideware. Ten minutes on the trigger taxonomy, reading the scripts aloud so reps hear the cadence. Ten minutes on the multi-year decision matrix. Fifteen minutes on the cohort scoreboard, where each rep whiteboards their three largest lands across four columns — ACV, 90-day success score, fired-trigger count, projected 18-month NRR. Reps who can fill all four columns are running the play; reps who cannot are transacting, and that gap is what you coach.

Close with five minutes on commitments and a field drill. Three personal commits from every AE and CSM: rebuild the Land-Success Contract on the top two open lands by end of week; fire at least three expansion triggers with joint outreach by end of month; hit 115%+ cohort NRR with a documented path to 120% by end of quarter. Then pair up — one AE, one CSM, five minutes — and run the team-growth trigger script cold, scored on three things only: named sponsor, named outcome, calendar-hold ask. That is the exact rep they run Monday morning.

Related questions

Should we ever land big in enterprise sales?

Yes — when the sponsor has budget and authority across all target teams, implementation capacity is proven, and time-to-value stays under 90 days per team. Structure it as a phased land with ramped commercial terms so the customer pays as each team goes live rather than all at once.

What if the customer refuses the 90-day success contract?

Treat refusal as disqualifying information, not an obstacle. It means you have a well-disposed bystander rather than a sponsor. Shrink the land, find the operational leader who actually owns the outcome, and get their signature instead — a mid-level owner beats an absent executive.

How do we stop reps from sandbagging into tiny lands?

Grade the land on mapped account potential, not absolute size. A land should be 20-40% of the documented expansion thesis. A $40K land against a $2M thesis is under-landed and should be coached up, exactly as a $350K single-team land should be coached down.

Does this play work for accounts under $25K ACV?

Partially. The trigger taxonomy and usage signals translate well and can run largely automated. The 90-day success contract with four executive calendar holds does not — the economics do not support that touch. Use a lightweight two-outcome version delivered through onboarding email sequences and in-product prompts.

How long before the Reboot shows up in reported NRR?

Expect 9-12 months before cohort numbers move, because the first lands under the new model need to reach their expansion window. Leading indicators arrive far sooner: trigger fire rate within 30 days, trigger conversion rate within 90, time-to-first-expansion within 180.

FAQ

What is the smallest credible land footprint?

One team, one workflow, one measurable outcome, deployed to roughly 8-25 daily users, generating real output within 60-90 days. It should represent 20-40% of the mapped account potential — small enough to deploy cleanly and stay under heavyweight procurement thresholds, large enough that the executive sponsor personally cares whether it succeeds.

What exactly goes into a 90-Day Land-Success Contract?

Three quantified outcomes chosen by the sponsor, a named mid-level owner for each, and four calendar holds booked live in the signature meeting: week-two kickoff, day-30 health check, day-60 color gate, day-90 QBR. It lives as a CRM custom object linked to the opportunity with automated reminders at days 30, 60, and 75.

Why fire the anniversary trigger at day 270 instead of near renewal?

Because by 60-90 days before renewal, the buyer's next-year budget is already allocated and you are arguing against sunk cost. At day 270 the budget cycle is still open, the deployment has nine months of results behind it, and the conversation is about growth rather than justification.

When is a multi-year contract appropriate?

Only after month nine of the land, and only when the day-60 gate came in green and at least one expansion trigger has converted. The ceiling is 10% off for two years and 15% for three. Before month nine you cannot distinguish a healthy land from a churning pilot, and discounting a bad deployment just buys discounted churn.

What NRR should a $25K-$500K ACV book target?

Aim for 120% net revenue retention, built from roughly 95% gross revenue retention plus 25-30 points of net expansion. One hundred percent is acceptable, 110% is respectable, and 120% is the commonly cited best-in-class bar. Below 95% GRR, pause expansion work and fix retention first.

What breaks this play most often after the Training?

Compensation. If AEs are paid on total contract value and CSMs on adoption alone, nobody owns expansion and trigger conversion falls below 25%. The fix is a shared cohort-NRR metric that makes a $150K land growing to $400K out-earn a $250K land that renews flat.

Sources

• https://www.saastr.com/
• https://tomtunguz.com/
• https://www.bvp.com/atlas/
• https://openviewpartners.com/
• https://www.gainsight.com/blog/
• https://sixteenventures.com/
• https://hbr.org/
• https://www.mckinsey.com/capabilities/growth-marketing-and-sales/our-insights
• https://a16z.com/
• https://www.gartner.com/en/sales

Related on PULSE

• [Account Planning for Enterprise Deals: Template for a Collaborative Team Exercise](/knowledge/st0791)
• [Top 10 sales enablement drills for enterprise software reps](/knowledge/st0638)
• [Top 10 sales training workshops for enterprise software teams](/knowledge/st0637)
• [Top 10 enterprise AE facilitator guides for 2027](/knowledge/st0586)
• [Top 10 enterprise AE workshop agendas for 2027](/knowledge/st0585)
• [Top 10 enterprise AE role-play scenarios for 2027](/knowledge/st0584)