RevOps & GTM
News Digest

The hottest topic in developer communities right now has barely appeared on any LinkedIn feed. It's called MCP — Model Context Protocol. And it's about to change how your entire revenue engine is built. Here is the problem MCP solves: Right now, every AI tool you use needs its own custom integration to talk to your CRM, your data warehouse, and your sequencer. One integration for Salesforce. One for HubSpot. One for Apollo. One for Gong. Every new AI tool you add = another bespoke integration to build and maintain. This is why your GTM stack feels like a house of cards. MCP is the fix. It's an open standard — think of it as a universal connector — that lets any AI agent securely read from and write to all your GTM tools through a single, standardised interface. What this means in practice: 🔍 Before MCP: "I need to build a custom API integration between my AI agent and Salesforce, then a separate one for HubSpot, and another for Apollo. Each one breaks every time someone updates a field schema." ✅ After MCP: "My AI agent connects to all my GTM tools through one protocol. I can ask it to: pull deal history from Salesforce, cross-reference it with product usage data, check the latest LinkedIn posts from my champion, and draft a personalised renewal email — all in one prompt." The RevOps teams already building on MCP are creating AI agents that can: → Research accounts and update CRM records automatically → Flag pipeline risk by querying across multiple data sources in real time → Trigger enrichment, routing, and sequencing from a single natural language command This isn't coming. It's here. It's just only being discussed in developer Slack channels right now. The GTM teams that understand this first will have a serious structural advantage. Have you started exploring MCP for your revenue stack yet? 👇 #RevOps #GTM #AI #MCP #SalesTech #GTMEngineering

Your lead score is tracking the wrong thing. Most CRM lead scores are built around individual behaviour: → Opened email = +5 points → Attended webinar = +15 points → Visited pricing page = +20 points → Downloaded whitepaper = +10 points Hit 50 points and you're "MQL ready." The problem? B2B buying decisions don't happen at the individual level. They happen at the account level — across a buying group of 6 to 10 stakeholders, most of whom your CRM has never tracked. Here is what is actually happening in your pipeline right now: Person A (the champion you've been nurturing for 3 months) has a lead score of 85. Your SDR has been following up with them weekly. But Person A doesn't control budget. They can't sign anything. They're an enthusiast, not a decision-maker. Meanwhile, their CFO visited your pricing page twice last week. No form fill. No webinar attendance. Lead score: 0. Your SDR has never reached out to them. This is the lead score trap. The teams winning pipeline in 2026 have stopped tracking individuals and started tracking accounts. They ask completely different questions: ❌ Old question: "Has this lead hit our MQL threshold?" ✅ New question: "How many stakeholders in this account have engaged with us, across how many touchpoints, over what period of time?" This is what buying group intelligence looks like. And it requires your CRM to be structured around accounts and decision-making groups — not just individual contacts with activity scores. Is your RevOps team still running individual lead scoring, or have you made the shift to account-level tracking? 👇 #RevOps #DemandGen #B2B #LeadScoring #GTM #SalesOps

The RevOps role is splitting into two very different career paths. Understanding the difference will change how you hire — or how you position yourself. Path A: The RevOps Administrator Their job is to maintain existing systems. → They manage CRM field updates and routing rules. → They build reports and dashboards for leadership. → They handle the tool admin queue (Salesforce, HubSpot, Outreach). → They're measured by tickets closed and dashboards delivered. This role is valuable. But it's a support function. Path B: The GTM Engineer Their job is to build automated revenue systems from scratch. → They design and implement signal detection pipelines (funding, job changes, intent data). → They build programmatic waterfall enrichment flows across multiple data providers. → They write code or use developer-first tools to replace fragile, expensive Zapier arrays. → They're measured by pipeline generated, enrichment coverage, and trigger-to-reply velocity. This is an architecture function. The GTM Engineer doesn't wait for a ticket. They don't ask "which field should I update?" They ask "what signal, if detected and acted on in under 30 minutes, would generate the most pipeline?" And then they build the system that makes that happen automatically. Why does this matter right now? Because AI tools only work when there's a clean, structured, automated data foundation underneath them. The GTM Engineer builds that foundation. The RevOps Admin maintains the tools on top of it. Both are necessary. But companies that only hire admins and then wonder why their AI investments aren't delivering ROI are making a fundamental architectural mistake. Which path are you on — or which type are you currently hiring for? 👇 #RevOps #GTMEngineering #SalesOps #B2B #Hiring #CareerDevelopment

The hottest debate in outbound sales right now: Should your AI SDR operate fully autonomously — or should a human review every email before it sends? Let me break down both sides clearly. 🤖 The Fully Autonomous Case (Team Artisan): → AI researches the prospect, personalises the email, and hits send — no human review. → Speed advantage: Can run 24/7 at scale without bottlenecks. → Cost advantage: Dramatically reduces SDR headcount costs. → Best for: High-volume outbound to cold, top-of-funnel audiences. 🧑‍💻 The Human-in-the-Loop Case (Team Controlled): → AI does the research and drafts the email. Human reviews and approves before sending. → Quality advantage: Catches hallucinations, tonal errors, and factually wrong personalisation before they reach the prospect. → Risk management: Protects domain reputation from the spam filter penalties that come from large volumes of low-quality AI emails. → Best for: Named accounts, enterprise prospects, and any situation where a bad email causes real damage. Here is what I've seen in practice: The teams using fully autonomous AI outbound on cold lists are seeing their domain reputation tank within 90 days. ISPs are getting increasingly aggressive at filtering AI-generated content at scale. The teams using human-in-the-loop AI — where AI drafts and humans approve — are running at 3–5x the output they had before AI, while maintaining reply rates and domain health. The nuance nobody is talking about: Autonomous AI is fine for ultra-high-volume, disposable domain outbound where individual reply rates are less important than raw pipeline volume. Human-in-the-loop AI is the right model for named accounts, referrals, warm audiences, or high-ACV deals. The mistake is applying one model uniformly to all outbound scenarios. Where does your team sit on this spectrum? Fully autonomous, fully human, or somewhere in the middle? 👇 #OutboundSales #AISDR #SalesTech #RevOps #GTM #B2B

Data circulating in RevOps communities this week: Approximately 55% of operations professionals are actively looking for new roles or open to opportunities right now. That is not a retention problem. That is a structural problem. Here is what's actually driving it: 1. "I'm treated as a support desk, not a strategic partner." The most common frustration. RevOps teams that spend 80% of their time closing tickets and building dashboards — instead of influencing pipeline strategy — are losing their best people fast. 2. "I'm being asked to implement AI tools on top of broken data foundations." Ops professionals know better than anyone that AI won't fix bad data. Being put in the position of deploying AI they know will fail — and then being blamed when it does — is demoralising. 3. "The GTM Engineer title exists elsewhere and pays 30–50% more." As the role bifurcates between Admin and Engineer, the most technically skilled RevOps professionals are migrating toward companies that give them technical scope and the GTM Engineer title. 4. "I have no seat at the strategic table." RevOps is now widely accepted as a strategic function. But in companies that still treat it as back-office admin, the talent that knows what RevOps can actually do is leaving. What are the companies retaining and attracting the best RevOps talent? → They give ops a seat in strategic GTM planning, not just execution. → They frame the role as architecture, not administration. → They invest in clean data foundations before asking ops to implement AI. → They measure RevOps by pipeline velocity and NRR, not tickets closed. If you lead a RevOps team: when did you last ask your ops people what problems they want to solve — not just which tickets they need to close? What's your experience of the RevOps talent market right now? 👇 #RevOps #SalesOps #GTM #Hiring #Leadership #RevenueOperations