Most SaaS companies don't have a strategy. They have a plan, a roadmap, a quarterly target, and a list of priorities. Those are useful artefacts, but they are not strategy. Strategy is the set of choices a company makes about where to play, how to win, what business model to run, and what to defend, given that it cannot be the best at everything. A roadmap describes what the company will do. A strategy describes what the company will not do, and why the choices it does make produce a defensible position over time.

The distinction matters because the modern SaaS landscape punishes companies that confuse the two. Distribution is now scarcer than product. AI-native challengers can rebuild incumbent features faster than ever. Acquisition costs keep climbing while buyers get more selective. The companies that compound through this environment are the ones that have made deliberate strategic choices: a defined segment, a sharp wedge, a defensible moat, a business model that produces good unit economics at scale, and a retention engine that turns existing customers into the primary growth lever.

This guide walks through that set of choices. It sits upstream of go-to-market execution (covered separately in GROU's GTM strategy guide), and is aimed at founders, CEOs, and senior operators making the strategic decisions that GTM execution then implements.

What SaaS strategy actually means

Roger Martin and A.G. Lafley framed strategy as five connected questions: what's the winning aspiration, where will we play, how will we win, what capabilities do we need, and what management systems will support those capabilities. Richard Rumelt framed it differently: strategy is a coherent response to a real challenge, built around a guiding policy and a set of coordinated actions.

Both framings point at the same idea. Strategy is not a list of goals. It is a clear-eyed diagnosis of the situation, a guiding choice about how to win in that situation, and the set of trade-offs that choice forces. A SaaS company without a strategy ends up doing a little of everything (PLG and SLG, SMB and enterprise, horizontal and vertical) and being competitive at none of it. A SaaS company with a strategy makes the hard choices early and then executes around them.

The five strategic questions worth answering for any SaaS company are:

→ Where to play (segment, vertical, geography, persona) → How to win (the wedge, the moat, the differentiator) → What business model to run (pricing, packaging, motion) → What to measure as the master metric (and NRR is almost always the right answer) → How to defend the position (the moat, the data flywheel, the distribution lock-in)

Each of these is a choice with trade-offs. Picking everything is picking nothing.

Where to play

The first strategic decision is the segment, the vertical, and the persona. SaaS companies that win in the modern landscape almost all start narrow. The category leaders that look horizontal today (HubSpot, Notion, Snowflake, Stripe) almost all started with a tightly defined initial segment and only expanded after they had defended the beachhead.

The strategic question is not "what is the largest TAM we can reach?" but "what is the smallest segment in which we can be the obvious choice?" That segment becomes the wedge. Once the company is the obvious choice in the wedge, expansion into adjacent segments becomes possible. Without the wedge, the company spreads thin across multiple segments and becomes the obvious choice in none.

Three sub-decisions sit inside the where-to-play question.

The vertical-vs-horizontal decision is one of the most important. Vertical SaaS (built for one industry: dental practices, construction firms, insurance brokers, restaurants) trades a smaller TAM for deeper domain functionality, lower churn, higher willingness to pay, and stronger defensibility. Horizontal SaaS (built for one function across all industries: CRM, accounting, project management) trades depth for breadth, with a larger TAM but more competition and weaker switching costs. Vertical SaaS has been one of the most consistent strategic positions of the last decade because the depth of domain functionality is hard for horizontal competitors to replicate.

The segment-size decision (SMB, mid-market, enterprise) drives almost every subsequent operational decision. SMB SaaS is high-volume, low-touch, low-ACV, high-churn. Enterprise SaaS is low-volume, high-touch, high-ACV, low-churn (when done well). Mid-market sits in between and is often the hardest segment to serve cleanly because it has enterprise expectations on an SMB budget. The segment choice determines the GTM motion (PLG vs SLG vs hybrid), the pricing model, the support model, the churn rate the business has to survive, and the unit economics that will or will not work at scale.

The geography decision is the last of the three. Most SaaS companies should start in one geography (typically the home market or the largest English-speaking market they have credibility in) and only expand once they have a defensible position. Expanding too early dilutes effort and produces a company that is mediocre in three geographies instead of dominant in one.

How to win

Once the where-to-play is decided, the how-to-win question becomes concrete. There are roughly four ways a SaaS company can win in its chosen segment, and most strategies combine two of them.

Cost or operational efficiency wins by being meaningfully cheaper or faster to deploy than the alternatives. This works in commoditised categories where the buyer is price-sensitive and the product is well-understood. It is hard to defend against well-funded competitors and tends to be a starting wedge rather than a long-term moat.

Differentiation wins by offering something the competition does not (or cannot). Deep vertical functionality, a workflow nobody else has built, an integration nobody else has shipped, a category-defining product experience. This is the most common winning strategy for SaaS companies that build durable positions. The risk is that "differentiation" without a real moat gets copied within a year.

Customer experience and brand wins by building a relationship with the user that competitors can't replicate at speed. Notion, Linear, and Figma have used this lens. The product is good but not categorically better than alternatives; the experience, the brand, and the community lock users in. This is harder than it looks and tends to require a founder with strong product taste and a willingness to invest in design and brand for years before it pays back.

Network effects or data flywheels win when each additional user makes the product better for every other user (Slack, Figma, Stripe Atlas), or when accumulated data produces a product the competition cannot match (Gong, Salesloft, large-scale ML-driven SaaS). These are the strongest moats available to SaaS companies and they are also the hardest to engineer. When a network effect is present, defensibility compounds and the strategic position becomes very hard to dislodge.

Most successful SaaS companies pick one primary winning strategy and reinforce it with one secondary lens. The clarity matters because every team in the company needs to know which way to lean when trade-offs come up.

The business model is a strategic decision

The pricing model, the packaging, and the motion are sometimes treated as tactical decisions to be optimised later. They are not. They are core strategic decisions that determine whether the company has unit economics that work at scale.

The pricing model itself has shifted significantly. Per-seat pricing, the dominant SaaS model for years, is under pressure from AI-native competitors that automate seat-level work and from buyers who push back on paying per user when AI agents do the work of multiple seats. Usage-based pricing (Snowflake, Twilio, Stripe) aligns price with value but creates revenue volatility. Hybrid pricing (a base platform fee plus usage on top) has become the most common modern compromise. Outcome-based pricing (paying for results, not access) is emerging in AI-heavy categories where the vendor can credibly tie price to a measurable customer outcome.

The right pricing model depends on three things: how value is created in the product (per user, per transaction, per outcome), how buyers are used to paying in the category, and how the company wants the revenue to behave (predictable subscription vs scaling with usage vs tied to results). The choice has knock-on effects through the entire business: sales compensation, finance forecasting, customer success motion, and competitive positioning all bend to the pricing model.

Packaging is the second decision. Two packaging philosophies dominate. The good-better-best approach (HubSpot, Salesforce, monday.com) creates clear upgrade paths and natural expansion revenue, at the cost of complexity in the buying decision. The simple/single-tier approach (Linear, Basecamp) trades expansion potential for buying friction, often making sense for products targeting a narrow user base. The packaging choice and the pricing choice need to be made together, not separately.

The motion decision is the third. Product-led growth (Slack, Figma, Notion, Calendly) lets users self-serve into the product before sales gets involved. Sales-led growth (most enterprise SaaS) leads with outbound, demos, and proof-of-concept cycles. Product-led sales (the modern hybrid: Zoom, Atlassian) uses self-serve adoption as the top of the funnel and sales to convert teams into enterprise contracts. Marketing-led growth (HubSpot's classic playbook) uses content and inbound as the primary acquisition engine. Account-based marketing concentrates resources on a defined target account list. The motion that fits depends on the segment, the deal size, the product complexity, and the buying process the customer expects.

For most modern SaaS, the right answer is a hybrid: PLG or PLS for the SMB and mid-market segment, ABM and SLG for the enterprise segment, with marketing and content underpinning both. The strategic discipline is in not trying to run all motions at full intensity at once. Each motion requires different skills, different tooling, and different metrics. Picking a primary motion and a secondary motion is a strategic decision; running four motions simultaneously is a sign that the strategy hasn't been made yet.

NRR is the master metric

Net revenue retention is the single number that tells you whether the SaaS strategy is working. It captures the percentage of revenue retained from existing customers over a defined period (typically a year), including expansion (upsells, cross-sells, seat growth) and net of contraction (downgrades, churn).

NRR matters because it is the cleanest single signal of product-market fit, customer success, pricing power, and expansion strategy combined. The benchmarks are widely understood. Top-quartile B2B SaaS companies post NRR around 110-115% or higher; the very best (Snowflake, Datadog, MongoDB at peak) sit in the 120-130%+ range. NRR below 100% means the existing customer base is shrinking each year, and any growth has to come from new logos, which is the most expensive form of SaaS growth.

The strategic implication is that NRR should be designed for, not hoped for. The pricing model, the packaging, the customer success motion, the expansion paths inside the product, and the segment choice all shape NRR. Companies that build for NRR from the start tend to compound; companies that bolt customer success onto an acquisition-led machine tend to plateau.

The historical SaaS playbook treated acquisition as the primary growth lever and retention as a hygiene factor. The modern playbook treats retention and expansion as the primary growth engine and uses acquisition to feed it. The shift is partly economic (acquisition costs have climbed sharply across most categories) and partly mathematical (a company growing existing accounts at 20% a year compounds faster than a company adding new logos at the same rate). Either way, the master metric is NRR, and any SaaS strategy that doesn't centre it is incomplete.

The metrics that sit underneath NRR are also worth naming. Gross revenue retention (NRR stripped of expansion) measures pure churn and product stickiness, with the best B2B SaaS companies sitting above 90%. LTV:CAC ratio measures whether the acquisition machine is producing customers worth more than they cost (3:1 is the floor; 5:1 and above is healthy). Payback period measures how quickly acquisition costs are recovered (under 12 months is excellent; under 24 months is acceptable). These three metrics, taken together, are the strategic dashboard. Everything else is operational detail.

Defensibility in the AI era

The defensibility question has changed materially in the last few years. Historically, SaaS moats came from a combination of features, integrations, switching costs, network effects, and brand. AI-native challengers can now rebuild feature parity faster than ever, which has weakened the feature-based moat dramatically. The defensibility decisions that matter now are different.

Data is the strongest emerging moat. SaaS products that accumulate proprietary data through customer use (sales conversations, support tickets, financial transactions, marketing campaigns) and then turn that data into a model or workflow that competitors cannot replicate, build a position that compounds over time. Gong's accumulated sales-call data, Stripe's transaction data, and the data flywheels inside large CRM and analytics platforms are examples. AI-native challengers can replicate the product but not the data, which means the defensibility shifts from "what does the product do" to "what does the product know."

Distribution is the second emerging moat. In an environment where building a competitive product is faster than ever, the company that can reach customers faster wins disproportionately. The companies with strong existing distribution (a large customer base, an active community, a recognised brand, a category-defining content engine) can ship a feature on Tuesday and have it adopted by tens of thousands of customers by Friday. The challengers with the technically better product but no distribution take years to reach the same scale.

Workflow lock-in is the third. SaaS products that become embedded in the daily workflow of a team (calendars, communication tools, code repositories, design canvases) build switching costs that survive feature parity. The user doesn't switch even when a better product appears, because the cost of changing the workflow is higher than the benefit of the new features.

Integrations and ecosystems are the fourth. A SaaS product that becomes the central connector for a customer's stack (Salesforce in the enterprise sales stack, HubSpot in the SMB marketing stack, Stripe in the payments stack) builds defensibility through the surrounding integrations rather than the product itself.

For most SaaS companies, the strategic question now is which of these four moats is achievable given the segment and stage. Feature differentiation is no longer enough. The strategy needs to name which moat the company is building toward and design every other decision (pricing, motion, capabilities) to reinforce it.

Distribution is the scarce resource

A few years ago, early-stage SaaS spent roughly 70% of its capital on building product and 30% on go-to-market. Today the ratio has flipped: closer to 30% on product and 70% on distribution. The shift reflects a market reality. Building a credible SaaS product has never been easier (modern infrastructure, AI-assisted development, mature open-source stacks); reaching customers has never been harder (saturated channels, rising acquisition costs, AI-driven content noise).

The strategic implication is that distribution should be designed into the company, not bolted on later. The strongest modern SaaS strategies treat content, community, and channel partnerships as primary strategic assets, not marketing tactics. The companies that built durable distribution engines early (HubSpot with content, Notion with community, Stripe with developer relations, Calendly with viral product loops) compound that distribution every year. The companies that treated distribution as something marketing would handle eventually find themselves with a great product nobody can find.

The execution side of the distribution question (which channels, which messages, which sequencing, which spend mix) is covered in detail in GROU's go-to-market strategy guide and the cold email outreach guide. The strategic point at this level is simpler: distribution is no longer a downstream operational concern. It is one of the four or five decisions that determine whether the SaaS strategy works.

Capabilities and management systems

The last two of Martin's strategic questions are easy to overlook because they sound operational. They are not.

The capabilities question asks: given the where-to-play and how-to-win choices, what does the company need to be exceptional at? A vertical SaaS company building deep domain functionality needs exceptional product depth and customer intimacy. A PLG SaaS company needs exceptional product onboarding and self-serve UX. A sales-led enterprise SaaS company needs exceptional sales process and customer success. A community-driven SaaS needs exceptional brand and content. The capabilities the company invests in should map directly to the winning strategy. Companies that try to be exceptional at everything end up exceptional at nothing.

The management systems question asks: how does the company support those capabilities operationally? This is where org design, hiring, tooling, compensation, and process come in. A PLG strategy supported by a sales-comp plan that pays only on closed enterprise deals will not work. A vertical SaaS strategy supported by generalist product managers without industry depth will not work. The systems need to reinforce the strategy, not contradict it.

Most strategic failures in SaaS are not failures of strategy on paper. They are failures of capability and system design that quietly contradict the stated strategy. The company says "we are PLG" and then hires three enterprise AEs. The company says "we are vertical" and then ships horizontal features to chase the next deal. The strategy on paper survives; the strategy in practice does not.

The takeaway

A winning SaaS strategy is not a list of priorities or a roadmap. It is the set of coherent choices about where to play, how to win, what business model to run, what master metric to optimise for, and what moat to build, supported by capabilities and management systems that reinforce those choices.

The modern environment has changed which choices matter most. Distribution has become scarcer than product. AI has weakened feature-based moats and elevated data, distribution, workflow lock-in, and ecosystems as the durable forms of defensibility. NRR has become the master metric that captures whether the strategy is working in practice. The shift from acquisition-led to retention-led growth has made the customer success and expansion motion as strategic as the acquisition motion.

The companies that compound through this environment are the ones that make these choices deliberately and early, then execute around them with discipline. The companies that confuse strategy with planning end up working hard on the wrong things.

For B2B SaaS founders and operators that want a partner to translate strategy into pipeline (LinkedIn content, multi-channel outbound, paid acquisition, podcast, repurposing engine), GROU builds and runs the systems end to end. Book a call.