Thursday, July 2, 2026

32 signals

GTM: Inside How Agency is Building to $1B with Fewer Than 100 People

**The GTM Newsletter · AI×GTM · Practitioner Story · Jul 2

Massive exits can feel like failures when they don't solve the core problem: 95% of customers at Drift received no human support despite $1.2B valuation, revealing fundamental unit economics misalignment
Industry spends 6x more on labor than software, yet invests disproportionately in customer acquisition over retention—AI agents positioned as solution to this structural inefficiency
Agency thesis: $1B revenue with <100 people is achievable through AI-powered customer organization, suggesting dramatic shift in GTM labor economics and scalability models
Founder identity crisis post-exit is real and underexplored—Torres frames $1.2B exit as 'biggest failure' due to unresolved customer support problem, not financial outcome

GTM: Why a $1.2B exit felt like his biggest failure, and the customer-obsession thesis behind Agency

GTMnow · GTM Ops · Practitioner Story · Jul 2

Exit success ≠ mission success: $1.2B Drift exit felt like failure because product was shut down and team dispersed post-acquisition—reframes founder definition of 'winning'
AI-native org structure thesis: Agency targets $1B valuation with <100 people (80-90% engineers) running on their own product, eliminating traditional sales/ops overhead
Sales is the last role AI eliminates: Torres explicitly states sales will be final frontier for AI automation, suggesting human judgment in customer relationships remains irreplaceable in near-term
Distribution > Product in AI era: Identifies distribution as harder problem than building AI agents themselves—critical insight for GTM leaders in crowded AI market
Value-add investor thesis: Selective about capital partners (Pat Grady, Brian Halligan)—signals shift toward founder-friendly investors who contribute beyond check-writing

Your ROI Calculator is S.H.I.T. - I analyzed 30 vendor ROI calculators. Most fall into one of six categories -- and most are theater.

revops · GTM Ops · Practitioner Story · Jul 2

Most vendor ROI calculators (majority of 30 analyzed) pre-load vendor-owned improvement assumptions rather than letting buyers control inputs -- creating indefensible claims when CFOs ask for basis
Six-category taxonomy reveals pattern: 'Vendor Benchmark Injector' is most common type, while 'Math in a Box' (honest arithmetic) and 'Honest Comparison Tool' (buyer-controlled) are rare
Forrester/IDC TEI studies are reused across competing vendors with near-identical disclaimer language, suggesting commoditized research rather than differentiated value proof
Transparency correlates with defensibility: calculators with 8+ buyer-controlled sliders undersell themselves but produce credible outputs that survive CFO scrutiny
Emerging buyer sophistication: RevOps and finance teams now actively challenge ROI calculator assumptions, creating vulnerability for vendors using theater-based tools

How sellers and CX at Profound use Prophet to see every deal, account, call, next step, and more in one place

the gtm engineer · GTM Ops · Practitioner Story · Jul 2

Profound built Prophet (internal AI platform) in 2 months because off-the-shelf tools cannot replicate proprietary sales methodology, analytics, and deal qualification logic—the real competitive asset is not data but 'living understanding of how we sell'
Modern AI extraction (call transcripts → MEDDPICC signals, action items, commitments) is now cheap and reliable enough to run nightly at scale, making custom build-vs-buy calculus fundamentally different than 2-3 years ago
Semantic search layers (chat on Salesforce) answer questions about data; Prophet does the work (writes briefs, scores deals, maps communications, recomputes health)—the distinction between query tools and workflow automation is the real decision point for GTM leaders

Seth Marrs (CSO @ Sandler): Agentic Sales A-ZTime-Sensitive

GTM Council · AI×GTM · Practitioner Story · Jul 2

