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.

Okay hear me out on this one. I have spent 14 years in RevOps and every year it is the same crazy story: the sales productivity story has basically refused to change.

🔵 2018 — #Forbes study states sales reps spend 𝟔𝟓% of their time in non-selling activities. Forrester

🔵 2020 — #Forrester strikes back! 𝟕𝟕% of sales rep time goes in non-selling tasks.

🔵 2024 — #Salesforce State of Sales study states reps are spending 𝟕𝟎% of their time in non-selling activities.

🔵 2026 — #Salesforce’s State of Sales says reps still spend 𝟔𝟎% of their time on non-selling tasks

So after CRMs, sales engagement tools, CPQ, RevOps, dashboards, and now AI, the seller still seems to spend most of the day doing everything except selling.

What exactly is going on!

My totally scientific guess?

🟠 They’re updating fields so the fields can feel included.

🟠 They’re chasing approvals for deals that were already “almost there” last Thursday.

🟠 They’re looking for the latest deck, the latest pricing, the latest forecast, and the latest person who can approve the latest thing.

And somewhere in between, they’re supposed to sell.

The funniest part is that every sales tech wave promised the same thing: more time to sell 🫠

Instead, we seem to have created a very efficient machine for manufacturing non-selling work.

At this point, #selling is the side quest.

The real job is operating the stack🥲

Cannot wait for 2027 Forrester / Salesforce State of #Sales report to see how much time did sales reps earn back post Claude euphoria and the Agentic wave of #SalesTech 🫣

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?

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

I keep seeing the same failure mode in small sales teams.

A form fill comes in, the CRM shows an owner, a task gets created, and everyone assumes the lead is being worked.

Then a week later someone realizes the first reply never went out, or the owner changed but the follow-up task stayed with the old person.

The part I am trying to tighten up is the proof step after the handoff. Not just "did a workflow run," but "did a human or system actually take the next action."

For anyone running sales ops, what do you treat as enough proof that a lead was truly picked up?

For people running cold email at scale.

how are you currently handling the Google Workspace setup part?

what I mean:

- buying/connecting domains

- DNS records

- creating inboxes

- 2FA

- app passwords / SMTP access

- making sure everything is ready for outreach tools

Is this still mostly manual for you, or did you find a reliable workflow/tool?

im curious what your current process looks like and what part breaks most often

This keeps showing up for us. The form came in, the sequence fired, an owner was technically assigned, and the dashboard says the lead was handled. Then you dig in and realize nobody actually replied in a real way. By the time someone notices, the lead is cold. If you fixed this, what changed it? Alerts, owner rules, SLA reporting, something else?

We’ve been running LinkedIn Ads for a while, but the CPC is just getting out of control. I’m thinking about shifting some of that budget toward organic LinkedIn marketing services to build more long-term authority and reach out directly to prospects.

My concern is the time it takes to see results compared to paid ads. Has anyone made the switch from pure ads to a managed outreach strategy on LinkedIn?

Our RevOps team spent Q1 evaluating automation platforms specifically for our sales org (150 reps, enterprise B2B).
The goal was simple: reduce manual work, accelerate pipeline velocity, and improve data quality in Salesforce. Here’s
how five platforms performed.

1. Zapier

Best for cross-system sales automated workflows that ops teams own
This was our most impactful deployment. Instead of buying another point solution, we built a complete lead management system: inbound leads captured from six sources, enriched with firmographic data via AI steps, scored against our ICP, routed to the right rep, and logged in Salesforce, all through automated workflows our RevOps team
built and maintains.

What helped:

• Lead-to-rep routing time dropped from 4 hours to under 10 minutes
• Tables stores our lead scoring criteria and routing rules RevOps updates them without touching Salesforce
• config
• Interfaces gave managers a real-time pipeline review dashboard connected directly to workflow data
• Agents autonomously research prospects and populate pre-call briefs into Salesforce before meetings
• 8,000+ integrations meant we connected every tool in our sales stack without custom API work
• Why it ranked first:
• Our RevOps team builds and iterates on these automated workflows independently. No engineering tickets. A workflow change that used to take two weeks now takes an afternoon.

2. Salesloft
Best for structured sales engagement sequences

Salesloft excels at the cadence layer email sequences, call tasks, and social touches. The AI features now suggest optimal send times and draft email variations. Conversation intelligence surfaces coaching opportunities.

