Tag: net revenue retention

  • CAC, LTV, and Payback Period: The SaaS Metrics RevOps Teams Should Track

    Customer acquisition cost (CAC) is what you spend to win a customer, lifetime value (LTV) is the gross profit you expect from that customer over time, and CAC payback period is how many months it takes to earn the acquisition cost back. Each is easy to calculate and easy to get wrong, and they only make sense read together.

    These three numbers show up in every board deck, and the figures people quote are often flattering for a reason: the formulas leave out costs. This guide gives you the standard formulas, a worked example, the most common ways the numbers mislead, and what RevOps has to set up to measure them honestly.

    The formulas

    Metric Formula What it tells you Common error
    Fully loaded CAC Total sales and marketing cost รท new customers won What a customer costs to acquire Counting only ad spend
    CAC payback period CAC รท (monthly revenue per customer ร— gross margin) Months to recover acquisition cost Using revenue instead of gross profit
    Customer lifetime value (LTV) (Monthly revenue per customer ร— gross margin) รท monthly churn rate Gross profit expected over the customer’s life Using revenue, or trusting a very long lifetime
    LTV:CAC ratio LTV รท CAC Return on each acquisition dollar Reading it alone, without payback or retention

    Keep your time units consistent. If churn is monthly, revenue per customer should be monthly too.

    A worked example

    These numbers are illustrative. In one quarter, a company spends $600,000 on sales and marketing and wins 40 customers. Each customer pays $2,000 a month. Gross margin is 80%, and monthly churn is 3%.

    Step Calculation Result
    CAC $600,000 รท 40 $15,000
    Monthly gross profit per customer $2,000 ร— 80% $1,600
    CAC payback period $15,000 รท $1,600 About 9.4 months
    LTV $1,600 รท 0.03 About $53,333
    LTV:CAC $53,333 รท $15,000 About 3.6:1

    Using revenue instead of gross profit, payback would look like $15,000 รท $2,000, or 7.5 months, nearly two months better than reality. A 3% monthly churn rate implies an average customer life of about 33 months. If churn were 1%, the formula would imply more than eight years, which is a guess, not a measurement. Many finance teams cap lifetime at three to five years to keep LTV honest.

    What goes into CAC changes everything

    The same company can report very different CAC depending on what it counts.

    What’s counted Cost CAC Payback LTV:CAC
    Ad spend only $150,000 $3,750 2.3 months 14.2:1
    Ad spend plus marketing team and programs $330,000 $8,250 5.2 months 6.5:1
    Fully loaded sales and marketing $600,000 $15,000 9.4 months 3.6:1

    A fourfold swing from the same business. Fully loaded CAC should include:

    • Salaries, commissions, bonuses, and benefits for sales, SDRs, and marketing
    • Advertising, events, content, and agency or contractor fees
    • Sales and marketing tools and the RevOps or sales operations time that supports them
    • Recruiting and onboarding costs for go-to-market hires
    • Any overhead your finance team consistently allocates

    The exact choices matter less than consistency, plus a written definition everyone uses. Also decide how to treat the lag between spending and winning: with a 90-day cycle, this quarter’s spend produces next quarter’s customers, so some teams match spend to the period it influences.

    A blended number hides the channels

    Using the same customer economics, split the $600,000 across channels.

    Channel Spend New customers CAC Payback LTV:CAC
    Outbound $240,000 12 $20,000 12.5 months 2.7:1
    Paid $150,000 8 $18,750 11.7 months 2.8:1
    Content and organic $120,000 14 $8,571 5.4 months 6.2:1
    Partners and referrals $90,000 6 $15,000 9.4 months 3.6:1
    Blended $600,000 40 $15,000 9.4 months 3.6:1

    The blended 3.6:1 looks respectable. Underneath, two channels sit below 3:1 and one is carrying the average. The table assumes every channel’s customers have the same revenue, margin, and churn, which is often untrue. To make the comparison fair, you need retention and revenue by source, which is what closed-loop reporting and revenue attribution provide.

    What’s a good number?

    The most quoted rule is an LTV:CAC of at least 3:1, usually traced to David Skok, who based it on mature SaaS companies with stable churn and payback under 12 months. Many benchmark roundups call 3:1 to 5:1 healthy. Payback targets vary widely: commonly under 12 months for small-ticket, self-serve motions, 12 to 18 months for mid-market, and up to about 24 months for enterprise, where contracts last longer. Several recent benchmark datasets put the median B2B SaaS payback in the mid-teens of months.

    Treat these as context, not targets. Published figures come from different samples and methods, and many come from agencies and vendors, so compare yourself with companies of similar size, deal size, and motion. The ratio also matters less than the combination: a 3:1 ratio with 12-month payback and strong expansion is excellent, while the same 3:1 with 30-month payback and shrinking accounts is fragile.

    Don’t read the ratio without retention

    LTV depends on churn, and the simple formula ignores expansion. If existing customers grow, LTV is larger than the formula says, and if they shrink, it’s smaller. That’s why LTV:CAC and payback belong beside net revenue retention and gross revenue retention, ideally by cohort. A revenue waterfall shows where the changes come from, and a land and expand motion legitimately shifts the calculation, because the first contract is only part of the customer’s value. For cohort-based views, track each acquisition cohort’s retention and payback over time instead of one blended figure.

    What RevOps needs to set up

    Input Source Common pitfall
    New customer definition and date CRM and billing Counting trials, renewals, or reactivations as new
    Starting recurring revenue per customer Billing Using bookings or list price instead of what was billed
    Original acquisition source CRM, locked at creation Source overwritten by later touches
    Sales and marketing spend by channel and period Finance Spend that doesn’t map to channels
    Gross margin Finance Using blended margin when subscription margin is what applies
    Churn and expansion Billing and revenue waterfall Different definitions of churn and contraction between teams

    Agree the definitions with finance in writing, calculate the metrics monthly, and review them in your RevOps meeting cadence. Your CRM and billing system need a matching account ID, or you won’t be able to connect acquisition source to retention.

    How to improve the numbers

    Lever What it moves Example
    Raise ACV or improve packaging Payback and LTV Introduce a higher tier with features buyers value
    Improve win rate CAC Tighten qualification and focus on your ideal customer profile
    Shorten the sales cycle CAC and payback Remove stalls and bring security review forward
    Cut low-yield spend CAC Reallocate from channels with poor payback
    Reduce churn LTV Faster onboarding and early health signals
    Grow expansion LTV Clear upgrade paths and an owner for growth
    Improve gross margin Payback and LTV Reduce hosting, support, or services costs per customer

    Pipeline and capacity affect CAC too. See our guides to pipeline coverage and sales capacity planning.

    Mistakes to avoid

    • Counting only advertising in CAC
    • Using revenue instead of gross profit for payback and LTV
    • Trusting a very long customer lifetime from a tiny churn rate
    • Reporting one blended number and never splitting by channel or segment
    • Mixing monthly and annual figures in one formula
    • Reading LTV:CAC without payback and retention
    • Comparing yourself with benchmarks from a different stage or motion

    Summary

    CAC is fully loaded sales and marketing cost divided by new customers. CAC payback period is CAC divided by monthly gross profit per customer. LTV is monthly gross profit divided by monthly churn, and LTV:CAC is LTV divided by CAC. In the worked example, a $600,000 spend and 40 new customers give a $15,000 CAC, 9.4 months of payback, and a 3.6:1 ratio.

    What’s counted in CAC can swing the ratio fourfold, and a blended figure can hide channels below 3:1. Use gross margin, fully loaded costs, and written definitions, cap lifetime assumptions, split by channel and cohort, and read the three metrics together with net and gross revenue retention. Benchmarks such as 3:1 and a mid-teens payback are context, not targets.

    FAQ

    What is CAC?

    Customer acquisition cost is the total sales and marketing cost to win new customers in a period, divided by the number of new customers won. Fully loaded CAC includes salaries, programs, tools, and overhead, not just advertising.

    What is CAC payback period?

    It’s the number of months it takes for a customer’s gross profit to repay the cost of acquiring them: CAC divided by monthly revenue per customer times gross margin.

    What is a good LTV:CAC ratio?

    A common minimum is 3:1, and 3:1 to 5:1 is often called healthy. A very high ratio can mean you’re under-investing in growth. Read it alongside payback and retention, and compare with similar companies.

    Should I use revenue or gross profit in the formulas?

    Gross profit. Using revenue ignores the cost of delivering the product and makes both payback and LTV look better than they are.

    Why does my LTV look so high?

    Because the formula divides by churn, so a very low churn rate implies an extremely long lifetime. Cap the lifetime at a few years, use cohort retention instead of a single rate, and check that CAC is fully loaded.

    How often should we calculate these metrics?

    Monthly or quarterly, using consistent definitions, and by channel and cohort as well as blended. Review them in your regular RevOps and finance meetings.

    How do expansion and net revenue retention affect LTV?

    The simple LTV formula assumes flat revenue. Expansion raises true lifetime value, and contraction lowers it, so track net and gross revenue retention by cohort and treat the simple ratio as a starting point.

    Who should own these metrics?

    Finance and RevOps together. Finance owns spend, margin, and revenue definitions, and RevOps owns the CRM data, source attribution, and reporting. Agree the definitions in writing.

  • What Is Net Revenue Retention? How to Calculate and Improve It.

    Net revenue retention (NRR) is the percentage of recurring revenue you keep from your existing customers over a period, usually 12 months, after counting upgrades, downgrades, and cancellations. It excludes revenue from new customers. An NRR above 100% means your existing base is growing on its own, and below 100% means it is shrinking.

    If your revenue grew 15% last year, a fair next question is how much of that came from customers you already had. NRR answers it. Two companies can post identical growth, but one is adding customers faster than it loses them, while the other is quietly compounding what it already has. Investors, boards, and RevOps teams care about the difference.

    This guide explains what NRR measures, how to calculate it, what a good number looks like, how to diagnose a weak one, and what actually improves it.

    How to calculate net revenue retention

    The formula is:

    NRR = (starting recurring revenue + expansion โˆ’ contraction โˆ’ churn) รท starting recurring revenue ร— 100

    Take the customers you had on day one of the period. Add what they expanded, subtract what they downgraded and what churned, and divide by what they paid on day one. Customers who signed during the period are not included.

    Here’s an illustrative example for a SaaS company with $2,000,000 in ARR at the start of the year.

    Line Amount
    Starting ARR from existing customers $2,000,000
    + Expansion (upgrades, extra seats, cross-sell) $300,000
    โˆ’ Contraction (downgrades) $80,000
    โˆ’ Churn (cancellations) $120,000
    Ending ARR from the same customers $2,100,000
    NRR $2,100,000 รท $2,000,000 = 105%

    These buckets are the same ones in a revenue waterfall, which is why a clean waterfall makes NRR easy to calculate and explain. New-logo revenue sits in a separate line and never enters the NRR math.

    NRR, GRR, and logo retention: what each tells you

    Metric What it counts Can it exceed 100%? What it tells you
    Net revenue retention Revenue kept plus expansion, minus contraction and churn Yes Whether the existing base is growing or shrinking
    Gross revenue retention Revenue kept after contraction and churn, with expansion excluded No, capped at 100% How leaky the bucket is
    Logo retention Share of customers kept, regardless of size No Whether you’re losing many small accounts or a few big ones

    In the example above, gross revenue retention is ($2,000,000 โˆ’ $80,000 โˆ’ $120,000) รท $2,000,000 = 90%. Look at NRR and GRR together. A 105% NRR sitting on a 90% GRR means you’re losing a tenth of your base every year and relying on expansion to cover it. That’s a different company from one with 105% NRR and 97% GRR.

    What is a good NRR?

    Benchmarks vary by source, company size, pricing model, and customer segment, so treat any single number carefully. Two recent datasets give a sense of the range:

    Source Sample Median NRR Higher performers Median GRR
    SaaS Capital, 2026 survey Bootstrapped B2B SaaS, $3M to $20M ARR 103% 117.9% at the 90th percentile 91%
    Aleph and Benchmarkit, calendar 2025 B2B SaaS panel 102% About 108% in the top quartile 84%, down from 88%

    The Benchmarkit data also found that usage-based companies had a median NRR near 108%, compared with about 98% for seat-based ones. So pricing model matters. The practical takeaway is that a median private SaaS company sits a little above 100%, and anything well above that is strong. Compare yourself with companies at a similar size, price point, and segment, not with the best public software companies.

    Why NRR matters

    Expansion revenue is cheaper than new-customer revenue, because you already have the relationship, the implementation, and the trust. High NRR lets a company grow with less acquisition spend, and it shows up in valuations. It’s also the measure that a land and expand strategy is built to move: land small, prove value, then grow the account.

    A blended number can hide the problem

    Here’s the same $2,000,000 base split by segment, with illustrative numbers:

    Segment Starting ARR NRR GRR
    Small business $600,000 92% 82%
    Mid-market $900,000 108% 93%
    Enterprise $500,000 115% 96%
    Blended $2,000,000 About 105% About 90%

    The blended 105% looks healthy. Underneath, the small business segment shrinks every year, while enterprise carries the average. Always break NRR down by segment, plan, and customer age. It also helps to cut it by acquisition source, which is where closed-loop reporting comes in: if you can trace each customer back to the channel that brought them in, you can see which sources produce customers who stay and grow, and which ones produce customers who churn in a year.

    Diagnose before you fix

    A weak NRR has three possible causes, and each needs a different response. Use your waterfall to see which component is the problem.

    What you see Likely cause First move
    Low GRR, with high churn Poor onboarding, weak fit, or unnoticed risk Study churned accounts; build early-warning signals
    Contraction is large Over-sold seats, unused licenses, or poor packaging Review seat utilization; right-size plans at renewal
    GRR is fine, expansion is small No upgrade path, or nobody owns growth Add packaging steps and name an expansion owner
    Strong in one segment, weak in another Ideal customer mismatch Tighten targeting and change how you serve the weak segment

    How to improve net revenue retention

    Reduce churn. Since expansion can’t outrun a leaky base for long, start here. Make the first 90 days count with a clear onboarding path and a defined first-value milestone. Build a customer health score so you can spot at-risk accounts early, and attach a playbook to each risk band. Track champion changes, since a departed sponsor is a common warning sign.

    Reduce contraction. Watch seat utilization and flag accounts using far fewer licenses than they pay for. Offer right-sizing before renewal, so a downgrade is a planned conversation and not a surprise. Review packaging to make sure the plans fit how customers actually use the product.

    Grow expansion. Design pricing with natural upgrade steps tied to value, such as seats, usage, or advanced features. Have usage thresholds trigger alerts for the account owner. Pursue cross-sell where a second team or product genuinely fits, and name one owner for expansion, whether in sales or customer success. Our guide to land and expand covers expansion levers in more detail.

    Be careful with price increases. A list price rise can lift NRR in the short term, but if churn follows, GRR drops and the gain disappears. Watch both numbers together.

    What your data needs to track NRR reliably

    • A matching account ID between your CRM and billing system, so revenue lines up with the right customer.
    • Recurring revenue per account at the start of each period, stored as a snapshot, so you aren’t recalculating history.
    • Agreed definitions for expansion, contraction, churn, and reactivation. Decide how to treat a customer who cancels and returns, and a plan change that lowers revenue but keeps the customer.
    • Consistent currency handling if you sell in several currencies.
    • A monthly review. NRR is a good fit for the monthly commercial review in a RevOps meeting cadence.

    Mistakes to avoid

    • Including revenue from customers who joined during the period
    • Mixing recurring revenue with one-time fees and services
    • Letting teams define churn and contraction differently
    • Reporting a blended number without segment breakdowns
    • Celebrating NRR while GRR falls
    • Comparing yourself with companies at a very different size or pricing model

    Summary

    Net revenue retention measures how much recurring revenue you keep and grow from existing customers: (starting revenue + expansion โˆ’ contraction โˆ’ churn) รท starting revenue. It excludes new customers and can exceed 100%. Read it alongside gross revenue retention, which excludes expansion and shows how leaky the base is. Recent benchmarks put the median around 102% to 103%, with usage-based companies higher than seat-based ones, though samples differ.

    Break NRR down by segment and acquisition source, because a healthy blended number can hide a shrinking segment. Use your revenue waterfall to see whether churn, contraction, or weak expansion is the problem. Fix churn first, then contraction, then grow expansion with clear upgrade paths and a named owner, and make sure your CRM and billing share account IDs and definitions.

    FAQ

    What is net revenue retention?

    It’s the percentage of recurring revenue retained from existing customers over a period, including expansion and subtracting contraction and churn. It excludes new customers.

    How do you calculate NRR?

    Add expansion to starting recurring revenue, subtract contraction and churn, divide by starting recurring revenue, and multiply by 100. Use only the customers who existed at the start of the period.

    What’s the difference between NRR and GRR?

    NRR includes expansion and can exceed 100%. GRR excludes expansion, counts only contraction and churn, and can’t exceed 100%. GRR shows how much you lose, and NRR shows the net result.

    What is a good NRR for B2B SaaS?

    Medians in recent benchmarks sit around 102% to 103%, with stronger performers at 108% or more, and some top-decile figures near 118%. Compare yourself with companies of a similar size, price point, and pricing model.

    Can NRR be too high?

    High NRR is rarely a problem, but it can hide weaknesses. If it relies on a few large expanding accounts while many small ones churn, GRR and logo retention will show the problem.

    Should NRR be calculated monthly or annually?

    The headline figure is usually annual, using a 12-month cohort. Many teams track it monthly on a trailing 12-month basis, which smooths seasonality. Whichever you use, keep the definition consistent.

    How do we improve NRR fastest?

    Diagnose first. If churn is the main drag, fix onboarding and early warning signals. If contraction is large, review seat utilization and packaging. If expansion is the gap, add upgrade paths and name an owner for growth.

  • Land and Expand: What It Means and How It Works

    Land and expand is a go-to-market strategy where you win a small, low-risk deal with a customer first (the “land”), prove the product’s value quickly, and then grow the account over time through more seats, departments, or features (the “expand”). It’s one of the main engines behind net revenue retention in B2B SaaS.

    If you’ve ever watched a vendor start with one team at your company and somehow end up with a company-wide contract two years later, you’ve seen land and expand in action. It’s not an accident. It’s a deliberate motion that a lot of successful SaaS companies build their entire go-to-market strategy around.

    This post breaks down what land and expand actually means, how the mechanics work, what the numbers look like, and how you’d start building one if you’re new to the concept.

    What Is Land and Expand, Exactly?

    At its core, land and expand is a B2B go-to-market strategy where a vendor secures a minimal presence in a prospective client’s organization, then gradually and systematically grows that presence within the account. Instead of asking a prospect to sign off on a massive enterprise-wide contract on day one, you lower the barrier to entry.

    Typically that means selling a low-cost, scoped-down, or even freemium version of the product to a single team or department. If that small group gets real value from it, you’ve got your opening to go back with proposals for broader deployment, more advanced features, or additional products.

    It’s a two-phase approach. A company first sells a small deal to one team or department (the “land”), proves value, and then grows the account over time by adding users, departments, features, or use cases (the “expand”).

    How Is It Different From Upselling or PLG?

    These terms get blended together, so a quick comparison helps.

    Term What it is How it relates
    Land and expand A planned small entry, then a planned growth path The whole strategy
    Upsell Selling a higher tier or more volume to an existing customer One tactic inside the expand phase
    Cross-sell Selling an adjacent product to an existing customer Another tactic inside the expand phase
    Product-led growth The product drives acquisition and conversion Often how the land happens
    Enterprise-wide first deal One large contract up front The opposite approach: more risk for the buyer, less room to grow

    How Does the Land and Expand Strategy Actually Work?

    The land phase and the expand phase each have a distinct job.

    The land phase is about acquiring the customer and making sure they succeed fast. The goal is to quickly demonstrate value, meet the customer’s initial needs, and build the foundation for a longer relationship. This is also where a messaging framework earns its keep, because the way you position that first small deal shapes whether the buyer sees room to grow later. If you haven’t nailed down how you talk about your product’s value, read up on what a messaging framework is before you build your land pitch.

    The expand phase kicks in once the customer is onboard and getting value. The focus shifts to identifying opportunities to grow the account and deepening the relationship through upselling, cross-selling, or adding seats.

    Here’s the part people often get wrong: the initial land deal shouldn’t be your full pitch. A rule of thumb some teams use is that the land should represent roughly 20 to 40% of what the account could eventually be worth. Treat that as a starting hypothesis, not a law. The principle behind it is sound, though: if you land at the maximum spend on day one, you’ve got nowhere to expand to later. That’s a positioning and segmentation problem as much as a sales one, which is why it connects closely to how you’ve segmented your market in the first place.

    What Does One Account Look Like Over Two Years?

    Here’s a made-up example to make the shape concrete. These numbers are illustrative, not benchmarks.

    When Event Change Account ARR
    Month 0 Land: one team buys a starter plan +$20,000 $20,000
    Month 6 Seat expansion as the team grows +$8,000 $28,000
    Month 12 Tier upgrade for security and admin features +$12,000 $40,000
    Month 18 Cross-sell: a second department adds a new module +$15,000 $55,000

    The land was about 36% of where the account ended up. Each expansion had a different trigger: headcount, a feature need, and a new use case. That’s the pattern to look for in your own accounts.

    Why Does Land and Expand Matter for B2B Growth?

    Because new-logo acquisition is expensive, and expansion revenue is comparatively cheap. You already have the relationship, the implementation, and the trust. The only thing left to do is grow it.

    This shows up most clearly in net revenue retention (NRR), which measures how much recurring revenue you keep and grow from existing customers over a period, after accounting for upgrades, downgrades, and cancellations. An NRR above 100% means your existing accounts generated more revenue than they started with, without a single new customer added.

    A simple, illustrative calculation: say a cohort of customers paid $1,000,000 in ARR a year ago. Over the year they expanded by $200,000, contracted by $50,000, and churned $100,000. That’s ($1,000,000 + $200,000 – $50,000 – $100,000) divided by $1,000,000, or 105% NRR. The cohort grew without any new customers.

    For context, benchmarks vary by source and customer size, but median private B2B SaaS NRR has been reported at around 101%, with SaaS Capital’s 2025 data showing companies with $25,000 to $50,000 ACV at a 102% median and 111% in the top quartile. Hitting well above 100% is the mark of a working expansion motion, not the default.

    Datadog is a commonly cited real-world example. Its filings describe a land-and-expand business model and report a trailing 12-month dollar-based net retention rate in the low 120s as of mid-2026, up from about 120% a year earlier. At the end of 2025, it reported that 84% of customers used two or more products and 33% used six or more, which is exactly what a successful expand phase looks like.

    Honestly, most “expansion” problems I see aren’t a sales skills issue. They’re a product and pricing design issue. If your pricing has no natural upgrade path and your product doesn’t surface usage limits or ROI data to the customer, there’s nothing for a rep to expand into, no matter how good they are at the pitch.

    What Are the Common Expansion Methods?

    Most land and expand motions rely on a handful of repeatable levers:

    1. Seat or volume expansion: licensing more users on the same team, or bringing the product to new departments.
    2. Tier migration or upgrade sales: moving a customer from a Starter or Professional plan to Enterprise, unlocking features like security, compliance, or automation.
    3. Cross-sell: selling an adjacent product or module to a team already using your core product.
    4. Usage-based growth: revenue that grows automatically as the customer’s usage increases, common in consumption-priced products.

    The best land and expand companies don’t rely purely on sales reps to drive this. Usage limits that trigger upgrade prompts, collaboration features that pull in adjacent teams, and admin dashboards that show department-level ROI all create expansion pressure inside the product itself.

    How Do You Build a Land and Expand Motion? (Checklist)

    If you’re setting this up for the first time, here’s a practical sequence to work through:

    1. Design the land offer on purpose. Decide what the first, small deal looks like and scope it so there is clear room to grow.
    2. Nail onboarding. The land phase lives or dies on whether the customer sees value fast. A clunky first 30 days kills any chance of expansion later.
    3. Build expansion signals into the product. Usage caps, collaboration prompts, and ROI dashboards do a lot of the expansion legwork without a rep lifting a finger.
    4. Assign a named expansion owner. Someone (sales, customer success, or a hybrid role) needs explicit responsibility for watching the account and acting on signals, rather than hoping expansion happens on its own.
    5. Treat every new department as a fresh discovery cycle. Don’t assume what worked with the first team applies to the next one.
    6. Track NRR every quarter. It’s the clearest read on whether your expand motion is working or just looks good in a deck.

    Pro tip: map your last 10 expansion deals and write down what actually triggered each one (a usage limit, a new hire, a renewal conversation). If you can’t find a pattern, you don’t have an expansion motion yet. You have a handful of lucky upsells.

    Where Land and Expand Goes Wrong

    • The land is too big. If the first deal is already the most the account will ever spend, there’s nothing left to expand into.
    • The land is too small to matter. A deal so tiny that nobody at the customer depends on it won’t create the pull that leads to expansion.
    • No one owns expansion. Sales assumes customer success will raise it, customer success assumes sales will, and the account sits.
    • Pricing has no upgrade path. Without natural steps between plans, every expansion becomes a custom negotiation.
    • Onboarding is treated as an afterthought. Customers who never reach value don’t expand, no matter how well the deal was sold.

    Where Land and Expand Fits in Your Broader GTM Strategy

    Land and expand isn’t a standalone tactic you bolt onto an existing sales process. It needs to be planned into your go-to-market strategy from the start, including how you scope the initial offer in your go-to-market launch plan and how you’ve segmented accounts so you know which ones even have room to expand. It also pairs naturally with certain motions, so it helps to understand your options in GTM motion types before you commit.

    Summary

    Land and expand is a go-to-market strategy where you win a small, low-risk first deal, prove value fast, and then grow the account through more seats, higher tiers, additional products, or rising usage. It’s different from a single upsell: it’s a planned entry point followed by a planned growth path, and it’s one of the main drivers of net revenue retention in B2B SaaS.

    To build one, design the land offer on purpose, get onboarding right, build expansion signals into the product, name an expansion owner, treat each new department as fresh discovery, and track NRR every quarter. The usual failures are a land that’s too big, no upgrade path in the pricing, and no clear owner for growing the account.

    FAQ

    Is land and expand the same as upselling?

    Not exactly. Upselling is one tactic inside the expand phase. Land and expand is the whole strategy: a deliberate small entry point followed by a planned growth path, not just a single upsell conversation.

    What’s a good net revenue retention rate for a land and expand business?

    It depends on your segment, and sources differ. Median private B2B SaaS NRR has been reported at around 101%, and companies with strong expansion motions sit well above that. Datadog, a well-known land-and-expand company, reported a low-120s trailing 12-month rate in mid-2026. Compare yourself against companies with similar contract sizes.

    Does land and expand work for smaller companies, or only enterprise SaaS?

    It works at both ends, but the shape changes. It’s especially common in SaaS and B2B sales, where companies start with a limited license or pilot and scale as trust and adoption grow, whether the account is a small business or a large enterprise.

    What’s the biggest reason a land and expand motion fails?

    Usually the land deal was priced or scoped too big to begin with. If the first deal is already the maximum an account will ever commit to, there’s no room left to expand.

    Do I need a customer success team to make land and expand work?

    You don’t strictly need one, but it helps. Customer success is often the function that spots expansion signals early, such as rising usage or new teams joining. Without a team, make sure someone else clearly owns watching those signals.

    How do I know how big my first deal should be?

    Start from what a single team needs to see real value, then check that there is at least a few times that amount of additional potential in the account. Some teams use 20 to 40% of eventual account value as a rough guide, but test it against your own expansion history.

  • What Is a Revenue Waterfall? A RevOps Beginner’s Guide

    A revenue waterfall is a chart that bridges your starting revenue to your ending revenue for a period, breaking out every gain and loss along the way: new business, expansion, contraction, and churn. It shows exactly where growth or decline came from, not just the final total.

    If you’ve ever stared at a quarterly revenue number and had no idea whether it grew because of new customers or just a couple of big upsells, you’ve felt the problem a revenue waterfall solves. A single top-line number hides the whole story. A waterfall forces that story into the open.

    This matters more the bigger your business gets. Once you have renewals, upgrades, downgrades, and churn all happening in the same month, you need a structured way to see what’s actually driving the change, not just the net result.

    What Is a Revenue Waterfall, Exactly?

    A revenue waterfall (sometimes called an ARR waterfall, ARR bridge, or revenue bridge) is a visual model that shows how your recurring revenue moved from one period to the next. It starts with your beginning revenue, adds everything that pushed it up, subtracts everything that pulled it down, and lands on your ending revenue.

    Think of it as a step-by-step accounting of change, not a snapshot. One finance-focused description puts it well: a revenue waterfall chart shows how a starting revenue figure changes through a series of gains and losses to reach an ending figure, and by the time you reach the final bar, you can see exactly what happened between point A and point B.

    If you’re still getting familiar with RevOps as a discipline, it helps to back up a step first. Our guide on what RevOps actually is covers the basics of how revenue operations connects marketing, sales, and customer success data into one system, which is exactly the kind of system a revenue waterfall depends on.

    How Does a Revenue Waterfall Work?

    The mechanics are simpler than the name suggests. Every dollar of revenue change during a period gets sorted into one bucket, and those buckets get stacked (or “waterfalled”) between your starting and ending numbers.

    A typical waterfall follows this flow:

    1. Start with beginning ARR or MRR. This is your recurring revenue total at the start of the period.
    2. Add new revenue. Money from brand-new customers signed during the period.
    3. Add expansion revenue. Upsells and cross-sells from existing customers who bought more.
    4. Subtract contraction revenue. Revenue lost from existing customers who downgraded.
    5. Subtract churned revenue. Revenue lost from customers who canceled entirely.
    6. Land on ending ARR or MRR. This becomes next period’s starting number.

    That sequence, start, add, subtract, end, is the whole model. The value isn’t in the math (it’s addition and subtraction). The value is in forcing every contract to get classified consistently, so finance, sales, and RevOps are all looking at the same definitions.

    A Worked Example With Real Numbers

    Abstract steps are easier to follow with numbers attached. Here’s a made-up quarter for a small SaaS company.

    Line Amount What happened
    Beginning ARR $2,000,000 Recurring revenue on day one of the quarter
    + New $300,000 Twelve new customers signed
    + Expansion $150,000 Existing customers added seats and tiers
    – Contraction $50,000 A few customers downgraded
    – Churn $100,000 Several customers canceled
    Ending ARR $2,300,000 $2,000,000 + $300,000 + $150,000 – $50,000 – $100,000

    Ending ARR grew by $300,000, or 15%. That looks healthy. But the waterfall shows something the top-line number doesn’t: $150,000 of the revenue the company had at the start of the quarter either shrank or left. Net of expansion, existing customers contributed $0 of growth. Every dollar of net growth came from new business.

    That’s a very different story from “we grew 15%.” It tells a RevOps team to look at retention, not just pipeline.

    What Are the Core Components of a Revenue Waterfall?

    Most revenue waterfalls track the same handful of movement types, though naming varies slightly by company:

    • New revenue from newly acquired customers
    • Expansion revenue from upsells or cross-sells to existing accounts
    • Contraction revenue from downgrades on existing accounts
    • Churned revenue from cancellations
    • Renewal revenue from contracts that simply continued

    Getting these categories consistent across teams is harder than it sounds. One breakdown of the process notes that consistent definitions across sales, finance, and RevOps are essential, because if sales calls a downgrade “churn” and finance calls it “contraction,” the waterfall won’t reconcile to anything. Honestly, this is where most waterfall projects quietly fail: not the chart, the definitions behind it.

    A few edge cases come up constantly and are worth deciding in advance. What counts as a downgrade versus a plan change that’s revenue-neutral? If a customer cancels and comes back two months later, is that churn plus new, or a reactivation? When a customer moves to a different product and pays less in total, is that contraction or churn plus new? There’s no universal answer. What matters is that you pick one rule and apply it every month.

    Pro tip: before you build anything in a BI tool, get sales, finance, and RevOps in a room (or a shared doc) and agree on one definition for each movement type. Write it down. Revisit it every time someone argues about a number.

    Revenue Waterfall vs. ARR Waterfall vs. Deferred Revenue Waterfall

    Here’s where it gets a little confusing, because “revenue waterfall” gets used for two related but different things.

    The version most RevOps and sales teams care about is the ARR or bookings waterfall: it tracks how your recurring revenue base grew or shrank through new business, expansion, contraction, and churn. This is the one that shows up in board decks and GTM reviews.

    The other version lives in accounting and finance. It tracks how booked or billed revenue gets recognized over time under revenue recognition standards like ASC 606, moving from deferred revenue on the balance sheet into recognized revenue on the income statement as you deliver the service. One comparison puts it plainly: a revenue waterfall in this sense shows what hit the profit and loss statement, as opposed to tracking the health of your customer base.

    Both are legitimate and both matter, they just answer different questions. RevOps typically owns or heavily influences the ARR version. Finance usually owns the recognition version. If you’re new to this, assume people mean the ARR/bookings version unless the conversation is specifically about accounting compliance.

    Why Does a Revenue Waterfall Matter for RevOps Teams?

    Because net revenue growth can lie to you. A company can post flat revenue while actually losing a chunk of its customer base to churn and masking it with one large expansion deal. Without a waterfall, nobody notices until it’s a much bigger problem.

    A waterfall gives you a single, shared view of revenue movement instead of three teams pulling three different numbers from three different systems. It also becomes a genuine diagnostic tool: when contraction or churn spikes in the waterfall, that’s a signal worth chasing down before it shows up in next quarter’s board meeting, not after.

    This kind of cross-functional reporting discipline is a good marker of RevOps maturity too. If your team can’t yet produce a clean, reconciled waterfall every month, that’s worth knowing. It’s one of the signals we cover in our breakdown of RevOps maturity stages, since the ability to build and trust a waterfall usually tracks with how far along your RevOps function actually is.

    Questions a Waterfall Helps You Answer

    Once you have a reliable waterfall, it starts answering questions that used to take a week of spreadsheet work:

    • Is growth coming from new customers or from the ones we already have?
    • Is churn getting worse, or did one large account distort the quarter?
    • Are customers expanding enough to offset the ones who leave?
    • Which period had the biggest drop, and what changed around then?
    • Does the number we told the board match what billing and the CRM say?

    That last question is quietly the most valuable one. A waterfall that reconciles between the CRM and billing is a sign your data is in decent shape. One that never quite adds up usually points to deals classified inconsistently, or contract changes that never made it into the CRM.

    Who Actually Owns the Revenue Waterfall?

    It depends on the company, but it shouldn’t live in a silo. RevOps usually owns the data pipeline and category definitions, finance usually owns the accounting accuracy, and sales and customer success leaders use the output to manage their teams.

    That shared ownership is part of why distinguishing these functions matters. If you’re unclear on where RevOps responsibilities end and sales ops or marketing ops responsibilities begin, our post on RevOps vs. sales ops vs. marketing ops walks through exactly where those lines sit.

    How to Build a Simple Revenue Waterfall: A Starter Checklist

    You don’t need enterprise software to start. A basic waterfall can live in a spreadsheet or a simple BI dashboard. Here’s a practical starting sequence:

    1. Pull your beginning ARR or MRR for the period from your CRM or billing system.
    2. Export every contract change (new, renewal, upgrade, downgrade, cancellation) that happened in the period.
    3. Classify each change into one of the standard buckets: new, expansion, contraction, or churn.
    4. Sum each bucket separately. Don’t net them against each other yet.
    5. Stack the buckets between your beginning and ending totals to confirm they reconcile.
    6. Review the result with sales, finance, and customer success before calling it final.

    That last step matters more than people expect. A waterfall that only RevOps has looked at isn’t trustworthy yet; it needs other eyes on it to catch misclassified deals.

    Common Mistakes to Avoid

    • Netting buckets together. Showing “net expansion” hides how much was churned and how much was upsold. Keep each bucket visible.
    • Skipping the reconciliation. If beginning plus movements doesn’t equal ending, something is misclassified or missing.
    • Changing definitions midstream. Redefining churn halfway through the year makes month-to-month comparisons meaningless.
    • Building it once and never refreshing. A waterfall is only useful on a regular cadence, usually monthly.
    • Using it only for the board. The biggest value comes when sales, customer success, and RevOps use it to ask what changed and why.

    Summary

    A revenue waterfall bridges beginning revenue to ending revenue for a period by breaking out every movement in between: new, expansion, contraction, and churn. It shows where growth actually came from, which a single top-line number can’t. The worked example in this guide shows how a company can grow 15% while existing customers contribute nothing net, a pattern only the waterfall makes visible.

    The model itself is simple addition and subtraction. The hard part is agreeing on definitions across sales, finance, and RevOps, and applying them consistently every month. RevOps usually owns the ARR or bookings version, while finance owns the revenue recognition version. To build your first one, pull beginning ARR, classify every contract change, sum each bucket without netting, confirm the totals reconcile, and review with the other teams before you trust it.

    FAQ

    Is a revenue waterfall the same as a sales funnel?

    No. A sales funnel tracks leads moving through stages toward a first deal. A revenue waterfall tracks how your existing recurring revenue base changes over time, including renewals, upgrades, downgrades, and churn, long after that first deal closes.

    Do I need special software to build a revenue waterfall?

    Not to start. A spreadsheet works fine for an early-stage company. As your contract volume grows, most teams move to a BI tool or a revenue recognition platform because manually classifying every contract change stops scaling.

    How often should we update our revenue waterfall?

    Monthly is the most common cadence for RevOps and GTM reporting, since it lines up with how most SaaS companies track MRR. Finance teams tracking revenue recognition under ASC 606 often need it on the same monthly cycle for compliance reasons.

    What’s the difference between an ARR waterfall and an MRR waterfall?

    They’re the same model applied to different time horizons: ARR waterfalls use annual recurring revenue, MRR waterfalls use monthly recurring revenue. Companies with shorter sales cycles or month-to-month contracts tend to lean on MRR waterfalls for faster signal.

    Why do sales and finance sometimes disagree on waterfall numbers?

    Usually because they’re using different definitions for the same movement type, like calling a downgrade “churn” in one system and “contraction” in another. Getting everyone aligned on shared definitions before you build the waterfall is the single biggest thing you can do to avoid this.

    What should we do if the waterfall doesn’t reconcile?

    Start by checking for contract changes that exist in billing but not in the CRM, or the reverse, then look for deals classified into the wrong bucket. A gap between beginning plus movements and ending ARR almost always traces back to a missing record or an inconsistent definition, not a flaw in the model itself.

  • How Product Led Growth CRM Supports SaaS Growth

    Product-led growth companies grow differently than sales-led ones, users activate themselves, expansion often starts inside the product before a rep ever gets involved, and the biggest revenue lever is frequently net revenue retention rather than new-logo acquisition. A product led growth CRM supports this model by connecting product usage data directly to revenue workflows, in ways that shape growth across the entire customer lifecycle, not just at the point of sale.

    That difference matters more than it sounds. A sales-led company can run a perfectly functional revenue engine on a CRM that only knows about deals, contacts, and rep activity, because that’s genuinely where most of the growth signal lives. A PLG company running the same kind of CRM is missing the actual growth engine entirely, since the signals that predict expansion and churn are happening inside the product, not inside a sales rep’s activity log.

    The Core Shift: From Sales-Driven to Usage-Driven Growth

    In a traditional sales-led model, growth is driven primarily by outbound and inbound sales activity acting on marketing-qualified leads. In a PLG model, growth is driven by users discovering value in the product itself, with sales acting on signals the product generates rather than initiating contact cold. A PLG CRM is what makes that second model operationally possible at scale.

    This shift isn’t just a change in tooling, it’s a change in who’s actually driving the growth conversation. In a sales-led model, a rep decides when to reach out based on their own judgment and a lead score. In a PLG model, the product itself is generating that judgment continuously, a user hitting a usage limit, inviting colleagues, or exploring a specific feature is effectively raising their hand in real time, whether or not anyone at the company is watching for it.

    Where a PLG CRM Directly Supports Growth

    1. Turning Self-Serve Activation Into a Repeatable Growth Engine

    By tracking which specific in-product actions correlate with long-term retention and expansion, a PLG CRM lets growth and product teams double down on the onboarding flows and features that actually drive activation rather than guessing based on anecdote. Without this, teams tend to rely on whatever the loudest customer said in a support call or whatever a product manager’s gut feeling suggests, which produces onboarding changes that feel reasonable but aren’t actually tied to what the data shows converts.

    This matters compounding over time. Once a team can reliably identify the two or three activation milestones that predict long-term retention, every future onboarding experiment can be measured against whether it moves users toward those specific milestones faster, rather than against a vague sense of “engagement” that doesn’t actually correlate with anything downstream.

    2. Identifying Expansion Opportunities Before the Customer Asks

    When usage data shows a team approaching a seat limit or hitting a usage cap tied to a paid tier, a PLG CRM can surface that as an expansion opportunity proactively, instead of waiting for the customer to reach out directly, supporting revenue growth through upsell. This is one of the clearest, most concrete ways a PLG CRM pays for itself, since a proactive outreach at the exact moment a team is approaching a limit converts meaningfully better than a generic quarterly check-in email.

    The alternative, waiting for the customer to initiate the upgrade conversation themselves, quietly leaves revenue on the table in two ways. Some teams simply work around the limit rather than upgrading, using a workaround that limits their own value from the product. Others do want to upgrade but never get around to it, since it’s rarely anyone’s top priority to proactively ask a vendor for a bigger bill.

    3. Reducing Time-to-Value for New Sales-Assist Motions

    As PLG companies mature, many add a sales-assist layer to help larger accounts get more value faster. A PLG CRM supports this by giving reps full context on what a user or account has already done in the product, so outreach is relevant rather than generic.

    This context difference shows up immediately in how a conversation actually goes. A rep opening with “I noticed your team has invited twelve people and is using the reporting feature heavily, have you looked at our advanced analytics tier?” lands completely differently than a rep starting from a blank contact record and asking generic discovery questions the customer has effectively already answered through their own usage.

    4. Supporting Net Revenue Retention as the Primary Growth Metric

    For many PLG companies, expansion and retention matter more to long-term growth than new customer acquisition. A PLG CRM built around usage-driven signals gives revenue and customer success teams the visibility needed to actively manage and improve NRR, rather than only reacting to churn after it happens.

    The distinction between managing NRR and reacting to churn is significant in practice. A team reacting to churn finds out an account is at risk when the cancellation request arrives, at which point there’s often very little left to do. A team actively managing NRR sees usage declining weeks or months earlier, while there’s still time to understand why and intervene, whether that means a check-in call, a feature walkthrough, or addressing a support issue that’s been quietly souring the relationship.

    5. Aligning Product, Marketing, and Sales Around the Same Growth Signals

    Because a PLG CRM centers on product usage data, it gives product, marketing, and sales teams a shared, consistent view of what’s actually driving growth, reducing the disconnect that often exists when each team relies on separate, siloed data sources.

    Without that shared view, it’s common for product to believe a feature is driving retention based on adoption numbers, while sales has no visibility into that signal at all and continues pitching based on whatever messaging worked eighteen months ago. A shared data layer doesn’t automatically produce alignment on its own, but it removes the most common excuse for its absence, that each team was simply looking at different numbers.

    A Simple Example of the Growth Loop in Practice

    1. A user signs up and activates a core feature, tracked automatically by the PLG CRM.
    2. Usage data shows the team is inviting more colleagues and approaching a plan limit.
    3. The CRM automatically flags the account as expansion-ready and routes it to a sales-assist rep.
    4. The rep reaches out with context specific to the team’s actual usage, rather than a generic upsell pitch.
    5. Post-expansion, the CRM continues tracking usage to flag future expansion or renewal risk.

    This loop, activation, signal detection, targeted action, continued monitoring, is the mechanism through which a PLG CRM directly supports compounding SaaS growth, rather than just recording what already happened.

    The word “compounding” is doing real work in that sentence. Each pass through the loop doesn’t just capture one expansion event, it also feeds back into the activation-milestone data from step one, refining which signals the team trusts for the next account and the one after that. Over enough cycles, the model of what actually predicts expansion or churn gets sharper, which is exactly the kind of improvement a purely reactive, spreadsheet-and-support-ticket approach can never produce on its own.

    What Happens Without This Infrastructure

    Without a PLG CRM, growth signals typically live scattered across a product analytics tool, a support inbox, and informal customer success knowledge, meaning expansion opportunities get caught late, if at all, and growth becomes reactive rather than proactive.

    This fragmentation has a specific, recognizable pattern. A customer success manager who’s been with the company a while might personally remember that a particular account has been growing fast and mention it in a team meeting, but that knowledge lives entirely in their head and disappears the moment they change roles or leave. A newer CSM covering the same account has no way to see that signal at all, since it was never captured anywhere systematic, and the expansion opportunity either gets caught late by coincidence or missed entirely.

    Growth Follows the Data You Can Actually Act On

    A product led growth CRM’s real contribution to SaaS growth isn’t the dashboards themselves, it’s making product usage data actionable for revenue teams in near real time, so expansion and retention become something the business actively manages rather than something that just happens or doesn’t.

    Summary

    A product-led growth CRM shifts revenue growth from a sales-initiated activity to something driven by usage signals the product itself generates. It supports growth in five concrete ways: turning activation data into a repeatable engine for improving onboarding, catching expansion opportunities before a customer asks, giving sales-assist reps real usage context instead of a blank contact record, making net revenue retention something a team actively manages rather than reacts to, and giving product, marketing, and sales a shared view of what’s actually driving growth instead of siloed, conflicting data.

    The growth loop this enables, activation, signal detection, targeted action, continued monitoring, compounds over time, since each cycle refines what the team trusts as a genuine predictor of expansion or churn. Without this infrastructure, the same signals still exist, but they live scattered across a product analytics tool, a support inbox, and individual team members’ memory, which means expansion opportunities and churn risk both get caught late, if they’re caught at all.

    FAQ

    How is a PLG CRM different from a traditional CRM?

    A traditional CRM is built around deals moving through a sales-owned pipeline, driven by rep activity. A PLG CRM treats product usage as the primary source of lifecycle data, with sales and customer success acting on signals the product generates, like activation milestones or usage approaching a plan limit, rather than initiating the process themselves.

    Does a PLG CRM replace the need for a sales team entirely?

    No. Most mature PLG companies add a sales-assist layer for larger accounts or enterprise upsell rather than staying purely self-serve forever. A PLG CRM supports that layer by giving reps full usage context when they do get involved, so outreach is targeted rather than a cold, generic pitch.

    Why does net revenue retention matter more than new customer acquisition for PLG companies?

    Because expansion revenue from existing accounts is often cheaper and more predictable than acquiring new customers, and a well-designed PLG CRM makes it possible to actively manage that expansion, rather than simply hoping it happens. Companies that only track new-logo acquisition can look like they’re growing while quietly losing ground on retention.

    What kind of usage signals typically indicate expansion readiness?

    Common signals include a team approaching or hitting a seat or usage limit tied to a paid tier, multiple users being invited within the same account, and increased adoption of features gated behind a higher plan. The specific signals that matter most vary by product, which is why mapping your own activation and expansion milestones matters more than adopting a generic model.

    What happens if a company delays adopting a PLG CRM?

    Growth signals continue to exist, but they stay scattered across a product analytics tool, a support inbox, and individual team members’ informal knowledge. Expansion opportunities get caught late or missed entirely, and churn risk typically only becomes visible once a cancellation request has already arrived, by which point there’s little left to do about it.