BDR replacement is vendor fiction—AI augments research/prep, not replaces headcount. CEOs optimizing for headcount cuts are solving the wrong problem.
Skill decay is measurable and immediate: 40%→80%→40% in 24 hours proves survey-based certification is obsolete. Real-time conversation data is the only valid proof.
Next-best-action models are over-engineered. Top-three options with peer success rates + rep agency + system learning creates better outcomes than deterministic recommendations.
Infrastructure-first architecture prevents catastrophic failure modes. Building AI on bought infrastructure beats custom solutions that break at scale (4,000 reps stuck on one data feed failure).
Revenue-per-rep normalized across role types (net-new, farmer, CSM) is the true metric—not activity counts or pipeline velocity.

Vercel Took a 10-Person SDR Team Down to 1. The Whole Thing Costs $5,000 a Year. With Vercel’s COO Jeanne DeWitt Grosser.Time-Sensitive

SaaStr — Jason Lemkin · AI×GTM · Practitioner Story · Jul 2

Vercel reduced a 10-person SDR function to 1.25 people with a $5K/year agent—32x ROI—by documenting deterministic workflows first, then encoding them into AI with human-in-the-loop validation for 6 weeks before autonomous operation
The 'tripod' build method (GTM engineer + data scientist + subject-matter expert) ensures agents mirror best-practice human workflows rather than replacing judgment; the best SDR reviewed every output until the agent reached 90th-percentile performance consistency
The narrative shift from 'automation = job cuts' to 'automation = role elevation' is critical for internal adoption—Vercel moved displaced SDRs into higher-value work, making this a productivity multiplier rather than a headcount reduction story
Production-scale metrics matter: 93% support case load, 96% content updates, 24/7 speed-to-lead improvements demonstrate this isn't theoretical—rough edges included, real costs disclosed, real people still in loop
GTM engineering as a discipline is emerging at scale-up stage; Vercel's approach suggests the future of GTM is workflow documentation → deterministic process design → AI encoding → human validation → autonomous execution

20VC x SaaStr: The Token ROI Crisis Comes for Everyone, Anthropic Wants Chinese Open Source Banned, and Microsoft Has Its Worst Month Since 2000Time-Sensitive

SaaStr — Jason Lemkin · GTM Ops · Thought Leadership · Jul 2

Token ROI crisis is real: 5x spend increases with no corresponding revenue lift, even at well-performing companies. Board-level scrutiny now required for AI spend approval.
Cost discipline lag: 5-month delay between aggressive AI ramp (Nov-Dec 2025 agentic coding boom) and actual cost controls, suggesting companies are now in correction phase.
Open-source shift accelerating: Coinbase reduced spend 50% while increasing token usage through model routing and better defaults—signals move away from frontier models to cheaper alternatives.
Binary outcome for software companies: AI adoption is now table-stakes; companies either accelerate revenue or become irrelevant. Adobe's $500M agentic revenue announcement followed by missed quarter exemplifies the disconnect.
Maturation required: AI spend must transition from experimental/unlimited to disciplined ROI-driven allocation, similar to traditional capex governance.

Microsoft Copilot Skills in ExcelTime-Sensitive

The Signal · Productivity · Tactical How-To · Jul 2

Microsoft Copilot in Excel has evolved significantly since February with introduction of Skills feature—a capability parity move against Claude's established Skills ecosystem
21 pre-built skills now available for repeatable workflows, suggesting Microsoft is moving from conversational AI to task-specific automation in spreadsheet context
Narrative shift from dismissal to capability recognition indicates potential inflection point in enterprise adoption of AI-assisted productivity tools, though article lacks concrete implementation evidence or ROI metrics

Vercel's Andrew Qu on why agents are a new kind of softwareTime-Sensitive

Swyx · AI Eng · Practitioner Story · Jul 3

Vercel is positioning agents as a new software primitive, not just an application of LLMs—this signals infrastructure-level thinking about agent deployment
Vercel's internal tooling (MCP libraries, eve framework, skills.sh) suggests they're building the scaffolding for agent-native development, similar to how they democratized serverless
The framing of 'Vercel itself turning into an agent' indicates platform companies are reconceptualizing their own architecture around agentic patterns—watch for this architectural shift across infrastructure vendors
Andrew Qu's role (Chief of Software focused on 'frontier' technologies) reflects how tier-1 platforms are dedicating senior engineering capacity to agents—signals this is not experimental but strategic

