Blog

  • CRM modernization: What it is and why it matters

    CRM modernization is the work of updating a CRM’s data model, workflows, integrations, reporting, and adoption so it supports how a revenue team actually operates today, including AI-assisted work. It may involve a new platform, but it often doesn’t. The goal is a system people trust and can change quickly, not a newer logo.

    Most CRMs don’t fail suddenly. They accumulate. Someone adds a field for one campaign and never removes it. A workflow gets built by a contractor who has since left. Two integrations each write to the same property. A few years later, reports disagree, nobody wants to touch the automation, and reps keep a private spreadsheet because they don’t trust the system. Modernization is the process of reversing that drift.

    This guide explains what CRM modernization includes, how to tell whether you need it, the paths you can take, and a phased approach that avoids the most common mistakes.

    What CRM modernization is, and what it isn’t

    Modernization usually includes It does not automatically mean
    Simplifying the data model and retiring unused fields Buying a new CRM
    Fixing workflow friction and documenting automation Turning on every new feature
    Connecting systems so customer data flows reliably Moving data as it is
    Building clean, governed data that AI can use Adding an AI assistant on top of messy data
    Making the CRM useful enough that reps adopt it Training people on the old process

    A simple way to think about it is four layers, each of which can need work:

    Layer What changes Example
    Data Model, quality, and ownership Remove duplicates, standardize values, give each field one writing system
    Process and workflow Stages, routing, handoffs, and automation A written process spec, then a tested rebuild
    Architecture and integration Connections, syncs, and custom code Replace fragile point-to-point syncs
    People and governance Adoption, ownership, and change control A named owner, a data dictionary, and a review cadence

    Signs you need it

    What you see What it usually signals
    Reps keep spreadsheets alongside the CRM The CRM isn’t useful enough, or data isn’t trusted
    Sales, marketing, and finance report different numbers Inconsistent definitions or disconnected data
    Duplicate records and blank key fields everywhere Data quality debt
    Nobody dares touch a workflow Undocumented automation
    Integrations fail quietly Fragile architecture
    Custom fields no one can explain Technical debt in the data model
    New admins take months to get productive Complexity that has outgrown its documentation
    AI features produce weak or confusing output Data that isn’t ready for AI

    Technical debt in a CRM looks like legacy customization, inconsistent object models, fragile integrations, and automation nobody has documented. Each one slows change and raises the cost of every future project.

    Why it matters

    Trust in the numbers. Forecasts, pipeline reports, and renewal views are only as reliable as the data and definitions behind them. When leaders stop trusting reports, they stop using them, and decisions revert to opinion. Fixing the foundations supports everything from closed-loop reporting to forecasting.

    Speed and cost of change. A tangled system makes every request slow. A simple request, like adding a stage or changing routing, turns into a risky project. Modernization cuts the time it takes to ship a change and lowers the cost of maintaining what you have.

    AI readiness. Modernization guidance keeps returning to the same point: AI tools disappoint when the data underneath is inconsistent, duplicated, or locked in separate systems. Most of the work of becoming AI-ready is data work, and it’s better done before you add AI features than after.

    A connected customer view. Revenue teams need marketing, sales, billing, product, and support data on one customer record. If your CRM can’t hold that, workflows like renewal alerts and expansion signals can’t work. Our guide to the best CRM for integrating customer lifecycle data covers what that requires.

    Adoption and productivity. If entering data feels like a tax, reps skip it, and the quality problem gets worse. A modern CRM reduces manual entry and gives users something back, such as clear next steps and useful summaries.

    Governance and risk. Clear ownership, access controls, and documented data flows make privacy compliance, audits, and security reviews easier.

    Four paths, and when each fits

    Path What it means Fits when Main risk
    Optimize in place Clean data, simplify configuration, document and fix automation on your current CRM The platform can do the job but has accumulated debt Treating symptoms if the platform truly can’t support your needs
    Re-architect Redesign the data model, stages, and integrations on the same platform The structure is the problem, not the vendor Rebuilding without a clear process spec
    Re-platform Move to a different CRM A platform limit blocks revenue, or costs no longer scale Carrying old problems into the new system
    Consolidate Merge several CRMs or tools into one Different teams run separate systems with conflicting data Disagreements over definitions and ownership

    Many organizations can improve performance, usability, and scalability by modernizing the CRM environment they already own, so don’t assume modernization means a move. If you do need to change platforms, our Salesforce to HubSpot migration checklist covers the mechanics, and our buyer’s guide to B2B SaaS solutions offers a framework for deciding whether to optimize, extend, replace, or wait.

    A phased approach

    Most risk reduction happens during planning and auditing, not during the migration itself. A phased approach lets you prove value early and catch problems while they’re cheap.

    Phase Key outputs Success check
    1. Goals and baseline Business outcomes, a few baseline metrics, an executive sponsor Everyone can state what “better” means
    2. Audit Data quality findings, inventory of custom fields, workflows, and integrations, list of reports that can’t break, adoption review You know what exists and what depends on what
    3. Design Simplified data model, agreed definitions, stage and routing rules, ownership, governance A written spec that sales, marketing, and finance have signed off
    4. Clean and migrate Deduplicated, standardized data; migration or restructuring in a tested order Counts reconcile and a spot-check passes
    5. Rebuild automation and integrations Workflows and syncs rebuilt from the spec and tested with sample records Critical flows work, and failures raise alerts
    6. Adopt and measure Training tied to real tasks, feedback loops, dashboards Active use and field completeness improve
    7. Add AI where ready Targeted AI use cases on clean data, with human review Each use case has a metric and a stop rule

    Two phases deserve extra attention. Phase 4 begins with data cleanup, because migrating poor-quality data just relocates the mess. Our guide to cleaning up HubSpot data walks through that sequence. Phase 5 depends on a process spec, because recreating weak workflows in a new system keeps weak workflows. For maturity context, our RevOps maturity model can help you judge how much to attempt at once.

    How to measure whether it worked

    Outcome Example measure
    Trust in reporting Gaps between CRM, billing, and board numbers
    Data quality Duplicate rate and completeness of key fields
    Adoption Active users and time spent on data entry
    Speed of change Time to ship a routine change, such as a new stage
    Revenue process Time to first touch, forecast error, handoff quality
    Maintenance load Admin hours per week and number of undocumented automations

    Baseline these in phase one, then recheck at 30, 60, and 90 days after go-live. If the numbers haven’t moved, the project delivered a new system and not a modern one.

    Keep it modern: governance

    Without governance, a freshly cleaned CRM starts accumulating debt again within months. Name one owner for the system, maintain a data dictionary listing each important property’s meaning, owner, and allowed values, and put changes through a simple review. Add a data and automation review to your quarterly RevOps meeting cadence. If you lack the capacity in-house, our comparison of a RevOps consultant vs. an in-house hire can help you decide how to staff it.

    Mistakes to avoid

    • Choosing a platform first and figuring out the problem afterward
    • Migrating poor-quality data and expecting it to improve
    • Recreating weak workflows instead of redesigning them
    • Ignoring reporting continuity, so key reports break at go-live
    • Overlooking integrations, especially billing, product, and marketing syncs
    • Assuming adoption will follow without making the CRM useful to reps
    • Adding AI too early, before data and definitions are ready
    • Going big-bang with no pilot, no rollback plan, and no named owner

    Forecasting, reporting trust, adoption, and integration continuity are the areas that most often break during modernization, so give them explicit tests before go-live.

    Summary

    CRM modernization updates a CRM’s data model, workflows, integrations, reporting, and adoption so it fits how your revenue team works today. It may include a new platform, but often means simplifying and governing the one you have. It matters because it restores trust in reporting, speeds up change, prepares data for AI, connects the customer view across teams, and lifts adoption.

    Choose among four paths: optimize in place, re-architect, re-platform, or consolidate. Work in phases, from goals and baseline through audit, design, cleanup and migration, automation rebuild, adoption, and AI. Spend most of your effort on planning, data, and process, then govern the result with an owner, a data dictionary, and a regular review.

    FAQ

    What is CRM modernization?

    It’s the process of updating a CRM’s data model, workflows, integrations, reporting, and adoption so it supports how your revenue team works now, including AI-assisted work. It may or may not involve changing platforms.

    Is CRM modernization the same as CRM migration?

    No. Migration moves data to a different system. Modernization is broader and can happen on your current platform. A migration is one possible part of modernizing.

    When should we change platforms instead of optimizing?

    When a real platform limit blocks revenue or costs no longer scale, and you’ve confirmed the problem isn’t configuration, data, or process. Otherwise the same problems tend to follow you to the new system.

    How long does CRM modernization take?

    It depends on scope. Targeted optimization can take weeks, a standard migration often takes around six to eight weeks, and projects with custom objects, code, or many integrations take longer. Phasing the work lets you show results earlier.

    How do we prepare our CRM for AI?

    Clean and connect the data, agree on definitions, document workflows, and set governance first. Then add AI to specific use cases with a measurable outcome and human review.

    What breaks most often during modernization?

    Forecasting, trust in reporting, user adoption, and integration continuity. Test each explicitly before go-live and keep a rollback plan.

    Who should lead a CRM modernization project?

    Usually RevOps, with an executive sponsor and input from sales, marketing, customer success, finance, and IT. Whoever leads needs authority over definitions and the time to own the work.

    How do we keep the CRM modern afterward?

    Assign an owner, keep a data dictionary, review changes before they go live, and revisit data quality, automation, and integrations every quarter.

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

  • How to Clean Up HubSpot Data: A Step-by-Step Guide

    HubSpot data cleanup is the process of auditing your CRM, backing it up, fixing properties and formats, merging duplicates, filling gaps, tidying lists and deals, and putting rules in place so bad data stops coming in. Done in that order, it turns a CRM people work around into one they trust.

    You probably know the symptoms. The same company appears three times with different spellings. Half your contacts have no owner or lifecycle stage. Reports disagree with each other, lead scores look random, and reps keep a private spreadsheet because they don’t trust the CRM. Almost every other RevOps project, from forecasting to attribution to automation, depends on getting this right.

    This guide walks through a practical cleanup sequence, with the HubSpot tools that help at each step.

    Before you start: define clean and protect yourself

    “Clean” means different things to different teams, so decide what you’re fixing. Pick the ten or so fields that drive decisions, such as lifecycle stage, owner, lead source, industry, company size, country, email, deal amount, close date, and closed-lost reason. Then name one owner for the project and agree with sales and marketing on a quiet window, so people aren’t editing records while you merge them.

    Also be careful with irreversible actions. In HubSpot, merged records cannot be reverted, so treat every merge as final. You can roll back rejected duplicate pairs for a limited time, but not merges. A backup is your safety net.

    Step 1: Audit what you have

    Start with HubSpot’s data quality tools, found under Data Management, then Data Quality. The overview page summarizes duplicate issues, formatting issues, and enrichment gaps, and the property insights show where properties are unused, empty, or duplicated. Set up the weekly data quality digest while you’re there, so changes show up in your inbox. Then build your own scorecard.

    Check How to find it Why it matters
    Duplicate contacts and companies Manage duplicates tool, plus exports Splits history, inflates counts, breaks reports
    Contacts with no owner or lifecycle stage A saved filter or list Leads go unworked; funnel reports are wrong
    Contacts with no company association A filter on associated company Account-level reporting and scoring fail
    Formatting problems Data quality formatting issues Breaks segmentation and personalization
    Empty key fields Property insights and filtered views Lead scoring and routing lack inputs
    Unused or duplicate properties Property insights Clutter and confusion
    Stale deals Open deals with past close dates Inflates pipeline and distorts the forecast

    Step 2: Back up before you change anything

    Export contacts, companies, deals, and any other objects you plan to touch, including the properties you’ll edit. Record the counts for each object. Export your lists and workflows’ configuration notes too, since you’ll want to know what depends on what. Store the files somewhere the team can find them, and keep them until the cleanup has been validated.

    Step 3: Fix the structure first

    Cleaning records before fixing the properties underneath them means doing the job twice. Review your properties for these issues:

    • Free text where a dropdown belongs. “USA,” “U.S.,” and “United States” are the same value to a human and three values to a report.
    • Duplicate or overlapping properties, such as two fields for lead source.
    • Unused properties with no data and no dependencies.
    • Unclear names and missing descriptions, which lead people to guess.

    Before you delete or merge any property, check where it’s used in workflows, lists, forms, and reports. For guidance on when to create your own, see our explanation of custom vs. default properties.

    Step 4: Standardize formats and values

    The data quality tool flags formatting issues, such as a name stored as “LORELAI GILMORE” that should read “Lorelai Gilmore,” and you can accept or reject its suggestions individually or in bulk on eligible plans. Data Hub Professional and Enterprise also let you set automation so new records with the same issue are fixed automatically. One caveat from HubSpot’s documentation: if a record is later overwritten, for example by an API or integration, with the same bad format, the tool may not flag it again, so fix the source too.

    For values that need consolidating, such as country names, industries, and job titles, use bulk edit or a cleaned import file to map the variants to one standard value. Then change the property to a dropdown so the problem doesn’t return.

    Step 5: Deduplicate carefully

    HubSpot’s duplicates manager compares record properties and surfaces likely pairs, with a daily scan. By default, contacts are compared on properties like name, email, phone, and company name, and companies on domain, name, country, and similar fields. Eligible plans can create custom rules with their own matching criteria. Work in this order:

    1. Companies first. Merging companies consolidates the contacts and deals attached to them, which makes later contact merges cleaner.
    2. Contacts next. Email is the usual unique identifier.
    3. Deals last, reviewing any that look like repeats of the same opportunity.

    Test on a small batch and review associated records before you merge in bulk. Use the similarity score to prioritize, and when you reject a pair, remember that it won’t reappear unless one of the records changes. Decide your merge rule in advance, such as keeping the record with the most recent engagement or the oldest create date, so you keep the best data and the original source.

    Step 6: Fill the gaps

    • Owners: assign owners to unowned records, using routing rules where possible.
    • Lifecycle stage: fix blanks and wrong values, using your agreed definitions. Our guide to HubSpot lifecycle stages explains the rules and the forward-only behavior to plan around.
    • Company associations: associate orphaned contacts with companies, by domain where it’s reliable.
    • Enrichment: the data quality tool shows enrichment coverage by property, which helps you see which fields enrichment can fill.
    • Required fields: make the key fields required on forms and, where your plan supports it, on deals.

    Step 7: Clean your lists, contacts, and deals

    Lists. Audit your lists for stale static lists, duplicates, and unused ones. Consider whether a static list should be an active one that updates itself, and check dependencies before deleting. Our post on active vs. static lists covers when to use each.

    Contacts. Review hard bounces, unsubscribes, and long-unengaged contacts. If you pay by marketing contacts, setting unengaged ones to non-marketing can reduce cost, and archiving or deleting old records should follow your retention and consent policy.

    Deals. Find open deals with past close dates, no amount, or inactive owners, and close, update, or reassign them. Make closed-lost reason a required dropdown. See our guide to HubSpot deal stages for the stage rules that keep pipelines honest, and deal slippage for why stale close dates matter.

    Step 8: Recheck scoring, routing, and reports

    Cleaning changes the inputs to your automation. After the cleanup, review your lead scoring model, since fit scores depend on filled-in fields like industry and company size. Retest routing rules, and spot-check key reports against your pre-cleanup exports. If you’re also planning a platform move, finish the cleanup first, as our Salesforce to HubSpot migration checklist explains.

    A before-and-after snapshot

    Track a handful of measures so you can show the result. These numbers are illustrative.

    Measure Before After 30 days
    Duplicate contact pairs 4,100 150
    Contacts with no owner 9,800 600
    Contacts with no lifecycle stage 12,500 1,200
    Companies missing industry 35% 12%
    Open deals with past close dates 240 20
    Unused properties 112 of 380 20 of 270

    Step 9: Stop the mess from coming back

    • Prevent at the source. Use dropdowns, required form fields, and validation instead of free text.
    • Automate formatting on new records, where your plan allows.
    • Control imports. Use a checklist: clean the file, match on a unique identifier, map fields deliberately, and test a small batch.
    • Review integrations. Check which system writes each field and whether syncs create duplicates.
    • Limit who can create properties and edit key fields.
    • Keep a data dictionary with each property’s meaning, owner, and allowed values.
    • Review quarterly. Use the data quality digest and add the check to your RevOps meeting cadence.

    Mistakes to avoid

    • Merging in bulk with no backup and no test batch
    • Cleaning records before fixing properties and dropdowns
    • Deleting properties or lists that workflows and reports still use
    • Fixing formats in HubSpot while an integration keeps writing bad values
    • Running the cleanup during active campaigns or pipeline reviews
    • Treating it as a one-time project with no owner
    • Deleting contacts without checking consent and retention rules

    Summary

    HubSpot data cleanup works best in a fixed order: define what clean means, audit with the data quality tools, back up, fix properties and dropdowns, standardize formats, deduplicate companies then contacts then deals, fill gaps in owners, lifecycle stages, and associations, clean lists, contacts, and deals, and then recheck scoring, routing, and reports. Because merges can’t be undone, test small batches and keep exports.

    The cleanup only lasts if you prevent the mess at the source with dropdowns, required fields, automated formatting, import controls, integration reviews, and a data dictionary, then review the results every quarter. Track a few before-and-after measures so the effort is visible.

    FAQ

    What is HubSpot data cleanup?

    It’s the process of auditing and fixing your CRM data: merging duplicates, standardizing formats, filling gaps, tidying lists and deals, and adding rules so errors don’t come back.

    Can I undo a merge in HubSpot?

    No. Merged records cannot be reverted. You can undo a rejected duplicate pair for a limited time, so back up and test on a small batch before merging in bulk.

    Where are HubSpot’s data quality tools?

    Under Data Management, then Data Quality. They cover duplicates, formatting issues, enrichment, and property insights. Some capabilities, such as custom duplicate rules and formatting automation, require Data Hub Professional or Enterprise.

    How does HubSpot find duplicates?

    It compares property values on a regular scan, such as email, name, and phone for contacts and domain, name, and country for companies, and assigns similarity scores. Eligible plans can create custom matching rules.

    How often should we clean our HubSpot data?

    Run a full review at least quarterly, and use the weekly data quality digest and automation to catch issues in between. After a migration, a large import, or a new integration, check sooner.

    Should I delete or keep old contacts?

    It depends on your retention and consent policies and applicable privacy rules. Many teams suppress or set unengaged contacts to non-marketing first, then delete according to a documented policy. Check with legal if unsure.

    Do I need to clean data before migrating or adding AI tools?

    Yes. Migrations, scoring, and AI features all inherit the quality of the data underneath them, so cleanup first is cheaper than fixing the same problems in a new system.

    Who should own data quality?

    Usually RevOps owns the standards, tooling, and reviews, while sales, marketing, and customer success own the accuracy of the data they enter. Name one accountable person.

  • How to Set Sales Quotas That Reps Believe

    A sales quota reps believe is one they can trace to a visible method, that reflects their territory and ramp, and that most of the team can reach with good work. The most reliable way to get there is to start with the company target from the top down, then test it against bottom-up capacity and territory potential before anyone sees a number.

    Every January, reps open their quota letters and do their own math. If the number looks like last year’s quota plus 20% because the board wanted 20%, they notice. Some sandbag their forecasts, some quietly start looking for another job, and some disengage by March. A quota is also a message about whether leadership understands the territory. This guide covers how to set quotas people trust.

    What “believable” means

    Test The question Failure sign
    Traceable Can a rep see how the number was built? “Where did this come from?” with no answer
    Fair Does it reflect territory potential, ramp, and seasonality? Flat quotas on very unequal territories
    Reachable Can most reps hit it with good performance? Only a few top reps ever make it
    Aligned to pay Does on-target earnings pay out at 100% of quota? Reps can’t tell what quota is worth
    Matched to the cycle Is the quota period at least as long as your sales cycle? Monthly quotas on a 90-day cycle

    Many sales teams miss on the “reachable” test. In Q2 2025, RepVue’s Cloud Sales Index found that more than half of SaaS reps missed quota, across roughly 246 companies. The Bridge Group’s 2026 AE benchmark put the share hitting quota at 48%, down from 51% in 2024. Benchmarks vary by source and definition, but the message is consistent: many quotas are set higher than the team can deliver.

    Top-down, bottom-up, or both?

    Method How it works Strength Risk
    Top-down Divide the company revenue target across regions, teams, and reps Rolls up to the plan Ignores territory reality; often unreachable
    Bottom-up Aggregate what each rep and territory can realistically produce Credible and grounded Reps may sandbag; total may fall short of the plan
    Hybrid Set the top-down ceiling, validate with bottom-up capacity, and reconcile the gap Ambitious but defensible Takes more time and cross-team work

    Use the hybrid. Top-down sets the ceiling, and bottom-up tests whether it’s reachable. Treat any gap as information, not a negotiation. If bottom-up capacity comes in meaningfully below the top-down target, you have three honest options: add capacity, raise productivity, or adjust the plan. Quietly assigning the full target to the team you have is the fourth option, and it’s the one reps notice. Our guide to sales capacity planning explains how to calculate the bottom-up number.

    How to set quotas step by step

    1. Start with the company target for new and expansion revenue, split by segment if they behave differently.
    2. Calculate capacity. Count ramped reps, ramping reps at partial capacity, expected attrition, and realistic attainment.
    3. Reconcile the gap between target and capacity, and decide how you’ll close it before assigning anything.
    4. Distribute by territory potential, not evenly. Use market size, existing customer base, pipeline, and past performance.
    5. Adjust for ramp and seasonality. A rep who starts mid-year or inherits a thin territory shouldn’t carry a full quota.
    6. Run sanity checks on quota-to-pay ratio, pipeline coverage, and historical attainment.
    7. Validate with frontline managers and a few top reps before locking the numbers.
    8. Communicate the method, not just the number, and deliver it before the period starts.
    9. Set mid-year rules for when quotas will be revisited, such as territory changes, departures, or a delayed product launch.

    A worked example

    Here’s an illustrative five-rep team. The numbers are made up. The company expects $4M in new ARR from this team and expects the team to land around 80% of the quota it assigns, so it sets total quota at $5M ($4M ÷ 0.8).

    Rep Situation Quota Rationale
    1 Mature territory, large customer base $1.3M High potential and strong renewals pipeline
    2 Mature territory $1.2M Consistent history
    3 Average territory $1.0M Close to the team average
    4 New territory, ramped rep $0.9M Lower existing base, fewer warm accounts
    5 Joined at the start of Q2, still ramping $0.6M Nine months, with ramp-adjusted productivity
    Total $5.0M 25% above the $4M target

    Two things to notice. First, quotas differ by territory and by ramp, and each difference has a reason a rep can follow. Second, the total quota exceeds the plan by 25%, because the plan assumes not everyone will hit. I’d recommend explaining that openly, since reps who discover hidden overassignment on their own tend to trust the rest of the process less. If average quota is $1.0M against $200,000 OTE, that’s a 5x quota-to-OTE ratio, inside the range often cited for SaaS account executives.

    Sanity checks before you publish

    Check Common rule of thumb What it tells you
    Quota-to-OTE ratio Often 4x to 6x for SaaS AEs; one dataset reports a median near 4.2x Whether the plan is affordable and pays fairly
    Pipeline coverage Often 3x to 5x of quota Whether enough pipeline exists to support the number
    Attainment spread Designs vary: roughly two-thirds of reps near 80 to 100%, or about 80% hitting quota Whether the quota is calibrated to the team
    Quota period vs. sales cycle The period should be at least as long as the cycle Whether reps can actually close within it
    Historical comparison Compare to the last four to six quarters by segment Whether the jump is realistic

    These rules of thumb come from vendors and consultants and conflict with each other, so use them as prompts, not standards. Decide in advance what attainment pattern you’d consider healthy, and judge the quota against that. Quarterly quotas are the most common across SaaS, with annual quotas more common on long enterprise cycles.

    Communicate, and deliver on time

    How you announce a quota matters almost as much as the number. A few habits help:

    • Deliver quotas before the period begins. One vendor survey found nearly 40% of organizations deliver quotas more than a month late, and reps work blind in the meantime.
    • Share the method. A one-page explanation of how targets were built, including capacity, territory potential, and assumptions, answers most objections before they arise.
    • Offer a structured review window. Let reps flag data errors, such as a missing customer or a wrong territory assignment, with a deadline and a named decider. It’s different from open-ended haggling.
    • Document adjustments. When a quota changes, record why.

    Revisit quotas on a schedule you announced in advance. The quarterly review in a RevOps meeting cadence is a natural home for comparing attainment, ramp, and territory performance against the plan. Pair it with consistent forecast categories so the forecast and the quota tell the same story.

    Watch for gaming and perverse incentives

    Rep input improves credibility, but it invites sandbagging, where reps low-ball estimates to secure easy targets. Reduce it by anchoring on historical data and territory potential, and by having managers validate. Also check what the quota rewards. A rep who hits a revenue number by discounting every deal 30% is technically on quota. Consider discount guardrails or margin-aware measures where discounting is a risk.

    Changes to quotas and commission plans can have legal and contractual implications, especially mid-period, so involve HR and legal and follow local employment rules.

    Mistakes to avoid

    • Setting last year’s quota plus a flat percentage for everyone
    • Assigning the full company target to the team you have, without checking capacity
    • Giving the same quota to unequal territories
    • Ignoring ramp for new hires and mid-year starts
    • Announcing quotas weeks after the period starts
    • Hiding the overassignment math, then letting reps discover it
    • Choosing a quota period shorter than the sales cycle
    • Changing quotas mid-year with no stated rule

    Summary

    A believable quota is traceable, fair, reachable, aligned to pay, and matched to the sales cycle. Build it with a hybrid approach: set the company target top-down, calculate bottom-up capacity, and treat any gap as information to resolve through hiring, productivity, or plan changes. Distribute by territory potential and adjust for ramp and seasonality, instead of spreading the target evenly.

    Sanity-check against quota-to-OTE ratios, pipeline coverage, and historical attainment, while recognizing that published rules of thumb conflict. Validate with managers, share the method, deliver quotas before the period starts, and set mid-year rules in advance. Guard against sandbagging and discount-driven attainment, and involve HR and legal when plans change.

    FAQ

    How do you set a sales quota?

    Start with the company revenue target, calculate realistic team capacity, reconcile the gap, distribute quotas by territory potential and ramp, sanity-check against pay and pipeline, then validate with managers before announcing.

    What is the difference between top-down and bottom-up quota setting?

    Top-down divides the company target among reps. Bottom-up builds from what each rep and territory can realistically produce. The hybrid approach sets the ceiling top-down, then tests it bottom-up.

    What is a good quota-to-OTE ratio?

    A common rule of thumb for SaaS account executives is about 4x to 6x OTE, and one dataset reports a median near 4.2x. Ratios vary with segment, deal size, and margins, so use it as a check, not a target.

    What percentage of reps should hit quota?

    There’s no single answer. Some designs aim for about two-thirds of reps near 80 to 100% attainment, others for roughly 80% of reps hitting quota. Define your target in advance and judge the quota against it. If almost no one hits, or almost everyone does, the quota is miscalibrated.

    Should we assign more total quota than the company target?

    Often, yes, because not every rep will hit. The amount depends on your expected attainment. Explain the logic openly to the team, since hidden overassignment erodes trust.

    How do you handle quotas for new hires?

    Adjust for ramp using your own historical data: a reduced or phased quota for the first months, or a ramped draw. Don’t hand a mid-year hire a full-year quota.

    How long should a quota period be?

    At least as long as your sales cycle. Quarterly is the most common in SaaS, while teams with long enterprise cycles often use annual quotas. Monthly quotas on a 90-day cycle mostly measure luck.

    When should we change a quota mid-year?

    Only under rules announced in advance, such as a major territory change, a rep departure, or a significantly delayed product launch. Document the reason, communicate it, and involve HR and legal.

  • What Is a Sales and Marketing SLA?

    A sales and marketing SLA (service-level agreement) is a written, two-way agreement between marketing and sales that defines what each team commits to at the lead handoff. Marketing commits to delivering leads that meet agreed quality and volume standards, and sales commits to following up within a set time, making a minimum number of attempts, and reporting back on what happened.

    If marketing says the leads are great and sales says nobody is qualified, you probably don’t have a leads problem. You have an agreement problem. Nobody wrote down what “qualified” means, how fast a rep should respond, or what happens to a lead that sales declines. An SLA turns those unspoken assumptions into rules both teams can measure.

    This guide explains what an SLA covers, offers a copyable template, and shows how to enforce it in HubSpot.

    What is a sales and marketing SLA?

    It’s an operating agreement, not a legal contract. The best ones are bidirectional. Marketing commits to quality and quantity, and sales commits to speed, follow-up, and feedback. Each commitment has a number, an owner, and a way to measure it, so a missed commitment shows up in a report instead of a argument.

    It’s also not a one-time document. Definitions and targets change as your product, market, and team change, so the SLA needs a review rhythm of its own.

    Why it matters: the cost of slow follow-up

    Speed is the most widely cited reason. A 2011 Harvard Business Review study of online sales leads, “The Short Life of Online Sales Leads,” found that firms that tried to contact a lead within an hour were nearly seven times as likely to qualify it as firms that waited even an hour longer, and over 60 times as likely as firms that waited a day or more. It also found an average response time of about 42 hours among companies that responded at all. The study is more than a decade old and covers online leads specifically, so don’t treat the multiples as a forecast for your business. The direction, though, matches what most revenue teams see: interest fades quickly.

    An SLA also stops leads from falling into a “black hole,” where marketing hands them over, sales never works or rejects them with no reason, and nobody learns anything. It connects directly to your lifecycle stage definitions, because the handoff happens at a stage change.

    What an SLA should cover

    Component The question it answers Example commitment
    Definitions What counts as an MQL, sales-accepted lead (SAL), and SQL? One written definition each, with required data
    Handoff and routing Who gets the lead, and how? Assigned within five minutes by territory rules
    Response time How fast does sales make first contact? Within one hour for demo requests
    Follow-up attempts How many tries, across which channels? At least three attempts over five business days
    Disposition and feedback What happens to every lead? Accepted, rejected, or recycled with a reason within ten business days
    Volume and quality What does marketing deliver? A target number of MQLs that meet the definition
    Reporting and governance How do we know, and who reviews it? A weekly compliance report and a monthly review

    Start with definitions, response time, follow-up attempts, and standard disposition reasons. You can add volume targets and finer detail once those are working.

    Tier response times by lead type

    A single response time for every lead is too blunt. A demo request signals far more intent than an ebook download. Here’s an illustrative tiering. The times are examples to adapt, not benchmarks.

    Lead type First touch Follow-up attempts Disposition due Escalation if missed
    Demo or pricing request Within 1 hour 4 over 5 business days 5 business days Notify the manager after 2 hours
    High-intent inquiry or trial signup Within 4 hours 3 over 5 business days 7 business days Notify the manager after 8 hours
    Content download or webinar attendee (MQL) Within 1 business day 3 over 10 business days 10 business days Reassign after 2 business days

    Define when the clock starts. It should start when the lead is created or reaches the MQL stage, not when a rep first looks at it. And decide how after-hours and holidays work, since a one-hour SLA means little at 2 a.m.

    A sales and marketing SLA template

    Copy this into a shared document and replace the bracketed values with your own.

    Section Template language
    1. Purpose This agreement defines how marketing and sales work together to turn leads into pipeline and revenue, and how we hold each other accountable.
    2. Definitions MQL: a contact who meets [fit criteria] and [engagement score or behavior]. SAL: an MQL that sales has reviewed and agreed to work. SQL: a SAL where [qualification criteria, such as budget, need, and timeline] are confirmed. Required data on every MQL: [company, title, email, source, lead score].
    3. Marketing commits to Delivering [X] MQLs per [month or quarter] that meet the definitions above. Passing complete data and a short context note (source, last action, interest). Reviewing rejected-lead feedback monthly and adjusting targeting.
    4. Sales commits to First contact within [time] for [lead type]. At least [number] attempts across [channels] over [days]. Updating the lead status after every attempt. Marking each lead accepted, rejected, or recycled, with a reason code, within [days].
    5. Routing Leads are assigned by [territory, round robin, or account owner]. Unassigned leads are reassigned after [time] to [fallback owner].
    6. Disposition codes Accepted. Rejected: [wrong fit, wrong contact, no budget, duplicate, other]. Recycled: [not ready, no response, future timing]. A reason is required for every rejection and recycle.
    7. Recycle rules Recycled leads return to marketing nurture and may re-enter as MQLs after [days or new activity].
    8. Escalation If a response or disposition deadline is missed, the lead owner’s manager is notified at [time]. Repeated misses are reviewed in the monthly meeting.
    9. Reporting RevOps publishes weekly: median time to first touch, SLA compliance rate, attempts per lead, acceptance rate, and rejection reasons.
    10. Review Sales, marketing, and RevOps leaders review monthly. Definitions and targets are revisited each quarter or when the ideal customer profile changes.
    11. Sign-off [Head of Sales], [Head of Marketing], [RevOps lead], dated and versioned.

    The definitions section depends on how your team scores and qualifies. See our guides to building a lead scoring model sales trusts and to BANT and MEDDIC for the criteria behind MQL and SQL.

    Enforcing the SLA in HubSpot

    An SLA that lives only in a document gets ignored. Build the commitments into the system:

    • Lifecycle stages and timestamps. HubSpot records the date a contact enters each lifecycle stage, so “time from MQL to first touch” is measurable.
    • Lead routing. Use workflows to assign an owner when a contact becomes an MQL, and create a task with a due date that matches the SLA. For tool options, see our guide to AI tools for routing, handoffs, and pipeline hygiene.
    • Lead status as disposition. Use lead status values, such as attempted to contact, connected, and unqualified, with a required reason for rejections.
    • Breach alerts. Build a workflow that notifies the owner’s manager when a lead sits with no logged activity past the deadline.
    • Reports. Create views for time to first touch, SLA compliance by rep and by lead type, acceptance rate, and rejection reasons.

    Some of these features, such as workflow actions that set properties, depend on your HubSpot plan, so check what yours includes. See also What Is a HubSpot Workflow?

    Metrics to track

    Metric What it shows Owner
    Median time to first touch Whether sales is meeting the speed commitment Sales
    SLA compliance rate The share of leads handled within the deadlines Sales and RevOps
    Attempts per lead Whether follow-up is real or a single call Sales
    Acceptance and rejection rates Whether the MQL definition matches what sales wants Marketing and sales
    Rejection reasons Where targeting or data is going wrong Marketing
    MQL-to-SQL conversion The end-to-end quality of the handoff Both

    Baseline these for a month before you set targets. If median first touch is 19 hours today, a one-hour target for every lead is a fantasy. A staged target, such as one hour for demo requests first, is more realistic. Outcomes feed back to marketing through closed-loop reporting.

    Extend the SLA past the handoff

    Many teams stop at the lead handoff, but the same logic helps later. Sales can commit to pipeline hygiene standards: a next step and close date on every open deal, stage updates within a set time, and a closed-lost reason on every loss. That keeps the forecast and marketing’s attribution reliable. Our guide to deal slippage shows what happens when those fields go stale.

    Mistakes to avoid

    • Writing an SLA that only binds sales, so marketing has no accountability for quality
    • Setting one response time for every lead type
    • Not defining when the clock starts, or what happens after hours
    • Letting reps reject leads without a reason code
    • Using the SLA to assign blame instead of to find and fix gaps
    • Skipping enforcement in the CRM, so the agreement lives in a document
    • Never reviewing the SLA after it’s signed

    Summary

    A sales and marketing SLA is a two-way agreement defining what marketing delivers, such as leads that meet agreed quality and volume standards, and what sales commits to, such as response times, follow-up attempts, and reasons for every rejection. It matters because slow follow-up costs conversions, and because shared definitions end the argument over lead quality. A well-known HBR study of online leads found that responding within an hour made firms nearly seven times as likely to qualify a lead as waiting one more hour, though the study is old and specific to online leads.

    Cover definitions, routing, response time, follow-up attempts, disposition and feedback, volume and quality, and reporting. Tier response times by lead type, define when the clock starts, and baseline before setting targets. Enforce the SLA with lifecycle stage timestamps, routing workflows, required reason codes, breach alerts, and compliance reports, and review it monthly.

    FAQ

    What is a sales and marketing SLA?

    It’s a written agreement between the two teams setting out what marketing commits to deliver and what sales commits to do with each lead, including response times, follow-up attempts, and feedback, with metrics for both.

    What should sales commit to in an SLA?

    A maximum time to first contact, a minimum number of follow-up attempts across channels, and a deadline to accept, reject, or recycle each lead with a standard reason code.

    What should marketing commit to?

    A volume of MQLs that meet the written definition, complete data and context on each lead, and a monthly review of rejected-lead feedback to improve targeting.

    How fast should sales respond to a lead?

    It depends on lead type and your baseline. High-intent requests such as demos often warrant minutes to an hour, while content downloads can allow a business day. Set tiers from your own data and tighten them over time.

    What’s the difference between an MQL, SAL, and SQL?

    An MQL meets marketing’s fit and engagement criteria. A SAL is an MQL that sales has reviewed and agreed to work. An SQL is a lead where sales has confirmed qualification criteria such as need, budget, and timing.

    Who owns the SLA?

    Sales and marketing leaders own the commitments, and RevOps typically owns the measurement, workflows, and reporting that make them enforceable.

    What happens if the SLA is missed?

    Define it upfront: automatic alerts to the manager, reassignment after a set time, and a standing agenda item in the monthly review. The goal is to find the cause, such as capacity, routing, or lead quality, not to assign blame.

    How often should we update the SLA?

    Review performance monthly and revisit definitions and targets quarterly, or whenever your ideal customer profile, product, or team structure changes.

  • RevOps Consultant vs In-House Hire: Costs and When to Choose Each

    A RevOps consultant is usually the better choice when you have a defined project, a cleanup, or uncertain scope, and an in-house hire is usually better when the work is continuous and needs deep company context. In the US, a RevOps manager typically has a base salary of roughly $100,000 to $140,000, while consultant retainers commonly run from the low thousands to about $15,000 a month. Many companies end up with a hybrid.

    Full disclosure: Revlyn is a RevOps consultancy, so weigh our view accordingly. The break-even math below doesn’t depend on who you hire, and some of the situations that follow point away from consultants.

    This guide compares the two options on cost, speed, risk, and fit, with a decision table and a transition plan for companies that start with one and move to the other.

    The options at a glance

    Option Typical scope Indicative cost (USD) Best for
    Project-based consultant or agency A defined build: CRM setup, migration, cleanup, reporting Often $12,000 to $60,000 per project One-off work with a clear end
    Retainer consultant Ongoing advice and a set number of hours Roughly $3,500 to $15,000+ per month Steady but modest needs
    Fractional RevOps leader Strategy plus hands-on work, around 10 to 20 hours a week Roughly $5,000 to $15,000 per month Growth-stage teams without a leader
    In-house RevOps manager Full-time ownership of systems, process, and reporting Base around $100,000 to $140,000, plus overhead Continuous work and deep context
    Hybrid An in-house operator plus a specialist for projects Salary plus occasional project fees Most scaling companies

    These ranges come from vendor and agency sources and vary widely, so treat them as indicative. One cost guide notes that no published study prices RevOps consulting as a product, which is a polite way of saying you should collect real quotes.

    The real cost of an in-house hire

    Most founders compare a base salary to a monthly retainer and stop. The full cost is larger:

    Cost component What to include
    Base salary US RevOps manager figures commonly sit between about $100,000 and $140,000, with salary averages from different datasets ranging from the high $90,000s to the high $100,000s
    Benefits and overhead Often estimated at 20 to 30% on top of salary
    Bonus and equity Variable pay, and equity at funded startups
    Recruiting and time to fill Agency fees or recruiter time, plus weeks or months of an empty seat
    Ramp time Roughly three to six months before full effectiveness is a common estimate
    Tools and training Licenses, certifications, and conferences
    Management time Someone senior has to direct the work

    An illustrative total: a $120,000 base plus 25% overhead is about $150,000 a year, before recruiting, bonus, tools, and ramp. Geography changes the picture considerably. One salary report puts North American RevOps manager base pay near $118,000 and European near $71,000, and published averages for India are lower still. Use local salary data for your market.

    The real cost of a consultant

    Consultants look cheaper per month but carry their own costs:

    • Pricing model matters. Hourly, project, and retainer pricing behave differently. Hourly rates can range from under $100 to $300 or more, and buying a project on a retainer can cost several times what the same project costs on a fixed fee.
    • Onboarding. A new consultant must learn your business, data, and politics, usually on your time.
    • Scope drift. Open-ended retainers tend to expand without a clear list of outcomes.
    • Knowledge walking out. If a consultant leaves or rotates, context goes with them unless it’s documented.
    • Dependency. You can end up unable to change your own system without paying someone.

    On the plus side, consultants typically start in days, bring patterns from many companies, and are easier to scale down if the work ends.

    The break-even question: how many hours do you need?

    The cleanest way to decide is by hours of steady work per week. Here’s an illustration with assumed numbers.

    • Fully loaded in-house cost: $150,000 a year
    • Consultant effective rate: $180 an hour (an assumption)
    • Break-even: $150,000 ÷ $180 is about 833 hours a year, or roughly 16 hours a week

    Below about 16 hours a week of steady work, the consultant is cheaper. Above it, the hire starts to win on cost per hour, as long as you can keep them busy with valuable work. A full-time employee also isn’t productive all 2,080 hours, since meetings and time off reduce it, which pushes the break-even a bit lower. Treat the result as a rough guide, then test it with real quotes.

    Cost isn’t the only variable. An employee builds context, owns outcomes, and is there for the unplanned requests that fill a typical week. A consultant offers breadth and speed on defined problems. That’s why the next table uses situations, not just dollars.

    Which to choose, by situation

    Situation Lean toward Why
    CRM migration or major re-implementation Consultant A bounded project that needs experience and speed
    Messy CRM and no agreed definitions Consultant, then hire Diagnose and design first; run it afterward
    Steady stream of daily requests, 20+ hours a week In-house Continuous work and context beat per-hour pricing
    No RevOps leader, unclear strategy Fractional leader Strategy without a full-time salary
    Need a specialist skill occasionally, such as attribution modeling Consultant Rare skills don’t justify a full-time role
    Several stakeholders needing a trusted internal owner In-house Relationships and accountability matter
    Uncertain scope or funding Consultant Easier to scale up or down
    Regulated or sensitive data and tight access control In-house, or a vetted partner Fewer outside hands on sensitive systems

    Use maturity to guide the choice

    Where your RevOps function stands matters as much as company size. Our RevOps maturity model describes the stages. A rough mapping:

    Stage What it looks like Common approach
    Early or reactive Spreadsheets, inconsistent definitions, firefighting Consultant or fractional leader to diagnose and build foundations
    Defined Systems and processes exist, but ownership is thin First in-house hire, with a consultant for projects
    Scaling Multiple teams, a growing tech stack, regular reporting In-house team plus specialists for spikes
    Advanced Forecasting, attribution, and planning are routine In-house team with targeted outside expertise

    If you’re unsure whether you’re ready for a dedicated hire at all, our post on the signs your company needs a dedicated RevOps hire is a good companion read, and a refresher on what RevOps is helps when writing the role description.

    Making a hybrid work

    A common pattern is a consultant or fractional leader who designs and builds, followed by an in-house operator who runs it. It works when the handoff is deliberate:

    1. Define outcomes, not hours, in the first engagement, such as “one agreed lifecycle model and a forecast report the board accepts.”
    2. Own the keys. Admin credentials, vendor accounts, and documentation belong to you, not the consultant.
    3. Require documentation. Data dictionary, workflow inventory, and process maps as deliverables.
    4. Overlap the handoff. If you hire in-house, have the consultant train them for a few weeks.
    5. Move the consultant to a narrower role. After the hire, use them for specialist projects or a periodic review.

    How to evaluate a consultant

    • Can they show recent work for companies at your stage and on your CRM?
    • Do they say what you shouldn’t do right now, or only what they’d sell you?
    • Who actually does the work, and how much seniority is involved?
    • What are the deliverables, and what’s the exit plan?
    • Will they hand over documentation and access without friction?

    For how different provider types compare, including certified platform partners, independent consultants, and fractional leaders, see our guide to CRM and RevOps providers. It’s written for Australian SaaS teams, but the provider-type comparison applies elsewhere.

    Mistakes to avoid

    • Comparing a salary with a retainer and ignoring overhead, recruiting, and ramp
    • Hiring full-time for work that is really a six-month project
    • Signing an open-ended retainer with no outcomes
    • Letting a consultant hold the only copy of the documentation
    • Hiring a junior admin and expecting strategy
    • Skipping the diagnosis, then solving the wrong problem

    Summary

    Choose a RevOps consultant for defined projects, cleanups, specialist skills, or uncertain scope, and an in-house hire for continuous work that needs company context. In the US, an in-house RevOps manager typically has a base of about $100,000 to $140,000, plus 20 to 30% in overhead and several months of ramp, while consultant retainers commonly run from about $3,500 to $15,000+ a month and projects from about $12,000 to $60,000. Treat all ranges as indicative and collect real quotes.

    A simple break-even check compares fully loaded hire cost with a consultant’s effective hourly rate. In the example, the two cost the same at about 16 hours a week. Use maturity stage and situation to decide, plan a deliberate handoff if you go hybrid, own your credentials and documentation, and define outcomes in any engagement.

    FAQ

    Is a RevOps consultant cheaper than hiring?

    For defined projects or modest ongoing needs, usually yes. For steady, full-time-sized workloads, an employee often costs less per hour, so compare against the hours of work you actually have.

    How much does a RevOps manager cost in the US?

    Base salaries are commonly cited between about $100,000 and $140,000, with different datasets giving averages from the high $90,000s to the high $100,000s. Add roughly 20 to 30% for benefits and overhead, plus bonus, equity, and recruiting costs.

    What is fractional RevOps?

    A part-time RevOps leader, often around 10 to 20 hours a week, who provides strategy and hands-on work without a full-time salary. It suits growth-stage teams that need senior guidance but not a full-time role.

    When should a company make its first RevOps hire?

    When steady RevOps work exceeds what a consultant efficiently handles, roughly 15 to 20 hours a week in the break-even example, and when ownership, context, and continuity matter more than breadth.

    Can I start with a consultant and hire later?

    Yes, and it’s a common path. Have the consultant document everything, keep your own admin access, and train the new hire during an overlap period.

    What are the risks of relying on a consultant?

    Scope drift, dependency, and lost knowledge if documentation is thin or people rotate. Reduce them with outcome-based scopes, owned credentials, and required documentation.

    Does location change the math?

    Yes. Salaries differ a great deal between the US, Europe, India, and elsewhere, while some consultants price globally in USD. Use local salary data and local quotes for your decision.

    What should a RevOps hire do in the first 90 days?

    Audit systems and data, agree on definitions with sales, marketing, and customer success, fix the highest-cost handoff, and set up a simple reporting cadence. Avoid starting with tool purchases before the process is clear.

  • HubSpot Deal Stages: How to Set Up Your Sales Pipeline.

    HubSpot deal stages are the ordered steps a deal moves through inside a sales pipeline, from first conversation to closed won or closed lost. Each stage carries a win probability, which HubSpot uses to weight your pipeline and forecast, and each can require specific properties before a deal moves forward.

    Most teams inherit the default pipeline, rename a stage or two, and never look at it again. Then the forecast misses, reps argue about what “Qualified” means, and the pipeline fills with deals that haven’t moved in months. The fix usually isn’t a new tool. It’s a pipeline designed around evidence.

    This guide covers how deal stages work, how to design them, how to set probabilities from your own data, how they connect to lifecycle stages and forecast categories, and how to set it all up.

    Deal stage vs. lifecycle stage vs. forecast category

    These four fields get mixed up constantly, so it’s worth separating them before you build anything.

    Field Lives on Question it answers
    Deal stage Deals How far along is this specific deal?
    Lifecycle stage Contacts and companies What is our overall relationship with this person or company?
    Lead status Contacts and companies What is a rep doing with this lead right now?
    Forecast category Deals How confident are we that this will close this period?

    HubSpot’s default deal stages

    HubSpot’s default sales pipeline ships with seven stages and a default probability for each. The sales pipeline is available in every Sales Hub tier.

    Default stage Default probability
    Appointment Scheduled 20%
    Qualified to Buy 40%
    Presentation Scheduled 60%
    Decision Maker Bought-In 80%
    Contract Sent 90%
    Closed Won 100%
    Closed Lost 0%

    They’re a reasonable starting point, but they mostly describe what the rep has done: scheduled, presented, sent. They don’t say what the buyer has done, which is what actually predicts a close. And the percentages are generic, not yours.

    Design principles for deal stages

    • Use buyer milestones, not rep activities. “Buyer confirmed budget range” is more reliable than “demo given.”
    • Keep it to roughly five to eight stages. Too few and you lose visibility. Too many and reps skip stages.
    • Write entry and exit criteria for every stage, in one sentence each.
    • One pipeline per genuinely different motion, such as new business versus renewals. Avoid creating pipelines for every segment.
    • No graveyard stage. A “follow-up” stage where stalled deals sit forever hides risk. Close them or define a rule for moving them out.

    An example B2B SaaS pipeline

    Here’s one illustrative design. Yours should reflect your own sales process.

    Stage Entry criteria (buyer evidence) Required properties
    Discovery The buyer agreed to a first conversation about a specific problem Deal source, use case
    Qualified The buyer confirmed the problem, a rough budget, and a decision process Budget range, decision maker, timeline
    Evaluation The buyer is testing or reviewing the product with named stakeholders Champion, competitors considered
    Proposal The buyer has a written proposal and agreed to review it Amount, close date, next step date
    Negotiation Terms are being discussed, and legal or procurement is involved Procurement path, signer
    Closed Won Contract signed Contract start date, billing contact
    Closed Lost The buyer chose another option or no decision Closed-lost reason (dropdown), competitor

    For help defining the qualification evidence behind these gates, see our comparison of BANT and MEDDIC.

    Set probabilities from your own data

    HubSpot multiplies each deal’s amount by its stage probability to produce weighted pipeline. If the probabilities are guesses, so is the forecast. Replace the defaults with your actual history. Pull the closed deals from the last 12 months and, for each stage, calculate the share of deals that reached it and eventually closed won. Here’s an illustrative example in which 60 deals were won:

    Stage Deals that reached it Eventually won Win rate (use as probability)
    Discovery 400 60 15%
    Qualified 250 60 24%
    Evaluation 150 60 40%
    Proposal 100 60 60%
    Negotiation 75 60 80%

    Every won deal passed through every stage here, which is why the “won” column is constant. In real data, some deals skip stages, so adjust for that. Recalculate each quarter, and consider separate pipelines or probabilities where deal size or segment changes the odds. For more on how weighting works, see our guide to weighted pipeline.

    How deal stages connect to lifecycle stages

    Deals drive part of the lifecycle stage on the associated contact and company. In HubSpot, a record becomes an Opportunity when it’s associated with a deal, and a Customer when it has at least one closed deal, provided you’ve turned on the settings that update lifecycle stage from associations. Lifecycle stages only move forward by default, so a customer isn’t pushed back to Opportunity when a new deal is created. Decide up front which of these updates you want, and review them in your settings. Our explanation of HubSpot lifecycle stages covers the details.

    How deal stages connect to forecast categories

    Stage probability is a statistical estimate based on history. A forecast category is a person’s judgment about this deal this period. They’re different, and many teams use both. HubSpot’s forecast can use a forecast category property on deals, and some teams add their own custom category property as a confidence overlay. Check how your forecast is configured before you rely on either.

    One way to keep them consistent is to map each stage to a default category and let reps adjust only with a stated reason. Here’s an illustrative mapping:

    Stage Default category
    Discovery, Qualified Pipeline
    Evaluation, Proposal Best Case
    Negotiation Commit, if the evidence criteria are met
    Closed Won Closed
    Closed Lost Not forecasted

    Our guide to forecast categories explains how to define each label by evidence, so Commit means the same thing for every rep.

    Enforce and automate

    A pipeline is only as good as the rules behind it. HubSpot lets you require properties when a deal enters or leaves a stage, which on Professional and Enterprise plans is one of the most useful and most overlooked settings. Pair it with automation:

    • Required properties at the stages shown above, including close date and amount before Proposal, and a closed-lost reason before a deal can be marked lost.
    • Workflows on stage change: create a task for the next step, notify the account team, or alert finance when a deal reaches Closed Won.
    • Stale-deal alerts: notify the owner when a deal has sat in a stage longer than your typical time.
    • Close-date checks: flag deals whose close date has been pushed more than once. Our explanation of deal slippage covers why this matters.

    Make the closed-lost reason a dropdown, not free text, so you can report on it. It’s also the raw material for win-loss analysis.

    Reports worth building

    • Weighted pipeline by stage and by owner
    • Stage-to-stage conversion rates
    • Average days in each stage, with a list of deals beyond your normal range
    • New pipeline created against target
    • Closed lost by reason, with deal count and value

    How to set it up in HubSpot

    1. Write your stages first. Draft names, entry and exit criteria, and required properties in a document, with sales leadership signing off.
    2. Open the pipeline settings. Go to Settings, then Objects, then Deals, then Pipelines. Deal stages are managed there, not through the general Properties menu.
    3. Create or edit the pipeline. Rename stages, add new ones, and drag to reorder.
    4. Set a probability for each stage from your historical data.
    5. Set required properties for the stages that need them, if your plan supports it.
    6. Move existing deals before deleting a stage. A stage that still holds deals can’t simply be removed, so map old stages to new ones first.
    7. Brief the team, then review conversion and days-in-stage after a month and adjust.

    Mistakes to avoid

    • Keeping HubSpot’s default probabilities without checking them against your data
    • Naming stages after rep activities instead of buyer milestones
    • Creating a stage for every possible situation, so reps skip around
    • Making a closed-lost reason optional or free text
    • Letting deals sit in stages with no close date or next step
    • Building several pipelines when properties or segments would do
    • Changing stage definitions mid-quarter without telling the team

    Summary

    HubSpot deal stages track how far along each deal is, and each carries a win probability that feeds weighted pipeline. The defaults, from Appointment Scheduled at 20% to Contract Sent at 90%, describe rep activity and use generic percentages. Better pipelines use five to eight stages tied to buyer milestones, with written entry and exit criteria, required properties, and probabilities calculated from your own closed deals.

    Deal stage differs from lifecycle stage, which describes the overall relationship, and from forecast category, which captures confidence this period. Deals move contacts and companies forward through lifecycle stages when associations settings are on. Enforce the design with required properties, workflows, stale-deal alerts, and a required closed-lost reason, then review the pipeline monthly.

    FAQ

    What are the default HubSpot deal stages?

    Appointment Scheduled (20%), Qualified to Buy (40%), Presentation Scheduled (60%), Decision Maker Bought-In (80%), Contract Sent (90%), Closed Won (100%), and Closed Lost (0%). They’re editable starting points.

    How many deal stages should a pipeline have?

    Most B2B teams do well with roughly five to eight. Fewer than that limits visibility, and more than that encourages reps to skip stages or guess.

    How do I change deal stage probability in HubSpot?

    Open Settings, then Objects, then Deals, then Pipelines, edit the pipeline, and set the probability for each stage. Base the numbers on how often deals at each stage actually closed in your last 12 months.

    Is deal stage the same as lifecycle stage?

    No. Deal stage tracks one deal’s progress. Lifecycle stage describes a contact or company’s overall relationship with you. A deal being created or closed can update lifecycle stage if the related settings are on.

    Can I require fields before a deal moves to the next stage?

    Yes. HubSpot lets you set required properties at the point a deal enters a stage, available on Professional and Enterprise plans. Use it for close date, amount, next step, and closed-lost reason.

    Should I use more than one pipeline?

    Only for genuinely different sales motions, such as new business and renewals. For differences like segment or region, use deal properties and filters instead, because more pipelines make reporting harder.

    How do deal stages relate to forecast categories?

    Stage probability is a historical estimate, while a forecast category is a judgment about confidence this period. Many teams map each stage to a default category and let reps adjust with a reason. Check how your HubSpot forecast is configured.

    What should I do with deals stuck in a stage?

    Set a normal time per stage, alert the owner when a deal exceeds it, and require a next step and close date. If nothing is happening, move the deal back to an earlier stage or close it with a reason.

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

  • What Is Win-Loss Analysis? How to Run One

    Win-loss analysis is the practice of systematically interviewing buyers after a deal closes, whether you won, lost, or ended in no decision, to understand the real reasons behind the outcome. It compares what buyers say with what your CRM and sales team say, and turns the gaps into changes in positioning, product, pricing, and process.

    Ask a sales leader why the team lost last quarter and you’ll often hear “price” or “timing.” Ask the buyers and you’ll hear something different: a business case nobody believed, a missing integration, a champion who left, a security review that stalled. The gap between those two stories is where win-loss analysis earns its keep.

    This guide explains what win-loss analysis is, why CRM data alone isn’t enough, and how to run a simple program, with a question guide, a coding frame, and a worked example.

    What is win-loss analysis?

    Win-loss analysis means picking a set of closed deals, interviewing the people who made the decision, labeling each conversation with the same reason categories, and comparing wins with losses inside a segment. It covers three outcomes: won deals, lost deals, and no-decisions, where the buyer chose to do nothing.

    It’s not the same as a deal review, where the team talks about its own deal, or a post-mortem driven by the rep’s memory. The defining feature is the buyer’s voice, collected by someone who didn’t sell to them.

    Why CRM loss reasons aren’t enough

    Almost every CRM has a “closed lost reason” field, and most of them are unreliable in the same ways. The rep fills in the dropdown minutes after a disappointing call, often choosing the option that feels least like a mistake, and price becomes the default explanation. Independent interviews regularly find that the recorded reason and the buyer’s actual reason differ. A fair summary: reps remember losses as price, while buyers remember them as risk, timing, or a business case nobody believed.

    What the CRM says What a buyer interview might reveal
    Price The ROI wasn’t clear, so any price felt too high
    Timing The champion couldn’t get an executive sponsor
    Went with a competitor The competitor had an integration we didn’t mention
    No response Security review stalled and nobody helped them through it

    That doesn’t make CRM fields useless. They’re good for volume and rough trends, and they help you choose which deals to interview. Treat them as labels that tell you where to look, not as findings.

    What you can learn

    Finding type Example Likely owner
    Positioning and messaging Buyers don’t understand how we differ from the alternative Product marketing
    Product gaps A missing integration appears in many losses Product
    Pricing and packaging The entry plan lacks one feature buyers expect Product and finance
    Sales process We rarely reach the economic buyer Sales leadership
    Competitive One competitor wins on onboarding speed Competitive intelligence

    How to run a win-loss analysis

    1. Define the question and scope. A vague goal produces vague findings. Try something specific: “Why are we losing mid-market deals to Competitor X?” or “What makes wins in our new segment different?”
    2. Select deals deliberately. Include wins, losses, and no-decisions, across deal size, industry, and rep. Interviewing only losses teaches you what went wrong but not what’s working.
    3. Interview soon after the decision. Sources range from two to six weeks, and recall fades quickly after that. Aim for within a month.
    4. Use a neutral interviewer. The account executive who owned the deal shouldn’t run it, and neither should their manager. Buyers soften criticism when they know who they’re talking to. A product marketer, researcher, or outside firm works better. Keep the rep debrief separate, and hold it after you have the buyer data.
    5. Recruit with a clear, low-effort ask. Offer a 20 to 30 minute call, explain the feedback is confidential and used to improve, and don’t use it to win them back. Try more than one person on the buying committee.
    6. Code every interview the same way. Use a fixed set of labels so you can compare across deals.
    7. Triangulate with your data. Compare interviews with CRM stage history, cycle length, and competitors, and note where they agree and contradict.
    8. Report with sample size and confidence, then act. Run a workshop where each priority finding gets an owner and a change to a specific asset: a deck, a pricing page, a playbook, a roadmap item.

    Questions to ask buyers

    Topic Sample question
    Trigger What was going on that made you start looking?
    Alternatives What options did you consider, including doing nothing?
    Criteria What mattered most in your decision, and how did that change along the way?
    Committee Who was involved, and who had the final say?
    Experience What was it like working with our team compared with the others?
    Turning point Was there a moment when you knew where this was heading?
    Concerns What worried you most about choosing us?
    Advice If you could change one thing about how we sold to you, what would it be?

    Ask about behavior and specific moments, not opinions in the abstract. “Walk me through what happened after the demo” gets better answers than “Did you like our product?” And listen more than you talk.

    A simple coding frame

    Pick one primary reason per interview, plus an optional secondary one, from labels like these. Adapt them to your business, and keep them fixed from quarter to quarter.

    Category Meaning
    Competitive loss The buyer chose a named competitor
    No decision The buyer kept the status quo
    Product gap A needed capability or integration was missing
    Value and price Cost was hard to justify against the expected return
    Evaluation and process We didn’t reach decision-makers or support the evaluation well
    Champion and sponsor The internal advocate left or lacked influence
    Timing and priority The project was deprioritized or delayed
    Trust and risk Security, vendor stability, or implementation risk worried the buyer

    Track timing and no-decision outcomes separately from true competitive losses. A deal pushed to next quarter isn’t the same as a deal lost to a rival, and mixing them hides what’s really going on.

    A worked example

    Imagine a team interviews 24 buyers from lost and no-decision deals. In the CRM, 14 of the 24 were logged as “price.” The numbers below are illustrative.

    Primary reason from interviews Deals Action
    Value and price 4 Review packaging at the entry tier
    Business case unclear 6 Create an ROI template and train reps to use it
    Product gap (integration) 5 Publish an integrations guide; raise on the roadmap
    Champion or sponsor lost 5 Multithread earlier; require a named executive sponsor by a set stage
    Security review stalled 3 Build a security answer pack
    Other 1 None

    The CRM said price in 14 of 24 deals. Buyers named it as the main reason in four. The biggest actionable themes were an unclear business case and a missing integration, and none of them would have shown up in the dropdown. With 24 interviews, treat the percentages as directional, not precise. Say so in the report.

    Connect it to deal slippage and pipeline hygiene

    Win-loss findings are most useful when they feed your day-to-day data. Three links are worth making:

    • Standardize the closed-lost field. Replace free-form or generic reasons with the categories from your coding frame, and make the field required. Add a competitor field. Our guide to closed-loop reporting covers how those outcomes flow back to marketing.
    • Watch for slippage. Deals that keep moving to the next quarter often end as no-decisions. Interviews can reveal why, and our explanation of deal slippage shows how to catch the signs earlier.
    • Tighten pipeline hygiene. If interviews show you rarely reach the economic buyer, require that field before a deal enters Commit. Qualification frameworks like BANT and MEDDIC turn findings into required evidence.

    Each quarter, compare your CRM loss reasons with the interview findings. If they diverge, recalibrate the dropdown. Over time the CRM field gets closer to reality, and you can use it for ongoing trend tracking between interview rounds. The customer journey map is also a useful companion, since interview answers often point to specific stages where buyers got stuck.

    In-house, third-party, or AI-assisted?

    Option Advantages Watch for
    In-house (product marketing or research) Low cost, deep product knowledge Buyers may be less candid; programs fade when people get busy
    Third-party firm Neutrality and reach to lost buyers Cost, and a smaller sample of deals
    AI-moderated interviews or surveys Scale and speed Depth and nuance vary; review transcripts yourself
    Hybrid Interviews for depth, surveys for breadth More to coordinate

    Whichever you choose, the same rules apply: someone neutral asks the questions, the labels stay consistent, and each finding has an owner.

    How many interviews are enough?

    Guidance varies. Some sources suggest 15 to 20 interviews per quarter to see clear patterns, and others suggest at least 10 to 15 deals before drawing conclusions about any single pattern. A thinner round is still useful if you label it directional. Fewer than about eight interviews per cycle starts to look more like anecdotes than patterns. Start small, keep the process steady, and let the sample grow.

    Mistakes to avoid

    • Letting the account executive or their manager run the interview
    • Interviewing only losses, so you never learn what’s working
    • Waiting months, so memories fade and buyers stop responding
    • Trusting the CRM dropdown without checking it against buyers
    • Reporting percentages from a tiny sample as if they were precise
    • Producing a report without owners or follow-up
    • Using the interview to try to win the deal back

    Summary

    Win-loss analysis interviews buyers after wins, losses, and no-decisions to find the real reasons behind outcomes. It matters because CRM loss reasons are written by reps in a hurry and tend to default to price or timing, while buyers describe different drivers, such as unclear business cases, missing integrations, lost champions, and stalled security reviews.

    To run one, define a specific question, select a mix of recent deals, use a neutral interviewer, interview within about a month, code every conversation with a fixed frame, and triangulate with CRM data. Report sample size and confidence, then assign owners to each finding. Feed the results back into your closed-lost field, your qualification rules, and your deal reviews so the CRM gets closer to the truth.

    FAQ

    What is win-loss analysis?

    It’s the practice of interviewing buyers after a deal closes, whether won, lost, or ended in no decision, to learn the real reasons behind their choice and use them to improve positioning, product, pricing, and sales process.

    Why isn’t the CRM loss reason enough?

    Reps usually choose it quickly and tend to cite price or timing. Buyer interviews often reveal different reasons. Use CRM fields for volume and trends, and validate them with real buyer conversations.

    Who should conduct win-loss interviews?

    Someone neutral: a product marketer, researcher, or outside firm. The rep who owned the deal and their manager should not, because buyers soften feedback when they know who is asking.

    How soon after a deal should we interview the buyer?

    Ideally within two to six weeks. Memory fades quickly, and recruiting gets harder with time, so aim for within about a month.

    How many interviews do we need?

    Some sources suggest 15 to 20 per quarter for clear patterns. Smaller rounds are still useful if labeled directional. Keep the process consistent and grow the sample over time.

    Should we interview wins as well as losses?

    Yes. Wins show what’s working and what to protect, and they give you a baseline to compare losses against. Also include no-decision deals, which are often the largest hidden source of lost revenue.

    How do we get buyers to agree to an interview?

    Keep the ask short, offer a 20 to 30 minute call, explain that feedback is confidential and used for improvement, not for selling, and send the request from a neutral person. Try multiple contacts on the buying committee.

    What do we do with the findings?

    Hold a short workshop, rank the findings, and map each to an owner and a specific change, such as a messaging update, an ROI template, a required CRM field, or a roadmap request. Then check next quarter whether the pattern moved.