You know the meeting.
Somebody pulls up a dashboard. Marketing has a number, and it’s up. Sales looks at the number the way you’d look at a receipt for something you don’t remember buying. Then somebody says either “the leads are junk” or “sales isn’t working them,” depending on who talks first.
Everyone else in the room studies their laptop.
I’ve sat in a lot of these. They’re remarkably consistent, which is the first interesting thing: different companies, different industries, different tools, same script. Two frustrated teams, each assuming the other one is being either lazy or willfully blind.
Here’s the ruling: they’re both right.
That’s not me being diplomatic. It’s the actual finding, and it’s the reason the fight never ends. Two teams describing two different things, both accurately, will argue forever, because neither one is ever wrong enough to lose.
But “you’re both right” is only useful if you can name why. In our work, it comes down to one of three things, and they look identical from across a conference table.
Marketing's testimony
Marketing has a rule. Maybe it’s a score, a form submission, a demo request, or a lifecycle stage that flips when a few conditions are met. Wherever it lives, the information is in a document somewhere on the company drive, applied the same way every time, and produces a number at month-end.
So when marketing says “we sent 140 qualified leads,” that’s accurate. One hundred forty records met the criteria. Marketing can show you the criteria and the 140.
Leadership measures Marketing on that number, which matters more than people admit. When your evaluation is based on volume against a threshold, you’ll optimize for volume against a threshold. (That’s not cynicism. That’s what happens to any human being with a goal.)
But meeting the rule doesn’t mean the rule predicts revenue. It only means the rule was followed.
Sales' testimony
Sales has a judgment. It’s usually not written down anywhere. It lives in the heads of people who’ve made thousands of calls and can tell you pretty quickly whether this one goes anywhere.
Sales isn’t applying the marketing team's criteria. Instead, Sales applies a test that includes things Marketing may never have asked about:
- Is the company the right size to buy our product/service?
- Can this person move a decision, or are they researching for someone who can?
- Does the timing seem real?
- Have the last four leads from this source gone nowhere?
So when sales says, “these are junk,” that’s also accurate. However, they are applying a different test.
Leadership measures Sales on closed revenue, which means every hour spent on a lead that doesn’t convert feels like an hour stolen from one that might. Reps aren’t refusing to call out of spite. They’re triaging, with incomplete information, under a number.
But experience isn’t proof. Sales judgment is genuinely valuable, but it also brings old assumptions about which industries, company types, and buyers are worth the phone call. Sometimes those assumptions are three years out of date, and nobody’s checked.
So which of the three is it?
Alignment doesn’t start with making one side accept the other’s version. It starts with naming which problem you actually have.
- A visibility problem. The lead or the engagement signal exists, but sales can’t see it in the system where they work.
- A definition problem. Both teams use a different test for what “ready for sales” means.
- A compliance problem. Both teams share a good definition, and people aren’t following it.
Three different problems, three completely different fixes, and they all sound the same in a status meeting.
More coaching isn’t the answer. Training doesn’t make a missing record appear in a rep’s queue. A stricter SLA won’t help if the definition is wrong. And if the agreement is sound and people ignore it, another workshop won’t substitute for management enforcing the process.
Yet compliance is the default diagnosis—every time. Now, you have lots of fun at a Tuesday standup with sales and marketing teams eye-rolling and internally seething because the other side still "doesn't get it right."
None of it resolves anything, because you can’t manage your way out of a disagreement about what a word means.
Sometimes the leads aren’t where sales can see them.
We’ve walked into engagements where a rep was certain that marketing had never generated a single piece of inbound interest for the market he covered. Not “not enough.” None.
He was partly right, which is the interesting part. Prospects in that market were engaging. However, the original integrators configured the HubSpot-to-Salesforce integration to sync only certain actions, so real buying signals sat in HubSpot, invisible to a sales team living in Salesforce.
Marketing thought it was generating engagement. Sales thought no engagement existed. Both teams were describing the evidence in front of them, accurately, and both descriptions were incomplete.
That was never a lead-quality argument. It was a visibility problem created by how the systems were wired, and no amount of accountability talk would fix it.
We’ve seen other versions. In one company, sales cherry-picked what marketing sent because reps had an unwritten conviction that an emerging segment was a bad fit. The segment turned out to have real potential, and the assumption kept those leads from getting a fair shot. In another case, sales held planning sessions about ideal customer profiles and personas while marketing worked from an entirely different set. Both groups were making rational decisions based on definitions they'd never reconciled.
Once the competing rules and the missing data were on the table, the argument stopped being mysterious. Now, that didn’t necessarily solve all the problems. Leadership from each team still has to work together to ensure there is an agreed-upon standard set of personas, ICPs, and lead handoff criteria. Then, those need to be operationalized in the system and documented.
(This is a cousin of the handoff failure Alanna wrote about in Sales and Marketing Handoffs: Two Gaps That Cost You Revenue. Sometimes nobody dropped it. Nobody was holding it.)
Four questions to tell them apart
Ask yourself these questions this week. Your team can do this exercise now. No consultant required.
1. Can sales actually see what marketing thinks it’s sending?
Don’t compare totals on two dashboards. Take a handful of real records and trace them from the marketing activity through the integration, the routing rules, the assignment, the notification, and into the rep’s queue.
Then, dig in to discover what the rep can actually see when follow-up was expected. Watch for nooks and crannies where leads may fall through the cracks: separate product lines, territories, or business units with their own ownership rules. That’s where records go quiet.
If marketing can see engagement that never reaches the right salesperson, you’ve got a visibility problem.
2. How does each team define “ready for sales”?
Ask both sides separately, in writing, without conferring.
Don't ask this question in a meeting. In a meeting, you’ll get a negotiated answer, and that’s worse than useless because it hides the mismatch between the two teams. Send two messages, get two documents, put them side by side.
Also, don't get hung up on MQL and SQL labels (yet). Remember, those lifecycle stages are containers for criteria, not the definitions themselves. Ask each team what fit criteria, behaviors, exclusions, and buying signals they actually care about.
If the two answers don’t match, you’ve got a definition problem, and everything downstream amplifies the mismatch.
3. Is the agreement being followed?
If both teams agree on lead definitions and handoff criteria, check whether routing rules are implemented correctly.
Look at response times, rejection reasons, and what happens to a lead that gets sent back. Then ask whether conversion actually improved the last time leadership pushed for better follow-up, or whether activity went up while outcomes stayed flat. If effort didn’t move the number, effort isn’t the variable. Stop pulling that lever.
4. Which criteria does the revenue data support?
If only team agreement were all it takes to make your handoff process work well. Agreement doesn't make a definition correct. Both teams can shake hands on criteria that don’t predict a single purchase.
Compare the criteria against other data like opportunity creation, conversion rates, disqualification reasons, and closed-won revenue. Maybe Marketing has a process that rewards behavior that doesn’t lead anywhere. Or Sales may be rejecting leads that convert later, or writing off a segment because it doesn’t look like the customers you’ve always had.
And don’t pretend the data is cleaner than it is. In many companies, incomplete dispositions, inconsistent lifecycle stages, selective syncing, and thin attribution limit what anyone can actually prove. Those limitations are findings, too. They tell you what must be fixed before you can evaluate lead quality.
The CRM doesn’t own the definition.
Ask who owns the sentence that says what qualified means.
You’ll usually get a pause, then some version of “well, it’s in HubSpot.” (Which is a beautiful answer, because it’s true and it’s not an answer.)
The software is faithfully enforcing a rule somebody configured, possibly during onboarding, possibly years ago, possibly before you changed your products, your markets, or the way you sell.
HubSpot’s own documentation is clear about the division of labor. The lifecycle stage property shows where a contact sits and supports the handoff between marketing and sales. The platform gives you the fields, automation, routing, and reporting. It doesn’t decide what qualified should mean for your business. That part was always yours.
Worth knowing: by default, automatic lifecycle updates only move a record forward. So a stage that got set too generously four years ago has been quietly collecting questionable records ever since. Yikes.
What this is actually costing you
Misalignment costs the average B2B company some dramatic percentage of revenue. That’s the kind of sentence that makes everyone nod and change nothing.
Here’s the version you probably recognize.
You spend Monday defending a number instead of making process revisions that move numbers in the right direction. Your QBR has two funnels in it; everybody in the room can see they don’t reconcile, and the meeting becomes about the discrepancy instead of the business.
When you ask for budget, you get told to prove the leads are good first. You can’t, because the measure of “good” is the exact thing in dispute, or the data is incomplete, or both.
And here’s the part nobody says out loud: an unresolved fight makes both functions look less credible to the executive who owns the number. Not because either team is wrong. Because from one level up, a permanent argument between two departments looks like nobody’s in charge of the outcome. You’re being evaluated on a problem you can’t solve by yourself, with authority you don’t have.
And that executive isn't wrong to read it that way. Both teams are accurately reporting their own numbers, and the company is still losing deals it should be winning. Being right about your own metric while the business goes sideways isn't a tie. It means the argument has been allowed to stand in for somebody answering to the number that actually matters.
The part that isn’t a whiteboard afternoon
Writing a shared definition sounds easy. It sounds like a two-hour session and a Google Doc.
The session is real. It isn’t the hard part.
The hard part is that the definition has to match how your business actually sells, and plenty of businesses sell in a shape that resists one clean rule. You might have a deal where the end user works at one company, the contract goes through a distributor, and a broker touched it in the middle. You might have three products with three different buyers and three different cycles all pouring into one funnel. The real qualifier might be something nobody has ever put in a field, like whether they’ve had the internal budget conversation yet.
If a definition doesn’t jibe with sales reality, you didn't fix anything.
A useful agreement covers more than a label. It says what counts as fit and buying intent, what disqualifies somebody, who owns the record and how fast they’re expected to touch it, what happens when a lead gets sent back, and how you’ll check the criteria against revenue later. (That last one is the piece almost everybody skips, which is how a good definition slowly becomes a wrong one.)
Then the system has to enforce it. Skip that part, and you'll have two definitions again by next quarter.
Somebody has to build the agreement into the lifecycle logic, the scoring, the sync rules, and the routing, then into the views and reports both teams actually look at. And it has to hold when a key person leaves, or when somebody bulk-edits 400 records on a Thursday afternoon. (It's always a Thursday afternoon.)
When this isn't an alignment problem
There's a version of this where the systems are fine, and the people aren't. Sales can see everything. Both teams work from the same definition. And a couple of reps still aren't touching their queues.
That's a management conversation. Have it. I'd rather tell you that than sell you something.
A working handoff doesn't mean the rest of your portal is in good shape, though. We've walked into instances where leads moved between teams exactly as they were supposed to, and the reporting still couldn't be trusted because two workflows had been quietly overwriting each other for a year. That's a different problem, and it's the kind that hides.
If leadership wants somebody brought in to declare a winner and vindicate one side, we’re the wrong call. That’s not alignment; that’s hiring a witness, and it usually makes things worse.
And if the stakeholders who understand how the business actually sells can’t be in the room, nobody can build an accurate qualification model. We’re not going to guess at it. Same goes for scope: if only one team engages us, we can find the gaps and fix what that team controls, but we can’t manufacture agreement from people who aren’t at the table. If Salesforce or another system belongs to a different partner or department, we can document what needs to change and work alongside them, but we won’t promise changes we can’t access.
If you don’t know which problem you have
Start with the four questions. Do that part yourself. It costs you nothing, and it might settle the whole thing without us.
If it doesn't, that's where we come in. We diagnose whether the breakdown is visibility, definitions, compliance, or a combination; help facilitate the agreement when the right people are in the room; and then build it into HubSpot as fields, automation, routing, and reporting so it actually holds.
There's a second thing that tends to happen when you get to question four, though. You go looking for proof that your criteria predict revenue, and you find out you can't answer the question yet. Dispositions are half-filled. Lifecycle stages mean three different things depending on who set them up and when. A sync has been dropping records that nobody knew about.
Those are findings. They're also a to-do list, and it's the kind of work we'd be doing for you whether or not anybody ever argued about lead quality.
So if the four questions point you toward a management conversation, go have that conversation. If they point you toward a portal that's been quietly telling you things that aren't true, that's a different conversation, and we're around for that one.
It usually starts with 30 minutes about which fight you're having, which is not the same thing as a pitch.
Book a call. Real humans, no deck.
Frequently Asked Questions
Usually because the two teams are applying different tests to the same records, or because sales cannot see everything marketing sees. Marketing applies a documented rule and can show every record that met it. Sales applies an unwritten judgment built from experience, which often includes factors the rule never asked about, like company size, signing authority, or timing. In some cases, leads and engagement signals never reach the rep's queue because of how system integrations or routing processes work. The first step is determining whether the conflict comes from visibility, conflicting definitions, or an agreement nobody is following.
A definition problem exists when sales and marketing do not agree on what qualified or ready for sales means. A compliance problem exists when both teams share a valid definition and process and people are not following it. The first requires a shared definition tested against revenue outcomes. The second requires management and accountability. Diagnosing a definition problem as a compliance problem is the most common mistake, and it is why more training and better dashboards rarely change anything.
Integration and routing rules determine which records and activities move between a marketing platform and a CRM. If engagement signals do not sync or records route incorrectly, marketing can believe it is generating demand that sales genuinely cannot see. Both teams then reach different conclusions from the information available in their own system, and the disagreement looks like a lead-quality argument when it is actually a data-visibility one.
Compare the criteria against opportunity creation, conversion rates, sales velocity, disqualification reasons, and closed-won revenue. Agreement between teams matters, but you should also test the definition against business outcomes and revise it as markets, products, and buying behavior change. Where incomplete dispositions or weak attribution limit what you can prove, those gaps are findings in their own right.