Please stop the AI Confidence Theater

Growth Stack Mafia · Enterprise AI · Thought Leadership · Jul 2

AI-SDR market exhibits 'confidence theater'—vendors and adopters projecting certainty without substantive proof of ROI or implementation success
Contrarian positioning against prevailing bullish AI narrative; signals growing skepticism in practitioner community about AI tool effectiveness
Emerging counter-narrative to ai-sdr-adoption hype; likely to resonate with GTM leaders experiencing implementation friction or underwhelming results
Title-driven insight suggests focus on gap between marketing claims and operational reality—key tension point for mid-market GTM teams

Do you ever piss off a customer

Sales and Selling · GTM Ops · Practitioner Story · Jul 2

Top performers face unique tension: pushing back on bad customer decisions damages short-term relationships but prevents long-term claims/reputation damage
Multi-stakeholder B2B sales require different value propositions per buyer persona (architects care about design/specs, contractors care about price, end-users care about outcomes)
Integrity-driven selling creates competitive advantage in complex sales but requires confidence to disagree with customers—especially architects with end-user influence
High-growth reps are often selected for mentoring, creating opportunity to codify their contrarian approach into company culture

Agentic AI Is a Coworker And Why Every Industry Built on Phones, Forms, and Follow Ups Should Be Paying AttentionTime-Sensitive

Demand Gen Report · AI Eng · Practitioner Story · Jul 2

Ford's April 2026 co-op approval of inride Trade Agent AI as a reimbursable line item signals organizational legitimacy for agentic AI as workforce, not tooling—a critical inflection point that precedes broader economy adoption
The 'work of remembering people' (phone calls, follow-ups, confirmations) is the universal pain point across industries with customer databases—automotive, healthcare, professional services—creating massive TAM for agentic solutions that handle systematic outreach
Existing customer economics are dramatically superior ($2,500 more front-end gross, 10x response rates) but operationally impossible to execute at scale with human BDCs; agentic AI solves the execution gap that has plagued these industries for decades
Cross-industry convergence signal: A physician and a Ford dealer face identical staffing/cost problems despite operating in completely different verticals, suggesting agentic AI adoption will follow similar patterns across phone/form/follow-up industries
Timing narrative: Author positions automotive as 'early' rather than 'late' for the first time in industry history, suggesting this is a genuine inflection point rather than incremental technology adoption

Most Sales Training Is Quietly Making You Worse at Selling. The Trainers Just Don’t Have Skin in Your Game

Sales and Selling · GTM Ops · Practitioner Story · Jul 2

Sales training industry has structural misalignment: trainers profit from delivery, not rep outcomes—creating incentive to over-complicate frameworks
Rigid methodology adoption often reduces rep authenticity and effectiveness; removing prescribed 'best practices' frequently improves both naturalness and results
The 'skin in the game' principle: advice from active quota-carriers tends toward simplicity and flexibility; advice from non-quota-carriers tends toward complexity and rigidity
Reps often internalize failure when frameworks don't work, rather than questioning the framework itself—a psychological dynamic trainers benefit from
Practical test: deliberately drop one training element for 2-3 weeks and measure impact—most reps report improved performance and authenticity

Using DSPy to evaluate and improve Datasette Agent's SQL system prompts

Simon Willison · AI Eng · Practitioner Story · Jul 2

DSPy enables systematic evaluation of LLM system prompts through structured testing—moving prompt engineering from intuition to measurement
Common optimization advice ('avoid redundant API calls') can create failure modes (column-name guessing loops) that aren't obvious without evaluation traces
Practical finding: schema context completeness (including column names vs. table names only) directly impacts LLM agent reliability in SQL generation tasks
Using Claude Code with async research tasks enables rapid prototyping of LLM evaluation workflows—meta-application of AI to improve AI systems

