I have sat in rooms where sales, marketing, and leadership all stared at the same dashboard and walked away with 3 different stories.
Marketing says volume is up. Sales says the leads are junk. Leadership says pipeline feels soft. Everyone points at the numbers. Almost nobody stops to ask whether the team is using the same definitions in the first place.
(go figure)... I believe that is usually where the argument starts.
In one of my previous in-house roles, we were generating a lot of demand on paper. Anywhere from 3K to 5K leads per month. Think about it… Most teams would die for that volue. The dashboard looked active. The top of funnel looked healthy.
And yet there was still tension around lead quality, conversion, and what was actually working.
The truth was not that the numbers were wrong. The truth was that people were using different meanings for the same stages.
A lead to one person was just a name in the CRM. To someone else, it was only qualified if it looked like our ICP. To sales, it was only worth paying attention to if it was ready to talk now.
That kind of mismatch creates bad conversations fast.
At one point, we realized that for every 100 leads coming in, only about 15 were actually in our ICP. Yea. That’s bad.
So even though one channel was bragging about cheap leads, the business outcome was weak at best.
The lead cost looked great on paper. We were paying $2-3 per lead. However, the downstream conversion did not.
Now, once we got honest about conversions (and revenue), we stopped celebrating the wrong metric.
We then shifted where our ad spend was going. Google Ads was taking roughly 80% of our budget, while Meta only had 20%.
We also tightened the targeting. Instead of ‘everyone’ being our audience, we only focused on SMBs.
Finally, we tightened the definitions of different lead stages.
Now we could actually say… this is a lead, this is an MQL, this is an SQL, this is what counts as real pipeline, and this is when sales owns the next move.
Everything got cleaner after that. Not easier. Cleaner.
Because once everybody was speaking the same language, the numbers started telling a more useful story.
Where The Real Problem Starts
Most teams think they need a better dashboard. Sometimes they do. But a lot of the time, what they really need is shared language.
If sales, marketing, and leadership all define qualified, opportunity, pipeline, or even conversion differently, the dashboard just becomes a prettier version of confusion.
That is why teams keep having the same meeting over and over again.
They are not really arguing about numbers. They are arguing about meanings.
Where To Lock Definitions First
If I were cleaning this up inside your company right now, I would start with simple 5 definitions.
Lead
What counts as a lead in the first place?
Is it any form fill?
Any hand-raiser?
Any contact record with usable data?
This sounds basic, but if the top of funnel is loose, everything downstream gets ugly fast.
In my experience, a lead is anyone with usable data, such as phone number and/or email. If one is real, it’s a lead. If neither is real, they don’t count.
Marketing Qualified Lead (MQL)
What makes a lead qualified enough for marketing to say, “this is worth working”?
In one of my older podcast episodes, I made the point that a lot of companies call leads unqualified when the real issue is that they never built a real follow-up system. That still holds up today.
You need to define qualifications based on real criteria, not frustration.
Sales Qualified Lead (SQL)
What has to happen before sales says, “this is a real opportunity”? (This is where the rubber hits the road.)
A reply?
A conversation?
A confirmed pain point?
Buying intent?
The more explicit this is, the faster you can spot whether the issue is lead quality, follow-up quality, or rep judgment.
Pipeline
What counts in pipeline and when?
Too many teams blur inquiry, lead, meeting, and opportunity together and then wonder why the revenue forecast feels off.
Pipeline should reflect real opportunity value, not just CRM activity.
NOTE: Keep in mind, your pipeline can have different stages with different values at each stage. For example, the Lead Stage can be the ‘full value’ of the potential opportunity, if you closed EVERY lead. Or, it can be a percentage, such as 25%. And, as the lead goes down the stages, the value increases.
Stage Movement
What specifically allows something to move from one stage to the next? These are your ‘triggers’, and these are non-negotiables.
If stage exits are vague, reps improvise, marketing overstates progress, and leadership loses trust in reporting.
Stage criteria protect the integrity of the funnel. Otherwise, you’r back to square one… everyone pointing fingers.
Why This Matters So Much
Once we had cleaner stage math, better things started happening.
We could look at conversion rates from MQL to SQL to customer and actually understand what a change upstream would mean downstream.
If lead quality improved by 10%, that was no longer just a nice idea. We could model the impact. We could see where the drop-off was. We could ask sharper questions.
That is where reporting starts becoming useful. It starts to become predictable.
Not when you add more charts. When you can finally trust what each stage means. And that trust changes behavior.
Sales stops dismissing everything as bad leads. Marketing stops hiding behind surface-level volume. Leadership stops getting pulled into circular debates about whose number is right.
The conversation becomes:
Where is the leak?
What changed?
What does this stage tell us?
What needs to be fixed next?
That is a much better conversation because we’re all speaking the same language.
A Simple Way To Audit This
If your team keeps arguing about numbers, do this:
Write down your definitions for lead, MQL, SQL, opportunity, and pipeline.
Ask sales, marketing, and leadership to define each one separately.
Compare the answers.
Circle anything that is inconsistent, assumed, or vague.
Fix the language before you touch the dashboard.
That one exercise will tell you a lot. Because most reporting problems do not start in the dashboard. They start much earlier, when the business has not agreed on what it is measuring.
And until that gets cleaned up, the team will keep having the same meeting, saying the same things, and walking away with the same frustration.
If this sounds familiar and you want help cleaning it up, reply with PIPELINE or book a GTM audit.
See you next week.
Javy
P.S. — Is there a topic or strategy that you’d like me to unpack? Drop me a line. Let me know what you’re thinking of. And, I’ll get it queued up for an upcoming newsletter.
Guest Podcast Appearance: The Backstory on Marketing and AI

I recently joined Guy Powell on The Backstory on Marketing and AI to talk about something a lot of founders and marketing leaders are feeling right now: AI can speed up a lot, but it does not fix a broken system.
We got into why random acts of marketing are still the enemy, how to find the wedge that is already working before you pile on more channels, and why stage clarity matters so much if you want a pipeline you can actually trust. We also talked about what happens when teams generate a lot of activity without enough structure behind it, how better lifecycle communication can create more hand-raisers, and why I still believe the back end of the funnel is where a lot of revenue gets won or lost.
If you are trying to make AI useful without turning your GTM motion into more noise, this one is worth your time.
Listen on Apple Podcast or watch on YouTube.
Playbook: Dashboards You Can Trust

If your dashboard creates more debate than clarity, the issue usually is not the chart itself. It is the CRM discipline, stage criteria, handoff logic, and shared definitions underneath it.
That is why this playbook is a good fit for this week’s newsletter. It pushes beyond surface-level reporting and gets into the real work of making the numbers trustworthy. When a company has clean definitions for lead stages, consistent ownership between teams, and reporting built around real buying movement instead of admin activity, the dashboard stops feeling political and starts becoming useful.
If your team keeps revisiting the same reporting questions every month, this is worth reading.

