The Go-To-Market Model

The most expensive slide I ever watched get approved had one word on it: Enterprise. The plan was to hire six field account executives, loaded at roughly $300K each, and point them at a product that sold for about $9K a year (numbers rounded, but close to what I was staring at). Nobody in the room did the division. A $300K seller carrying a $9K product has to win and keep something like 33 accounts a year just to cover their own cost, before a dollar of margin, before marketing spend, before the solutions engineer they will ask for on the second call. The motion could not pay for itself at that price, and no amount of sales coaching was going to bend the arithmetic. We were about to bolt a pit crew onto a bicycle.

That is the mistake the GTM Model exists to prevent. In The Growth Model we placed a company on the S-curve and named the twelve revenue breakpoints. Breakpoint 4 is the GTM Model, and Revenue Architecture puts it at the very top of the six-model stack: the one layer operators touch every day. Its whole job is to answer one question before anyone gets hired: which motions does the math allow?

One chart picks the motion

Two numbers select a motion, and only two: the average recurring ACV a customer produces per year, and how many customers or deals you have to serve per year to reach your ARR target. Plot ACV on the X axis and customers-per-year on the Y axis, both on a log scale, and every software business falls somewhere along one downward-sloping band. A $50-a-year product needs 100,000 paying customers to reach $5M ARR, so it can only ever be served by the product itself. A $500K-a-year product needs ten, so it gets a team. ACV sets the ceiling on what you can spend per customer, and spend-per-customer is the whole definition of a motion.

Segment is not the motion

It is tempting to read the X axis as “company size” and stop there. Do not. Revenue Architecture is explicit that a market segment (consumer, pro-user, SMB, mid-market, enterprise, Fortune 500) is a different axis from the motion. A 40-person startup can sign a $120K deal that needs a full field motion. A division of a Fortune 500 can swipe a card for a $40-a-month seat through pure self-serve and never speak to a human. Segment describes who the buyer is. Motion describes how much it costs you to find, win, and keep them. You sell the deal, not the logo, and the deal sits at a point on the map that its ACV and volume decide.

Five touches, one operating system

The taxonomy that unifies the whole map (credited in the book to David Skok) is the five touch motions: No, Low, Medium, High, Dedicated. Their power is that they cut across marketing, sales, and customer success at the same time. A No-Touch customer is marketed to by the product, sells themselves, and gets served by a help center. A Dedicated-Touch account has a named marketing program, a named-account sales team, and a CSM who reports up to an executive. Same five bands, three functions, one shared language. Each motion also runs on a different growth engine, so picking the motion also picks what your teams have to be good at.

Figures are representative anchors from Revenue Architecture (motion engines, Fig 10.10 cost-to-serve, Table 10.10 GRR targets), not a forecast. Read the table as one continuous arc: every step up the touch ladder buys you a larger deal and charges you an order of magnitude more to serve it.

Cost has to match lifetime revenue, not first-year ACV

Two traps live in that last column. The first: cost-to-serve rises exponentially, not linearly, as you climb the ladder. Roughly $10 to serve a No-Touch customer in year one, $100 Low, $1,000 Medium, $10,000 High, and north of $100,000 Dedicated. Every human you insert into the motion multiplies cost five to twenty times. So the real question is never “can this rep close the deal,” it is “does the lifetime revenue of the customer clear the cost of the motion that won them.”

The rule Revenue Architecture gives is clean. A motion is sustainable when total GTM cost (acquisition plus retention plus expansion) sits at or below about 20% of the revenue the customer produces over your chosen horizon. Above 50% you are lighting money on fire. Between 40 and 50% is a path-to-sustainable you have to actively repair.

The trap most operators fall into is selecting the motion on first-year ACV. Compute LTV forward instead: project ARR out over the horizon with retention and expansion compounding, then sum it. A $15K deal that expands to $60K over three years can fund a higher-touch motion that a static $15K never could, which is why the book says to base the motion on multi-year ACV including NRR. Two roles show up to run the expansion side of that math: the Account Manager (about $180K OTE, carrying hundreds of accounts) and, for the seven-figure accounts, the Strategic Account Manager (north of $1M OTE).

Durability is GRR by motion

The Growth Model chapter ended in the durability phase, where growth comes from customers you already have. The GTM Model gives durability a number, and the number is GRR, not NRR. NRR flatters you: a 5 to 7% annual price increase can hold NRR above 100% while customers quietly walk out the back. GRR cannot be dressed up that way, so it is the honest durability metric, and the target rises with touch (and therefore with ACV): No 80%, Low 85%, Medium 90%, High 95%, Dedicated 98%. The logic is symmetrical with cost-to-serve. If you spend $100,000 a year to keep a Dedicated account, it had better not churn. A High-Touch motion sitting at 85% GRR is underwater on the one axis it is built to win.

PLG and PLS

The No and Low end of the map has a name when you run it on purpose: Product-Led Growth. Dave Boyce’s framing is that users experience the product before they buy it, which turns the product into its own top of funnel and closes the word-of-mouth loop we drew back in the systems chapter. PLG is durable and cheap, and it is also a lead engine for everything to its right. Product-Led Sales (PLS) is PLG fused with a sales-led motion: free usage inside an account becomes the signal a High-Touch team acts on. Atlassian is the canonical case, developer-led adoption feeding an enterprise motion. You do not have to choose PLG or sales. The map lets you run PLG as the front door to a higher-touch back end.

Run three motions, not twelve

The discipline that ties the chapter together is restraint. Revenue Architecture’s rule is to run at most three GTM motions until you cross $50M ARR, and when you want the next leg of growth, launch a new product rather than a fourth motion. Every motion you add multiplies the tools, the vocabularies, and the handoffs (the interoperability problem from The Operating Model), and most companies drift from three motions near $30M to a dozen near $150M without ever deciding to. Each motion also has to clear its own maturity ladder in order: reach scalability, then sustainability (ideally before it hits $10M ARR on its own), then durability. You cannot skip a stage, and you cannot borrow a motion’s sustainability from the one next to it.

So the GTM Model hands operations a shortlist: here are the two or three motions the math allows, here is the cost each is permitted to carry, and here is the GRR each has to hold. That is the design. The rest of this course is how you run it. Module 4 opens where the highest-cost motions live or die day to day, on the board. In Pipeline Management and Deal Velocity we take the High and Medium Touch motions off the map and turn “which motion” into “which deals, moving how fast, through which gates.”