Tag: customer success

  • Customer Onboarding Workflows: How to Shorten Time to First Value

    A customer onboarding workflow is the repeatable sequence of steps, owners, triggers, and checkpoints that takes a new customer from signed contract to first value. Shortening time to first value (TTFV) means removing every step that doesn’t move the customer toward that first meaningful outcome, and automating the waiting, reminding, and handing off that slows everything else down.

    The deal closes, the celebration happens in Slack, and then nothing happens for two weeks. The customer success manager hasn’t been told what was promised, the customer’s admin is waiting for a kickoff invite, and the contract that was so urgent during the sales cycle sits unused. Those quiet weeks are where renewals are won or lost, because customers who don’t see value early start questioning the purchase.

    This guide shows how to define first value, find where onboarding time goes, design a workflow with clear triggers and owners, and measure whether it’s working.

    Start by defining “first value”

    First value is the first tangible result the customer cares about. It’s not “the kickoff happened” or “the account is configured.” Define it with the customer at kickoff, make it measurable, and pick one milestone per customer segment, so every early task points at it.

    Weak definition (an action) Stronger definition (an outcome)
    Admin logged in First live workflow running on real data
    Integration connected First report built from live data and shared with the sponsor
    Training completed Ten team members have completed their first task in the product
    Account configured The first invoice, ticket, or campaign processed end to end

    Time to first value is the number of days from signature, or from closed-won, to that event. It’s the headline metric for the rest of this guide.

    Where the days actually go

    Most teams assume onboarding is slow because setup is hard. Often the time goes to waiting. Here’s an illustrative breakdown of 52 days from closed-won to first value.

    Phase Days Who controls it
    Waiting for the handoff to reach the CSM 6 Us
    Scheduling the kickoff 8 Shared
    Data, integration, and security setup 21 Mostly the customer
    Configuration 7 Us
    Training 5 Shared
    Waiting on a stakeholder or a decision 5 The customer
    Total 52

    Only about a quarter of those days are hands-on work. The rest is handoff lag, scheduling, and customer-side readiness. That points to the highest-leverage fixes: capture the right information before the deal closes, trigger the handoff automatically, and get the customer’s technical prerequisites started in the sales cycle, not after it.

    Segment onboarding into tracks

    One onboarding model for every customer either overserves small accounts or underserves large ones. Most B2B teams define a small number of tracks, typically a high-touch track led by a CSM for complex accounts and a low-touch, largely self-serve track for the rest.

    Track Fits Touch model Core workflow
    High-touch Complex integrations, security reviews, many stakeholders Dedicated CSM or implementation lead Mutual success plan, weekly check-ins, project plan
    Mid-touch Moderate complexity Pooled CSM plus guided setup Kickoff call, checklist, scheduled office hours
    Tech-touch Simple setup, fast first value Automated, in-app guidance Triggered emails, in-app checklist, a help channel

    Assign the track from deal data, such as contract size, number of integrations, and security requirements, and record it on the deal so the workflow can route automatically. Set the thresholds from your own customers, since common ARR cut-offs vary widely.

    The onboarding workflow, stage by stage

    Stage Trigger Automated actions Human actions Exit criteria
    1. Handoff Deal moves to closed-won Create the onboarding project; notify the CSM; send a welcome message; require handoff fields Rep confirms commitments and stakeholders CSM has the full handoff packet
    2. Kickoff Handoff complete Send a scheduling link within a day; circulate a prework checklist Agree the first-value milestone, owners, and dates in a shared plan Mutual success plan signed off
    3. Setup Kickoff done Assign customer tasks; send reminders; flag blockers older than a set number of days Resolve technical and security issues Integrations live; data flowing
    4. Enablement Setup complete Role-based training invites; in-app guides; short videos Live training for key users Key users active
    5. First value Usage event fires Detect the milestone; notify the CSM; send a recognition message Confirm value with the sponsor Milestone confirmed and recorded
    6. Transition First value confirmed Start health scoring; schedule the first review Plan adoption and expansion Account moves to ongoing customer success

    Stage one is where onboarding is often won or lost. The handoff packet should carry stakeholders, the commitments made during the sale, success criteria, technical requirements, commercial terms, and any billing details. Our guide to quote-to-cash covers the contract and billing side of that handoff, and our piece on routing, handoffs, and pipeline hygiene covers tools that help.

    Automations that earn their keep

    Trigger Automation Owner
    Deal closed-won Create the onboarding record, assign the track, notify the CSM RevOps
    No kickoff scheduled within two business days Escalate to the CSM manager CS lead
    Customer task overdue by five days Send a reminder, then loop in the executive sponsor CSM
    No product activity for seven days after setup Alert the CSM and add the account to a stalled watchlist CSM
    First-value event detected Record the date, notify the team, and start health scoring RevOps and CS

    The timings above are examples to adapt. You can build most of this with CRM workflows, and many teams add an onboarding or implementation platform such as Rocketlane when projects get complex, plus in-app guidance for the tech-touch track. Whatever you use, make sure onboarding status flows back to the CRM so the whole revenue team can see a stalled implementation, not just the CS team.

    What to measure

    Metric What it tells you
    Time to first value Days from closed-won to the first-value milestone
    Onboarding cycle time by phase Which stage is slowing everything down
    Onboarding completion rate The share of customers finishing the plan
    Activation rate The share of users or accounts reaching the activation event
    Stalled accounts Accounts with no progress for a set period
    Early support tickets per account Whether setup friction is generating avoidable questions

    Baseline these for each track before you set targets. Published benchmarks are of limited help because definitions differ. One 2025 benchmark of 62 B2B SaaS companies, for example, reported an average activation rate around 37.5% and a time to value of about a day and a half, but those figures describe product-led signups, not enterprise implementations that take weeks. Compare yourself only with like for like.

    Early onboarding data is also your earliest health signal. Feed milestone completion, stalled status, and early support volume into your customer health score, so a customer that’s behind at day 30 shows up before the renewal conversation. Faster, smoother onboarding supports net revenue retention directly.

    A before-and-after example

    Using the illustrative 52-day example, a team makes four changes: technical discovery moves into the sales cycle, handoff fields become required, the handoff triggers automatically, and an in-app setup wizard replaces manual integration steps.

    Phase Before (days) After (days) What changed
    Handoff to CSM 6 1 Automatic trigger and required fields
    Kickoff scheduling 8 2 Scheduling link sent within a day
    Data, integration, security 21 12 Prework started in the sales cycle; setup wizard
    Configuration 7 5 Templates for common setups
    Training 5 4 Role-based in-app guides
    Waiting on stakeholders 5 3 Overdue reminders and sponsor escalation
    Total 52 27 About 48% faster

    None of the changes are exotic. They’re mostly about removing waiting. Use your own phase data to find the equivalent opportunities.

    Use the journey map to find friction

    Numbers show where time goes. Customers tell you why. Add an onboarding stage to your customer journey map, interview a handful of recent customers about what slowed them down, and compare their answers with your phase data. Common findings include unclear prerequisites, security reviews that start too late, and a champion who’s too busy to coordinate internally.

    Mistakes to avoid

    • Defining success as “kickoff held” or “configured” instead of an outcome
    • Treating every customer the same instead of assigning a track
    • Starting technical prerequisites after the contract is signed
    • Running onboarding in a private internal tool the customer can’t see
    • Letting the handoff depend on someone remembering to send a message
    • Measuring completion of tasks but not time to first value
    • Declaring victory at go-live without confirming value

    Summary

    A customer onboarding workflow takes a customer from closed-won to first value through defined stages, triggers, owners, and exit criteria. Start by defining first value as an outcome, agreed with the customer at kickoff. Then break down where the days actually go, since much of the time is usually handoff lag, scheduling, and customer-side readiness, not hands-on work.

    Segment customers into high-touch, mid-touch, and tech-touch tracks, build a six-stage workflow with automated triggers and a shared success plan, and add alerts for stalled accounts. Measure time to first value, phase cycle times, completion, and activation against your own baseline, feed early signals into your health score, and use the journey map and customer interviews to find the friction behind the numbers.

    FAQ

    What is a customer onboarding workflow?

    It’s the repeatable sequence of steps, owners, triggers, and checkpoints that moves a new customer from signed contract to first value, usually with a mix of automation and human touchpoints.

    What is time to first value?

    It’s the elapsed time from signature or closed-won to the first meaningful outcome a customer cares about, defined for each segment. It measures how quickly customers see a return on their purchase.

    How do you define first value?

    As an outcome, not an action. “Admin logged in” is an action, while “first live workflow running on real data” is an outcome. Agree it with the customer at kickoff and make it measurable.

    What is a mutual success plan?

    A shared document that lists the customer’s goals, milestones, owners, and dates, so onboarding is a jointly owned project with visible commitments on both sides.

    Should every customer get the same onboarding?

    No. Segment by complexity and size into tracks such as high-touch and tech-touch, route each customer automatically from deal data, and adjust the touch model to what each segment needs.

    Which metrics matter most?

    Time to first value, cycle time by phase, completion rate, activation rate, stalled accounts, and early support tickets per account. Baseline them by track before setting targets.

    How can we automate onboarding without losing the human touch?

    Automate the waiting, reminding, and handing off, such as triggers, task assignment, and stall alerts, and keep people for the moments that need judgment, like kickoff, security issues, and confirming value with the sponsor.

    When should onboarding start?

    Before the contract is signed. Capture technical requirements and success criteria in the sales cycle, and start security and integration prework early, so the clock doesn’t begin from zero at closed-won.

  • 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.