The Five Kinds of Model Routers That Cut AI CostsTime-Sensitive

The Information · AI×GTM · Quick Take · Jul 2

Model routers are emerging as a cost-control mechanism as enterprises face rising AI model pricing and internal tokenmaxxing behavior
Five distinct router architectures exist (standalone products, cloud provider features, DIY IT solutions) suggesting the category is still fragmenting and consolidating
Task-based routing (e.g., email summarization on cheaper models vs. complex reasoning on GPT-4 class) is the primary value driver—not all AI work requires frontier models
Snowflake and Palo Alto Networks are early adopters demonstrating cost savings, signaling enterprise willingness to optimize model selection
This trend reflects broader AI infrastructure maturation: moving from 'use the best model for everything' to 'use the right model for each task'

My takeaway from Money 20/20 for your GTM teamTime-Sensitive

B2B Sales - Forrester · AI×GTM · Quick Take · Jul 2

Money20/20 Amsterdam conference surfaced 'trust' and 'agentic commerce' as dominant GTM themes in fintech
Banks have three concrete trust requirements: AI reliability, customer data/money/identity safety, and bank-level compliance
Content is incomplete/truncated—insufficient detail to extract GTM-specific insights or implementation guidance

llm-coding-agent 0.1a0

Simon Willison · AI Eng · Tool Release · Jul 2

Simon Willison built a Claude-style coding agent on his LLM library framework using agentic prompting—demonstrating that AI can autonomously scaffold projects with spec, tests, and commits
The agent implemented unrequested features (Python API class) that the creator found valuable, suggesting AI agents can exceed specification through emergent capability
Tool design matters: the agent has granular controls (--yolo, --allow patterns) for safety/approval workflows, indicating production-ready thinking for autonomous code execution
This is a working alpha (0.1a0) shipped to PyPI with real CLI and API interfaces—not a concept, showing rapid iteration velocity on agent frameworks

AI Sales Roleplay vs Manager Sales Roleplay vs Peer Practice

The Best Sales Certifications to Get in 2025 | Revenue · AI×GTM · Vendor Content · Jul 2

Sales improvement requires moving practice OUT of live deals into controlled environments where failure has no cost—AI role-play enables unlimited repetition without human resource constraints
Three formats (AI, manager-led, peer) develop different skills at different speeds; best teams use all three strategically rather than choosing one
AI role-play's core advantage is availability + consistency + volume—same buyer psychology every time, enabling 5-10x more reps per scenario than human-dependent formats
The contrarian insight: traditional sales environments force reps to develop skills at direct expense of pipeline—this is a hidden cost most orgs don't quantify

The Headcount Audit to back your AI investment decisions

The Workflow · Enterprise AI · Tactical How-To · Jul 2

AI adoption stalls not due to technology gaps but organizational ownership gaps—the initiative belongs to everyone and moves for no one
The real ROI calculation should focus on either extracting more output from existing headcount OR avoiding a hire you'd otherwise need to make
A structured 'Headcount Audit' diagnostic can identify the single most expensive repetitive workflow and match it to the right-sized AI solution (from $20 Claude to custom build) before any spend
AI investment decisions should be treated like any other capital allocation—with clear payback period calculations and benchmark metrics

How Many Sales Tools Does Your Team Actually Need in 2026?

The Best Sales Certifications to Get in 2025 | Revenue · GTM Ops · Tactical How-To · Jul 2

Tool sprawl costs $5K-$15K per integration annually in maintenance alone; most orgs underestimate this hidden expense
Context switching between 5+ tools costs reps 1+ hour daily in lost productivity (15-25 min per switch × multiple daily switches)
Consolidation to 4-6 core tools solves three simultaneous problems: data fragmentation, integration overhead, and adoption friction—not just budget
Contrarian insight: The problem isn't AI/new tools; it's that 2-3 tools in most stacks duplicate capabilities already owned, and 1-2 were never adopted post-purchase
Framework provided: Audit current stack against 'does this deliver measurable pipeline/revenue impact we can't get elsewhere?' Most tools fail this test

