Author: Kartik Mishra

  • HubSpot Sequences vs. Workflows: What’s the Difference?

    HubSpot workflows are system-level automation: they run on criteria you set, work across contacts, companies, deals, and tickets, and can branch, delay, and update records. HubSpot sequences are rep-level outreach: a series of one-to-one emails and tasks sent from a rep’s own inbox to one prospect, which stops automatically when the prospect replies or books a meeting. The fastest test is to ask who the message is from and whether it should stop when a human responds.

    Teams often use one tool for both jobs and get poor results. Nurture emails sent as a “sequence” don’t scale. Sales follow-ups built as a “workflow” feel like marketing blasts and keep sending after the prospect has answered. This guide explains the difference, shows when to use each, and shows how to combine them without sending a prospect two competing messages.

    The differences at a glance

    Dimension Sequences Workflows
    Purpose One-to-one rep outreach One-to-many operational and marketing automation
    Owner The rep or sales team RevOps, marketing, or operations
    Sender The rep’s connected inbox A shared or system address
    Trigger Rep enrollment, with limited auto-enrollment by plan Forms, property changes, page visits, deal stage, and more
    Logic Linear steps: emails and tasks with delays Branching, delays, and conditions
    Works on Contacts Contacts, companies, deals, tickets, and other objects
    Email type One-to-one business email Marketing email with subscription rules
    On reply Unenrolls on a genuine reply or a booked meeting Continues according to its own logic
    Other actions Tasks for the rep Set properties, rotate owners, create tasks, send internal notifications, and more

    Sequences are built for a person writing to a person. Workflows are built for a company’s systems acting on records. A third difference is where replies go. A reply to a sequence email lands in the rep’s inbox and is tracked in HubSpot, while a reply to a marketing email goes to the reply-to address, which HubSpot isn’t connected to, so that reply isn’t tracked.

    Which one should you use? Ten scenarios

    Scenario Use Why
    Nurture emails to hundreds of MQLs Workflow Marketing email at scale, with subscription handling
    A rep following up after a demo Sequence Personal, from the rep, and stops on reply
    Assign an owner and create a task when a form is submitted Workflow It updates records and routes work
    Outbound to a prospect list Sequence One-to-one outreach with calls and tasks mixed in
    Update lifecycle stage when criteria are met Workflow Property automation, no email involved
    Notify the team when a deal reaches a stage Workflow Internal notifications and tasks
    Webinar follow-up to all attendees Workflow Bulk, branded, and trackable as marketing
    Personalized follow-up after a meeting Sequence It should read like a person wrote it
    Re-engage stalled deals Workflow plus sequence The workflow finds the deals and creates tasks, and a rep sequence does the outreach
    Renewal reminders from a CSM Sequence or workflow task Use a sequence if the CSM sends it personally, and a workflow if the task is internal

    Three questions settle most cases. Is it one-to-one or one-to-many? Should it stop when the person replies? Does it need to act on records, such as changing a property or creating a deal? If you answer “one-to-one, yes, no,” build a sequence. If you answer “one-to-many, no, yes,” build a workflow.

    Using them together: a worked flow

    The strongest setups assign each tool its natural job. Here’s a common pattern for inbound leads.

    Step Tool What happens
    1. A prospect submits a demo form Workflow Sets lifecycle stage and lead status, assigns the owner, and creates a task with a due date that matches your SLA
    2. The rep reviews the lead Sequence The rep enrolls the contact in a short sequence of personal emails and call tasks
    3. The prospect replies or books a meeting Sequence The contact is unenrolled automatically
    4. A meeting is booked Workflow Creates the deal, updates the lifecycle stage, and notifies the account team
    5. The sequence ends with no reply Workflow Updates lead status, moves the contact into marketing nurture, and logs the outcome

    This keeps the personal outreach with the rep and the record keeping with the system. For the pieces around it, see our guides to lifecycle stages, the sales and marketing SLA, and AI tools for lead handoff.

    Plans, seats, and limits

    Topic Sequences Workflows
    Subscription Sales Hub or Service Hub Professional or Enterprise Available across Hubs; sending marketing email from a workflow needs Marketing Hub Professional or Enterprise, with some Service Hub options for service emails
    Seats and setup An assigned paid seat, sequences permissions, and a connected personal inbox Workflow permissions; no personal inbox required
    Daily sending Per-user daily limits, reported as 500 on Professional and 1,000 on Enterprise over a rolling 24 hours Email volume scales with your Marketing Hub contact tier
    Automatic enrollment Professional supports limited auto-enrollment set up inside a sequence The “enroll in sequence” and “unenroll from sequence” actions are Enterprise-only
    One at a time A contact can be in one sequence at a time A contact can be in many workflows

    HubSpot changes tiers, limits, and step counts regularly, and published guides don’t always agree, so confirm current numbers in HubSpot’s knowledge base before you design around them. If your plan lacks the workflow-to-sequence action, a practical workaround is to let the workflow create a task for the owner, who then enrolls the contact in a sequence.

    Stop sales and marketing automation from colliding

    The most common failure isn’t picking the wrong tool. It’s running both on the same person. A prospect gets a marketing nurture email on Tuesday and a personal sequence email on Wednesday, each unaware of the other.

    Collision Fix
    A contact is in a marketing nurture and a sales sequence at once Add enrollment exclusions so nurture workflows skip contacts who are in an active sequence, using the available “currently in a sequence” filter or a property you maintain
    A contact in an open deal still gets cold nurture Exclude open-deal contacts from top-of-funnel workflows
    A rep enrolls someone who has unsubscribed or opted out Check subscription and consent status before enrollment and apply your policy consistently
    Nobody knows which automation sent what Keep a shared inventory of workflows and sequences with owners and purpose
    Duplicate records create duplicate enrollments Clean duplicates first, as in our guide to clean CRM data

    Email law and consent rules apply to both tools, and the right approach varies by country, so have your legal counsel confirm what applies to your outreach.

    Building both well

    • Sequences: keep them short, mix emails with call or LinkedIn tasks, personalize the first line, and write each email to stand alone. For where AI helps and where it hurts, see our guide to AI sales email drafting.
    • Workflows: define the enrollment criteria and the goal first, add re-enrollment rules deliberately, and test with a few records before turning it on. Our workflow explainer covers the basics, and designing RevOps workflows covers the process side.
    • Both: write the process down before you build, name an owner, and review performance monthly.

    How to measure each

    Tool Metrics
    Sequences Reply rate, meetings booked, performance by step, and how many contacts finish without responding
    Workflows Enrollment, goal completion, conversion to the next lifecycle stage, and email engagement
    Both together Time to first touch, meetings per lead, pipeline created, and lead-to-opportunity conversion

    Tie these back to outcomes using closed-loop reporting, so you can see which automation produces pipeline and not just opens.

    Mistakes to avoid

    • Using sequences for mass nurture, then hitting daily send limits
    • Using workflows for rep outreach that should stop when someone replies
    • Letting prospects sit in marketing nurture and a sales sequence at once
    • Skipping unsubscribe and consent checks before enrollment
    • Building automation without owners, so nobody knows what is running
    • Assuming workflow-to-sequence enrollment is available on every plan
    • Measuring opens instead of replies, meetings, and pipeline

    Summary

    HubSpot workflows automate processes across records, with branching logic, property updates, and marketing email at scale. Sequences automate one rep’s outreach to one contact from the rep’s own inbox, and stop on a reply or booked meeting. Choose by asking whether the message is one-to-one or one-to-many, whether it should stop on reply, and whether it needs to act on records.

    The best setups combine them: a workflow routes the lead, a rep runs the sequence, and a workflow handles what happens next. Confirm plan, seat, and limit details with HubSpot, exclude contacts from overlapping automation, check consent before enrolling, and measure replies, meetings, and pipeline instead of opens.

    FAQ

    What is the main difference between HubSpot sequences and workflows?

    Sequences are one-to-one outreach from a rep’s inbox that stops when the prospect replies or books a meeting. Workflows are system automation across records that can branch, update properties, and send marketing email at scale.

    Which HubSpot plans include sequences?

    Sales Hub Professional and Enterprise, and Service Hub Professional and Enterprise. A paid seat, sequences permissions, and a connected personal inbox are required. Confirm current details with HubSpot.

    Can a workflow enroll a contact in a sequence?

    Yes, on Sales Hub or Service Hub Enterprise, using the “enroll in sequence” action, and the sender needs a paid Enterprise seat. On lower plans, a workflow can create a task for a rep to enroll the contact.

    Do sequences stop when someone replies?

    Yes. By default, a contact is unenrolled when they reply or book a meeting. Workflows don’t do this automatically, so you have to build the logic yourself.

    Can a contact be in a sequence and a workflow at the same time?

    Yes, but it often causes double messaging. Add exclusions so marketing nurture workflows skip contacts who are in an active sequence or open deal.

    Are there limits on how many emails a sequence can send?

    Yes. Sequences have per-user daily sending limits, reported as 500 on Professional and 1,000 on Enterprise, and limits on steps and enrollment. Workflow email volume depends on your Marketing Hub contact tier. Check HubSpot’s current limits.

    Which should I use for cold outbound?

    A sequence, since it’s personal, comes from the rep, mixes emails with call tasks, and stops on reply. Make sure you have a lawful basis and consent where required, and have counsel confirm your approach.

    Should marketing or sales own these tools?

    Sales usually owns sequences and marketing or RevOps owns workflows, but one team, usually RevOps, should keep an inventory of both so they don’t collide.

  • The Complete Guide to SaaS Solution Evaluation

    SaaS solution evaluation is the process a buying team uses to compare software options against a defined use case and reach a decision everyone can stand behind. For cross-functional teams, the hard part isn’t comparing features. It’s getting RevOps, sales, finance, security, legal, and customer success to agree on what matters before the vendors start presenting.

    Most evaluation guides assume one buyer. Real B2B software purchases involve several people with different priorities, and the evaluation often stalls or ends in regret because those priorities were never reconciled. This guide shows how to organize the group, turn disagreement into weights and gates, score fairly, and document the decision.

    Why alignment decides the outcome

    Gartner puts the typical complex B2B purchase at six to ten stakeholders, and Forrester’s broader counts run higher. More people means more priorities. A 2025 Gartner survey found that 74% of B2B buying teams showed what it calls unhealthy conflict, which it defines as conflicting objectives, disagreement over the best course of action, or being overruled by outside decision-makers.

    An earlier Gartner study of 1,120 enterprise technology purchases points the same way. Among buyers who reported high regret, 89% said team members had different, often conflicting objectives for the purchase, compared with 9% of those with no regret. High-regret buyers also took seven to ten months longer on average. These come from large enterprise purchases, so treat the figures as directional for a growth-stage team, but the lesson travels: unresolved conflict at the start becomes regret at the end.

    Set roles and decision rights first

    Before you speak to a vendor, decide who does what. Name one decision owner, usually the RevOps lead or the executive who owns the workflow, who is accountable for the recommendation. Name an executive sponsor to break ties. Then give each function a defined lane. Here’s an illustrative RACI, where R is responsible, A is accountable, C is consulted, and I is informed.

    Activity Sponsor Decision owner Daily users Finance Security and IT Legal and procurement
    Define use case and success metric C A/R C C I I
    Set gates (must-haves) I A C R R C
    Weight criteria I A R R R C
    Score vendors I A R R R C
    Security and data review I C I I A/R C
    Contract and terms I C I C C A/R
    Final decision C A/R C C C C

    Each function should own the criteria it knows best. Security scores security, finance scores total cost, and daily users score usability. Nobody should score everything, and nobody should be asked to rate what they can’t judge.

    Step 1: Agree on one use case and one value scenario

    Write the use case in a card: the metric, the current value, the target, the owner, and the data involved. Our guide to B2B SaaS use case mapping explains the format, and evaluating by revenue bottleneck helps you choose which problem deserves a purchase. Then add a one-sentence group value scenario that everyone can sign: “We’ll know this worked when median first response drops from 19 hours to under one hour, without adding admin headcount.” A shared scenario keeps individual wish lists from taking over. Gartner’s research makes a related point from the seller side: framing for the group’s shared goal improves consensus, while framing for each individual’s agenda damages it.

    Step 2: Gather requirements once, in one place

    Interview each stakeholder separately for 20 to 30 minutes before any group meeting. Ask what a good outcome looks like, what would make them veto a vendor, and what they’ve seen go wrong before. Record answers in one shared requirements document and freeze it at a set date. A requirements document on its fifth version eight weeks in is not diligence. It’s a sign that someone keeps moving the goalposts. Allow changes only through the decision owner, with a reason.

    Step 3: Weight criteria with a priority-points exercise

    Instead of debating weights in a meeting, have each stakeholder allocate 100 points across the criteria privately. Average the results, and look hard at where the spread is widest. Here’s an illustrative example.

    Criterion RevOps Sales lead Finance Security CS lead Average Range
    Workflow fit 30 40 20 15 30 27 15 to 40
    CRM integration 30 10 10 25 15 18 10 to 30
    Security and data 10 5 10 45 5 15 5 to 45
    Total cost 10 15 50 5 10 18 5 to 50
    Adoption and usability 20 30 10 10 40 22 10 to 40
    Total 100 100 100 100 100 100

    The averages give you starting weights. The ranges give you the real conversation. Security and cost show the biggest disagreement, because for the people who own them, they’re not preferences. They’re constraints. The fix is to move them out of the weighted score and into gates: security either passes your review or the vendor is out, and total cost either fits the budget ceiling or it doesn’t. Keep weighting for what’s genuinely tradeable, like fit, integration, and adoption.

    Step 4: Run gates and parallel review lanes

    Security, legal, finance, and operations reviews usually run in parallel, and they often start late. Start them early and run them alongside demos, or they’ll reopen the decision at the end.

    Lane What it checks Typical evidence
    Security and IT Access controls, audit logging, data location, sub-processors, certifications Security questionnaire, architecture overview, compliance reports
    Legal and procurement Data processing terms, liability, termination, renewal pricing caps Draft contract and data processing agreement
    Finance Total cost at 24 months, payment terms, usage-based exposure Written quote at two sizes
    Operations Integration, migration, admin load, support hours Test on your own data

    Step 5: Evaluate on your own data and score independently

    Ask each finalist to run your scenario, using your data and rules, not a polished sample. Label every score by evidence level (claimed, shown, tested, or proven) and cap untested claims. Have each evaluator score independently before any discussion, then discuss only the criteria where scores differ by two points or more. Our guide to SaaS solution scorecards covers the mechanics, including anchored scales and a sensitivity check.

    Step 6: Hold a consensus session

    Once the scores are in, bring the group together for one working session of 60 to 90 minutes. Show the totals, the weights, the evidence levels, and each vendor’s biggest risk. Ask each stakeholder a single question: “Can you live with this recommendation, and if not, what specifically would change your view?” That separates a real objection from a preference. If top scores are within about five points, agree a time-boxed pilot with a success metric, instead of arguing. If someone raises a new criterion late, add it only if it would have changed the weights, and rerun the numbers in front of everyone.

    Step 7: Write the decision down

    A one-page decision memo preserves the reasoning and prevents the same debate at renewal. Include the use case and value scenario, the finalists, scores with evidence levels, the gates each passed, the biggest risk for each, what you’re trading away, the owner, the metric you expect to move, and a review date 90 days out. Add that review to your quarterly RevOps meeting cadence.

    An eight-week plan

    Week Activity Output
    1 Name the decision owner and sponsor; write the use case and value scenario Roles and a shared goal
    2 Stakeholder interviews; freeze requirements; run the priority-points exercise Requirements and weights
    3 Set gates; build a shortlist of two or three Gates and finalists
    4 to 5 Scenario demos on your data; start security, legal, and finance reviews in parallel Evidence and review progress
    6 Sandbox or pilot on the top candidates Tested scores
    7 Independent scoring; consensus session A recommendation
    8 Decision memo; negotiate terms Signed decision and contract

    Treat the timeline as a template. Smaller purchases can run faster, and complex integrations or security reviews may need longer. If your evaluation is for a services partner, not a product, our guide to choosing a HubSpot partner adapts the same ideas.

    Warning signs inside your own buying group

    • The requirements document keeps growing after it was supposed to freeze
    • Reviews get “delegated” back and forth between functions with no conclusion
    • Procurement joins before any vendor is preferred, and negotiates on politics, not price
    • One stakeholder stops responding after a vendor they didn’t prefer advances
    • Different people describe the goal of the purchase in different words
    • The executive sponsor hasn’t been in a meeting since kickoff

    When you see two or more, stop adding demos and fix alignment: revisit the value scenario, the decision rights, and the weights.

    Mistakes to avoid

    • Letting every stakeholder score every criterion
    • Debating weights live, where the loudest voice wins
    • Treating security and budget as preferences instead of gates
    • Starting legal and security reviews after the decision is “made”
    • Skipping the executive sponsor, so ties go unresolved
    • Allowing new criteria late with no rule for changing weights
    • Writing no decision memo, so the reasoning disappears by renewal

    Summary

    SaaS solution evaluation for cross-functional teams is mostly an alignment problem. Gartner finds that most buying teams show unhealthy conflict, and that purchases with conflicting objectives are far more likely to end in regret. Start by naming a decision owner and sponsor, define each function’s lane, and agree on a single use case and a shared value scenario.

    Gather requirements once and freeze them, use a private priority-points exercise to set weights, and convert constraints like security and budget into gates. Run security, legal, and finance reviews in parallel, test on your own data, score independently, and settle close calls with a pilot. Hold a consensus session, write a one-page decision memo, and review the result at 90 days.

    FAQ

    What is SaaS solution evaluation?

    It’s the process a buying team uses to compare software options against a defined use case, using agreed criteria, evidence, and decision rights, so the final choice is explainable and shared.

    Who should be on the evaluation team?

    A decision owner, an executive sponsor, daily users, and representatives from finance, security or IT, and legal or procurement. Keep the core group small, and consult others as needed.

    How do we handle stakeholders who disagree on priorities?

    Collect priorities privately using a points exercise, look at the spread, and turn hard constraints into gates. Discuss the criteria with the widest disagreement, and let the sponsor break any remaining tie.

    Who should make the final decision?

    The person accountable for the outcome, usually the RevOps lead or the executive who owns the workflow, with input from the others. Security and legal should hold authority over their own gates.

    How long should an evaluation take?

    Roughly four to eight weeks for many growth-stage purchases, longer with complex integrations or heavy security review. Starting parallel reviews early is the biggest time saver.

    Should security and cost be weighted criteria?

    Usually they work better as gates, with a pass or fail on your security requirements and a budget ceiling, plus a weighted score for the tradeable differences within those limits.

    What if a stakeholder raises a new requirement late?

    Route it through the decision owner. Add it only if it would change the weights or gates, and if so, rerun the scores openly so everyone sees the effect.

    How do we avoid buyer’s regret?

    Align on one goal early, test on your own data, resolve conflicts before the contract, document the decision, and review results at 90 days. Regret most often traces back to unresolved disagreement at the start.

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

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

  • HubSpot Lead Scoring: How to Build a Model Sales Trusts

    A HubSpot lead score is a number, or a pair of numbers, that ranks contacts, companies, or deals by how well they fit your ideal customer and how engaged they are, so sales knows who to contact first. A model sales trusts is built from your own closed-won data, kept simple enough to explain, split into fit and engagement, and calibrated against real outcomes.

    Most lead scoring fails for one reason: reps stop believing it. A few high-scoring leads turn out to be students or competitors, a few great prospects score low, and within a quarter the score becomes a column nobody opens. Trust is hard to rebuild once it’s gone, so this guide is about earning it from the start.

    Why sales stops trusting scores

    What reps say Likely cause Fix
    “High scores are junk.” Engagement counted without fit, so students, competitors, and job seekers score well Separate fit from engagement and require both
    “Good leads score low.” Missing data, or offline signals like events and calls aren’t scored Fill key properties and add the signals that really predict deals
    “Everyone’s score keeps climbing.” No decay or cap, so old activity inflates scores Add decay, a maximum score, and negative criteria
    “I don’t know why this lead scored 80.” An opaque model nobody explained Keep criteria few and documented, and share them with the team
    “Marketing and sales disagree on an MQL.” No shared definition or follow-up rule Agree a threshold, owner, and response time together

    Notice that none of these are tool problems. They’re design and communication problems, which means you can fix them before you touch a setting.

    Step one: let closed-won data decide what matters

    Don’t start by brainstorming criteria. Start by comparing your last 12 months of closed-won deals against closed-lost and stalled ones. Ask what the winners had in common before they ever talked to sales.

    • Company traits: size, industry, region, tech stack, growth stage.
    • Person traits: job title, seniority, department.
    • Behaviors: pricing page visits, demo requests, repeat visits within a short window, event attendance.
    • Anti-signals: personal or competitor email domains, regions you don’t serve, no activity for months.

    Then take that list to two or three of your best reps and ask them to challenge it. Their reactions are worth more than any template, and they’ll be more likely to trust a model they helped shape. For help with the qualification logic behind it, see our guide to BANT and MEDDIC.

    Step two: score fit and engagement separately

    Fit asks whether this is the right kind of person at the right kind of company. Engagement asks whether they’re showing interest now. A single blended number hides which one is driving the score, and that’s where trust breaks. HubSpot’s lead scoring tool supports engagement scores, fit scores, and combined scores that evaluate both, so you can show reps both views.

    A simple way to read the pair: high fit with low engagement is a nurture target, low fit with high engagement is a likely time-waster, and high on both is the hot lead. That one-line explanation does more for adoption than any amount of documentation.

    Step three: keep the model small

    A model with 40 rules can’t be explained or debugged. Aim for roughly 8 to 12 criteria per score, with weights that reflect how strongly each one predicts a deal. Here’s an illustrative starting model. The points are examples, not recommendations.

    Score Criterion Points Why
    Fit Company size within your target range +20 Closed-won deals cluster here
    Fit Industry in target list +15 Higher win rate in these industries
    Fit Job title matches buyer or champion persona +15 Reaches the people who buy
    Fit Region outside the markets you serve -20 Can’t be sold or supported
    Fit Competitor, student, or agency domain -30 Engages heavily but never buys
    Engagement Demo request +30 Strongest buying signal
    Engagement Pricing page visit (decays after 30 days) +10 Late-stage research
    Engagement Two or more visits in seven days +10 Active evaluation
    Engagement Marketing email click (capped) +3 each, max 9 Weak signal, so capped
    Engagement No activity for 90 days -15 Interest has gone cold

    Three design choices do most of the work. Negative scoring removes obvious junk. Caps stop low-value activity, like email clicks, from stacking into a high score. And decay makes sure old behavior fades, which keeps scores from only ever rising.

    Step four: tie scores to a handoff and a response time

    A score only changes behavior if something happens at a threshold. Agree on three things with sales before you launch:

    • The threshold. For example, a lead becomes an MQL when fit reaches 30 and engagement reaches 25. The numbers are illustrative. Calibrate them in step five.
    • The owner and response time. Who gets the lead, and how fast do they follow up? Put it in writing.
    • The feedback path. How do reps mark a bad lead so the model learns from it?

    In HubSpot, score properties can drive segments, workflows, and reports. Use a workflow to move a contact to MQL and create a task for the owner when the thresholds are met. Our explanation of HubSpot lifecycle stages shows how to define that handoff, and What Is a HubSpot Workflow? covers the automation.

    Step five: calibrate against what actually happened

    Before you roll out, backtest. Apply the scoring rules to leads from the last year and see whether higher scores converted better. Here’s an illustrative result:

    Score band Leads Became opportunities Conversion
    0 to 29 600 12 2%
    30 to 59 300 24 8%
    60 to 100 100 25 25%

    What you want is a steady climb. If the top band doesn’t convert noticeably better than the middle, the model is mis-weighted, and you should fix it before sales sees it. After launch, review monthly at first: conversion by score band, the leads reps rejected, and the closed-won deals that scored low. Those misses are the most useful data you have. Our guide to closed-loop reporting covers how to trace leads through to revenue so you can run this check.

    Setting it up in HubSpot

    HubSpot’s current lead scoring tool lives under Marketing and replaces the older HubSpot Score property, which has been retired. If any of your workflows, lists, or reports still reference that legacy property, they won’t reflect current scores, so rebuild them on the new tool.

    • Objects and plans: contact scores are available in Marketing Hub, company scores in Marketing Hub or Sales Hub, and deal scores in Sales Hub. AI-generated engagement and fit scores are limited to Marketing Hub Enterprise. Plan details change, so confirm what your subscription includes.
    • Score types: build an engagement score, a fit score, or a combined score, depending on what you want reps to see.
    • Permissions: you need edit permissions for Lead Scoring to create or change scores.
    • Data: fit scores depend on filled-in properties such as company size and industry, so check completeness first. A fit score built on empty fields scores everyone the same.
    • Recalculation: scores can take time to update across a large database after you turn them on, so don’t judge results in the first hour.

    If you’re considering AI or predictive scoring, our overview of AI lead scoring explains how it differs. For many smaller teams, a transparent manual model outperforms a black box because there isn’t yet enough closed-won data to train anything reliable, and reps can see the logic.

    Govern the model, or it will drift

    Scoring models decay as your product, market, and buyers change. Name an owner, usually RevOps, keep a change log of every edit with the reason, and review the model quarterly with sales. When you change criteria, tell the team what changed and why, because a score that shifts without explanation damages trust faster than a bad one.

    Mistakes to avoid

    • Building the model without sales in the room
    • Scoring only the person and ignoring the company
    • Letting email opens and clicks inflate scores
    • Skipping negative criteria, caps, and decay
    • Setting thresholds before backtesting
    • Launching with no response-time rule and no feedback loop
    • Never reviewing the model after launch

    Summary

    A lead scoring model sales trusts starts with your own closed-won data, not a template. Compare winners with losers, validate the findings with your best reps, and keep the model small, around 8 to 12 criteria per score. Score fit and engagement separately so reps can see why a lead ranks high, and use negative criteria, caps, and decay to keep scores honest.

    Agree on thresholds, owners, and response times with sales, then backtest the model against past results before launch and review it monthly afterward. In HubSpot, use the current lead scoring tool, not the retired score property, and check which plan features you have. Name an owner, keep a change log, and revisit the model every quarter.

    FAQ

    What is lead scoring in HubSpot?

    It’s a tool that assigns points to contacts, companies, or deals based on fit and engagement criteria you define, so teams can prioritize follow-up. Scores can drive segments, workflows, and reports.

    Which HubSpot plan do I need for lead scoring?

    Contact scoring requires Marketing Hub, and some capabilities, such as AI-generated scores, are limited to Enterprise. Company scores can use Marketing Hub or Sales Hub, and deal scores use Sales Hub. Confirm current plan details with HubSpot.

    What happened to the old HubSpot Score property?

    It was retired and no longer updates, so workflows, lists, and reports that rely on it need rebuilding on the current lead scoring tool.

    Should I use a fit score, an engagement score, or a combined score?

    Most teams benefit from seeing both. Separate fit and engagement scores explain why a lead ranks high, and a combined score can drive the MQL threshold. Start with whichever your reps will actually understand.

    Is manual or predictive scoring better?

    For many smaller teams, manual scoring is easier to explain and doesn’t need much training data. Predictive or AI scoring can help once you have a large, clean history of closed-won deals, but reps still need to understand and trust it.

    How many criteria should a model have?

    Roughly 8 to 12 per score is a sensible target. More than that becomes hard to explain and debug, and reps stop trusting what they can’t understand.

    How often should we review the scoring model?

    Monthly for the first few months after launch, then quarterly. Review conversion by score band, leads reps rejected, and closed-won deals that scored low, and record every change.

  • Salesforce to HubSpot Migration: A Practical Checklist

    Migrating from Salesforce to HubSpot comes down to three jobs: map Salesforce’s data model onto HubSpot’s, load records in an order that keeps relationships intact, and rebuild automation by hand, because it doesn’t transfer. Plan roughly six to eight weeks for a standard setup, and longer if you have custom objects, Apex code, or heavily customized flows.

    This checklist walks through the phases in order, with the checks that catch problems early. It’s written for RevOps leads and Salesforce admins who need a plan they can hand to a team.

    Before you start: four decisions

    1. Why are you moving? Cost, usability, or one platform for marketing and sales. The reason shapes what you bring across and what you leave behind.
    2. How much history comes with you? Active contacts, open deals, and recent closed deals are the usual core. Archive the rest instead of importing everything.
    3. Which HubSpot plan do you need? Custom objects require Enterprise, and workflow and reporting features vary by tier. Decide before you design.
    4. Who owns the project? One named owner, with a Salesforce admin and a sales and marketing sponsor involved.

    How Salesforce objects map to HubSpot

    Salesforce HubSpot Notes
    Account Company Import before contacts and deals
    Contact Contact HubSpot treats email as the unique identifier, so resolve duplicates first
    Lead Contact HubSpot has no Lead object; use lifecycle stage and lead status
    Person Account Contact Decide how to represent any associated company
    Opportunity Deal Rebuild pipelines in HubSpot instead of copying stages blindly
    Campaign HubSpot campaign or list Choose based on how you use campaigns
    Case Ticket Requires Service Hub
    Custom object Custom object Enterprise only; create objects and associations before importing
    Owner HubSpot user and owner Map every owner, or records arrive unassigned
    Flow, Process Builder, Apex Workflows or custom code actions Rebuilt by hand, not migrated

    Phase 1: Audit and clean in Salesforce

    Data problems compound in a new system, so fix them at the source. Run a data quality audit before you export anything.

    • Find duplicate contacts and companies, invalid emails, and records missing required fields.
    • Flag contacts with no account, since they’ll arrive in HubSpot without a company association.
    • Decide which stale leads, old deals, and unused custom fields to archive instead of migrating.
    • List every report and dashboard leadership relies on, so you can rebuild them.
    • Inventory automation, integrations, and AppExchange apps, including who depends on each.
    • Review picklist values, because HubSpot dropdowns need matching options.

    Phase 2: Design the HubSpot side first

    • Pipelines and stages. Build them in HubSpot before loading deals. Use this as a chance to simplify.
    • Properties. Create custom properties for the fields you’re keeping, with matching types and dropdown values.
    • A Salesforce ID property. Store the original Salesforce record ID on every migrated record, so you can reconcile, de-duplicate, and trace problems later.
    • Lifecycle stage and lead status. Decide how Salesforce lead statuses map. Our guide to HubSpot lifecycle stages explains the options.
    • Users, teams, and permissions. Create them before import so owners can be mapped.
    • Custom objects and associations, if you’re on Enterprise, created before any import.

    Then build a field mapping document: one row for every field you plan to migrate, with its type, format, and any picklist translation. Anything not in the document doesn’t move.

    Also decide which reporting fields to preserve, because history is hard to rebuild. At minimum, carry over the original lead source and detail, the Salesforce created date (in a custom date property), campaign history, lifecycle stage dates, owner, and closed-lost reason. Without them, your revenue attribution and funnel reports start from zero.

    Phase 3: Load in dependency order

    Importing in the wrong order breaks associations silently: the records exist, but they’re orphaned. Parents first, then children.

    Order Load Check
    1 Users and owners Every owner in Salesforce has a HubSpot match
    2 Companies Counts match; Salesforce IDs populated
    3 Contacts, with company associations Duplicate emails resolved; unassociated contacts flagged
    4 Deals: open first, then closed-won history Pipelines exist; amounts, close dates, and owners correct
    5 Tickets, if used Associated with the right contacts
    6 Activities and notes Attached to the right records

    Test the whole sequence in a sandbox or with a small batch first. A tiny rehearsal is cheaper than cleaning up a full load.

    Phase 4: Rebuild automation

    Salesforce automation does not migrate. Flows, Process Builder automations, Apex triggers, and formula fields all have to be rebuilt.

    Salesforce HubSpot approach
    Lead assignment rules Rotation and routing workflows
    Flows and Process Builder Workflows with equivalent branching
    Apex triggers Workflows with custom code actions, or an API integration
    Formula fields Calculated properties or workflow logic
    Email alerts Notifications and internal emails
    Lead scoring HubSpot score properties

    Build the workflows but keep them paused until data validation is finished, or a half-checked import will trigger emails and tasks to the wrong people. For background, see What Is a HubSpot Workflow?

    Phase 5: Validate before you go live

    • Reconcile counts for each object against Salesforce.
    • Spot-check about 5% of records by hand for each object, comparing field values and formats.
    • Check associations: every contact with a Salesforce account should have the right company, and every deal the right contact and company.
    • Verify owners, so no records are unassigned.
    • Run key reports side by side in both systems and explain any differences.
    • Test workflows with test records, then switch them on.
    • Get sign-off from sales and marketing leaders, not just the project team.

    Phase 6: Cutover and the first 30 days

    1. Agree a freeze window for Salesforce edits, or define a delta load for changes made during cutover.
    2. Load the final delta and re-run your count checks.
    3. Repoint integrations such as email, calendar, billing, and product data to HubSpot.
    4. Switch on the validated workflows and train users on the new pipeline.
    5. Keep Salesforce read-only for a defined period, so people can look things up.
    6. Review at 30 days: data quality, adoption, broken automation, and report accuracy.

    If you run both systems in parallel, HubSpot’s Salesforce connector can keep data in sync during a phased move. Decide which system owns each field and which direction it syncs, and avoid two-way writes on the same field, or the systems will overwrite each other. Hold the sync off during bulk imports.

    What doesn’t migrate cleanly

    • Automation: Flows, Process Builder, and Apex are rebuilt, not moved.
    • Formula fields and other calculated logic.
    • Files and attachments: they don’t sync through the native integration, so plan a separate approach if you need them.
    • Reports and dashboards: rebuild them in HubSpot.
    • Custom object relationships: lookups and associations need manual mapping.
    • Account hierarchies: support is limited, so check how parent-child accounts will appear.

    A realistic timeline

    Weeks Focus
    1 to 2 Decisions, audit, and cleanup
    3 to 4 HubSpot design, field mapping, sandbox rehearsal
    5 to 6 Loads and validation
    6 to 7 Automation rebuild and testing
    7 to 8 Cutover and close support

    That’s a standard CRM-only migration. Custom objects, Apex code, and AppExchange apps can push it toward 12 weeks or more. Use your own data volumes and complexity to adjust it.

    Mistakes to avoid

    • Importing contacts or deals before companies, which orphans associations
    • Copying Salesforce stages into HubSpot without redesigning the pipeline
    • Migrating every field and record instead of what’s actually used
    • Leaving owners unmapped, so automation fails
    • Activating workflows before validation
    • Skipping original source and date fields, which resets your reporting history
    • Declaring victory at go-live without a 30-day review

    Summary

    A Salesforce to HubSpot migration maps Accounts to Companies, Opportunities to Deals, and Leads to Contacts with lifecycle stage, since HubSpot has no Lead object. Clean and audit in Salesforce first, design pipelines and properties in HubSpot, build a field mapping document, and keep the Salesforce ID on every record. Load users, companies, contacts, deals, tickets, and activities in that order, because the wrong order silently breaks associations.

    Automation doesn’t migrate, so rebuild it as workflows and keep it paused until validation is done. Reconcile counts, spot-check about 5% of records, and run key reports side by side. Expect around six to eight weeks for a standard setup and longer with custom objects or code, and preserve source and date fields so your reporting survives the move.

    FAQ

    How long does a Salesforce to HubSpot migration take?

    Around six to eight weeks for a standard migration of contacts, companies, deals, and activities. Custom objects, Apex code, and heavily customized automation can push it toward 12 weeks or more.

    What happens to Salesforce Leads in HubSpot?

    HubSpot has no Lead object, so leads become contacts. Use lifecycle stage and lead status to preserve their status, and plan for duplicate emails, since HubSpot treats email as a unique identifier.

    Do Salesforce workflows and flows migrate?

    No. Flows, Process Builder automations, Apex triggers, and formula fields must be rebuilt as HubSpot workflows, custom code actions, or integrations.

    Which HubSpot plan do we need?

    It depends on what you’re bringing. Standard objects work across tiers, but custom objects require Enterprise, and workflow and reporting capabilities vary by plan. Decide the plan before you design the data model.

    Can we run Salesforce and HubSpot together during the transition?

    Yes, the Salesforce connector can keep data in sync during a phased move. Decide which system owns each field and the sync direction, and avoid two-way writes on the same field.

    What should we leave behind?

    Outdated leads, unused custom fields, old workflows, and legacy structures that no longer add value. Archive them in Salesforce or an export so nothing is lost, but don’t carry them into the new system.

    How do we keep attribution and reporting history?

    Map original lead source, created date, campaign history, lifecycle stage dates, and closed-lost reasons into HubSpot properties before you import. Reports rebuilt after the move will only be as good as the fields that came across.

  • RevOps Meeting Cadence: Weekly, Monthly, Quarterly Guide

    A RevOps meeting cadence is the recurring set of weekly, monthly, and quarterly reviews a revenue team runs to turn pipeline and revenue data into decisions. Weekly meetings catch near-term deal risk, monthly meetings spot trends, and quarterly meetings reset strategy, capacity, and territory plans.

    If you’ve ever sat through a Monday pipeline call that somehow turns into a 45-minute debate about next year’s territory map, you already know what happens when cadence layers get mixed up. The meeting runs long, nobody leaves with a clear next step, and you’re back in the same room next week discussing the exact same deal.

    That’s not a meeting problem. It’s a cadence problem. And if you’re building out RevOps (short for Revenue Operations, the function that aligns sales, marketing, and customer success data and process under one system) for the first time, getting the rhythm right early will save you months of meeting fatigue later.

    What is a RevOps meeting cadence?

    A RevOps meeting cadence is a layered system of recurring reviews, each with its own purpose, data, decision-maker, and follow-up. It’s not just a pile of calendar invites. A real cadence treats revenue meetings as a decision system: each one needs inputs, decision rights, an output, an owner, and a way to follow up on what gets decided.

    Honestly, most teams blur the layers together because nobody defined the boundaries up front. One weekly forecast call becomes slow because someone brings up a quarterly planning question. Keep the layers separate and each one gets faster, not slower.

    Layer The question it answers Typical attendees Inputs Output
    Weekly What needs action right now? Sales managers, RevOps, relevant reps Live CRM pipeline and forecast, at-risk deals, SLA exceptions Owners and dates for deal actions
    Monthly What is trending, and why? Sales, marketing, and customer success leaders, RevOps Trailing-month metrics: win rate, cycle length, deal size, revenue movement Decisions on resourcing, pricing, or process
    Quarterly Does the operating model still fit? Revenue leadership, finance, RevOps Full-quarter results, capacity, territory and segment performance Changes to headcount, territories, targets, or process

    Why does a RevOps meeting cadence matter?

    Without a defined cadence, a revenue system tends to decay. Definitions drift, fields stop getting updated, routing rules go stale, and nobody notices until a forecast misses. A regular review is how you catch what’s changed in the data, the process, or the tools before it becomes expensive.

    There’s also a real cost to running cadence badly. A simple calculation shows why. A weekly 60-minute meeting with eight attendees consumes eight hours a week, or about 416 hours over a year, before anyone counts preparation. Multiply that by every recurring meeting on the calendar and it’s easy to see why leaders feel buried. The fix isn’t fewer meetings by default. It’s meetings that each have a clear job and a visible output.

    For a deeper look at how reporting should flow into these reviews, our guide to closed-loop reporting covers how data feeds back so decisions stick.

    What should weekly RevOps meetings cover?

    Weekly meetings exist to answer one question: what needs action right now? That means pipeline inspection, forecast review, high-risk deal review, and any SLA (service-level agreement, the internal promise for how fast a team responds to a lead or ticket) exceptions that need attention this week. Teams with recurring revenue often add a short review of urgent renewal risks.

    A good weekly review runs on live CRM data, not a static slide or an exported spreadsheet. The moment leadership starts reviewing numbers from a spreadsheet instead of the actual system, the team quietly learns that the CRM is optional, and adoption erodes from there. Keep the agenda fixed week to week too. A variable agenda turns into status theater fast, where people talk instead of deciding. And leave broad strategy out of it entirely.

    Minutes Agenda item Output
    5 Forecast and coverage snapshot from the live CRM Shared view of where we stand
    20 Deals flagged at risk, slipping, or missing evidence Named action and date per deal
    10 SLA exceptions and unassigned leads or accounts Reassignments and fixes
    10 Escalations and decisions needed from leadership Decisions logged

    For help with the forecast portion, see our explanation of forecast categories and our guide to deal slippage, which cover the deal-risk patterns weekly reviews are best at catching.

    Pro tip: end every weekly review item with a name and a date attached. If an issue leaves the room without an owner and a deadline, it just comes back next week unchanged, and you’ve wasted everyone’s time twice.

    What should monthly RevOps meetings cover?

    Monthly cadence sits in the middle. It’s less granular than a weekly pipeline check and less strategic than a full quarterly reset. This is where you look at trailing-month data like win rate, sales cycle length, average deal size, and whatever shows up in your revenue waterfall (the breakdown of how revenue moves between new, expansion, contraction, and churn) to see whether performance is trending the right way.

    The monthly review is where RevOps earns strategic value. A weekly meeting may clean up one late-stage deal. The monthly review should ask why late-stage deals keep missing required evidence, which points to a qualification or enablement fix. If RevOps walks in with the same slide deck every month and nobody leaves with a decision, the meeting has become a status update wearing a strategy hat. Include finance whenever the discussion affects planning, and use governed metric definitions so people don’t argue about what “win rate” means.

    What should quarterly RevOps meetings cover?

    Quarterly reviews, often called QBRs (Quarterly Business Reviews), are where you step back from the day-to-day and ask bigger questions. Does the territory model still make sense? Do we have the right headcount and capacity? Do targets, segments, or the operating model need to change? A quarterly rhythm gives enough time to measure real performance shifts while keeping the team accountable on a fixed schedule.

    It’s also the meeting teams skip first when things get busy. That’s a mistake. It’s usually the one meeting that catches a broken process or a stale territory map before it turns into a bigger rebuild six months later. Plan for 60 to 90 minutes with a data packet circulated in advance, so the time goes to decisions instead of reading slides aloud.

    What belongs in which meeting?

    When a topic lands in the wrong layer, the meeting runs long and the decision stalls. A quick sorting guide helps:

    Topic Right layer Why
    A specific deal slipping this month Weekly Needs action before the period closes
    Leads sitting unassigned Weekly An SLA problem that gets worse by the day
    Win rate dropping for three months Monthly A trend that needs a cause, not a quick fix
    Changing a discount policy Monthly A pricing decision informed by trailing data
    Redesigning territories Quarterly A structural change with planning impact
    Hiring plans and capacity Quarterly Depends on full-quarter results and finance

    When a topic arrives in the wrong place, don’t fight it in the moment. Write it in a parking lot and route it to the layer where it belongs.

    Keep a decision log

    The cheapest way to make a cadence stick is a shared decision log. Each row records the date, the decision, the owner, the due date, and the status. Open each meeting by reviewing last time’s items. It takes five minutes and ends the pattern of the same issue returning unchanged. RevOps typically owns the log, so cadence hygiene doesn’t depend on any one manager’s memory.

    How do you build a RevOps meeting cadence? (Step-by-step)

    1. Map your current meetings first. List every recurring revenue meeting you already run and who attends. You’ll likely find overlap you didn’t know existed.
    2. Assign each meeting to a layer. Decide which are weekly (current-period risk), monthly (trend patterns), or quarterly (strategy and planning).
    3. Define the decision each meeting must produce. If a meeting can’t point to a decision it’s supposed to make, cancel it or replace it with an async update.
    4. Set the required data packet. Each meeting should have a standard set of metrics and context prepared in advance.
    5. Name an owner for every action item. Every decision needs a name and a due date before the meeting ends.
    6. Review the cadence itself once a quarter. Check whether each meeting is still earning its spot on the calendar.

    A simple audit helps with step three. For each recurring meeting, ask three things: did it produce a decision in the last month, could the same information have gone out as a written update, and would anyone notice if it disappeared? Keep what passes, merge what overlaps, and cut what fails all three.

    If you’re still mapping out what RevOps owns across these layers, our guide on what RevOps is is a good starting point before you build out a full cadence.

    Mistakes to avoid

    • Reviewing exported spreadsheets instead of the live CRM, which teaches the team the system is optional.
    • Letting the agenda change every week, which turns reviews into status updates.
    • Mixing layers, such as redesigning territories in the weekly pipeline call.
    • Skipping the quarterly review when the quarter gets busy.
    • Leaving decisions without owners and dates, so the same issue returns next week.
    • Never auditing the cadence itself, so meetings outlive their purpose.

    Summary

    A RevOps meeting cadence is a layered set of weekly, monthly, and quarterly reviews, each with one job. Weekly meetings answer what needs action now, using live CRM data and a fixed agenda. Monthly meetings explain trends and produce resourcing, pricing, or process decisions. Quarterly reviews test whether territories, headcount, and the operating model still fit.

    To build one, map your current meetings, assign each to a layer, define the decision it must produce, prepare a standard data packet, and name an owner and date for every action. Keep a decision log, route off-topic items to the right layer, skip nothing at the quarterly level, and audit the cadence itself every quarter. The goal is leaders spending less time reconciling and more time deciding.

    FAQ

    How many RevOps meetings should a revenue team actually run?

    It depends on team size and maturity, but a reasonable baseline is one weekly pipeline review per sales team, one monthly commercial review at the leadership level, and one quarterly business review across the full revenue organization.

    What’s the difference between a weekly pipeline review and a QBR?

    A weekly pipeline review looks at what’s moving right now and flags deals that need attention this week. A QBR looks back across the full quarter and asks whether the strategy, territory plan, or capacity needs to change.

    Who should own the RevOps meeting cadence?

    RevOps should govern the rhythm, including the agenda structure, data packets, and follow-up log, while functional leaders in sales, marketing, and customer success own performance in their areas. RevOps keeps the system honest. It doesn’t replace the leaders who run it.

    How long should a QBR run?

    There’s no universal figure, but 60 to 90 minutes works for many teams, with the data packet shared in advance. Executive-level reviews often run shorter than rep-level ones because they focus on decisions and portfolio rollups.

    What happens if we skip the quarterly review?

    You lose the one checkpoint built to catch operating-model problems before they compound. Teams that skip it tend to find out about a broken process or outdated territory plan the hard way, usually during a bigger and more painful rebuild later.

    Can some of these meetings be async?

    Yes. If a meeting exists mainly to share numbers and doesn’t need a live decision, a written update with a short comment window often does the job. Save live time for decisions, disagreements, and escalations.

    What should be in the data packet?

    A fixed set of governed metrics for that layer, a short list of exceptions or anomalies, and last period’s open action items. Prepare it before the meeting so the time goes to decisions instead of assembling numbers.

  • What Is a Customer Journey Map? A Beginner’s Guide

    A customer journey map is a visual tool that lays out every step, touchpoint, and emotion a prospect or customer experiences while interacting with your business, from the moment they realize they have a problem through purchase, onboarding, and renewal. B2B teams use it to spot friction and align marketing, sales, and support around the same story.

    If you’ve ever sat in a meeting where marketing, sales, and customer success each described “the customer experience” differently, you already know why this matters. Everyone’s looking at the same buyer, but through a different window.

    A journey map puts all those windows in one room. It’s not a fancy design exercise. It’s a working document that shows you where deals stall, where support tickets spike, and where you’re quietly losing people who should have converted.

    What Is a Customer Journey Map, Exactly?

    At its simplest, a customer journey map is a visual representation of every experience a customer has with your brand, product, or service. It captures the touchpoints, emotions, and pain points a buyer runs into at each stage of their relationship with you, not just the moments when they’re actively buying.

    Think of it as a timeline with texture. Instead of just listing “visits website, books demo, signs contract,” a good map also notes what that person was thinking and feeling at each step, and which channel or team they interacted with to get there.

    That’s different from a workflow map, which documents the steps a customer takes to accomplish one specific goal. A full customer journey map covers the whole relationship, including what happens after the contract is signed.

    Customer Journey Map vs. Buyer Journey Map: What’s the Difference?

    People use these terms interchangeably, and that causes confusion. A buyer journey map visualizes the steps a customer goes through as they move toward a purchase decision. A customer journey map is broader: it covers the full lifecycle, including what happens after the deal closes, like onboarding, renewal conversations, and advocacy.

    If your team only maps the path to closed-won, you’re missing half the picture. Churn, expansion, and referrals all happen on the other half.

    Tool What it shows Best used for
    Buyer persona Who the customer is: role, goals, concerns Deciding who you’re mapping
    Buyer journey map Steps toward a purchase decision Improving marketing and sales
    Customer journey map The full relationship, from awareness through renewal and advocacy Aligning marketing, sales, onboarding, and support
    Sales funnel Conversion rates between stages Measuring volume and drop-off

    A sales funnel tells you what happened: 100 leads in, 10 deals out. A journey map tells you why, by showing the actions, thoughts, and friction points behind each stage, including the parts that happen before someone enters your funnel and after they leave it.

    Why Does a Customer Journey Map Matter for B2B Teams?

    Here’s the problem most B2B companies run into: their buyer isn’t one person. Gartner has put the typical buying group for a complex B2B solution at six to ten decision-makers, and Forrester’s 2026 research counted even more stakeholders when you include everyone who influences the decision. The exact number depends on how you count, but the direction is consistent. Each person arrives with their own research, priorities, and concerns, and a journey map forces you to account for that instead of designing everything around one imaginary buyer.

    Mapping the journey also surfaces blind spots. Picture a support team that keeps getting the same confused calls right after a customer signs up. Without a map connecting “signed contract” to “first support call” to “what the customer was actually trying to do,” that pattern is easy to miss. It just looks like noise. A journey map turns that noise into a traceable gap you can fix.

    Honestly, most of the “we have a leaky funnel” conversations we see at Revlyn aren’t a lead-volume problem. They’re a journey-mapping problem: nobody has documented what happens to a prospect between MQL and signed contract, so nobody can point to where they’re dropping off.

    What Stages Does a B2B Customer Journey Map Usually Include?

    Most B2B journey maps use some version of these stages, though you should adjust them to fit your actual sales motion. For each, document the buyer’s goal, the question they’re asking, the touchpoints they use, and the team that owns them.

    Stage Buyer’s goal Typical question Common touchpoints Owner
    Awareness Understand the problem “Is this worth solving?” Search, content, peers, events Marketing
    Consideration Compare options “Who does this well, and for companies like us?” Website, reviews, comparison pages Marketing and sales
    Decision Get internal buy-in “Is it safe, affordable, and worth the switch?” Demos, proposals, security reviews Sales
    Purchase Sign and set up “What happens next?” Contract, invoicing, kickoff Sales and finance
    Onboarding and use Reach first value “How fast can we get this live?” Setup calls, in-app guides, support Customer success
    Retention and advocacy Confirm value, grow, recommend “Did we get what we paid for?” Reviews, renewal talks, referrals Customer success and sales

    This is also where your market segmentation pays off, because a VP of Finance and a procurement manager will have very different questions at the exact same stage.

    What a Finished Map Looks Like

    Here’s a condensed, made-up example for a B2B reporting tool, showing how a map moves from observation to fix.

    Stage What the buyer does What they ask or feel Friction found Possible fix
    Consideration Compares three vendors and reads the pricing page “Will this fit our data setup?” Pricing page doesn’t mention integrations Add an integrations section and a short comparison guide
    Decision Brings in IT and finance for sign-off “Is it secure? What’s the total cost?” The security questionnaire takes two weeks Publish a security overview and a ready answer pack
    Onboarding An admin connects data sources “How fast can we get this live?” Many first-week tickets ask about one connector Add an in-app guide and a setup checklist
    Renewal Reviews usage before renewing “Did we get value?” The champion left and nobody uses the dashboard Schedule 90-day check-ins and train a second owner

    Each fix is small and specific. That’s the point. The map’s job is to turn “something feels off” into a short list of concrete changes with owners.

    How Do You Build Your First Customer Journey Map?

    You don’t need design software or a six-week project plan to get started. Here’s a simple checklist:

    1. Pick one segment or persona. Don’t try to map every buyer type at once. Start with your most common or highest-value customer segment.
    2. List the stages your buyer actually goes through, using the six above as a starting point.
    3. Gather evidence from real sources: support tickets, sales call notes, CRM stage timestamps, win-loss and churn reasons, and a handful of direct customer interviews.
    4. Map touchpoints to each stage (website, email, demo call, onboarding call, support ticket).
    5. Note the emotion or question the buyer has at each stage (“Is this worth the switching cost?” or “How fast can we get this live?”).
    6. Flag the friction points where customers get stuck, confused, or drop off.
    7. Assign an owner to each stage so someone is responsible for fixing the gaps you find.

    Pro tip: don’t skip the indirect touchpoints. Word-of-mouth mentions, industry event conversations, and peer recommendations shape a B2B buyer’s decision just as much as your website does, and they’re easy to leave off a first draft.

    If you’re mapping the journey for a brand-new product, pair this work with a proper go-to-market launch plan, since your messaging and channel choices at each stage should flow from the same research. And if you’re exploring a self-serve or free-trial model, look at how the journey shifts under different GTM motions, including product-led growth, where the product itself becomes the main touchpoint instead of a sales rep.

    Connect the Map to Metrics

    A map nobody measures against becomes a poster. Choose one metric per stage so you can tell whether a fix worked.

    Stage Example metric
    Awareness Engagement among target accounts, branded search
    Consideration Demo or contact requests from the target segment
    Decision Win rate and sales cycle length
    Purchase Days from closed-won to first invoice
    Onboarding Time to first value, early support tickets per account
    Retention and advocacy Renewal rate, net revenue retention, referrals

    Many of these come straight from your CRM. HubSpot’s lifecycle stage date stamps show how long contacts spend between stages, and closed-loop reporting connects those stages back to the sources that produced revenue.

    Mistakes to Avoid

    • Mapping from inside the building. A map built from internal assumptions shows how you wish customers behaved.
    • Stopping at the signature. Onboarding, renewal, and expansion are where much of the revenue risk sits.
    • Mapping every persona at once. Start with one segment and add others once the first is useful.
    • Treating one buyer as the whole account. B2B purchases involve groups, so note who else gets involved at each stage.
    • Producing a poster and nothing else. Without owners, fixes, and metrics, it won’t change anything.

    Summary

    A customer journey map is a visual document of every touchpoint, question, and friction point a buyer meets from first awareness through purchase, onboarding, renewal, and advocacy. It’s broader than a buyer journey map, which stops at the purchase decision, and it explains the why behind the numbers a sales funnel only counts. For B2B teams, where buying groups often include six to ten or more people, it keeps marketing, sales, and customer success working from the same story.

    To build one, pick one segment, list the stages, gather evidence from tickets, calls, and customers, map touchpoints and questions, flag friction, and give every stage an owner. Then attach a metric to each stage and review the map when your product, process, or buyers change. A short list of specific fixes beats a beautiful poster.

    FAQ

    Is a customer journey map the same as a buyer persona?

    No. A persona describes who your customer is. A journey map describes what they do and feel as they move through stages with your company. You typically need personas first, then build a map for each one.

    How often should we update our journey map?

    Treat it as a living document, not a one-time project. Revisit it whenever you launch a new product, change your sales process, or notice a shift in how customers are buying.

    Do small B2B companies really need a formal journey map, or is this just for enterprise teams?

    Small teams arguably need it more. You have less room for a bad onboarding experience to go unnoticed, and a simple map can take an afternoon to sketch out.

    What’s the difference between a current-state map and a future-state map?

    A current-state map documents how customers experience your business today, including the rough spots. A future-state map sketches the experience you’re designing toward. Most teams start with current-state, since it gives you a baseline to improve from.

    What tools do people actually use to build these?

    Plenty of teams start with a whiteboard, a spreadsheet, or sticky notes on a wall. Dedicated mapping tools exist too, but the format matters far less than talking to customers before you draw anything.

    How many customers should we interview?

    There’s no fixed number, but a handful from your target segment, mixing recent wins, long-term customers, and a churned account or two, usually surfaces the main patterns. Combine interviews with support tickets and CRM data so you’re not relying on a few voices.

    Who should own the journey map?

    Often RevOps or product marketing, because the map crosses teams. Each stage should still have its own owner responsible for fixing the friction found there.

  • Demand Generation vs. Lead Generation: Key Differences

    If you’ve ever sat in a marketing planning meeting and heard someone say “we need more demand gen” right after someone else said “we need more leads,” you’ve probably wondered if those are actually two different things. They are. And mixing them up is one of the quickest ways to waste a marketing budget.

    Demand generation builds awareness and interest in your product before someone is ready to buy, while lead generation captures contact information from people who’ve already shown that interest. One creates the market, the other harvests it. You need both, but they’re not interchangeable, and they’re measured completely differently.

    Let’s break down what each one actually means, why founders and revenue leaders mix them up so often, and how to figure out where your team should be spending its energy right now.

    What is demand generation?

    Demand generation is the set of marketing activities aimed at making your target market aware that a problem exists and that your company has a credible way to solve it. It’s not about collecting a name and email address. It’s about getting someone who’s never heard of you to start recognizing your brand as relevant to a problem they have.

    This usually happens through ungated content (meaning no form fill required), social posts, podcasts, webinars, SEO, and PR. A useful way to think about demand gen: it’s the work that happens before anyone is ready to talk to sales.

    There’s a well-known heuristic in B2B marketing called the 95:5 rule. Professor John Dawes of the Ehrenberg-Bass Institute described it in a paper published by LinkedIn’s B2B Institute in 2021, and it says that only about 5% of potential B2B buyers are in the market at any given time. The other 95% either don’t know they have the problem yet or aren’t ready to act. Demand generation exists to educate and stay visible to that larger group, so that when they do become ready, your company is the one they think of first.

    That’s a slow burn by design. Demand generation compounds over time instead of delivering an instant spike in pipeline, which is exactly why it’s so often the first budget line cut when a quarter gets tight. Its payoff shows up months later, and that makes it hard to defend in a spreadsheet built around this quarter’s numbers.

    Honestly, that’s a mistake I see founders make constantly. They treat demand gen like a nice-to-have instead of the thing that makes lead gen cheaper and more effective down the line.

    What is lead generation?

    Lead generation is the process of collecting contact information from prospects who’ve already shown interest, so your sales team has someone to follow up with. This is the gated e-book, the demo request form, the webinar sign-up, the “book a meeting” button.

    Where demand gen asks “how do we make our market smarter about this problem,” lead gen asks a narrower question: “how do we capture the people who are ready to talk right now?” It’s a conversion mechanism, not an awareness mechanism.

    Lead generation is measurable in a way demand gen often isn’t. You can count form fills, calculate cost per lead, and track conversion rates in a dashboard by Friday afternoon. That immediacy is exactly why lead gen tends to get more budget love in cash-strapped early-stage companies: it’s easier to defend because the numbers show up fast.

    But here’s the catch. Lead generation can only capture demand that already exists. If nobody in your market knows your category exists or cares about the problem you solve, there’s nothing for your lead-gen forms to harvest, no matter how good your landing pages are.

    Demand generation vs. lead generation at a glance

    Demand generation Lead generation
    Goal Build awareness and interest in the problem and your brand Capture contact details from interested people
    Audience The whole target market, mostly not ready to buy People already showing interest
    Typical tactics SEO, podcasts, social, PR, webinars, ungated guides Gated assets, demo requests, landing pages, retargeting
    Gated or ungated Mostly ungated Usually gated
    Key metrics Reach among your target accounts, engagement, branded search, direct traffic Form conversion, cost per lead, lead-to-meeting rate
    Time to results Months Days to weeks
    Main risk Hard to attribute, easy to cut High volume, low quality when no demand exists

    Why the “5% in market” figure shifts by category

    Treat 95:5 as a mental model, not a law. Dawes himself describes it as a heuristic, and the share of buyers in the market depends on how often your category gets re-evaluated. A rough way to estimate it: divide the time window by the average time between purchases.

    Buyer re-evaluates the category every Share in market in a given quarter
    1 year 25%
    2 years 12.5%
    3 years About 8%
    5 years 5%
    10 years 2.5%

    These are simple illustrations using a three-month window. Plug in your own customers’ replacement cycle and you get a rough sense of how much of your market a lead-gen form could ever reach at once. Some intent-data vendors argue that modern signals reveal more in-market buyers than the 5% figure suggests, so test it against your own data instead of taking any number as given. The practical point holds either way: in most B2B categories, the majority of your market isn’t ready today.

    Why does the difference actually matter?

    If you fund lead generation without any demand generation underneath it, you end up buying ads and running gated campaigns against an audience that doesn’t understand what you do or why it matters. That typically shows up as high volume, low quality: lots of form fills, very few that turn into real sales conversations.

    If you fund demand generation without any lead capture mechanism, you build awareness that never gets converted into pipeline. You’re educating the market and then letting prospects wander off to a competitor with a better call to action.

    The two strategies are sequential, not competing. Demand generation fills the top of the funnel with people who understand your category and trust your brand. Lead generation then narrows that wider group to the people most likely to buy right now. Skip one, and the other works a lot harder for a lot less.

    This is also where positioning and segmentation come in. You can’t run effective demand generation without a clear point of view on who you’re talking to and why your solution matters to them. That’s why market segmentation and a clear value proposition come before any campaign spend, and why sharp positioning is what makes your demand gen content land instead of blending into the noise.

    Symptoms that point to the gap

    What you’re seeing Likely gap First thing to check
    Plenty of form fills, few meetings Demand or targeting Whether the audience matches your ideal customer profile
    Good awareness, weak conversion Lead capture Offers, calls to action, and form friction
    Sales says leads are poor Demand upstream, or qualification Source mix and what happens between lead and meeting
    Paid results rise while branded search stays flat Little demand is being created Whether any ungated, educational content is working
    Long sales cycles with confused buyers Category education Whether prospects understand the problem before the first call

    How to measure each without mixing them up

    The most common measurement mistake is judging demand generation by the same dashboard as lead generation. Last-click form fills will always favor lead gen, because that’s where the click happens. A fairer approach uses different measures for each, and then connects both to revenue.

    • For demand generation: reach among your target accounts, engagement on ungated content, branded search volume, direct and organic traffic trends, and the answers prospects give when asked “how did you hear about us?”
    • For lead generation: form conversion rate, cost per lead, lead-to-meeting rate, and meeting-to-opportunity rate.
    • For both: pipeline and revenue by source, which is where closed-loop reporting comes in, so you can see which activities lead to paying customers and not just clicks.

    Self-reported attribution is worth adding to every form. People often can’t trace a purchase to a click, but they can tell you they heard you on a podcast or saw a colleague share your guide. That context rarely shows up in a click path.

    A quick checklist to figure out where to invest first

    1. Audit your pipeline source. If most of your “leads” are low-quality form fills that never book a call, you likely have a demand problem, not a lead-capture problem.
    2. Check your brand recognition. If prospects have never heard of you before a sales rep cold-calls them, lead gen tactics alone won’t fix that.
    3. Look at your sales cycle length. Long, confusing sales cycles often mean buyers don’t understand your category yet, which is a demand gen gap.
    4. Match the tactic to the funnel stage. Use ungated, educational content for awareness-stage prospects, and gated, specific offers for people already comparing solutions.
    5. Set separate metrics for each. Track reach, engagement, and brand lift for demand gen, and form fills, cost per lead, and conversion rate for lead gen. Mixing the two hides which one is underperforming.

    Pro tip: if your sales team keeps complaining that “marketing leads are garbage,” don’t rush to fix the lead forms first. Check whether there’s any real demand generation happening upstream. Most lead-quality complaints are demand problems wearing a lead-gen costume.

    Mistakes to avoid

    • Gating everything, which turns demand generation into a lead-capture exercise and shrinks the audience you reach
    • Cutting demand generation first when budgets tighten, then wondering why lead costs rise
    • Comparing the two on the same metrics and concluding that demand gen “doesn’t work”
    • Running demand generation with no clear audience or message
    • Building awareness with no visible next step for people who are ready to talk

    Summary

    Demand generation builds awareness and interest before buyers are ready, mostly through ungated content, and pays off over months. Lead generation captures contact details from people who have already shown interest, mostly through gated offers, and shows results within days or weeks. They work in sequence: demand generation creates the audience that lead generation converts, which is why funding only one produces either low-quality leads or awareness that never turns into pipeline.

    The 95:5 heuristic from Ehrenberg-Bass says only a small share of B2B buyers are in the market at once, and that share depends on how often your category is re-evaluated. Measure the two separately, then connect both to revenue with closed-loop reporting. If you’re deciding where to invest first, check your pipeline sources, brand recognition, and sales cycle length, and don’t blame lead forms for a demand problem.

    FAQ

    Is demand generation the same as brand awareness?

    Not exactly, though they overlap. Brand awareness is one outcome of demand generation, but demand gen also includes educating the market about a problem and positioning your company as the solution, not just making your logo recognizable.

    Which should a small B2B team prioritize first, demand gen or lead gen?

    It depends on where you already stand. If your market has no idea your category exists, lead gen tactics alone won’t save you, and you need demand generation first. If you already have decent brand recognition but a leaky conversion process, lean into lead gen.

    Can one person run both demand gen and lead gen?

    At an early-stage company, yes, often the same marketer wears both hats. Keep the goals and metrics separate even if the person is the same, so you know which lever you’re pulling.

    Do demand gen and lead gen use different content?

    Generally yes. Demand gen tends to rely on ungated, educational content like blog posts, podcasts, and social content. Lead gen typically uses gated assets like e-books, webinar registrations, or demo requests, where a prospect trades contact details for something valuable.

    How long does demand generation take to show results?

    There’s no universal timeline, but it’s consistently described as a longer-term play than lead generation, since it compounds awareness and trust over months rather than producing an immediate spike in form fills.

    Is the 95:5 rule a hard rule?

    No. It’s a heuristic. The share of buyers in the market at a given moment depends on how often your customers re-evaluate the category, so estimate it for your own market instead of assuming 5%.

    How do I prove demand generation is working?

    Track leading signals like branded search, direct traffic, engagement among target accounts, and self-reported attribution, then tie pipeline and revenue back to source. Expect the evidence to build over months, not weeks.