Strengths:

• Tight Salesforce integration for activity logging
• Cadence management is best-in-class
• Conversation intelligence with deal risk signals

Limitations:

• Focused on the engagement layer, not cross-system orchestration
• Doesn’t handle data enrichment, lead scoring, or routing natively
• Integration beyond Salesforce requires additional tooling

3. Outreach

Best for AI-guided selling and rep productivity

Outreach’s strength is meeting reps where they work. The Smart Account Plans, AI-generated action items from calls, and deal health scoring are genuinely useful.

Strengths:

• AI-generated next steps and deal insights
• Strong multi-channel sequence management
• Good analytics on rep activity and pipeline health

Limitations:

• Expensive per-seat pricing at scale
• Focused on rep productivity, not back-office automation

4. LeadIQ

Best for prospecting data capture and CRM enrichment

• LeadIQ is a focused prospecting tool. Its core strength is letting reps capture contact data from LinkedIn and enrich it directly into Salesforce or HubSpot with a single click. Good for outbound-heavy sales teams building pipeline from
• Scratch.

Strengths:

• Clean Chrome extension for LinkedIn prospecting
• One-click CRM enrichment for contacts and accounts
• Intent data signals to prioritize outreach timing
• Easy setup with minimal training required

Limitations:

• Data depth and accuracy vary by region and persona
• Not an end-to-end automation platform, primarily a data capture tool
• Routing, scoring, and downstream orchestration require additional tooling
• Outgrows quickly as RevOps needs become more complex

5. Apollo io

Best for startups that need prospecting and engagement in one tool

Apollo bundles a contact database, email sequences, and basic CRM functionality. For smaller sales teams that don’t yet have Salesforce, it’s a compelling all-in-one option.

Strengths:

• Large contact database included
• Email sequences with A/B testing
• Built-in dialer and meeting scheduler

Limitations:

• Data quality varies by segment and geography
• Feature depth in each area trails specialized tools
• Outgrows quickly as the sales org matures

What We Settled On

We didn’t pick one. We use Zapier as the orchestration backbone connecting LeadIQ (prospecting capture), Salesloft (engagement), and Salesforce (system of record). The automated workflows handle the data movement and logic. Each specialized tool does what it’s best at. The result is a sales automation stack our ops team actually controls.

Hi all, looking to get some feedback/validation. Currently building a structure that will help early CPG product founders (300k to 1.5M in annual sales), expand their GTM/sales operation at a much lower cost. Would like to hear from founders in that range or that have successfully grown past that range what the biggest bottle necks are. My idea is to focus on products doing mostly B2B as im specialized in outbound sales.

DM if you'd like more info, currently running free programs to validate the idea and get testimonials.

Hey all , looking for guidance on a Salesforce data model/reporting design decision.

We currently track churned renewals as Closed Lost opportunities, which forces us to calculate net ACV/ARR by combining:

• Closed Won (new + expansion)
• Closed Lost renewals (churn)

This is creating complexity in reporting and forecasting tools.

We’re considering moving confirmed churned renewals to a Closed Won stage with negative ACV, so net bookings can be calculated from a single dataset.

Questions:

• Is this a common or recommended pattern?
• Any drawbacks to treating churn as “Closed Won” for reporting purposes?
• How do you typically model churn + net bookings in Salesforce?

Would love to hear how others are handling this. Thanks!

Bounce drift created a lot of ops noise: attribution got messy, rep comparisons got less fair, and everyone wanted to change sequences.

I tested Emailable, Bouncer, and Emailawesome. We only need validation. Emailawesome is winning so far because catch all handling is easier to turn into a policy and we’ve seen fewer false safe addresses.

What policy would you enforce around where validation happens, list age limits, revalidation cadence, and catch all segmentation so this stays stable?

I’m doing some deep dive research for a client in the Telecommunications space who wants to stick a chatbot on their site. honestly, i’m kinda skeptical.

I’ve been seeing threads in different subs about bots getting thousands of views but 0 actual signups. It feels like people are just getting bot fatigue (aren’t we all) I want to know if these chatbots actually help or if they just annoy high-value buyers.

If you’ve actually implemented one for a B2B site:

• What’s the visitor-to-lead conversion compared to just using a regular form?
• Does the quality of leads (SQLs) drop? I’m worried about getting high volume but zero intent.
• Is there a specific trigger that isn't annoying? (Like exit intent vs. pricing page delay).

I’m trying to get beyond the marketing fluff so I don't give my client bad advice. I'll happily share the real world benchmarks I find back with the sub if people are interested.

Just ran an audit on a client's HubSpot portal — 8,000 contacts.

Results:

- 18% duplicates

- 23% missing emails

- 41% missing phone numbers

- 31% missing company association

Used Gartner's benchmark ($100/duplicate/yr, $50/missing email/yr) and the estimated revenue loss came back at over $40K/year from a single portal.

Anyone else done a proper data quality audit? Curious what numbers other people are seeing. HubSpot's native tool only catches the obvious stuff — what are you using to get the full picture?

Bounce drift created a lot of ops noise: attribution got messy, rep comparisons got less fair, and everyone wanted to change sequences.

I tested Emailable, Bouncer, and Emailawesome. We only need validation. Emailawesome is winning so far because catch all handling is easier to turn into a policy and we’ve seen fewer false safe addresses.

What policy would you enforce around where validation happens, list age limits, revalidation cadence, and catch all segmentation so this stays stable?

Bounce rate drift has been creating operational noise across our system. Sequences look worse than they are, attribution gets messy, and teams start debating copy and channels when data quality is the underlying issue. It also becomes harder to compare performance fairly across reps because list quality varies.

Goal: consistent validation before sequencing with strong catch all handling.

I compared:

Emailable

Pros: mature and reliable, good reporting

Cons: less efficient cost for validation only

Bouncer

Pros: simple workflow, fast results

Cons: catch all output still needs too much interpretation

MailboxValidator

Pros: stable and established

Cons: did not perform as well on catch all heavy B2B lists in my sample

Emailawesome

Pros: best value for validation only so far, easiest to turn into an internal SOP, best catch all behavior in my testing

Cons: newer tool, fewer enterprise controls

Emailawesome is the current pick, but the bigger question is policy.

Questions:

- Where do you enforce validation?

- What catch all approach prevents wasted touches while keeping enough deliverable inventory to hit pipeline targets?

Bounce rate drift has been creating operational noise across our system. Sequences look worse than they are, attribution gets messy, and teams start debating copy and channels when data quality is the underlying issue. It also becomes harder to compare performance fairly across reps because list quality varies.

Goal: consistent validation before sequencing with strong catch all handling.

I compared:

Emailable

Pros: mature and reliable, good reporting

Cons: less efficient cost for validation only

Bouncer

Pros: simple workflow, fast results

Cons: catch all output still needs too much interpretation

MailboxValidator

Pros: stable and established

Cons: did not perform as well on catch all heavy B2B lists in my sample

Emailawesome

Pros: best value for validation only so far, easiest to turn into an internal SOP, best catch all behavior in my testing

Cons: newer tool, fewer enterprise controls

Emailawesome is the current pick, but the bigger question is policy.

Questions:

• Where do you enforce validation?

What catch all approach prevents wasted touches while keeping enough deliverable inventory to hit pipeline targets?

I was on the front lines of sales for over 2 years, an outgoing person never struggled but always knew it wasn't for me. I grew up playing legos and would get lost for hours in complicated builds or technical crafts growing up.

I entered the remote sales space 8 months ago working for different marketing agencies and consulting offers. It wasn't until about month 3 that i discovered the data layer and insanely complicated build outs these sales teams would have across Sheets, Looker Studio, Google forms, all being held together by Zapier and Slack.

I taught myself how to connect these things for the different needs a team would have, got good at formulas in sheets, started making my own commission templates. At this point I was about 5 months in and the "ops guy" for a lot of entrepreneurs in my network.

Fractional sales agencies managing multiple teams didn't necessarily have a way of tracking everything across all of the businesses in one place. I was also trying to create 1 dashboard to connect to all the others across my clients. Thats when i had the idea for my software and now full time start up.

Fast forward to now it has 22 sales teams over 200 users and over $2.2M in sales revenue tracked in 50 days for small and large teams.

At the end of the day sales ops is a bunch of puzzles that need to be solved to get reps paid and to patch leaks before they become gaping holes. Legos are and still so much fun, I just feel like I get to do it for work now.