Sales is a GTM function. Marketing is a GTM function. Customer success is a GTM function. These days even product is a GTM function ask anyone running product-led growth.
Enablement? Everyone says yes. Politely. At kickoff.
So run the membership test the same three questions every other function passes without thinking. Does your work product reach the market? Do you carry a revenue number? Are you in the room when revenue decisions get made?
Marketing's asset lands in front of the buyer; it carries pipeline. Sales talks to the buyer; it carries the quota. CS talks to the buyer; it carries net retention. Product ships what the buyer touches; it carries adoption and expansion. Four functions, four buyer touchpoints, four numbers, four seats.
Enablement fails all three questions. Not narrowly. Structurally.
Either everyone is being polite, or enablement as currently plumbed is not a GTM function. It's both.
The syllogism nobody finishes
Here is a small logic exercise that reveals everything. Premise one: the CEO owns go-to-market. Nobody disputes this, GTM strategy is a board-level artifact with the CEO's name on it. Premise two: enablement is part of go-to-market. Everyone agrees politely, at kickoff.
Conclusion: the CEO owns enablement.
Say that out loud. No CEO believes it. CEOs believe they fund enablement. Ownership sounds like this: I can name its number, I would feel it inside a quarter if it vanished, and I will defend it to the board in a downturn. CEOs can do all three for demand generation and retention. For enablement they can name the line item.
A syllogism with agreeable premises and an unbelievable conclusion means one of the premises is false. Nobody is willing to say the CEO doesn't own GTM. So the room quietly drops the other one and enablement's membership turns out to be ceremonial: claimed in January at kickoff, waived in November at budget.
Check the agendas
If you want to know what an industry actually believes, ignore what it says and read its conference agendas.
Walk the main stage of any GTM conference. Pipeline math, category strategy, pricing, retention, AI in the sales motion keynote after keynote by people who owe numbers. Now count the enablement talks. When enablement appears at all, it is a side room, an afternoon slot, a booth. Meanwhile enablement built its own conferences, its own communities, its own awards, an entire parallel universe, warm and thriving and separate.
A separate room is not an insult. It is a diagnosis. Adjacency is not membership. (Hold onto the parallel universe, though. It comes back at the end of this piece as something else entirely.)
Same test, closer to home: when does enablement enter your company's GTM conversation? Twice a year budget season, when it must justify existing, and kickoff season, when it runs the show for a week and then returns the stage. The pipeline council meets weekly. Revenue planning runs quarterly. Enablement is in neither room.
None of this is disrespect. It is bookkeeping. A GTM conversation is a conversation between people who owe numbers. No number, no seat. No seat, no stage. The conference agenda is just the org chart read aloud.
The wall
So why doesn't enablement carry a number? Not because enablement people can't count. Because of where the work stops.
Every other GTM function's output reaches the market. Enablement's output terminates at the rep. The training, the certification, the battlecard, all of it is absorbed by a rep, translated through memory, and re-emitted days later inside a conversation enablement never sees. The rep is a wall between enablement and the buyer, and every question about enablement's value dies at that wall.
Why can't enablement prove revenue impact? The wall you cannot attribute what you cannot follow. Why is enablement first cut in a downturn? The wall every other function defends its budget with a revenue line; enablement defends with belief. Why does it report into sales as a cost center instead of sitting at the revenue table? The wall.
And notice where the wall puts the function in time: enablement operates before the deal, training, content, certification and after it, call reviews, win-loss analysis. It is structurally absent from the one place go-to-market actually happens: inside the deal, while it is being decided.
Nobody decided enablement wasn't GTM. The plumbing decided.
The mission was never the problem
Here is what makes this worth fixing rather than mocking: enablement's mission make the whole team able to win is arguably the most go-to-market mission in the building. Every dollar of quota flows through a moment enablement tried to prepare someone for. The people who chose this work chose leverage: help one rep, help every deal that rep ever touches.
The mission was never the problem. The era was. For thirty years, work that reached the market required a human courier, and enablement got the courier model: prepare the rep, hope the preparation survives the trip. Measured against what was possible, enablement wasn't failing. It was operating at the ceiling of its plumbing.
The constraint changed. In the Agentic Era, work can cross the wall.
The adjustment can arrive inside the live deal instead of inside a course. The comparison sheet can land in the buyer's deal room instead of a content library. The thread from program to practice to call to pipeline can be traced instead of believed which means the function's work can carry a number for the first time: not completions, not certifications, but revenue capacity per rep, unlocked and attributable.
And when the work crosses the wall, the answer to the title question flips. The function that decides how well every rep executes every deal isn't a GTM function. It is the function that determines what the rest of go-to-market is worth. Many of the people already doing this work have started calling themselves Revenue Activators same mission, re-plumbed to reach the deal.
And now the parallel universe returns as the head start it actually is. The function that built its own conferences, its own communities, its own awards built the one thing every other transition has to assemble from scratch: its people, already organized, already talking to each other every week. The separate room was never the problem. The community never lacked a room. It lacked a number.
Run the syllogism again
Now go back to the logic exercise that broke, and change one word.
Premise one: the CEO owns go-to-market. Premise two: Revenue Activation unlocking revenue capacity from the team you already have is part of go-to-market.
Conclusion: the CEO owns Revenue Activation.
Say that out loud. Nothing breaks.
Find the CEO willing to disown it the one who will stand in front of a board and say “I do not own unlocking revenue from the team I already pay for.” The sentence refuses to be said. The same test that quietly exiled enablement from GTM cannot even generate discomfort here, because there is nothing in the claim a CEO could push away.
Same mission. Same logic. Opposite result. The difference is what the words claim. “Enablement” names an activity pointed at employees and activities get delegated, budgeted, and cut. “Revenue Activation” names an outcome pointed at the market and outcomes are the things CEOs own. You cannot own a support function. You can only fund it.
The syllogism was never broken. It was waiting for a premise worth owning.
The seat
When the work carries a capacity number the CEO can read, the CEO owns it the way they own demand and retention not as a line item, but as an instrument. Nobody will have to argue for the Revenue Activator's seat at the revenue table. Nobody argues anyone into that room. The number argues.
So: is enablement a GTM function? As plumbed no, and every conference agenda, budget cycle, and unfinished syllogism has been telling us so for years. Re-plumbed and renamed for what it actually does it doesn't join the GTM conversation.
It becomes what the conversation is about.
If this piece describes you, the room where the shift is being worked out already exists the people re-plumbing the mission call themselves Revenue Activators, and they gather at revenueactivator.ai Bring the mission. The number is waiting.
.avif)
