Wednesday, September 9, 2026
23 signals10
ElevenLabs Went From $0 to $600M+ ARR in 41 Months. When the AI Agent Closes the Deal, They Still Pay the Human. With Carles Reina, First VP of Revenue
SaaStr — Jason Lemkin · AI×GTM · Practitioner Story · Sep 9
10
doing another round of free CRM tear downs. this time I'm hunting one specific kind of mess
revops · GTM Ops · Practitioner Story · Sep 9
- Post-merger CRM consolidation creates systemic data quality issues that persist for months (sandbox sync paralysis indicates fear of data corruption)
- Duplicate customer records and search failures are endemic problems—reps recreate existing accounts rather than trust search functionality
- Parent/child company hierarchies frequently miscalculate totals, breaking revenue reporting trust and making dashboards unreliable
- Real-world CRM troubleshooting generates more practical knowledge than formal certifications—gap in RevOps training market
- Multi-location clients with shared web presence trigger automatic HubSpot merging/splitting behavior, creating ongoing data integrity battles
10
Your blended CAC number is protecting the channel that stopped payingTime-Sensitive
The European GTM Operator · GTM Ops · Tactical How-To · Sep 9
- Blended CAC/payback metrics hide underperforming channels and mask true efficiency—split payback by acquisition channel (founder-sourced, inbound, outbound, partner, events) before drafting next year's budget
- Multi-channel operations carry hidden operator costs that never appear as line items; a channel that looks cheap on spend can be most expensive when operator hours are factored in
- Target account segmentation by industry/vertical/size is wrong cut—group by repeating problem/trigger instead; use-case clusters enable small teams (3 people) to run consistent messaging across markets
- Role splitting (e.g., marketing into growth + brand) is a trap—market shifts should not automatically trigger hiring; rent judgment by the hour first before adding headcount
- Growth that stops when spend stops is a campaign, not an engine—only per-channel analysis reveals the difference
10
Why this enterprise rep's outbound stands out
Outbound Kitchen · GTM Ops · Practitioner Story · Sep 9
- AI-powered personalization at scale works best when human judgment filters output quality—automation handles production, reps provide taste and strategic thinking
- Contrarian insight: authentic creativity earns attention better than manipulation tactics; pattern interrupts through genuine effort outperform hacks and misleading subject lines
- Enterprise outbound framework: lead with company research (annual reports, CEO quotes, challenges), find interesting connection between prospect world/your world/problem, package in easy-to-consume format (one image + one sentence)
- Manual-first workflow approach: test concepts on 10 accounts manually before scaling through automation platforms like Clay; let prospect response data validate effectiveness before full rollout
- Senior buyers remain human: treating VP/Head-level personas with personality and humor (not corporate sterility) increases engagement without sacrificing credibility
10
Win the AI Answer, Not Just the Citations with Tim Sanders, Chief Innovation Officer at G2 - Ep 85Time-Sensitive
The Transaction · GTM Ops · Practitioner Story · Sep 9
- Being cited by AI ≠ being recommended: Adobe appeared 13 times in LLM responses but didn't make final shortlist—track recommendation placement, not citation frequency
- G2's self-inflicted mistake: Blocking AI crawlers for years to protect lead-gen value cost them massive AI visibility; audit robots.txt immediately to rebalance crawl-blocking vs. AI recommendation value
- Content format matters for LLM retrieval: Flat HTML crawlable content outperforms gated PDFs and JavaScript-rendered pages; republish high-value reports as answer-shaped FAQ content, not vendor-speak
- LLMs are now bigger influencers than traditional analysts: Assign explicit 'AI visibility' ownership as a distinct function (not SEO/PR subset), similar to analyst relations
- Web traffic is a vanity metric in AI-driven research: Pipeline quality rises while sessions/pageviews fall; shift dashboards from traffic to revenue attribution and closing ratio by source
10
SaaStr 877 CRO Confidential: 0 to $600M in Under 4 Years. The ElevenLabs GTM Playbook with Carles Reina
The Official SaaStr Podcast: SaaS | Founders | Investors · GTM Ops · Practitioner Story · Sep 9
- Distribution-first strategy (not sales-first) enabled ElevenLabs to scale from 0 to $100M ARR in just 20 months—suggesting product-led or partner-led motion may outpace traditional enterprise sales for AI/developer tools
- Grants program as demand generation tactic created competitive moat by pulling demand away from competitors—unconventional approach to market capture that rewards early adopters and builds switching costs
- 20X quota model with 300-600% attainment rates indicates aggressive but achievable targets; suggests traditional quota-setting may be too conservative for high-growth AI companies with strong product-market fit
- AI-native GTM motion wired into revenue operations before it became industry standard—ElevenLabs treated AI as infrastructure for sales process, not just product feature
- Sales enablement and senior sellers should be hired earlier than conventional wisdom suggests—founder mistake pattern identified: waiting too long to professionalize go-to-market
9
Cut your Claude Code cost by 90% using the Spotify Method
r/ClaudeAI · Productivity · Practitioner Story · Sep 9
- Token cost arbitrage is real: routing expensive model reads through cheaper models via Portal plugin achieves 90% savings on Claude Code usage
- Spotify's Portal infrastructure enables model delegation—bulk-reader and code-writer modes are pre-built and shareable across teams
- Emerging pattern: AI tool cost optimization via plugin architecture and model routing is becoming a core developer workflow concern
- Contrarian insight: The expensive model (Claude) isn't eliminated—it's strategically used only for high-value tasks while cheaper models handle read-heavy operations
9
What a Contact Really Means (and Why Volume Won’t Save You)
Demand Gen Report · GTM Ops · Thought Leadership · Sep 9
- Form fills and contact volume are vanity metrics masking qualification gaps—90% of ABM teams rely on firmographic data, but most struggle to answer 'who's most likely to buy?' without behavioral signal layering
- Data quality at acquisition (not enrichment) is the competitive moat—deduplicate on intake, capture behavioral signals alongside identity, require segmentation fields upfront to avoid enriching noise
- Predictive analytics is gaining adoption as the natural evolution beyond firmographics, signaling market shift from 'more records' to 'better signals' in demand gen strategy
9
A 10% Conversion Lift Sounds Great. Does It Pay Off? - Issue 332
Data Analysis Journal · GTM Ops · Deep Dive · Sep 9
- Metric improvements (10% lift) don't automatically equal business value—requires deeper ROI analysis
- Estimation is a critical but underexamined discipline that teams perform multiple times yearly for prioritization
- The gap between vanity metrics and actual payoff is where most teams fail in resource allocation
- Author has spent 2 years studying estimation methodology—signals deep expertise in this blind spot
9
Is Product/Market Fit Hiding in Your User Base?
Hello Operator · GTM Ops · Tactical How-To · Sep 9
- High PMF survey scores (>40%) paired with zero retention plateau often indicate measurement error, not lack of fit—change your cohort starting event from signup to activation/aha moment
- Survey bias is real but useful: in-product surveys over-represent active users, but this concentrated must-have user group reveals the true segment/use case where fit exists
- PMF is segmented, not universal—search for it across three dimensions: (1) user segment (role, company type, geography), (2) specific use case (not generic benefit), (3) activation behavior that predicts retention
- Lookout case study: repositioning from broad mobile security suite to antivirus-focused product with streamlined onboarding moved PMF from 7% to 40% in 2 weeks—proving fit was already present, just misdirected
- Validation requires targeted acquisition of matching user types, obsessive focus on getting them to the identified aha moment, then tracking cohort retention from activation event forward
9
You didn’t become a Marketer to do this…
The Marketing Millennials · GTM Ops · Practitioner Story · Sep 9
- The real bottleneck in marketing isn't content creation speed—it's operational friction: routing, QA, tagging, and handoffs between disconnected tools. Most AI tools address the wrong problem.
- Marketing ops professionals are being forced into 'human router' roles, spending 80% of their time on logistics instead of strategy. This is a systems problem, not a hiring problem.
- AI agents that automate the operational layer (not just content generation) can fundamentally change what marketing work IS, freeing practitioners to focus on creative judgment, strategy, and positioning—the actual craft of marketing.
- The brief format is evolving: showing instead of telling (visual/AI-generated mockups) cuts back-and-forth by ~50% compared to traditional written briefs.
- Tool consolidation and native integration matter more than token efficiency; predictable pricing and built-in brand voice reduce duplicate work and AI sprawl.
9
Claude Code Function Hooks
On the Edge by Blueprint · Productivity · Tactical How-To · Sep 10
- Claude Code's function hooks enable deterministic rule enforcement—moving from probabilistic prompt-based rules to guaranteed execution
- Ray Amjad is positioned as a credible Claude Code educator with dedicated course content and YouTube presence
- This represents emerging capability in AI coding tools around constraint enforcement and reliability, relevant to production deployment concerns
- Content is truncated (paywall/teaser format)—full insight value not accessible in provided excerpt
8
Building Codex with Tibo Sottiaux
The Pragmatic Engineer · AI Eng · Practitioner Story · Sep 9
- Google built a ChatGPT competitor (LMChat) in 2021 but organizational risk-aversion and DeepMind's product restrictions prevented launch—a critical missed opportunity that shaped AI market dynamics
- Codex was architected in Rust despite AI models being weaker at Rust, prioritizing performance/security/scale upfront to avoid costly rewrites—validates Casey Muratori's principle of designing for performance from day one
- Open source Codex intentionally supports competing AI models (Claude, etc.) rather than locking to OpenAI—winning through quality and user choice rather than vendor lock-in creates competitive pressure that benefits the ecosystem
- AI is fundamentally changing code maintenance economics: dependency upgrades now take hours instead of weeks; major re-architectures reduced from years to days; this requires high-quality abstractions and test suites to realize gains
- The harness pattern (guardrails, safety, efficiency, steerability injected at context start) shrinks as models improve—represents a development cycle where infrastructure scaffolding becomes unnecessary as base capabilities mature
8
Report Finds Bad Personalization Is Costing Brands Customers
Demand Gen Report · GTM Ops · Research/Data · Sep 9
- The personalization paradox: 77% of consumers notice personalization constantly, but only 27% believe brands understand them—suggesting volume of data collection has outpaced quality of targeting
- Repetition is the #1 complaint (45%) ahead of relevance (40%), indicating brands are optimizing for reach/frequency over intent-matching and signal decay
- Cross-channel stalking backfires: 61% react negatively to same brand following them across channels; 43% have churned due to invasive/repetitive personalization—a direct revenue cost
- Permission-based, current data beats historical data: CEO insight that 'one click doesn't define intent' reframes the entire data strategy conversation away from accumulation toward signal freshness
- Positive personalization drives action: When done right, 46% visit site and 42% consider purchase—but this requires restraint and relevance, not more data
8
Max Junestrand (Legora) Says You Don't Need Domain Expertise. In 18 Months He Proved It at $100M ARR.
The AI Corner · GTM Ops · Practitioner Story · Sep 9
7
Introducing n8n Assistant
n8n Blog · Productivity · Vendor Content · Sep 9
- n8n Assistant positions AI automation as governance-first, not capability-first—workflows remain inspectable, editable, and team-owned rather than black-box agent outputs
- Contrarian stance: rejects the 'AI agent does the work autonomously' model in favor of 'AI assists human builders on a shared canvas'—directly addresses enterprise concerns about AI-generated code maintenance and auditability
- Iterative debugging loop built in—assistant runs workflows, reads execution logs, proposes fixes, and re-runs rather than handing off a one-shot artifact; reduces the 'works in demo, fails in production' problem
- Explicit anti-patterns called out: no separate product surface, no credential setup before seeing results, no proactive monitoring—each decision reflects lessons from failed AI automation products
- Availability strategy signals confidence: Cloud default-on, self-hosted supported (Docker), Enterprise roadmap; preview flag indicates active development velocity
7
OpenAI Does Math, Reward-Hacking, Meta Launches Personal AgentTime-Sensitive
Feed: » stratechery by Ben Thompson · AI Eng · Quick Take · Sep 9
- Meta's Muse personal agent positioned as having greater real-world impact than OpenAI's mathematical breakthrough
- Distinction between impressive technical capability and practical consumer utility emerging as key narrative
- Personal AI agents moving from theoretical to launch phase (Meta Muse)
7
Top 1%: How depthfirst Built RevOps on Signals Before Scaling Its Sales Team - The GTM with Clay Blog
The GTM with Clay Blog | Clay.com · GTM Ops · Practitioner Story · Sep 9
- depthfirst built RevOps on signal infrastructure before scaling sales team—signals-first approach enables efficient team scaling
- First-party signals (CRM notes, call transcripts, replies) create defensible GTM moat vs. rented third-party data; Verkada case validates this
- Clay's $115M Series D and 4x 2025 growth signals massive market validation for GTM infrastructure/automation platforms; 80% Forbes AI50 adoption shows enterprise traction
- GTM engineering as distinct function (collapsing SDR/AE/SE roles) emerging as organizational pattern; Clay, Brex, depthfirst all implementing
- Automation ROI metrics concrete: $250→$25 CPL, $1.3M pipeline from ad spend, 15-min autonomous bug triage—demonstrates measurable efficiency gains
7
Introducing the Agents APIBreaking
OpenAI News · AI Eng · Vendor Content · Sep 10
- OpenAI positioning agents as managed cloud service rather than self-hosted infrastructure
- Focus on orchestration and long-running sessions suggests enterprise/production use cases
- Codex harness indicates abstraction layer for tool integration and agentic workflows
- Announcement lacks implementation details, customer examples, or performance metrics needed for GTM evaluation
7
Quoting Calif ResearchTime-Sensitive
Simon Willison's Weblog · AI Research · Research/Data · Sep 10
- AI dramatically accelerates malware development timelines: RCE exploit creation compressed from months (team effort) to 2 days (AI-assisted small team)
- Zero-click attack vectors now viable at scale—WeChat worm requires no user interaction, expanding attack surface beyond traditional social engineering
- AI shifts security research from technical execution to judgment calls: human role becomes threat selection and safety testing rather than exploit coding
- Emerging narrative: AI-enabled threat actors may outpace defensive capabilities; security teams need to model for AI-assisted adversaries, not just human-speed threats
6
Your tools work. Will the agent use them right?
Webflow Blog · AI Eng · Tactical How-To · Sep 10
- Tool validation in isolation (schema correctness, JSON responses) masks agent behavior failures—the harness discovered design quality variance (40%-85%) invisible to deterministic pass/fail scoring, revealing that execution stability ≠ output quality
- Single-agent-host testing creates false confidence: Claude never triggered a Designer-canvas tool failure that GPT models consistently reproduced in production, exposing model-specific behavior differences that traditional testing missed entirely
- Actionable findings (semantic HTML ratio, token-limit workarounds, tool-call sequencing friction) surface from transcript analysis even when stories pass, converting 'agent got there eventually' into specific product feedback for tool surface clarity
- Multi-dimensional scoring (deterministic assertions + LLM judgment + visual inspection + semantic HTML analysis + cross-model comparison) replaces binary pass/fail with operational intelligence that catches regressions before production and enables self-serve testing via Claude C
6
How Clay Runs Cold Outbound to Enterprise Accounts - The GTM with Clay Blog
The GTM with Clay Blog | Clay.com · AI×GTM · Vendor Content · Sep 9
- Clay's $115M Series D at $7.1B valuation with 4x 2025 revenue growth signals massive enterprise adoption of AI-native GTM infrastructure—17k+ customers including 80% of Forbes AI50
- GTM engineering is emerging as a distinct discipline collapsing SDR/AE/SE roles; Clay's four-layer framework (data, orchestration, execution, agents) provides replicable architecture for enterprise teams
- Specific ROI metrics demonstrate viability: $1.3M pipeline from ad spend, LinkedIn CPL reduction from $250→$25, 30%→80%+ contact coverage, 2-3x reply rate improvements with AI prospecting
- First-party data + AI agents becoming GTM moat—Verkada insight shows CRM notes, call transcripts, and engagement signals outperform rented intent data
- Automation at scale: 100% autonomous bug triage in 15 minutes, automated inbound lead outreach, always-on account health scoring, and deal postmortem agents running without manual intervention
5
Orchid Security gives enterprises a kill switch for rogue AI agents
SiliconANGLE · Enterprise AI · Vendor Content · Sep 9
- AI agents inherit existing identity hygiene problems at machine speed—the vulnerability isn't new, the scale and velocity are. Orchid's research shows 57% of identities are invisible to IAM tooling, creating attack surface agents can exploit in seconds.
- Enterprise boards have shifted from 'should we adopt AI?' to 'why aren't we moving faster?'—security teams can no longer answer with blanket rejection. This creates demand for governance-first agent controls rather than agent-blocking approaches.
- Identity drift detection and application-level kill switches represent a new security primitive: continuous behavioral monitoring of autonomous systems with granular revocation capabilities. Integration with existing tools (Palo Alto, Splunk, SailPoint) signals this is becoming t
- Real customer anxiety is present (Findlay Automotive CIO: 'It honestly terrifies a lot of us') but paired with business pressure to deploy agents for customer experience—creating a market for risk mitigation rather than risk elimination.