Skip to content
Back to blog

How to Analyze HubSpot CRM Data Without an Analyst

guides
hubspot
revops
sales

Every revenue leader has the same Friday afternoon ritual. Open HubSpot. Click the Deals tab. Look at the pipeline value. Stare at it for a minute. Try to convince yourself the number means something.

It does not, on its own. Pipeline value without coverage ratios, weighted probability, and stage conversion is a vanity metric. And HubSpot's built-in reporting will not give you those numbers without either a paid Operations Hub seat or an analyst who knows where to look.

There is a faster way that does not require either.

What HubSpot tells you. What it doesn't.

HubSpot is a great CRM. It is a tolerable reporting tool.

The built-in dashboards will show you:

  • Total pipeline value
  • Deals by stage
  • Activity counts (calls, emails, meetings)
  • Win rates, eventually, on closed deals

What they will not show you, without significant configuration:

  • Stage-to-stage conversion rates over time. Is your demo-to-proposal conversion getting worse? HubSpot's funnel report shows current state, not the trend.
  • Weighted pipeline coverage vs target. The right metric for "are we going to hit the number?" is weighted pipeline divided by quota. HubSpot does not compute that.
  • Velocity by deal segment. How long does an SMB deal take vs an enterprise deal? Are deals slowing down in the middle of the funnel?
  • Cohort behaviour of inbound vs outbound deals. Same value at top of funnel, very different conversion rates, very different time to close.

These are RevOps questions. They are also the questions your VP of Sales asks the day before the QBR.

Connect HubSpot. Ask in plain English.

Anna connects to HubSpot via OAuth, read-only. She reads your deals, contacts, companies, and activities — using your actual property names, not a generic schema. Custom pipelines, custom stages, custom deal properties all work.

Once connected, the analysis becomes conversational. No HubSpot Operations Hub seat. No exporting deals to a spreadsheet. No filtering through 14 saved views to find the one that almost answers the question.

The pipeline health prompt

Here is the prompt to start with:

"Analyse my pipeline health for this quarter. Show me weighted pipeline coverage, stage-to-stage conversion vs the prior two quarters, and flag any stage where conversion has dropped significantly."

Anna pulls every active deal, applies the stage probabilities you have set in HubSpot (or asks if you have not set them), computes weighted pipeline, and benchmarks against your last two quarters of closed-deal history. She runs a simple statistical test on each stage transition to flag the ones that have moved meaningfully — not just "looks lower," but "this drop is bigger than your normal week-to-week noise."

A typical answer might look like:

Weighted Pipeline
$1.84M
2.3x quota
Demo to Proposal
34%
vs 48% Q4
Avg Deal Cycle
47 days
+11 days

Pipeline coverage looks fine — 2.3x quota is healthy. But the demo-to-proposal drop is the story. The deals are reaching demo at a normal rate. They are just not converting through. That is a qualification problem, a competitive problem, or a product-fit problem. None of them are solved by adding more top-of-funnel.

The deal-velocity prompt

Velocity is the metric most teams ignore until the quarter is half over.

Try this:

"Compute average days-in-stage for every pipeline stage, this quarter vs last quarter. Break it out by deal size — under $25K, $25-100K, and over $100K."

Anna runs the calculation per segment and per stage. The pattern she usually surfaces: enterprise deals slow down at one specific stage, mid-market deals slow down at a different one. Generic "deals are slowing" advice is useless. "Enterprise deals are spending 22 days in legal review, up from 9" is something you can act on this week.

After the velocity answer, ask "which deals contributed most to the slowdown?" Anna lists the specific deal names. You take that list to your one-on-one with the AE. The conversation stops being abstract.

The inbound vs outbound question

Most B2B teams have both motions. Most cannot answer with confidence which one is more efficient — because the question requires segmenting deals by source, computing conversion at every stage, and weighting by ACV.

Paste:

"Compare inbound vs outbound deals on win rate, average ACV, and time to close. Control for deal size."

Anna pulls deals by lead source, runs the stage-by-stage comparison, and accounts for deal size differences so you are not comparing a $10K SMB inbound to a $200K enterprise outbound and pretending they are equivalent.

The answer often surprises. Inbound usually wins on velocity. Outbound usually wins on ACV. The interesting finding is which segment of inbound matches outbound on ACV — that is where you double down.

Cross-referencing HubSpot with Stripe

This is the part that no HubSpot report can do.

Connect Stripe alongside HubSpot. Now you can ask:

"For deals closed in the last 6 months, compute actual revenue realised vs the deal value at close. Where is the gap biggest?"

Anna joins HubSpot deals to Stripe subscriptions on the customer or company name, computes the variance, and shows you which deal sizes or segments most often shrink between contract and realised revenue. Some deals get smaller through downgrades. Some never start because the contract was signed but never activated. Both show up as "closed-won" in HubSpot. Neither is the same as money in the bank.

This is the analysis a RevOps analyst would build over two weeks of SQL work. With both connectors active, Anna runs it on demand.

What about Salesforce?

The native Salesforce connector is on the roadmap. In the meantime, the Composio MCP catalog covers Salesforce — connect that and the same prompts work against your Salesforce schema. The methodology does not change; the source does.

Methodology your VP can audit

The reason this matters more in RevOps than in most analytical contexts: when your VP asks "where did this number come from?", the answer cannot be "Anna told me."

Every Anna answer includes the methodology. Which deals were included. Which stages were excluded. What probability values were used for weighting. What test was run to determine significance. The answer is auditable. If your VP does not believe the demo-to-proposal drop, they can read the methodology and challenge the assumptions.

That is the difference between a RevOps tool and an analyst. The output is defendable.

One prompt to start

Open HubSpot. Note the question that is going to come up in your next pipeline review. Most likely it is one of:

  • Are we going to hit the number this quarter?
  • Why is conversion dropping in the middle of the funnel?
  • Which AE is actually driving more revenue, controlling for territory?
  • Is inbound paying for itself?

Connect HubSpot. Paste the question. Try it at heyanna.studio.