SaaS go to market strategy

Most go to market documents describe five motions and then decline to pick one. That is the failure. A motion is a resource allocation decision, and the cost of leaving it undecided is that you fund two half motions, neither of which produces enough signal to defend in a board meeting.

So this page picks. Below you get the conditions each motion genuinely requires, a decision tree keyed to four inputs, the proof assets you have to build before launch, a 90 day sequence with owners attached, and the early signals that tell you the motion was wrong while it is still cheap to change. The general mechanics of SaaS marketing sit elsewhere; this is the sequencing layer on top.

The five motions and the conditions each one requires

A motion is not a preference. Each one has entry requirements, and a team that launches without them spends two quarters discovering that in public.

Product led means the product does the selling. The buyer signs up, reaches a useful outcome without talking to anyone, and enters a card. Figma, Calendly, Loom and PostHog all run this shape. It requires three things you either have or you do not: usage instrumentation good enough to see activation (Amplitude, Mixpanel or PostHog), self serve billing that handles tax and dunning (Stripe is the default), and an onboarding path a stranger can complete on a Tuesday afternoon without a call.

Sales led means a human carries the deal. It fits products where value arrives after configuration, data migration or an integration, and where four or more people sign off. Gong and 6sense both sell this way. The entry requirements are reference customers who will take a call, a security page that survives a vendor assessment, and a pricing structure a CFO can model.

Marketing led means demand already exists in search and social, and your job is to capture it and route it. Ahrefs, Semrush and Klaviyo grew largely this way. It requires content and SEO capacity that will not run dry in month four, a conversion path that does not dead end in an ebook, and patience measured in three quarters rather than three weeks.

Partner led means someone else owns the distribution. Apps living inside the Shopify, Salesforce, Atlassian or Slack marketplaces run this way. It requires an integration that stays healthy through the platform’s release cycles, a listing that ranks inside the marketplace’s own search, and a revenue share you can actually afford after the platform takes its cut.

Community led means practitioners talk to each other more than they read vendors. Webflow and PostHog both have versions of this. It needs a real practitioner on staff whose name people recognise, twelve to eighteen months, and a tolerance for pipeline you cannot attribute.

Motion	Hard requirement you cannot fake	ACV fit	Time to first real signal	Main failure mode
Product led	Activation inside one session, self serve billing	Under $15K	4 to 8 weeks	Signups that never convert above a price ceiling
Sales led	Two callable references plus a security page	$50K and up	10 to 16 weeks	Reps manufacturing collateral instead of selling
Marketing led	Sustained content capacity and a live conversion path	$5K to $60K	6 to 9 months	Traffic that grows while pipeline does not
Partner led	A stable integration and an affordable revenue share	$2K to $40K	2 to 4 quarters	Platform changes the rules and the channel evaporates
Community led	A named practitioner on staff, not a community manager	Any	3 to 6 quarters	Unattributable pipeline that finance eventually defunds

The decision tree: four inputs, taken in this order

Run the inputs in sequence and stop at the first one that gives a clear answer. Contract value first, time to value second, buyer count third, implementation burden fourth.

Annual contract value sets the outer boundary. Under 5,000 dollars, a sales conversation costs more than the deal returns, so product led or partner led are the only viable answers. Above 100,000 dollars, no self serve funnel will carry the procurement weight, so sales led it is. Everything between is a genuine choice.

Time to value breaks the tie inside that range. If a new user can produce something they would show a colleague inside one session, product led still works at surprisingly high contract values. If the first useful output requires importing two years of data or connecting to a system of record, a trial will just generate a graveyard of half configured accounts.

Buyer count is the third gate. One buyer with a budget means self serve remains possible. Three to five buyers means somebody has to coordinate them, and that somebody is either a sales rep or your champion working unpaid on your behalf. Six or more, which Gartner’s research puts as typical for complex B2B purchases, means a committee and a sales led motion.

Implementation burden is the last check and it overrides the others. If go live requires services work, you need humans in the funnel regardless of price, because the churn from unsupported implementations will eat whatever acquisition efficiency the self serve motion bought you.

The B2B SaaS Go to Market Strategy guide works through the segmentation and positioning inputs that sit upstream of this tree. If you want the decision written down in a format a founder and a board member can both read, use the B2B SaaS Go to Market Plan Template rather than starting from a blank document.

Why hybrid is the default answer above 25,000 dollars

