The 9 Capabilities of a Modern Strategy Team (Stratridge Framework)

A positioning practice at a scaling SaaS company is not one function. It's nine specific capabilities that together produce the strategic coherence customers, investors, and employees can feel. Most companies have three or four of the nine operating at reasonable maturity and are missing the others entirely. The gaps — which vary by company — are where positioning fails in visible, diagnosable ways.

The Stratridge framework below names the nine capabilities, gives a maturity signal for each, and recommends the sequence in which a company should build them. The nine map to the operational work a strategy function has to do; they're not aspirational. A capability-maturity audit against this framework produces, in 90 minutes, a clear picture of which parts of positioning a company operates well and which parts are being winged.

My team had built five of the nine capabilities without knowing the other four existed as distinct work. We'd been failing in ways that felt like 'positioning is hard' without realizing we were missing specific pieces of the practice. Naming the capabilities was the first step toward building the ones we'd been skipping.

The nine capabilities

Most companies have capabilities 1, 3, 5, and 6 at baseline maturity — every company has some version of a positioning brief, tracks competitors somewhat, has some battle cards, runs some launches. The gap is usually in 2, 4, 7, 8, and 9 — the capabilities that require ongoing operational discipline rather than point-in-time artifacts.

Maturity signals for each capability

The maturity of each capability can be read from specific operational signals. Below, the signals that distinguish a mature capability from a performative one.

Capability 1 · Positioning brief maintenance

Mature signal: The brief is a living document with visible version history, a named owner, and a scheduled quarterly review. A new hire finds it in 2 clicks. It's edited at least once a quarter with dated changes.

Performative signal: A PDF from 18 months ago, circulated when people ask. Nobody has edited it in the last year because "it's still accurate." Nobody can point to the current version vs. the old one.

Capability 2 · Message consistency discipline

Mature signal: A quarterly audit measures consistency across 20+ surfaces against specific metrics (category noun match, ICP fit, claim-evidence density). Drift is named in monthly reports to the CMO. Specific surfaces are remediated on a tracked cadence.

Performative signal: The brand team "keeps an eye on consistency" without specific measurement. Drift gets noticed reactively when an executive reads something off-brief and complains. No number anyone can cite for current consistency.

Capability 3 · Competitor monitoring with taxonomy

Mature signal: Competitors are tiered (A/B/C). Different signal types are tracked at different cadences. Monthly monitoring meeting produces decisions (routed to Ignore, Monitor, Respond, Preempt) with named owners. The monitoring program can cite how many specific decisions it produced last quarter.

Performative signal: Competitors are tracked "as needed." Signals come into Slack unfiltered. The PMM spends time scanning but can't name three decisions the monitoring produced this quarter.

Capability 4 · Win/loss analysis in depth

Mature signal: Structured interview methodology, segmented by sales motion (PLG, hybrid, sales-led). Monthly or quarterly synthesis. Findings route to product, marketing, sales with named owners and follow-up tracking. Different methods applied to churn vs. lost deals.

Performative signal: Reps tag deals in CRM at close; a report summarizes the tags quarterly; nobody interviews buyers systematically. Most "findings" are rep theories, not verified buyer signals.

Capability 5 · Battle-card operation

Mature signal: 4-box cards for the top 10–15 competitors. Cards are distributed in the sales-enablement tool with usage tracking. Quarterly refresh; cards not used in two quarters get archived. Specific cards have documented win-rate impact.

Performative signal: 40 cards exist in a shared drive. Most haven't been updated in 18 months. Sales team knows about 5 of them; uses 2.

Capability 6 · Launch playbook execution

Mature signal: Standard launch process documented and followed. Pre-mortem happens T-3 weeks. Launch brief is one page. Retrospective happens at T+30 with tracked follow-ups. Different playbook shapes for enterprise-tier launches, self-serve launches, deprecations, betas.

Performative signal: Every launch feels like the first launch. Checklists get assembled ad-hoc. Retrospectives happen when someone remembers to schedule them. The company's execution quality varies wildly by which PMM is running which launch.

Capability 7 · Strategic-context memory

Mature signal: A decision log exists and is current. New hires are onboarded against the log; they can answer "why do we do X" questions in their first week without having to ask a human. The CEO or chief of staff writes a quarterly strategic-context memo. Board materials include the decision log as a standard section.

Performative signal: The context lives in the founder's head. New hires spend months "coming up to speed" through 1:1 conversations. When someone senior leaves, the company loses a material part of its strategic memory.

Capability 8 · Positioning-to-product alignment

Mature signal: Every major feature has a positioning-fit memo. Roadmap reviews include positioning-layer tagging. PMM and product leadership meet weekly for 30 minutes. The product team can explain which positioning claim each new feature supports.

