r/SalesOps

Background: I've been seeing a lot of "just connect Claude to your CRM via MCP and it'll handle your reporting" takes lately and I wanted to actually pressure-test that. Specifically: how accurate is the output when you ask it the kind of questions you'd actually ask in a monthly review.

So I built a ground-truth dataset for an anonymized sample company. Around 40 metrics (bowtie funnel actuals (leads, MQLs, SQLs, SAL pipeline, won, expansion, retention), actuals vs forecast comparison, channel attribution at every stage, rep performance, post-funnel expansion and retention by motion. Basically the stuff a CRO would actually look at. Then I asked Claude the same questions through the HubSpot MCP connector and compared.

HubSpot MCP returned like 10 out of 40 metrics. None of the 10 matched ground truth.

I was expecting some misses. I was not expecting the pattern of the misses, which is what I want to talk about.

I went in thinking I'd find dirty-data problems (duplicates, missing fields, etcc). What I actually found is a schema problem, and it's kind of more interesting (and harder to fix) than dirty data.

Examples of what came back:

When I asked for # of MQLs this month, HubSpot MCP returned the count of every contact currently sitting at or above MQL lifecycle stage. Cumulative, not period-based. So instead of 22 it returned 43. Same issue with SQLs: returned 30 instead of 5, off by 500%. The connector just doesn't have a concept of stage-transition logic, because HubSpot itself stores lifecycle as a current-state field, not as an event log.

Won revenue came back as the sum of closed-won deal amounts, which sounds right, except it missed all the post-closing upsells. So $16.5K instead of $87.4K, off by 81%. A CRO acting on $16.5K vs $87.4K draws the literal opposite conclusion about the month.

Channel attribution returned nothing useful. HubSpot stores hs_analytics_source (Organic, Direct, Paid Social, etc.) which is traffic source, not revenue channel taxonomy. There's no mapping from "Paid Social" to "Outbound" or "Referral" to "Partner", that classification layer doesn't exist in raw CRM, you have to build it.

Actuals vs planned returned nothing at all. HubSpot doesn't store forecast targets. No plan layer means there's nothing to compare against, which is fine, except Claude didn't say "I don't have plan data" ... it just... didn't address that part of the question.

That's actually the thing that bugged me most. Across all 40ish questions, Claude never flagged uncertainty. Never said "I'm not sure how your team defines MQL" or "this number looks cumulative, did you want period-based?" It just confidently returned numbers. If you didn't know to check, you'd never know.

The conclusion I keep landing on: an MQL in HubSpot and an MQL in your monthly review are not the same object. The connector gives you raw CRM access. A monthly review needs interpreted metrics, stage-transition logic, period-based counting, post-closing revenue concepts, a channel taxonomy that doesn't exist in the source schema, and a plan layer that lives in a spreadsheet somewhere. None of that is in the CRM, so none of it comes through the MCP.

Which means the "just plug Claude into HubSpot" pitch is doing a sleight-of-hand. The MCP is a data access layer. A revenue review needs a semantic layer. Different problem.

Two things I'm curious about from this sub:

1. For anyone running MCP connectors in production already: what's your sanity-check process before a number from one of these hits a board deck? Like is anyone actually catching this stuff, or is the trust just... assumed?
2. Where are you drawing the line between "use AI for drafting/summarizing" vs "use AI for numbers you'd act on"? Because I think there's a real answer there and I haven't seen anyone articulate it cleanly.

My supervisor keeps forwarding me these future of work articles about AI agents replacing repetitive tasks. Most of the case studies I find are just SaaS companies doing outbound volume play. B2G is a different beast the timelines are massive and the compliance docs are a nightmare. Has anyone integrated an agent into a gov sales workflow to reduce the work load?

Been thinking about this a lot lately. We've had enrichment running in our CRM for a while now and the time savings are real, but I keep noticing gaps where the data just. isn't right. Wrong job titles, emails that bounce, company sizes that are way off. And I get it, some decay is inevitable, recent data suggests somewhere between 30-50%, of CRM data goes stale pretty quickly, so no tool is going to be perfect. But there's a difference between normal decay and systematically bad data that reps are actually acting on. The thing that bugs me is how much the claimed accuracy numbers diverge from what people actually report using these tools day to day. Some tools are advertising 90%+ match rates but users are seeing bounce rates well above the 3-5% threshold that starts seriously hurting deliverability in practice. So you end up with reps reaching out to the wrong person at a company, that restructured six months ago, which isn't just wasted effort, it's a bad first impression. And honestly the landscape has gotten more complicated, not less. Waterfall enrichment across multiple providers helps with match rates but it also means more sources to QA and more privacy compliance stuff to think about. Meanwhile agentic AI is getting layered into a lot of these tools now for real-time qualification and routing, which is cool, but garbage in garbage out still applies. Curious how others are handling this. Are you doing any kind of spot-checking or validation layer on top of your enrichment, or, just accepting that some percentage of the data will be wrong and building your sequences around that?

I’ve been building a small HubSpot sidebar app called FollowUp AI for sales follow-up.

It works inside the contact record and helps generate:

• structured internal follow-up notes
• a ready-to-edit follow-up email draft

It uses contact/company CRM context and doesn’t require call recording.

I’m looking for a few beta testers who actually use HubSpot for sales outreach and are open to giving honest feedback. First 3–4 testers can get free Pro access for 1 year in exchange for real usage and feedback.

If you have:

• a HubSpot portal with real contact records
• Using HubSpot for sales outreach

DM me and I’ll send the install link.

Like... you spend months learning internal logic that has nothing to do with your actual job. you become the unofficial admin for tools that were supposed to be self serve. and then the moment you leave, none of that knowledge transfers and the next person starts from scratch

I've heard it described as if you need someone specialized just to operate a process, you probably don't want that process long term. and honestly that hit different

I didn't want to carry that burden at my next company and I don't think anyone in ops should have to. what's the process in your stack that quietly turned you into a specialist when you were just trying to do your job😬

you spend all this time optimizing domains, copy, deliverability, inbox rotation, follow ups

then someone finally replies with interest and the reply sits in the inbox for 2 hours because it got buried between everything else

we started building a tool around exactly that problem

it checks incoming replies, detects buying intent, gives the lead an intent rating, and instantly shows the phone number and context so you can call while the lead is still engaged

right now we’re looking for a few people doing real outbound work who want to shape the product together with us through feedback and workflow input

early testers get extended free access in exchange for honest feedback

if interested, send me a dm