Ask any marketing leader what their job is and they'll tell you: generate pipeline.
Ask any sales leader what their job is and they'll tell you: close pipeline.
Same goal. Same company. Same direction.
So why does the conversation between these two teams so reliably turn into a negotiation about whose fault it is that the number is wrong?
It's not a goals problem. Both teams want revenue. Both teams understand that revenue is the point. The tension isn't about what they're trying to accomplish.
It's about what they mean when they use the same words.
Here's the conversation I've watched play out at more companies than I with I had other admit.
Marketing says leads are up. Sales says the leads are bad. Marketing says conversion rate looks fine in the dashboard. Sales says half those "conversions" never answered a single call. Marketing says SQL volume hit target. Sales says those weren't SQLs.
Both sides have data. Both sides believe their data. And both sides are right — about their own version of the definition.
The problem isn't that marketing is generating the wrong leads or that sales is being too selective. The problem is that nobody ever sat in a room together and agreed on what the words mean.
What is a lead? What makes it qualified? Who decides when it crosses from MQL to SQL — and what has to be true for that to happen? When does a contact become an opportunity? When does an opportunity become a real deal versus a CRM placeholder?
These aren't rhetorical questions. They are the foundation of every funnel metric, every pipeline report, and every forecast your company produces. If marketing and sales are using different answers, every number downstream is measuring something different than you think it is.
Definitions don't get documented at most early-stage companies because nobody thinks they need to.
The first few hires figure it out informally. The sales rep and the marketer sit near each other, talk constantly, and develop a shared working understanding of what they mean. It's inefficient but it works well enough.
Then the team grows. The marketer who had the shared understanding leaves or moves into a different role. The new hire reads the job description, not the tribal knowledge. The sales team adds two more reps who never had the original conversation.
And now you have five people using the same vocabulary to describe five slightly different things — and a funnel report that looks coherent but isn't measuring anything consistently.
The definitions didn't break. They were never written down.
There are dozens of terms that benefit from shared definitions, but these four are the ones that cause the most damage when they're ambiguous.
MQL — Marketing Qualified Lead What specific criteria make a contact an MQL? Is it behavioral (visited pricing page, downloaded a resource), firmographic (company size, industry, job title), or both? Who can designate a contact as an MQL — only marketing, or can sales do it too? What disqualifies one?
SQL — Sales Qualified Lead What has to be true before a contact becomes an SQL? Has a human spoken to them, or is this still score-based? What does "qualified" actually mean — budget confirmed, authority identified, timeline established? Is this a gate or a gradient?
Opportunity When does a contact or lead become an opportunity in the CRM? Is it when a meeting is booked, when a demo happens, when a proposal is requested? This definition directly determines your pipeline accuracy, because every deal that shouldn't be an opportunity inflates your forecast.
Closed Lost This one gets ignored the most. What makes a deal closed lost versus just stalled? Who can mark a deal closed lost — only the rep, or can a manager do it? Is there a required reason field, and are those reasons standardized? Closed lost data is the most underused source of product, pricing, and positioning insight at most companies — and it's only useful if the field means the same thing to everyone who fills it in.
The goal isn't perfect taxonomy. It's shared understanding.
When marketing and sales agree on what an MQL is, marketing stops optimizing for volume and starts optimizing for quality. When the SQL definition is written down and enforced at the handoff, the "these leads are bad" conversation stops happening — because both teams are looking at the same criteria.
When the opportunity definition is clear, pipeline accuracy improves without anyone cleaning the data manually. When closed lost reasons are standardized, you start to see patterns: deals that lose on price cluster in a specific segment, deals that lose to a specific competitor come from a specific channel, deals that stall indefinitely share a common profile.
That's not a reporting win. That's a strategic one.
The companies that grow efficiently aren't the ones where marketing and sales never disagree. They're the ones where marketing and sales disagree about the right things — strategy, messaging, channel mix — rather than burning cycles relitigating what a qualified lead is every quarter.
Schedule one meeting. Not a strategy session. Not a team offsite. One working session where marketing and sales sit down together — ideally with someone neutral facilitating — and write down what they mean.
Start with MQL and SQL. Get specific. Write the criteria. Pressure-test them against real examples from the last 90 days. Find the edge cases and decide how to handle them before they happen again.
Then put the definitions somewhere everyone can find them — not a Google Doc that gets linked once in Slack and never opened again. In the CRM, on the properties themselves, where the person entering the data sees the definition at the moment they need it.
Then revisit them every six months. Not because the definitions will be wrong, but because your business will have changed — and the definitions need to change with it.
Misalignment between marketing and sales is one of the most solvable problems in a revenue system. It doesn't require new technology, new headcount, or a reorganization.
It requires a conversation that most companies have never actually had.
Photo by Brett Jordan on Unsplash