I end every AI session with two questions

r/ClaudeAI · Productivity · Practitioner Story · Jul 2

Two-question framework (confidence gaps + blind spots) systematically surfaces AI reasoning failures before they compound
AI models admit uncertainty ~6-7 items per session, but 25% of these represent critical gaps that could invalidate downstream work
Sam Altman's 'what am I missing' question acts as meta-check against unknown unknowns—addresses AI's tendency toward false confidence
Practical workflow hack: treating AI as unreliable narrator requiring validation rather than oracle improves output quality measurably

Understand to participate

Simon Willison · AI Eng · Thought Leadership · Jul 2

Cognitive debt is the hidden cost of AI-assisted coding: passive consumption of agent-generated changes erodes your ability to participate meaningfully in future iterations
Understanding-to-participate is a prerequisite for effective human-AI collaboration, not optional overhead—lack of fluency directly limits project velocity and creative direction
The challenge isn't whether coding agents work, but whether developers can maintain sufficient conceptual depth to guide increasingly sophisticated autonomous changes

Teaching AI to run with the turbines

MIT Technology Review AI · Enterprise AI · Practitioner Story · Jul 2

Industrial AI success requires years of foundational data infrastructure and governance BEFORE deploying agentic systems—not the reverse. Woodside's multi-year investment in predictive analytics and ML across operations enabled their current autonomous agent capabilities.
The contrarian insight: AI in high-stakes industrial environments is designed to AUGMENT human expertise, not replace operators. The 'Startup Advisor' copilot for LNG plant operations exemplifies human-AI collaboration in mission-critical workflows.
Enterprise AI maturation follows a pattern: isolated experiments → standardized platforms → governed data → repeatable deployment patterns. Organizations must rethink both technology stacks AND work processes simultaneously ('Think big, prototype small, scale fast').
The emerging narrative: Industrial AI is graduating from consumer-facing hype (chatbots, image generators) to consequential infrastructure layer. Companies that invested in operational foundations years ago are now positioned to deploy autonomous enterprise systems.

The website of the future may assemble itself for every visitorTime-Sensitive

Swyx · AI Eng · Deep Dive · Jul 2

Personalization is shifting from segment-based selection to real-time, visitor-specific page assembly powered by agentic AI systems
Adobe's 'agentic site' demonstrates the technical feasibility of intent interpretation + content retrieval + dynamic composition at scale
This represents a fundamental architectural change: from static/templated experiences to generative, context-aware web experiences built per-visitor
The 'audience of one' concept challenges traditional content management and marketing automation workflows
Implications span content strategy, technical infrastructure, and competitive differentiation for enterprise platforms

Brian Armstrong Runs 1,200 AI Agents at Coinbase. Here Is the Operating Model He Just Handed Every Founder.Time-Sensitive

The AI Corner · AI Eng · Practitioner Story · Jul 2

Coinbase has operationalized 1,200 AI agents as full-time equivalents (40-60 hour workweeks), fundamentally changing headcount economics and the team-size debate in tech
Counterintuitive quality signal: bug rates and incidents are declining per line of code shipped despite massive agent deployment—suggests AI agents improve code quality, not just velocity
Operating model shift is now replicable: Armstrong has handed founders a blueprint for rebuilding companies around AI agents rather than bolting them on as features
Revenue systems must be agent-native: Attio example shows CRM/revenue infrastructure needs redesign for AI agent workflows (83% faster triage, zero missed leads)
The productivity multiplier is real and measurable: 1,200 agents = equivalent human workforce but with better quality metrics and lower operational friction