Performative signal: Product ships features; marketing writes copy about them afterward. Quarterly "alignment meetings" happen but produce no structural changes. Features get shipped that don't obviously fit the positioning, and marketing has to back-fit the story.

Capability 9 · Executive communication flow

Mature signal: Board materials include a strategic-context section separate from metrics. Investor updates have a decisions log and open-questions memo. Strategic narrative shifts are named explicitly and explained. Executives across functions can articulate the company's current positioning without coaching.

Performative signal: Board materials are metrics decks. Investor updates are metrics emails. Strategic shifts are discovered by the board mid-meeting rather than previewed. Different executives describe the company's positioning differently to external audiences.

The capability-maturity audit

A 90-minute audit against the nine capabilities produces a clear picture. The structure:

The audit's value is not the scoring itself. It's the forced conversation about which capabilities the team has been performing vs. operating. The scoring makes the distinction legible; the operational work that follows is where the maturation happens.

The sequence: which capabilities to build first

Not every company should build the same capabilities in the same order. The right sequence depends on company stage and current gaps. Three typical sequences:

Sequence A · Pre-Series B (5–30 customers)

Priority at this stage: build capabilities 1, 4, and 7. The positioning brief, win/loss analysis, and strategic-context memory. Everything else can wait. The reason: at this stage, the company is still learning what it is. The three priority capabilities produce the learning that later capabilities operationalize.

Sequence B · Series B through early Series C ($30–80M ARR)

Priority: mature capabilities 1 and 7 (if still weak), build capabilities 2, 3, and 5. Message consistency, competitor monitoring, battle cards. This is the operational-discipline phase — the company has enough customers and competitive exposure that the basic strategic infrastructure has to work.

Sequence C · Enterprise scale ($80M+ ARR)

Priority: all nine capabilities, with specific focus on 8 and 9. Positioning-to-product alignment and executive communication flow. At this scale, the company has enough surface area that the cross-functional and executive-level capabilities become load-bearing. Companies that reach this scale with weak 8 and 9 often stall on category leadership they can't articulate publicly.

Common capability-pairs that fail together

Three pairs of capabilities that tend to fail together, and why.

Pair 1: Capabilities 1 and 7. Positioning brief maintenance and strategic-context memory. Both require documentation discipline. Companies weak on one are usually weak on the other. The fix is shared infrastructure — a single documentation system covering both.

Pair 2: Capabilities 4 and 5. Win/loss analysis and battle-card operation. Win/loss produces the findings; battle cards operationalize the response. A company with strong win/loss but weak battle-card discipline wastes the win/loss findings; a company with battle cards that aren't informed by win/loss produces cards disconnected from actual competitive dynamics.

Pair 3: Capabilities 2 and 8. Message consistency and positioning-to-product alignment. Both touch the question of whether the company is saying and building the same thing. Companies weak on both produce positioning that diverges from product reality; the consistency audit and the alignment audit have to be run together to surface the divergence.

The team shape that supports all nine

Companies at full maturity usually have a specific team structure:

• Strategic lead (CMO or VP Positioning): owns capabilities 1, 7, and 9. Strategic coherence.
• Senior PMM or Head of PMM: owns capabilities 2, 4, 5, and 6. Operational discipline.
• Competitive intelligence specialist: owns capability 3. Monitoring and signal work.
• PMM-product liaison: owns capability 8. Cross-functional alignment.

At smaller scale, these roles collapse. At early stage, one founder-CMO may own all nine; at Series A, two PMMs share them; at Series B, a CMO and 3-person PMM team covers the capabilities. The structure matures as the company matures; forcing a larger structure too early is expensive, and running a lean structure too long under-invests in the capabilities that require dedicated ownership.

What the framework is not

Three things worth naming explicitly.

It's not a checklist. The nine capabilities overlap, reinforce each other, and don't operate in isolation. Treating them as nine separate boxes to tick produces teams that operate each capability shallowly. The goal is integrated maturity, not compartmentalized execution.

It's not a grade. A company scoring 2/3 across all nine capabilities is operating better than a company scoring 3/3 on three and 1/3 on six. The framework exists to identify imbalances, not to produce a report-card average.

It's not static. The capabilities that matter most shift as the company scales and as the category evolves. A mature framework for 2026 might have a tenth or eleventh capability by 2028. The framework is a snapshot of what matters now; the team should be willing to evolve it as operational reality shifts.

The nine capabilities are the Stratridge framework for assessing a modern strategy team's maturity. Companies running the audit against this framework usually find the exercise clarifies where their positioning practice is strong vs. shallow. The clarifying is the value; the operational work to close the gaps is what follows. Most companies complete their first full capability-maturity run in a quarter and produce a 12-to-18-month investment plan against it. The framework is the skeleton; the operational buildout is the real work.