A B2B SaaS go-to-market strategy. Pricing decides the motion.

The short answer. Pricing decides the motion, not the other way round.

A B2B SaaS go-to-market strategy has to answer three questions a generic GTM plan skips, because a subscription business earns most of its lifetime value after the first sale, not at the point of it. Which average contract value decides between product-led and sales-assisted. How pricing and packaging are structured to drive expansion once a customer is in, rather than just to close the first deal. And which single metric actually tells you the motion is working, which for SaaS specifically is net revenue retention, not new-logo count. Bessemer Venture Partners' annual State of the Cloud report, one of the industry's most cited SaaS benchmarking studies, puts best-in-class net revenue retention at 120 percent or higher: the threshold public and late-stage SaaS companies use to judge whether the existing customer base is expanding faster than it churns.

This is a different layer from the question a go-to-market strategy for startups answers, which channel to test first and how to prove it manually before scaling it, and it sits above the mechanics a product-led go-to-market guide covers, defining the activation moment and the PQL threshold within a motion already chosen. A SaaS-specific GTM strategy is the layer underneath both: how the product is priced and packaged for a B2B buyer, and how that pricing structure funds the expansion revenue a subscription business is actually built to earn.

How it works in practice. Four decisions, in order.

The first decision is which motion the product's average contract value can actually support. OpenView Partners, which has published an annual SaaS benchmarks report for close to a decade, has consistently found ACV the clearest single signal for motion fit: companies with an average contract value under roughly 10,000 to 20,000 US dollars a year skew heavily product-led, since the deal size can't justify a human sales cycle, while ACV above that range increasingly needs a sales-assisted layer to close the deal and to configure it correctly for the buyer. Picking the motion before checking this number against the actual pricing is how a founder-led team ends up hiring a sales rep to close deals too small to earn back the rep's time, or leaving a self-serve flow in place for a deal size that genuinely needs a human in the loop.

The second decision is the pricing model itself: seat-based, usage-based, tiered flat-rate, or some blend. Seat-based pricing is the easiest to explain to a buyer and the easiest to forecast, but it caps expansion at headcount growth alone. Usage-based pricing ties the invoice to the value the customer is actually getting, which tends to produce a more natural expansion path, a customer using the product more simply pays more, but it needs genuinely reliable usage metering and a buyer sophisticated enough to accept a variable bill. Tiered flat-rate packaging sits between the two: predictable for the buyer, with expansion triggered by hitting a tier's feature or usage ceiling. None of the three is inherently correct; the right one depends on whether the product's value scales more with seats, with usage, or with which features a customer needs unlocked.

The third decision is designing the packaging so the upgrade path is obvious before a customer ever needs it. A pricing page with five tiers and no clear signal of which one a growing customer will outgrow first is a missed expansion opportunity built into the product from day one. The tier boundaries should map to a real usage or team-size threshold the product can actually detect, so the upgrade conversation can start from the product itself, a usage warning, a feature gate, a seat limit, rather than from a rep cold-calling an account to ask if they'd like to pay more.

The fourth decision is what "activated" means, defined specifically enough that it can trigger the first expansion motion. A trial signup is not activation. A defined in-product behaviour, a certain number of teammates invited, a first integration connected, a first workflow completed, is activation, and it should be the same behaviour the sales or customer success team uses to decide when to have the first expansion conversation. Vague activation definitions are the most common reason a SaaS company's product-led motion produces plenty of signups and very little revenue: nobody in the business can point to the moment a free or trial user actually got value.

Sitting underneath all four decisions is a fifth, quieter one: who actually signs off. A SaaS ideal customer profile defined only by industry and company size misses the part that determines the motion most directly, the buying committee. A five-thousand-dollar-a-year tool a single manager can expense on a card needs none of the multi-stakeholder proof points a fifty-thousand-dollar annual contract requiring procurement, security review and a budget owner's sign-off will demand. Mapping the buying committee against the ACV tier, not just against the company's headcount, is what tells a SaaS team whether the sales motion needs a security questionnaire template and a procurement-friendly contract ready to go, or needs nothing more than a clear pricing page and a fast trial-to-paid flow.

