Thirteen go-to-market motions were extracted from studying 131 successful SaaS companies. You should be running one of them. Most teams run four at once, badly, and call the result a strategy.
The count is not the interesting part. The interesting part is that picking is the whole game, and almost nobody treats picking as a decision with a method behind it.
Why four badly beats one well, for a while
Running four motions feels like risk management. If outbound stalls, content is warming. If content is slow, events are booked. Nothing is ever completely dead.
It also means nothing is ever completely alive. Four motions at a quarter of the attention each produce four sets of mediocre inputs, and mediocre inputs are indistinguishable from a market that does not want you. That is the expensive part: you cannot tell the difference between a motion that failed and a motion you never actually ran.
One motion, run properly, is falsifiable. It either produces pipeline or it does not, and either answer is worth having.
Thirteen motions resolve into five engine families
The thirteen are not a framework somebody drew on a whiteboard. They came out of studying 131 successful SaaS companies and asking what each one actually did to acquire customers, then collapsing the answers until the list stopped shrinking.
Thirteen is the right number for diagnosis and the wrong number for building. You cannot build thirteen things. You build one, and the thirteen collapse into five families that share an architecture.
| Family | What it does | When the diagnostic routes here |
|---|---|---|
| Signal Inbound | Detects intent in search and content behaviour, then routes it into revenue action | Traffic exists and converts badly |
| Signal Outbound | Sources accounts, detects buying signals, maps the committee, sequences across channels, classifies replies | No inbound, and the list is the problem |
| Trust | Delivers proof to a named account list until the account knows you before the first call | Long cycles, few accounts, high contract value |
| Heat-to-Webinar | Turns one brief into a full webinar funnel, from acquisition through post-event follow-up | An expert-led business with a teaching motion |
| Trust Authority | Founder-led proof that compounds into inbound demand | The founder is the product |
Read the third column again. Every routing condition is a statement about your current situation, not about which motion is best. There is no best. There is only which one your constraints have already chosen for you.
The one question that picks yours
Before the diagnostic, before the indexes, there is a single question that eliminates most of the table: where is your bottleneck, in the only three places a bottleneck can be?
- Nobody knows you. The problem is attention. Trust Authority or Heat-to-Webinar.
- People know you and do not convert. The problem is intent capture. Signal Inbound.
- You know exactly who should buy and cannot reach them. The problem is access. Signal Outbound or Trust.
Most teams answer this wrong because they answer it about the market rather than about themselves. "Our buyers are hard to reach" is usually "we never built a list." Those need different engines.
Where the thirteen still matter
The thirteen are the diagnostic vocabulary, scored against five readiness indexes. They exist so the routing decision is made against evidence rather than against whichever motion the last agency happened to sell.
The output of that diagnosis is one motion. Not a ranked shortlist, not a phased roadmap across three. One, built as a complete operating system, with the other twelve explicitly not built.
The part nobody puts in the deck
A second engine costs less than the first, because the context, the wiring and the scoring gates already exist. That is a real argument for sequencing and a terrible argument for starting with two.
Starting with two means neither has a clean signal, and the shared infrastructure you were counting on gets built to serve a compromise between them. Build one properly. Add the second onto working foundations.
When the answer is none of them
Four conditions where picking a motion is premature, and the honest move is to fix the input first.
An offer you have not defined. Every motion in the table amplifies an offer. Amplifying an unclear one industrialises the confusion.
A list that is wrong. Signal Outbound on a bad list fails faster than manual outreach on a good one, and teaches you nothing except that the machine works.
A market of forty accounts. Write to them by hand. You do not need an engine to contact forty people.
No proof yet. Trust motions deliver proof. If there is none to deliver, you are building distribution for an empty pipe.
What this is built on
We have shipped 10 revenue MicroSaaS and 10 operating systems on this architecture, each one demoable on a fifteen-minute call. That is the standard we would hold anyone to, including ourselves: if it cannot be shown working inside fifteen minutes, it is a diagram.
Our receipts
The thirteen motions come from 131 studied SaaS companies. The architecture they feed has shipped 10 revenue MicroSaaS and 10 operating systems, every one demoable on a fifteen-minute call, with two public named cases: Entrepreneurs Oasis and Lab Experience.
Behind the routing sits 20 years carrying B2B quota across the Gulf and the Levant at Cisco, Avaya and Uniphore. The motions were not selected by preference.
So pick
Take your last two quarters. Write down every motion you actually ran, not the ones in the plan. Mark each one with the honest reason it is on the list: because the diagnosis pointed there, or because nobody stopped to ask.
The second list is where your quarter went. Pick one from the first, and put the rest down.
Frequently asked questions
How many go-to-market motions are there, and how many should we run?
How do we choose which GTM motion to build?
When is it too early to pick a motion at all?
See how the layer installs.
This is a working system we build, operate for 90 days, then transfer. See the full install.
Explore the engine