AIEWF Daily Dispatch: Autoresearch and the tension between AI and human agencyTime-Sensitive

Swyx · AI Eng · Quick Take · Jul 2

Autoresearch represents a paradigm shift: agents maintaining and improving systems in outer loops while primary inner loops execute tasks—moving from static to self-improving architectures
Anthropic's framing of 'models are grown, not developed' signals industry movement away from waterfall AI development toward continuous discovery and adaptation patterns
The tension between AI agency and human control is becoming a design philosophy question, not just a safety concern—how much autonomy should systems have to modify themselves?

Skill engineering and the case against one-shot AI design

Swyx · AI Eng · Deep Dive · Jul 2

One-shot AI design (asking agents to redesign entire systems at once) is fundamentally flawed; iterative steering with domain-specific vocabulary is more effective
Skill engineering as emerging discipline: giving AI agents granular, human-interpretable commands (e.g., 'make bolder,' 'quieter,' 'denser') rather than monolithic prompts
Human creativity remains essential—the goal is to remove humans from execution, not ideation; AI should amplify designer intent, not replace it
Domain knowledge + context + steering mechanisms = prerequisite for capable AI agents; generic instruction-following is insufficient

[AINews] not much happened todayTime-Sensitive

Swyx · AI Eng · Quick Take · Jul 2

Claude Fable 5 relaunch triggered immediate multi-model orchestration adoption across Cursor, Devin, and Perplexity rather than single-model dependency — signaling architectural shift in AI tooling
Frontier model constraints (safety fallbacks, rate limits, cost) are driving builders toward model-combination strategies with specialized roles (reasoning vs. implementation vs. verification)
Practical outcome: developers using Fable 5 only for high-value reasoning/planning while delegating other tasks to cheaper/faster models report substantial improvement in end-to-end PR yield
Market signal: Tool consolidation accelerating as vendors rapidly integrate latest models, suggesting competitive pressure on model access and orchestration capabilities

Agent Runs now available in the Vercel MCP and CLI

Vercel Blog · AI Eng · Vendor Content · Jul 3

Vercel expanding agent observability tooling with MCP and CLI integrations for eve framework—signals platform consolidation around agent debugging/monitoring
Self-referential agent capability (agents inspecting their own runs via CLI) represents emerging pattern of agent autonomy in development workflows
Feature set (trace inspection, token usage, reasoning visibility) indicates developer demand for agent transparency—potential GTM signal for observability-first agent platforms

Microsoft's 6,000-Person AI PushTime-Sensitive

Bloomberg Technology · Enterprise AI · Quick Take · Jul 2

Microsoft is replicating Palantir's forward deployment engineer model at scale (6,000 people), signaling that enterprise AI ROI depends on implementation services, not just software
The move mirrors AWS's successful playbook—suggesting major cloud vendors are shifting from product-centric to services-centric AI go-to-market
Enterprise bottleneck is execution/integration, not AI capability availability—creates moat for vendors with deployment capacity

Tesla Caps Employee AI Spend at $200 per Week After Adoption PushTime-Sensitive

The Information · Enterprise AI · Quick Take · Jul 2

AI token consumption at scale is a material cost problem—Tesla engineers were spending thousands/week before caps, suggesting enterprise AI economics are worse than marketed
Even AI-native companies (Tesla/xAI partnership) need governance guardrails; this signals cost control will become a major enterprise AI adoption blocker
The $200/week cap with approval workflows indicates companies are moving from 'adopt AI everywhere' to 'AI as controlled resource'—a significant shift in enterprise AI strategy

How to automate Claude safely with Zapier MCP

The Zapier Blog · Productivity · Vendor Content · Jul 2

AI tool proliferation in enterprises creates governance/security blind spots that IT teams struggle to manage
MCP (Model Context Protocol) represents emerging pattern of adding governance layers to AI integrations
Zapier positioning itself as safe integration layer between Claude and enterprise tech stacks—governance-first approach