Each Monday, a short list of the sharpest sales + GTM thinking from the past week. Not summaries — read the originals, they're better. Just what's worth your time.
Four pieces this week.
1. Sangram Vajre — "Your GTM motion and your revenue motion are not the same thing"
Sangram Vajre (co-founder and CEO of GTM Partners, creator of GTMonday) has been sharpening a distinction that most GTM teams blur past: there's a difference between a GTM motion (how you go to market — inbound, outbound, PLG, partner-led, etc.) and a revenue motion (the deliberately designed system connecting a specific ICP, a specific product, a specific GTM approach, and clear ownership across sales, marketing, CS, and RevOps). Most companies have GTM motions. Very few have revenue motions — they let them evolve by default, then wonder why revenue breaks at scale.
His core provocation: "AI doesn't fix a broken GTM — it multiplies it." Companies seeing real AI ROI have a GTM operating system that connects strategy to execution first, then layer AI on top. The implication is pointed: if your ICP definition is fuzzy, your motion ownership is unclear, and your RevOps data is siloed, adding AI to that stack doesn't improve the signal — it amplifies the noise. The partner-led motion, he notes, is underrated heading into the back half of 2026 — buyers exhausted by best-of-breed proliferation are increasingly buying through trusted ecosystems, not cold pipelines.
→ GTMonday by GTM Partners — the full Revenue Motions framework, including the six motion types and ownership map.
2. David Zhu — "Your GTM stack isn't a system — it's a Frankenstein"
David Zhu (co-founder and CEO of Reevo), on the GTMnow podcast with Scott Barker (Ep. 190), makes the case that the assembled-point-solutions approach to GTM — a CRM here, a sequencer there, an intent tool somewhere else — has created what he calls the "$10B Frankenstein Stack." The integration debt alone consumes enormous RevOps bandwidth. But the deeper problem is institutional knowledge loss: every new tool is a new data silo, and the accumulated context about why deals were won or lost never unifies into something a rep (or an AI) can reason over.
Reevo came out of stealth in November 2025 with $80M raised and is building what Zhu calls a "vertically integrated AI revenue operating system" — the bet being that AI-native platforms that unify marketing, sales, and CS from the start will replace the Frankenstein Stack over the next several years, the same way Salesforce replaced disconnected spreadsheets in the early 2000s. His argument isn't that point solutions are bad — it's that the integration layer holding them together has become the actual product, and most companies are accidentally in the business of building it.
→ GTMnow Ep. 190 — "Inside Reevo's $80M Bet to Kill the $10B Frankenstein Stack"
3. Becc Holland — "The SDR org is optimizing for metrics that don't move deals"
Becc Holland (founder and CEO of Flip the Script) laid out the most honest diagnosis of the current state of sales development I've heard this cycle. Her argument: most SDR teams are still optimizing for lagging-indicator metrics — call volume, email volume, sequences sent — that feel like management but aren't. The KPIs that matter (conversations that actually change a prospect's understanding, outbound personalized to the specific trigger in front of the rep, pipeline that converts) require a different operating model, not just more activity.
Her specific provocation: in 2026, personalization isn't a luxury. The teams still treating outbound as a volume game are watching connect rates collapse, but the reflexive response is usually to add more tools rather than fix the underlying motion. More automation applied to underpowered personalization is still underpowered personalization — it's just cheaper and faster. The real fix is design: knowing what signal actually matters for this account at this moment, and building outreach around that.
→ The State of Sales Development with Becc Holland (Revenue.io Podcast, Ep. 825)
4. KD Dorsey — "'Improve your discovery' is not coaching"
Kevin "KD" Dorsey (CRO at Finally, founder of Sales Leadership Accelerator) has been making a pointed argument that most sales coaching feedback is uselessly vague. "Improve your discovery" is not coaching. "Work on your objection handling" is not coaching. Coaching is specific, diagnostic, and tied to a precise definition of what excellent looks like for this rep, at this deal stage, against this ICP. The shorthand he's built the Sales Leadership Accelerator around: WGLL — What Good Looks Like — which has to be defined before any coaching can be meaningful.
His extension into AI is the part worth sitting with: if you can't articulate WGLL precisely, you can't use AI to help you coach. Call analysis tools are only as useful as the rubric you feed them. "If I know what's happening with AI on the calls, then I can do AI issue diagnosis. From there, I can do AI coaching. And from there, I can do AI role play" — all of it downstream of a precise definition of excellence at each stage of the motion.
→ Sales Leadership Accelerator — KD's community for managers building $100M+ revenue orgs, including the BIPSY and WGLL frameworks.
Common thread this week. All four are circling the same structural problem from different angles: the old operating defaults were designed for a world where tools were simple, buyers were unsophisticated, and data was scarce. None of those things are true anymore. Vajre: your revenue motion probably evolved — it wasn't designed. Zhu: your tech stack is a Frankenstein, not a system. Holland: your SDR KPIs measure activity, not reality. Dorsey: your coaching is generic, not diagnostic. The through-line: in a world of abundant data and AI-assisted execution, the bottleneck moves to design precision — what does "good" actually look like, defined carefully enough that a human or an agent can execute toward it?
Next Monday: a new four.
If you've read something this week worth flagging in next week's list — hello@mallin.io.