If you work in go-to-market — sales, partnerships, field strategy, enablement — you've probably noticed that your AI-augmented output now spans territory that used to belong to 4-5 separate functions. You can synthesize market signal across dozens of accounts, generate competitive positioning, model acquisition economics, and draft partnership frameworks — all in the same week, all by yourself.
The problem isn't capability. The problem is that your role was designed before any of this was possible.
The Relay Architecture
Here's how go-to-market has historically worked inside most technology companies:
Engineering builds → Product defines → Go-to-market carries it to customers.
The go-to-market function sits downstream. It doesn't decide what gets built, how it's priced, or which markets to enter. It executes against those decisions. The value was in translation and distribution — making complex things legible to buyers, then relaying buyer feedback back upstream.
In practice, this means:
- Strategy teams synthesize market signal (not you)
- Product marketing owns positioning (not you)
- Finance models acquisition economics (not you)
- Corporate development structures partnerships (not you)
- Product management decides what goes on the roadmap (not you)
Your job? Cover your accounts. Generate pipeline. Close deals. Relay feedback. Repeat.
The a16z framework for scaling go-to-market orgs describes this architecture clearly: go-to-market leaders "operate alongside a small team — as both a player and a coach — to do whatever it takes to close deals or reach customers." The scope is execution, not strategy. The decisions happen elsewhere.
Why It Was Designed This Way
This wasn't arbitrary. Pre-AI, the relay model made sense because human bandwidth was the binding constraint.
One person couldn't simultaneously track 50 accounts, generate positioning variations, model unit economics, negotiate partnership terms, AND synthesize field evidence for product roadmap decisions. That workload required specialization. You needed a marketing team, a strategy team, a rev ops team, a partner team, and a product team — each owning their slice.
The relay architecture was a rational response to bandwidth scarcity. Every layer between an idea and its execution existed because no single person could span the full loop.
The Collapse
AI removes the bandwidth constraint. Not entirely — but enough to break the relay model's assumptions.
A Norwest Venture Partners analysis of the emerging "GTM Engineer" role documents this collapse: one person now "owns the knowledge base, the systems layer, how agents interact with each other, and the entire lead flow process." Their benchmark data shows companies using AI tools are 3x more likely to have raised revenue targets, while SDR and BDR hiring is declining.
Clay, the data enrichment platform, frames their version more sharply: the GTM Engineer "collapses SDR, AE, and SE roles into one." Three specialized relay nodes become one decision-maker with AI agents handling execution.
What one AI-native person in a go-to-market function can now span:
| Previously Required | Now Possible Solo |
|---|---|
| Strategy team synthesizes market signal | AI scans 50+ accounts, surfaces patterns in real-time |
| Marketing + agencies generate positioning | One person generates, tests, iterates positioning daily |
| RevOps/Finance models acquisition economics | AI models unit economics on the fly |
| BD + legal drafts partnership frameworks | One person structures, negotiates, iterates frameworks |
| PM synthesizes field feedback into roadmap | Quantified evidence delivered directly to product leadership |
The relay function collapses into a decision loop: sense market → synthesize → decide → execute → measure → iterate. One person. One loop. AI handles the execution layer.
The Structural Gap
Here's what's actually happening: the person evolved, but the container didn't.
Microsoft's 2026 Work Trend Index calls this phenomenon "blocked agency" — employees whose AI-augmented capabilities exceed what their role definition allows them to act on. Among AI users surveyed, 58% say they're producing work they couldn't have done a year ago. But only 13% say they're rewarded for reinventing their work.
Jared Spataro, Microsoft's CMO for AI at Work, puts it directly: "When the system itself has a governor on the speed that it can go, it doesn't matter how fast an individual can run."
A Workday study from January 2026 frames the same gap: "Employees are using 2025 tools inside 2015 job structures." Less than half of roles have been updated to reflect AI capabilities.
BCG's June 2026 research quantifies the tension: 67% of regular AI users report improved job satisfaction, but 41% simultaneously report increased cognitive load. They call it the "joy paradox" — AI makes the work better while making the role container feel more constraining.
For someone in go-to-market, this lands as a specific frustration: you're operating across product influence, market strategy, customer acquisition, and partnerships — but your decision rights, metrics, and scope are still drawn around the relay function. You're measured on pipeline generated, not on strategic decisions made.
What Needs to Change
The question isn't whether go-to-market teams should adopt AI tools. Gartner projects 95% of seller research workflows will begin with AI by 2027, up from less than 20% in 2024. Adoption is happening.
The question is whether organizations will redesign go-to-market roles to match the expanded agency those tools unlock.
The World Economic Forum frames the destination clearly: "Human value moves to the work around execution — context, responsibility, trust, and decision-making authority."
For go-to-market specifically, that means transitioning from:
Relay (carry decisions downstream, relay feedback upstream) → Decision (synthesize signal, make strategic calls, own outcomes across product, market, and customer dimensions)
The expanded scope isn't "do the same work faster." It's a category shift from execution against someone else's decisions to making the decisions yourself — across product influence, market strategy, customer acquisition, and partnerships.
BCG warns that 50-55% of US jobs will be reshaped by AI in the next 2-3 years. For go-to-market roles, "reshaped" doesn't mean automated away. It means the scope explodes while the org chart stays frozen.
The Unresolved Thing
I don't have a clean answer for how to navigate this transition inside an existing organization. The research is clear on what needs to happen — role redesign, expanded decision rights, new metrics. But the practical path from "I'm operating at expanded scope" to "my org acknowledges and structures for that scope" remains unsolved.
The Augment Code survey found that only 19 of 219 engineering leaders have updated role definitions to match jobs that have fundamentally changed. The words respondents used to describe how they feel: "excited, anxious, invigorated" — all at the same time. That tracks.
What I know: the AI-native practitioners who are furthest ahead on the adoption curve — Microsoft's data puts this group at roughly 16% of the workforce — are the ones feeling this tension most acutely. The capability is real. The organizational permission isn't.
The relay model served its purpose when bandwidth was the constraint. Bandwidth isn't the constraint anymore. The constraint is organizational imagination.