What good looks like. A worked example.

An early-growth-stage B2B SaaS company I advised was pricing purely per seat, regardless of how much of the product a team actually used, and had settled into a net revenue retention rate hovering around 95 percent, meaning the existing customer base was shrinking in dollar terms even as new logos kept the top-line number moving. Expansion revenue was close to zero: customers either bought a block of seats up front and never came back to buy more, or churned when a champion left and nobody else in the account had ever been prompted to use the product more widely.

The fix was repackaging around a usage tier sitting alongside the existing seat count, with the product itself surfacing a clear, specific prompt once an account crossed roughly 80 percent of its tier's monthly usage allowance, well before the ceiling forced an awkward conversation. Customer success was given the same usage data, so the first expansion conversation happened based on a concrete signal rather than a quarterly check-in. Within two quarters of the change, net revenue retention moved from 95 percent into the low 110s, driven almost entirely by expansion within the existing base rather than any change to new-customer acquisition, which had stayed roughly flat across the same period. Nothing about the product's core pricing tier changed for existing customers who never crossed the usage threshold, which mattered commercially: the fix grew revenue from customers already getting value, rather than forcing a repricing conversation with every account regardless of whether they had actually earned one.

Pitfalls to avoid. Where SaaS GTM plans go wrong.

The first is copying a competitor's pricing page without checking whether the competitor's ACV and buyer sophistication actually match. A pricing structure built for a self-serve, prosumer-adjacent buyer does not translate cleanly onto a product selling into procurement-heavy enterprise accounts, and the reverse is just as common: a founder over-engineers an enterprise-style tiered contract for a product that could be selling itself through a simple self-serve flow.

The second is chasing new-logo count while ignoring net revenue retention, which lets a genuinely leaking bucket hide behind a healthy-looking top-line growth number for several quarters before the leak becomes visible in the bank balance. A GTM report that only shows new customers acquired is showing half the picture for a subscription business.

The third is leaving activation undefined, covered above, which quietly breaks both the product-led motion's own reporting and the sales-assisted team's ability to know when a self-serve account is ready for a human conversation.

The fourth is sales-assisting every inbound self-serve customer regardless of deal size, which is the mirror image of under-resourcing a large deal. A rep's time spent qualifying and closing a five-hundred-dollar-a-year account is time not spent on the accounts the ACV threshold above says actually justify a human sales cycle.

The fifth is rebuilding the pricing page every quarter before any cohort has had time to mature enough to show whether the last change actually moved retention. Expansion and churn signals take at least one full billing cycle, often two, to read reliably, and a pricing structure changed again before that window closes makes it impossible to know what caused what.

The sixth is treating the motion chosen at launch as permanent. A product that starts self-serve at a low ACV often finds, twelve or eighteen months in, that its best customers are paying meaningfully more than the original pricing assumed and would happily take a sales-assisted enterprise tier the original packaging never offered them. The motion should be revisited against the ACV threshold at least once a year, not locked in at the founding pricing decision.

My rule with SaaS founders building this: decide the pricing and packaging before deciding the channel strategy, since the motion has to fit what the product can actually charge and how that charge grows, not the other way round. A brilliant outbound sales motion selling a product priced to cap its own expansion revenue is optimising the wrong half of the business.

The seventh, and the one that skews a GTM plan's read on itself, is measuring churn only by logo count rather than by dollar value. A SaaS company can lose a meaningful number of small accounts while dollar retention actually improves, because the accounts staying and expanding are worth more than the ones leaving, and the reverse can be just as true: logo count can hold steady while the dollars quietly shrink because the accounts renewing are downgrading. Reporting both figures separately, not blended into one churn percentage, is what keeps a GTM review honest about which problem, if any, actually needs fixing.