The Lab is live. 15 essays from the frontier of AI-native GTM.

Read

Article

v1.0

Building an AI-native GTM operation

Why adding AI to existing tasks leaves the operating model unchanged, and what an Operating Layer needs to connect instead.

Daniel Remedios

Daniel Remedios

CEO & Founder

October 16, 2026

2

mins

If you were building your GTM organisation today, with AI available from day one, would you build anything that resembling the operation you have now?

📖 A Friday thought, and a five-minute ready for the weekend.

Over the last two years, we've spoken with hundreds of GTM leaders, explored countless use cases and spent thousands of hours building towards an AI-native operating model.

And one observation keeps coming back:

We're adding AI everywhere. But we're largely running the same operation.

→ Research accounts faster
→ Writing emails faster
→ Summarising meetings faster
→ Generating reports faster

All useful. All improvements.

But the underlying work hasn't fundamentally changed.

People still have to connect the evidence, maintain context, interpret what's happening, decide what matters and coordinate what happens next.

AI has made individual tasks faster. It hasn't necessarily made the organisation more intelligent.

🧠 That led us to a different question:

What if we stopped adding AI to the existing GTM operation and designed the operation around AI instead?

We started imagining what that would actually require:

→ An operation that continuously understands every prospect, account, deal and customer
→ Shared context and memory that persists across Sales, Marketing and Customer Success
→ Intelligence that identifies what matters, reasons about the next best action and involves humans where judgement is needed
→ A system that learns from every decision, action and outcome

Not simply better tools for people to operate.

An operation that understands, decides, acts and learns.
Continuously.

And here's the architectural consequence.

To make that possible, you need something the traditional GTM stack as never designed to provide.

An Operating Layer for AI.

A shared foundation connecting evidence, context, memory, decisions and actions across the entire commercial organisation.

This is the distinction we've spent two years exploring between AI-assisted and AI-native GTM.

👉 We've now distilled 15 essays from The Lab into a five-minute field guide:

From AI-assisted → AI-native GTM.

The carousel below is a preview of the thinking.

👇 If you’re a CEO, CRO or RevOps leader exploring what it means to build an AI-native operation, I’d love to compare notes
💬 Comment or DM me and I’ll share the full five-minute read

Cover of The Lab field guide, ‘From AI-assisted to AI-native GTM,’ with a subtitle describing a five-minute guide to the operating model beneath commercial work; Revenue Labs and London appear in the footer.
Foreword by Daniel Remedios describing conversations with GTM leaders, faster AI-assisted tasks, and the question of designing the whole operation around AI; his name and Revenue Labs founder title appear near the bottom.
A two-by-two chart compares SaaS-native GTM, AI-assisted SaaS, and an AI-native GTM system across execution speed and operating model; the AI-native quadrant is purple and lists Context, Memory, Skills, Agents, Decision Traces, and Learning.
Text page headed ‘More AI. Same operating model.’ It describes faster research, email drafting, and call summaries while noting that people still work out what is happening and coordinate what happens next.
Three stacked panels compare SaaS-native, AI-assisted, and AI-native GTM: people connect systems, AI adds faster outputs, and a purple shared operating layer connects people with CRM, email, calls, and success systems.
A four-column maturity test compares SaaS-native, AI-assisted, AI-native, and self-upgrading systems, followed by links to essays titled ‘The AI-Native Operating Model’ and ‘The AI-Native GTM Maturity Curve.’
Text page headed ‘The work beneath the work.’ A Monday pipeline-review example describes a £200,000 CRM deal, a manager checking calls, email, and Slack, and the term ‘Reconstruction Tax.’
Two diagrams compare evidence from CRM, calls, email, Slack, product usage, and support being separately reconstructed by five roles with the same sources feeding a purple Shared State used by those roles; a bottom row lists time, latency, loss, variance, and repetition.
Text panel explains that connecting tools does not fix repeated context reconstruction, followed by links to ‘The Missing Operating Layer’ and ‘The Economics of Coordination.’
Closing page asks whether the reader wants to move from AI-assisted to AI-native GTM and invites them to send a direct message for the five-minute read.

Originally posted on LinkedIn

v1.0

This essay is versioned. Where our thinking develops materially, we will update the version and explain why - the revision history is preserved, not polished away.