Why Your Sales and Marketing Numbers Don't Match (and how to fix it)
Updated: 5 days ago
Picture the quarterly review. Marketing reports $2.4M in pipeline. Sales reports $1.6M. Both pull from the same CRM, and both are right by their own rules. When sales and marketing numbers don't match, the cause is usually definitions, dates, data and systems that were never set up to agree.
This post covers the six most common causes, where to check each one, what the gap costs you, and the seven steps to one pipeline number your whole team trusts.
The short answer: Sales and marketing numbers don't match because each team counts pipeline with different definitions, date fields, attribution rules and, often, different systems. Fix the definitions first, then the data, then the reporting. A new dashboard on top of mismatched inputs just shows the disagreement faster.
Why don't sales and marketing numbers match?
Sales and marketing numbers don't match because the two teams measure different things and call them the same name. Marketing often counts pipeline when a lead qualifies or an opportunity is created. Sales often counts open deals at a certain stage, by close date. Add duplicate records and two systems, and the totals split.
In our work with growth-stage SaaS teams, the gap usually comes from a few causes stacked on top of each other, not one big error.
What are the six most common causes?
Cause | What you see | Where to check |
1. Different definitions | Marketing's "pipeline" includes deals sales doesn't count | Your written MQL, SQL and opportunity definitions (if they exist) |
2. Different date fields | Same deals land in different months | The date field each report filters on |
3. Duplicate and unlinked records | Totals inflate, or deals have no source | Duplicate contacts and companies; deals with no associated contact |
4. Lifecycle stage drift | Contacts sit in stages that don't match their deals | Lifecycle stage vs. deal stage on the same records |
5. Different attribution rules | Marketing claims deals sales calls self-sourced | Sourced vs. influenced logic in each report |
6. Two systems, two truths | HubSpot and Salesforce totals differ | Sync settings, field mapping and sync errors |
1. Different definitions
A marketing qualified lead (MQL) is a lead that meets marketing's agreed criteria for sales follow-up. If those criteria live in one person's head, every report interprets them differently. The same goes for "opportunity" and "pipeline." One team counts every created deal. The other counts only deals past discovery.
2. Different date fields
A report filtered by deal create date and one filtered by close date will never agree. Neither will a report using the date a contact became an MQL versus the date the deal was created. Pick one date field for each question you answer, and label it on the report.
3. Duplicate and unlinked records
Duplicate contacts and companies double-count leads and split activity across records. Deals with no associated contact or company break source tracking, so marketing can't get credit and sales can't see history. Both problems grow quietly with every import and integration.
4. Lifecycle stage drift
Lifecycle stages describe where a contact or company sits in your funnel. Deal stages describe where a deal sits in your sales process. When automation moves one and not the other, a contact can show as a "Lead" while its deal is in negotiation. HubSpot's lifecycle stage documentation lists eight default stages, and many teams never adjust them to match how they actually sell.
5. Different attribution rules
Sourced pipeline counts deals marketing created. Influenced pipeline counts deals marketing touched at any point. Both are useful, but they answer different questions. When marketing reports influenced and sales hears sourced, the meeting turns into a debate about whose number is real.
6. Two systems, two truths
Many SaaS teams run marketing in HubSpot and sales in Salesforce. If field mapping, sync rules or record ownership aren't set up carefully, records drift apart. Each system then reports its own version of pipeline, and both teams can point to a screen that proves them right.
What does a pipeline mismatch cost you?
A pipeline mismatch costs you forecast accuracy, budget decisions and leadership time. When the board deck uses one number and the sales forecast uses another, nobody can say with confidence which channels work. Budget ends up following whoever argues best.
The data side has a price too. Poor data quality costs organizations at least $12.9 million a year on average, according to Gartner research. Your number will be smaller than an enterprise's, but the pattern holds: bad inputs create rework, missed follow-up and decisions made on guesses.
Be careful with the alignment statistics that circulate online. Many popular figures, such as "aligned companies generate 208% more revenue," trace back to studies from a decade or more ago, as The Starr Conspiracy points out. Your own pipeline gap is the more useful number.
How do you get one pipeline number everyone trusts?
You get one pipeline number by agreeing on definitions, choosing one system of record, cleaning the data, and only then building shared reporting. The order matters. Teams that start with a new dashboard usually rebuild it within a quarter, because the inputs never changed.
A single source of truth for pipeline is one agreed set of definitions, data and reports that sales, marketing and leadership all use to measure pipeline. Here's how to build it:
Write shared definitions. Define lead, MQL, SQL, opportunity, sourced pipeline and influenced pipeline in one short document. Get sales, marketing and leadership to sign off.
Choose one system of record for each object. Decide which system owns contacts, companies and deals. The other system reads from it.
Clean the data. Merge duplicates, associate deals with contacts and companies, and fill missing source fields. Then set rules that keep it clean.
Tie lifecycle stages to real events. Use automation so a contact's lifecycle stage moves when its deal moves.
Agree on attribution for each question. Use sourced pipeline to judge channels and influenced pipeline to judge marketing's reach. Label every report with the one it uses.
Build one shared dashboard. One dashboard, one date field per metric, and one owner. Retire the side reports.
Review it monthly. Hold a short sales and marketing review of the numbers and the definitions. Update the definitions doc when the business changes.
This is the same order we follow in our Discover, Design, Build, Enable and Optimize approach, which you can read about on our How We Engage page.
How long does it take to fix?
Most teams can agree on definitions in a few working sessions. Data cleanup and system changes take longer and depend on how many records, integrations and teams are involved.
When isn't it a systems problem?
Sometimes the numbers don't match because the teams disagree about strategy. If sales and marketing target different customer profiles or territories, cleaner data will just show that disagreement more clearly. Settle who you sell to and how deals are qualified first. Then the systems work can stick.
Get to one pipeline number
If your sales and marketing numbers don't match, start with a short discovery of your definitions, data and systems. Market Launch Consulting builds the revenue operations infrastructure your GTM runs on, from CRM architecture to shared reporting. See our services, or talk to us about your pipeline.
Frequently Asked Questions:
What is a single source of truth for pipeline?
A single source of truth for pipeline is one agreed set of definitions, data and reports that every team uses to measure pipeline. It usually lives in your CRM, with one owner and one shared dashboard.
Should marketing report sourced or influenced pipeline?
Marketing should report both and label each clearly. Sourced pipeline shows which programs create new deals. Influenced pipeline shows how marketing supports deals already in motion.
Who should own pipeline definitions?
Revenue operations should own pipeline definitions, with sign-off from sales and marketing leaders. If you don't have a RevOps function, assign one leader to own the definitions document and the monthly review.
Can HubSpot and Salesforce report the same pipeline numbers?
Yes, HubSpot and Salesforce can report the same pipeline numbers when one system is the system of record for deals and the sync is mapped field by field. Most mismatches between them come from sync rules, unmapped fields or records that fail to sync.
Do we need a RevOps hire to fix this?
Not always. Many growth-stage teams fix pipeline reporting with a defined project, then hand ownership to an existing leader. A full-time RevOps hire makes sense once the systems and team are large enough to need daily ownership.