The product led data is genuinely good, and it is also routinely misread. OpenView’s benchmark work has put median annual growth for product led companies at roughly 35 percent against 26 percent for non product led peers, and found product led companies achieving comparable growth on around 39 percent less sales and marketing spend. Those numbers are real. They are also aggregates across a population dominated by low contract value products.

That retention gap is the part that matters for anyone above 25,000 dollars. Acquisition efficiency is only half the equation, and self serve expansion inside a 400 person company tends to stall at the team that first adopted. Somebody has to go ask the neighbouring department, and in practice that somebody is a human being with a quota.

The practical shape is not complicated. Keep the self serve trial, because it is the cheapest qualification engine ever built: an account with four active users and one core action completed tells you more than any lead score. Then attach sales above a usage or contract threshold, and let everything below that threshold stay entirely self serve. The mid market SaaS marketing playbook covers how to size that threshold from your own conversion data.

Here is the opinion. Above 25,000 dollars ACV, hybrid is the default and single motion purity costs roughly a year. Teams that hold out for pure product led at that contract value usually spend three quarters optimising onboarding before admitting the blocker was procurement, and teams that refuse to build a trial spend the same period paying AEs to do product demos that a sandbox would have done better.

Who should ignore that advice: anyone under 10,000 dollars ACV with a genuinely horizontal product and a support team that can absorb the volume. For you, adding sales too early is the expensive mistake, and the right next move is SaaS advertising strategy work to feed the funnel you already have.

The proof each motion demands before you launch

Every motion is really a claim about why a stranger should trust you, and each claim needs different evidence. Build the evidence before the launch, not during it.

The sales led row is where most launches underinvest. A rep with no references and no security page spends the first two quarters building collateral between calls, and the cost of that shows up as a doubled cost per opportunity that nobody traces back to the missing assets. Vanta and its competitors exist because that security page has become a gating requirement rather than a nice touch.

The 90 day launch sequence, with owners

Ninety days is enough for a sales led or marketing led motion to produce first pipeline, and enough for a product led motion to produce a conversion rate you can trust. Anything longer is usually positioning work that has not been forced to a decision.

The step teams skip is the fifth one. Routing is unglamorous, costs almost nothing, and quietly determines whether the other 89 days produce anything. A demo request that waits four hours converts at roughly a third of one answered in five minutes, which is why Chili Piper and similar tools pay for themselves inside a quarter at any mid market contract value.

For a version of this sequence with the calendar and budget already filled in, the SaaS marketing plan template and the SaaS marketing budget template are the two documents to open next. Lesson two of the foundations course, choosing your go to market motion, walks through the same tree with a worked example if you would rather be taught it than read it.

The signals that say you picked the wrong motion

You get these signals around month four, and almost everyone ignores them until month nine. The cost of that delay is roughly two quarters of burn and one head of marketing.

The first two are the common ones, and they point in opposite directions. Plot every self serve conversion from the last two quarters against contract value and look for the cliff. Below it, cards get entered without a conversation. Above it, accounts stall in whatever your CRM calls trial expired. That cliff is your actual ceiling, and for most B2B products it lands between 15,000 and 30,000 dollars.

What it costs to change once you have committed: about two quarters and a hiring cycle. Moving from product led to hybrid means hiring inside AEs who ramp in three to four months, which is fine. Moving from sales led to product led is harder, because it requires product work you have to queue behind the roadmap and a pricing change that annoys existing customers. That asymmetry is the real argument for running the decision tree before the first hire rather than after the second.

Where AI native products break this tree

Products built around a model change two of the four inputs, so the tree needs an amendment. Time to value often collapses to minutes, which pulls toward product led even at contract values that would historically have demanded sales. Buyer count often expands, because a security or legal reviewer now has opinions about training data, retention and model providers that they did not have about a database.

The result is a common pattern: a product that demos itself in 90 seconds and then sits in procurement for eleven weeks. If that is you, the motion is hybrid, and the proof assets that matter most are the model and data ones rather than the usual case studies. Marketing an AI native SaaS product covers the specific assets that unblock those reviews.

What to do this week

Open a document and answer four questions with actual numbers: your median ACV over the last two quarters, the hours between signup and first useful output, the number of people on your last five closed won deals, and whether go live needs services work. That is your motion, and it takes about 40 minutes to find rather than a strategy offsite.

Then pick the single proof asset your motion requires that you do not have, and build it before you spend anything on channels. If you want to see the whole sequence run end to end on a real company, the worked SaaS marketing strategy example follows one team from segment definition through to first pipeline, including the parts that did not work.