RevOps Isn't About the Tool. It's About the Answer.

One of the most common things I hear when a company brings me in for RevOps work is some version of this: "We have HubSpot. Why can't we just see our funnel?" Or "why can't I get a straight answer on our close rate?" Or "we're spending all this money on marketing and I have no idea what's actually working."

The data is there. It really is. HubSpot is a genuinely powerful CRM and the reporting suite has come a long way. But having data in a system and being able to answer strategic questions with it are two completely different things. That gap is exactly what RevOps exists to close.

I got an email from a client's leadership team this week asking for a set of sales funnel reports. Monthly cohort funnel, stage velocity, days to close, conversion by segment. I read it, closed my laptop, opened it back up, and started thinking through how we were going to make it happen. Because my honest answer was: we could technically build these in HubSpot, but it would be slower, messier, and less accurate than pulling the data and doing it in Excel.

So that's what we did… well, technically Google Sheets. And the client said it was "more visibility than we've ever had."

That's RevOps.

RevOps Is Not "HubSpot Admin"

This is the misconception I bump into the most. RevOps is not about knowing which button to click in your CRM. It's about owning the integrity of your revenue data and making sure leadership can actually make decisions with it.

That means knowing what your CRM is good at and what it isn't. Auditing your data before you build reports on top of it. Choosing the right tool for the right analysis. Making your methodology transparent and auditable. Telling a clean story, not pulling a screenshot.

HubSpot is a great place for your data to live. It's not always the best place to work with it.

What HubSpot Reporting Is Actually Great At

To be clear, HubSpot's native reporting is the right tool for a lot of things. Anything that needs to be live, operational, and checked regularly belongs there.

Real-time pipeline health and deal counts. Sales activity tracking (calls, emails, meetings this month). Lead source attribution, who's coming in and from where. Lifecycle stage distribution across your database. Rep-by-rep performance scorecards. Marketing-to-sales handoff metrics.

These live in HubSpot because they need to update constantly and your team is already in the platform. That's the right call. This is your RevOps operational layer.

Where It Gets Complicated

The trouble starts when leadership asks the questions that actually drive strategy:

Has our close rate been getting better or worse over the last 12 months? Where exactly in the funnel are we losing deals, and has that changed? How long does it take a deal to close, by the month it was created? Are certain segments converting at a higher rate than others? Is marketing-sourced pipeline converting at the same rate as sales-sourced?

HubSpot can gesture toward these answers. But it wasn't designed for cohort-based, longitudinal analysis... the kind of work where you're not asking "what's happening right now" but "what story does the last year of data tell us?"

And here's the part that matters most: your data might be telling a different story than HubSpot's native funnel view suggests.

When I exported the deals and actually looked at the data, the first thing I noticed was that a huge portion of deals weren't starting at the top of the funnel at all. They were being created mid-pipeline or straight into Closed Won. If we'd used HubSpot's built-in funnel report without catching that, the conversion percentages would have looked completely wrong. Not because HubSpot was broken, but because nobody had gone into the data and asked "wait, is this actually measuring what we think it's measuring?"

If you're the RevOps person presenting funnel metrics to leadership and those numbers are off because of data entry patterns nobody caught, that's your credibility on the line.

That's a RevOps catch. That's the whole job.

Month-by-Month: The View That Changes Everything

One of the highest-value things RevOps can deliver to a leadership team is a monthly cohort view of the funnel. You take every batch of deals created in a given month and track that specific group through the pipeline independently.

This is fundamentally different from a snapshot of what's in your pipeline today. It answers the question: for every group of deals we've ever started, how did they actually convert?

When you run this analysis, you start seeing patterns that summary reports will never surface:

Seasonality. Certain months consistently produce better conversion. You can plan headcount and budget around it instead of guessing.

Process changes. Did that new sales playbook you launched in March actually move the needle by April and May? Cohort data tells you. A snapshot doesn't.

Ramp-up lags. Deals created this month won't close for 60+ days. Comparing this month's close rate to last month's is an apples-to-oranges mistake that misleads leadership. Cohort views prevent that.

Outlier distortion. One massive deal can make an entire month look like a win. Cohort views make that visible instead of hiding it in an average.

HubSpot doesn't have a native report that shows you the funnel conversion for deals created in January as one column, February as the next, March as the next. That's a pivot table. Excel is built for exactly this.

And once the framework is built, you paste in next month's export and the whole thing recalculates. Your leadership team gets a monthly story, not a one-time snapshot.

The RevOps Reporting Stack (In Practice)

Here's how I approach it when a client needs this kind of analysis:

Export from HubSpot. Pull all deals with the properties the analysis calls for. Stage entry dates, amounts, deal type, create date, close date, source, owner. HubSpot makes this easy.

Audit before you build. This is the step people skip, and it's the most important one. What's your actual funnel population? Are fields populated the way you think they are? Are there data entry patterns that would skew your results? Are reps creating deals at the right stage? Is lifecycle data clean enough to support the analysis? This is where RevOps earns its keep. You'll find things here that change the whole shape of the report, and often surface process problems that need fixing upstream.

Build with a clear methodology. In Excel, you're in control. Document your assumptions. Make your segment definitions editable (a single threshold cell that recalculates everything is beautiful). Make the data traceable so anyone can audit a number back to a source record. When your VP of Sales asks "where did this number come from?" you can show them, row by row. A report nobody trusts is worthless.

Present a story, not a dashboard. A clean Excel workbook with two or three well-built charts tells a better story in a leadership meeting than a HubSpot screenshot that requires a ten-minute explanation. Functional over pretty. The data is what matters. And for RevOps, the ability to walk leadership through the methodology is just as important as the number itself.

The Real Value

The client who told us this was "more visibility than we've ever had" wasn't reacting to a fancy dashboard. They were reacting to clarity. For the first time, they could see how deals actually moved through their funnel over time, where the bottlenecks were, how long each stage was taking, and which segments were converting and which weren't.

That clarity changes conversations. Instead of "I feel like we're losing deals at the proposal stage," it's "our proposal-to-close conversion dropped 12% in Q2, and here's the cohort data that shows it." Instead of "we need more leads," it's "our top-of-funnel volume is fine, the problem is stage three velocity." Instead of sales and marketing pointing fingers at each other, everyone is looking at the same data and having the same conversation.

Those are RevOps conversations. And they lead to different decisions than gut feelings do.

When to Use Which

Here's the simple version:

Use HubSpot reporting for the operational layer. Anything your team needs to see regularly, anything that should update in real time, and anything tied to daily or weekly operations. Pipeline views, activity dashboards, lead source tracking, rep scorecards, lifecycle stage distribution, marketing-to-sales handoff metrics. Build these in HubSpot and let them run.

Pull the data into Excel for the strategic layer. Cohort analysis, historical funnel performance, conversion trends over time, days-to-close analysis, source-to-close attribution, and any question where the methodology matters as much as the answer. Anything where you need to control for data quality, filter out edge cases, or build something auditable that you can present to leadership with confidence.

RevOps Is a Practice, Not a Platform

RevOps is not about having the fanciest tech stack or knowing every feature in your CRM. It's about making sure your revenue data is clean, your reports are trustworthy, and your leadership team can actually answer the questions that matter.

Sometimes that means building in HubSpot. Sometimes it means pulling the data and doing the work in Excel. Good RevOps is knowing the difference and delivering the answer either way.

If you want help building a reporting stack that gives your team operational visibility and your leadership strategic clarity, that's what we do.