The numbers were in there. The metrics were pulled, formatted, and presented on time. But I wasn't telling anyone what the numbers meant. What had changed, why it mattered, or what we should do differently as a result. I was reporting activity and calling it insight.
I don't think I'm alone in this. It's actually quite a natural place to start. You learn to pull the data, you get comfortable with the tools, and it takes a while to realise that the data on its own isn't the point. The story it's telling is the point.
That shift, from reporting numbers to explaining what they mean, is what this piece is about. What follows is the framework I've landed on. Not as a perfect system, but as a structure that's helped me make that shift in a practical way.
Start with the question, not the metrics
The mistake I made early on was starting with what I could measure and building the report around that. The better approach, which sounds obvious in hindsight, is to start with the question the business is actually asking.
In most B2B companies, that question is some version of: what is marketing contributing to revenue? Everything in the framework should be oriented around answering that, as clearly and honestly as possible.
The five layers
Volume: where are leads coming from and how many?
This is the starting point, not the headline. Volume without context doesn't tell you much, but you need it as the foundation for everything else. Broken down by source, it also starts to tell you which channels are working and which aren't.
Quality: how many are actually the right fit?
This is where a lot of reporting frameworks fall short. Reporting on lead volume without filtering for ICP fit gives you a number that looks good but doesn't tell you anything useful. A hundred leads that don't match your ICP criteria are worth less than ten that do.
Getting this layer right requires a clear ICP definition and a consistent way of applying it, which is harder than it sounds, but worth the effort.
Velocity: how long are they taking to move through the funnel?
Velocity metrics tell you where the friction is. Where are prospects slowing down? Where is the handoff to sales taking too long? Where are deals getting stuck?
These are also often the earliest indicators that something is changing, before it shows up in pipeline numbers. A slowdown in velocity at a specific stage usually means something, whether that's a messaging issue, a process issue, or a shift in the market.
Conversion: where are we losing people, and why?
At each stage of the funnel, what percentage of leads are progressing? Where are the biggest drop-off points?
This layer is where the most actionable insights tend to live. A consistent drop-off at a specific stage usually points to something fixable, whether that's lead quality, messaging, the sales process, or something else. The important thing is to look at it honestly rather than glossing over the numbers that are uncomfortable.
Pipeline and revenue: what did marketing actually generate?
This is the number the business cares most about, and it should be the number the framework is designed to surface clearly. Marketing-generated pipeline, marketing-influenced pipeline, and the revenue contribution of each, reported consistently over time.
I want to be honest here: getting this right is hard, and attribution in B2B is rarely clean. Most buying journeys involve multiple touchpoints across a long period of time, and claiming precise attribution is often overconfident. What you can do is get directionally accurate and be transparent about the methodology.
The data infrastructure reality
Here's the thing I wish someone had told me earlier: you can only report accurately on what your systems are set up to capture. If the CRM data is inconsistent, the lead source tracking is incomplete, or the automation isn't working correctly, no reporting framework will fix that. The framework is only as good as the data underneath it.
This means that building a reporting framework and fixing the data infrastructure are often the same project. It also means it takes time, genuinely sometimes months, to get to a place where the reporting is reliable.
That can be frustrating when there's pressure to have clean answers quickly. My honest advice is to be transparent about where you are in that process. A leadership team that understands why the reporting is still being built is easier to work with than one that's been presented with confident numbers that later turn out to be unreliable.
A framework that fits your context
The five layers above are a starting point, not a prescription. Every business is different, and the metrics that matter most will depend on your stage, your sales cycle, and what the leadership team needs to see.
The goal isn't a perfect dashboard. It's a consistent, honest answer to what marketing is generating for the business. Build towards that, be transparent about what you don't yet know, and keep improving it over time.
That's what I've tried to do, and it's still a work in progress.