Blog

GTM is not a synonym for sales

Beth Yehaskel · August 21, 2026

In the last twelve months, "GTM" has quietly become a synonym for "sales."

GTM team, meaning the sales team. GTM leader, meaning an account executive. GTM Ops, meaning sales ops. It happened without anyone deciding it, the way most expensive mistakes do.

Language is not decoration. What we name is what we fund. When "GTM" means "sales," the budget, the tooling, the headcount, and the leadership attention all flow to the top of the funnel, and the rest of the revenue system runs on whatever is left.

The bucket is leaking, and the leaks are growing

While everyone's attention is pulled back to the top of the funnel, the retention numbers have been drifting the wrong way. Median gross revenue retention has slipped from roughly 90 percent to 88 percent over three years, and median net revenue retention sits at about 101 percent, according to Benchmarkit. Two points of GRR sounds small until you compound it across a customer base and three years.

Meanwhile the growth is coming from the customers we already have. Expansion accounts for about 67 percent of new ARR at companies above $100M ARR, and 58 percent at $50M to $100M. And it costs about $2 to acquire a dollar of new-customer ARR against about $1 for a dollar of expansion ARR.

So the cheaper, larger source of growth is post-sale, and it is the part we keep leaving out of the definition of GTM.

Even the newest job title tells the story

"GTM Engineer" is a title that barely existed two years ago. Henley Wing Chiu at Bloomberry analyzed 1,000 GTM Engineer job postings and found that nine of the ten core responsibilities also appear in RevOps Engineer postings. The one thing that sets them apart is a priority on outbound prospecting. Hardly a new role, and hardly a definition of go-to-market. It is sales ops with a fresh name and a narrower brief.

Seven functions, one broken promise

Here is why the GTM system has to be more than sales. This is how things often move:

1. Sales commits to a capability that technically exists.
2. Implementation discovers it needs six weeks of services nobody scoped.
3. Customer success inherits a customer who never reached first value.
4. Support absorbs the ticket volume, quarter after quarter.
5. Product never hears why, because none of that data crosses a system boundary.
6. The account churns at month fourteen.
7. Marketing loses the case study it was counting on for next year's pipeline.

Seven functions. One broken promise. And yet sales hit quota, so that team goes to club.

Nothing in that chain shows up in a sales dashboard. Every handoff in it is a place where the revenue system leaks, and every one of them is invisible if "GTM" stops at the closed-won date.

What to do about it

Start by drawing the system as it actually runs, from first touch through renewal and expansion, with the handoffs between functions marked. Most leadership teams have never seen this on one page, and the picture alone changes the conversation about where the next dollar should go.

Then look at where the money and the attention are going against where the growth is coming from. If two thirds of new ARR is expansion and two thirds of the investment is acquisition, that is not a strategy. It is a naming problem that became a funding problem.

I have been calling it a GTM system for a few years now, and it still does not fully land. If you have found a cleaner way to talk about the whole thing, I would like to hear it.

← All posts