How AI Agents Let GTM Teams Scale — Justin Joyce, Cloudflare @aiDotEngineer
How AI Agents Let GTM Teams Scale — Justin Joyce, Cloudflare  @aiDotEngineer
Uploaded August 2026 | Updated September 2026, 3 weeks ago
Cloudflare's weekly go to market summary is written by three agents in sequence: one drafts from the data, a second checks that draft against the data, and a third, the tone agent, rewrites it so risks and opportunities land with equal weight. Justin Joyce's team read every run for two to three months before trusting it. Joyce works in sales operations and strategy at Cloudflare, after seven years on the machine learning side, and his diagnosis is that traditional go to market does not scale. Operations rebuilds the same analysis in spreadsheets every week, or ships dashboards that meet most needs and not all. Salespeople carry two gaps: the context gap, switching between a prospect call and an adoption call while gathering everything in between, and the expert gap between your best rep and one still ramping.

His answer is three pillars. Scale analysis with skill files carrying business context and the questions people actually ask, so someone who cannot write SQL stops queuing behind someone who can, and two hours of work becomes five minutes. Scale insight by pushing the story out rather than waiting for someone to open a dashboard, since metric adoption is always uneven. Then self service: Cloudflare OS, an internal agentic workspace on Workers and Durable Objects where reps pull forecast briefs, QBR decks, account plans, and renewal prep against centrally reviewed expert skills. He puts the result at twice the efficiency, credits skill curation and a tight feedback loop, and is candid that quoting, approvals, and CRM writes are the harder problems still ahead.

Speaker info:
- linkedin.com/in/justin-j-22132912
- cloudflare.com

Timestamps:
0:00 - AGI pills, and a route into sales ops via machine learning
2:09 - Why traditional go to market does not scale
3:01 - The context gap and the expert gap
4:56 - Three pillars
6:53 - Skill files that let non SQL users query the data
9:00 - There is a story in the data; stop making them search
11:18 - Drafter, reviewer, tone agent
12:09 - Cloudflare OS: a self service agentic workspace
15:43 - What worked: curation, feedback loops, layering
17:11 - Next: CRM writes, and reining in the explosion
How AI Agents Let GTM Teams Scale — Justin Joyce, CloudflareMemory Harnesses for Long-Running Research Agents — Stefania Druga, Sakana.aiHow Claude Code Works - Jared Zoneraich, PromptLayerThe biggest challenge in your stack? Evals, Evals, Evals - 2026 State of AI Engineering resultsWelcome to AIE LEAD - Alex Lieberman, TenexHow Forward Deployed Engineering is done at Cognition — Jia WuWhy Agent Hype can fall short of reality – Joel Becker, METRGadgets: Personal app vibe coding that is actually safe — Kenton Varda, CloudflareTell the Robot What You Want — Sandhya Subramani, AWSMoving away from Agile: Whats Next – Martin Harrysson & Natasha Maniar, McKinsey & CompanyMaking Codebases Agent Ready – Eno Reyes, Factory AIWhy Agentic Systems Need Ontologies — Frank Coyle, UC Berkeley
AI Engineer |

How AI Agents Let GTM Teams Scale — Justin Joyce, Cloudflare

SHARE TO X SHARE TO REDDIT SHARE TO FACEBOOK WALLPAPER