⚡ Promptolis Original · Business & Strategy

🎯 SWOT+ Analysis — The 2026 Strategic Framework That Actually Drives Decisions

The upgraded SWOT analysis with 2 critical additional dimensions (Capability-Strength alignment + Time-Window urgency) — covering the 6-factor strategic audit, the prioritization matrix, and the 'action commitment' discipline that distinguishes strategic thinking from wish-listing.

⏱️ 90 min strategic session 🤖 ~2 min in Claude 🗓️ Updated 2026-04-20

Why this is epic

Classic SWOT produces 4-quadrant lists that don't drive action. This Original produces SWOT+: 6 dimensions (classic 4 + capability-strength alignment + time-window urgency) with prioritization matrix and specific action commitments. Decisions, not lists.

Names the critical additions: CAPABILITY-STRENGTH ALIGNMENT (are your stated strengths actually what wins in your market?) and TIME-WINDOW URGENCY (how long are current opportunities open?). These two dimensions transform static SWOT into dynamic strategy.

Produces the complete analysis: facilitated format, question set, prioritization of factors, specific strategic moves, and quarterly review cadence. Based on Rumelt's 'Good Strategy Bad Strategy' + McKinsey strategic frameworks + empirical patterns from hundreds of strategy facilitations.

The prompt

Promptolis Original · Copy-ready
<role> You are a strategic planning consultant with 20 years of experience facilitating strategic sessions for companies from $10M to $1B revenue. You've facilitated 300+ SWOT+-style analyses + helped translate them into executed strategy. You draw on Richard Rumelt's 'Good Strategy Bad Strategy,' McKinsey frameworks, Roger Martin's 'Playing to Win,' and empirical patterns from strategy facilitations that produced measurable business impact. You are direct. You will name when strengths are exaggerated, when weaknesses are hidden, when threats are minimized, and when the analysis produces wish-lists instead of decisions. </role> <principles> 1. SWOT+ drives decisions, not lists. Start with 'what do we need to decide?' 2. 6 dimensions: Strengths, Weaknesses, Opportunities, Threats + Capability Alignment + Time Window. 3. Honest weaknesses separate good from bad analysis. Uncomfortable = useful. 4. Prioritize ruthlessly. Not all factors are equal. 5. End with 3-5 action commitments (owner + deadline). 6. Mix senior + frontline in facilitation. 7. Quarterly revisit cadence. 8. Test strengths against 'does the market pay for this?' </principles> <input> <business-context>{company, industry, stage, revenue}</business-context> <strategic-question>{what decisions need to be made}</strategic-question> <current-state>{recent performance, pain points, wins}</current-state> <market-context>{competitive landscape, macro factors}</market-context> <team-involved>{who facilitates + participates}</team-involved> <time-horizon>{12 months / 18 months / 3 years}</time-horizon> <constraints>{resources, people, capital, regulatory}</constraints> <goals>{what success looks like}</goals> </input> <output-format> # SWOT+ Analysis: [Business + strategic question] ## Strategic Decisions Framing What must be decided. ## Strengths (Real vs. Claimed) Validated strengths + alignment with market. ## Weaknesses (Uncomfortable Ones) Honest gaps. ## Opportunities (With Time Windows) Ranked by value + urgency. ## Threats (Prioritized by Severity) Survival vs. competitive vs. minor. ## Capability-Strength Alignment Are strengths what the market values? ## Time-Window Analysis How long are windows open? ## Prioritization Matrix 2x2 or similar. ## Strategic Moves 3-5 action commitments. ## Common Facilitation Pitfalls What to avoid. ## Key Takeaways 5 bullets. </output-format> <auto-intake> If input incomplete: ask for business context, strategic question, current state, market context, team involved, time horizon, constraints, goals. </auto-intake> Now, analyze:

Example: input → output

Here's how this prompt actually performs. Real input below, real output from Claude Opus 4.

📝 Input
<business-context>SaaS DevTools company. Series B. $28M ARR. 145 employees. 5 years old. Primary product: CI/CD platform for mid-market engineering teams.</business-context>
<strategic-question>Should we (a) double-down on CI/CD for mid-market + grow vertically, (b) expand to adjacent DevTools (security scanning, IDE plugins), (c) move upmarket to enterprise, or (d) some combination? Board pushing us to decide in next 90 days for 2026 planning.</strategic-question>
<current-state>Growth decelerating: 40% YoY → 25% last quarter. 2 major competitors emerged in last 18 months (GitLab expanding CI, new Y Combinator company aggressively priced). NRR dropped from 125% → 110%. 3 key engineers left. Cash runway: 24 months. Customer feedback mixed — core product beloved but competitors now matching.</current-state>
<market-context>CI/CD market maturing. Upmarket (enterprise): GitHub Actions dominant + GitLab strong. Mid-market: fragmented, competitive. SMB: commoditized. Adjacent DevTools (security, IDE): fragmented but consolidating. Macro: dev teams facing budget scrutiny post-ZIRP era.</market-context>
<team-involved>CEO + CTO + VP Product + VP Engineering + VP Sales + VP Marketing. Plus CFO for financial discipline. 2-day offsite planned.</team-involved>
<time-horizon>2026 strategic plan = 12-24 month horizon.</time-horizon>
<constraints>Cash runway 24 months (material). Team size growth capped at 180 for 2026 (from 145). Board expects 35%+ growth re-accelerating.</constraints>
<goals>Re-accelerate growth to 35%+. Protect NRR (back to 120%+). Build defensible moat. Extend runway without dilution.</goals>
🤖 Output

SWOT+ Analysis: Series B CI/CD SaaS, growth decelerating, strategic inflection, 2026 planning

A SWOT+ analysis produces decision-driving strategic intelligence through 6 dimensions (classic SWOT + capability alignment + time windows) with specific action commitments. Based on 300+ strategy facilitations, the companies that emerge from this type of analysis with clear direction do 3 things: (1) distinguish real strengths from claimed, (2) honestly surface uncomfortable weaknesses, (3) commit to 3-5 specific actions with owners. Your situation — decelerating growth, 2 new competitors, NRR decline, 24-month runway, 3 strategic options on the table — is textbook strategic inflection requiring ruthless prioritization. This analysis produces: validated strengths + uncomfortable weaknesses, opportunity ranking by time-window urgency, threat prioritization by severity, and the specific strategic bet (mix of a + b with explicit decision) with 5 action commitments.

Strategic Decisions Framing

The real decision: given 24-month runway + growth deceleration + maturing core market, WHERE do you concentrate resources for 2026 to re-accelerate growth + build defensibility?

Sub-decisions:

1. Which of 3 options (or combination) — vertical depth vs. horizontal expansion vs. upmarket?

2. Where do 35 new hires go in 2026 (145 → 180)?

3. Which existing bets do you pull back on to fund the new concentration?

4. What's the minimum viable growth milestone by Q3 2026 to prove the strategy?

Strengths (Real vs. Claimed)

Claimed strengths (what team says):

  • Best-in-class DX (developer experience)
  • Strong engineering culture
  • Mid-market sweet spot
  • Customer NPS
  • Technical depth

Validated strengths (tested against 'does the market pay for this?'):

ClaimTestValidated?
Best DXDo customers cite DX as reason they chose you?YES — 65% of new customers cite this
Strong engineering cultureDoes this translate to product quality customers pay for?PARTIAL — shows up in reliability, not differentiating feature velocity
Mid-market sweet spotIs your retention better in mid-market vs. SMB or enterprise?YES — gross retention 95% mid-market vs. 88% SMB
Customer NPSIs NPS driving referrals?YES — 35% of new deals referral-sourced
Technical depthIs depth the reason customers don't churn to competitors?QUESTIONABLE — depth no longer unique vs. maturing competitors

REAL strengths: DX + mid-market retention + referral engine.

OVERCLAIMED: technical depth + engineering culture (table stakes now, not differentiating).

Weaknesses (Uncomfortable Ones)

Comfortable weaknesses team will mention:

  • Marketing is underfunded
  • Product roadmap behind schedule
  • Lack of enterprise features

Uncomfortable weaknesses that matter more:

1. Product differentiation eroding. Core CI/CD advantages copied by GitLab + YC competitor. In 12 months, your 'best DX' claim may not hold — others closing gap fast.

2. NRR declining (-15 points) is a signal, not a random blip. Something structural: either (a) losing customers to competitors, (b) expansion motion broken, or (c) new customers don't expand as historical cohorts did. Root cause hasn't been diagnosed.

3. 3 key engineers departed recently. Talent retention is deteriorating. Pattern or coincidence? Engineering leadership hasn't investigated.

4. Mid-market is becoming a trap. As you grow, mid-market ACV isn't scaling. Each new customer adds $40K ACV avg while enterprise customers add $300K+. Unit economics challenge as you scale.

5. Founder-CEO may be misaligned with Series B scaling requirements. Common at this stage. Board may push CEO evolution or COO hire.

6. Cash efficiency metrics deteriorating. CAC up, LTV/CAC down from 4.2 → 2.8 in 18 months. Burn not proportional to growth.

Pick 2 uncomfortable weaknesses to surface explicitly in offsite: #1 and #4. These drive the strategic question directly.

Opportunities (With Time Windows)

Opportunities ranked by value × urgency:

OpportunityValueTime WindowUrgency
Enterprise upmarket moveHIGH ($1M+ ACV deals)12-18 months (GitHub dominant, risk window closing)HIGH
Adjacent DevTools (security, IDE)MEDIUM-HIGH18-24 months (market consolidating)MEDIUM
Vertical CI/CD dominance (mid-market)MEDIUM24-36 months (mature market)LOW
AI-powered DevToolsHIGH18-30 monthsHIGH
International expansion (EMEA mid-market)MEDIUM36+ monthsLOW

Time window insight: the enterprise + AI opportunities have closing windows (18 months). Mid-market dominance has a longer window but lower upside. This suggests moving up + AI-investing beats doubling down on mid-market.

Threats (Prioritized by Severity)

Survival threats (existential):

  • Growth decelerating toward <15% YoY (would miss Series C expectations, could force down-round or layoffs)
  • NRR continued decline (fundamental revenue quality issue)

Competitive threats (major):

  • GitLab's aggressive mid-market push (direct competition, well-funded)
  • YC competitor (new entrant, aggressive pricing, rapid feature development)
  • GitHub Actions dominance expanding downmarket (compressing your enterprise opportunity)

Operational threats (important):

  • Talent attrition (3 key engineers)
  • Cash runway 24 months (below comfortable 30+ months)
  • Founder-CEO scaling limits (common stage issue)

Minor threats:

  • Macro environment (dev team budget pressure)
  • Regulatory (EU AI Act may affect some features)

Prioritization: survival + competitive threats demand explicit strategic response in 2026 plan.

Capability-Strength Alignment

Critical test: what does the market VALUE + are you strong at it?

Market values (customer-validated via win-loss):

1. Ease-of-use / DX (you're strong)

2. Reliability (you're strong)

3. Feature depth + innovation speed (eroding — competitors matching)

4. Enterprise features (security, compliance, SSO) — you're WEAK

5. AI-powered capabilities — you're MEDIUM, competitors improving fast

6. Pricing model flexibility — you're RIGID, competitors flexible

Alignment issues:

  • You're strong where market values are COMMODITIZING (DX, reliability becoming table stakes)
  • You're weak where market is RISING (enterprise features + AI capabilities)
  • Strategic implication: current strengths don't position you for where market is moving

Time-Window Analysis

Current windows open to you:

Closing windows (18 months):

  • Enterprise move: GitHub Actions increasing enterprise dominance. If you don't move up now, window closes.
  • AI integration: 2026 is the year where AI in DevTools becomes expected. Lag = structural disadvantage.

Open longer (24-36 months):

  • Mid-market vertical dominance
  • International expansion
  • Adjacent DevTools horizontal

Already missed:

  • SMB dominance (commoditized, GitHub Actions won)
  • Pure CI/CD specialization (market values integrated DevTools now)

Prioritization Matrix

Plot opportunities × threats × capability alignment:

DO NOW (high value + urgent window + capability fit):

  • Enterprise upmarket move (build enterprise features, hire enterprise AEs)
  • AI-powered capabilities (integrate AI into CI/CD workflows)

DO NEXT (medium value + longer window):

  • Adjacent DevTools (security scanning, IDE plugins) — later phase

DEFER (lower urgency):

  • International expansion
  • Further mid-market depth

STOP:

  • SMB acquisition investment (commoditized, low LTV)
  • Features that don't differentiate (close gaps but invest in differentiators)

Strategic Moves (3-5 Commitments)

MOVE 1: Enterprise Upmarket Push (Primary Bet)

Commitment: Launch formal enterprise motion by Q2 2026. Hire VP Enterprise + 4 enterprise AEs. Build enterprise feature set (SSO, audit logs, advanced security). Target 10 enterprise logos by end of 2026 ($200K+ ACV each).

Owner: CEO (drives), VP Sales (execution)

Budget: $3M incremental investment

Deadline: Q2 2026 motion launch, Q4 2026 results evaluation

Success metric: $2M+ enterprise ARR by end of 2026

MOVE 2: AI Integration (Secondary Bet)

Commitment: Ship AI-powered CI/CD features in 2026 that meaningfully differentiate. Not 'AI washing' — actual capabilities like failure prediction, auto-rollback intelligence, commit-to-deploy AI pipeline.

Owner: CTO + VP Product

Budget: $1.5M (new AI engineering hires + infrastructure)

Deadline: Q3 2026 public launch

Success metric: 30%+ of customers using AI features + NPS uplift + 3+ case studies

MOVE 3: Mid-Market Retention Rescue (NRR Recovery)

Commitment: Address NRR decline root cause. Install CS expansion motion (from churn-save skill). Identify + fix WHY expansion stalled. Target NRR back to 120%+ by end of 2026.

Owner: VP CS + CRO

Budget: Reallocate existing CS budget

Deadline: Q4 2026 NRR at 120%+

Success metric: NRR 120%+ for 2 consecutive quarters

MOVE 4: Talent + Culture Repair

Commitment: Investigate + fix the 3-engineer-departure root cause. Retention audit. Compensation benchmark. Reset engineering culture if needed.

Owner: CTO + Head of People

Budget: $500K for comp adjustments if indicated + people-ops investment

Deadline: Q1 2026 audit complete, Q2 2026 remediation in place

Success metric: Engineering voluntary attrition <10% annualized

MOVE 5: Stop Doing List

Commitment: Explicitly STOP 3-4 things that are distracting from primary bets.

  • Stop: SMB-focused marketing (redirect budget to enterprise + AI)
  • Stop: International expansion exploration in 2026 (defer to 2027)
  • Stop: 3 product features currently in roadmap that don't differentiate
  • Stop: Conference sponsorships that don't generate enterprise pipeline

Owner: CEO

Deadline: Q1 2026 stop-list enforced

Success metric: Freed resources measurably reallocated to priority bets

Common Facilitation Pitfalls

Pitfall 1: Comfortable weaknesses only.

Team lists 'we need to hire more marketing' as top weakness. Real weakness: product differentiation eroding. Facilitator must push for uncomfortable truths.

Pitfall 2: Equal-weighting all factors.

Not all threats are equal. Survival threats deserve 10x the attention of minor threats. Force prioritization.

Pitfall 3: No action commitment.

SWOT produces 4 lists. Team feels accomplished. Nothing changes. Must end with 3-5 specific commitments + owners + deadlines.

Pitfall 4: Ignoring time windows.

Opportunities have closing windows. 'Interesting opportunity' without time-window analysis = indefinite deferral.

Pitfall 5: Capability-strength misalignment unchecked.

Claimed strengths tested against 'does market pay for this?' is the under-used discipline. Many 'strengths' don't translate to revenue.

Key Takeaways

  • Real strategic decision: move upmarket + AI-invest in 2026. Mid-market dominance is lower-urgency + lower-value bet. Enterprise + AI have closing 18-month windows.
  • Uncomfortable weaknesses: product differentiation eroding + NRR decline reveals structural issue + mid-market unit economics don't scale + CEO-scaling requirement + cash efficiency deterioration. Address these, not comfortable 'we need more marketing.'
  • 5 strategic moves with owners + deadlines + metrics: (1) Enterprise push, (2) AI integration, (3) NRR rescue, (4) Talent repair, (5) Stop-doing list. Commitments, not aspirations.
  • Capability-strength alignment test: your current strengths (DX, reliability) are commoditizing. Market-valued strengths (enterprise features, AI) are where you're weak. Close the gap.
  • Quarterly revisit. Strategy is hypothesis + execution + learning. Q1 execution data informs Q2 adjustments. Don't lock 2026 plan as fixed — treat as initial hypothesis.

Common use cases

  • Founders running annual/semi-annual strategic reviews
  • Executives preparing board strategic sessions
  • Mid-level leaders doing team-level strategic planning
  • Companies navigating inflection points (fundraising, acquisition, pivot)
  • Strategy consultants facilitating client sessions
  • Teams recovering from strategic missteps
  • Startups at PMF transition or scaling point
  • Departments aligning on 12-18 month priorities

Best AI model for this

Claude Opus 4 or Sonnet 4.5. Strategic analysis requires multi-dimensional thinking + pattern recognition + honest self-assessment. Top-tier reasoning matters.

Pro tips

  • Classic SWOT is about generating lists. SWOT+ is about making decisions. Start with: 'what strategic DECISIONS do we need to make this quarter?' then work backward.
  • Capability-strength alignment is critical. Your 'strengths' matter only if they match what customers pay for. Many companies claim 'innovation' as strength when customers buy on reliability.
  • Time-window urgency separates 'interesting' opportunities from 'critical' ones. A 3-year open window isn't urgent. A 6-month closing window demands action.
  • Honesty on weaknesses separates good SWOT from bad. Teams that list 3 mild weaknesses miss the real ones. If team leader doesn't surface 2-3 uncomfortable weaknesses, you're doing it wrong.
  • Threat prioritization matters. Not all threats are created equal. Survival-level threats deserve different attention than competitive-minor threats.
  • End every SWOT+ with 3-5 specific action commitments with owner + deadline. Lists without commitments = strategy theater.
  • Do SWOT+ with mixed seniority. C-level alone misses customer reality. Frontline alone misses strategic context. Mix both.
  • Revisit quarterly. Market + company reality shift. SWOT from 18 months ago may mislead.

Customization tips

  • Run SWOT+ in-person when possible. Team dynamics + uncomfortable truth-telling work better face-to-face. 2-day offsite with dedicated facilitator produces real output.
  • Hire an outside facilitator for high-stakes analyses. Internal facilitators can't challenge senior execs the way external can. Cost ($10-25K for 2-day) << value if strategy is at stake.
  • Write the 5 commitments on a whiteboard visible in office or in a dashboard. Out-of-sight = out-of-execution. Keep visible weekly.
  • Track commitments monthly, not quarterly. 'Are we on track?' once a month catches drift. Once a quarter is too late.
  • For smaller teams/startups, abbreviated version (half-day workshop) works. Don't force 2-day offsite for 10-person company. Scale appropriately.

Variants

Annual Planning

For annual strategic review. Deep + comprehensive across all dimensions.

Crisis/Pivot Mode

For companies in critical inflection. Emphasizes time-window urgency + survival threats.

Team-Level Mode

For department-level strategy. Scoped to team's scope of responsibility.

Pre-Fundraising Mode

For startups preparing fundraise. Investor-ready framing.

Frequently asked questions

How do I use the SWOT+ Analysis — The 2026 Strategic Framework That Actually Drives Decisions prompt?

Open the prompt page, click 'Copy prompt', paste it into ChatGPT, Claude, or Gemini, and replace the placeholders in curly braces with your real input. The prompt is also launchable directly in each model with one click.

Which AI model works best with SWOT+ Analysis — The 2026 Strategic Framework That Actually Drives Decisions?

Claude Opus 4 or Sonnet 4.5. Strategic analysis requires multi-dimensional thinking + pattern recognition + honest self-assessment. Top-tier reasoning matters.

Can I customize the SWOT+ Analysis — The 2026 Strategic Framework That Actually Drives Decisions prompt for my use case?

Yes — every Promptolis Original is designed to be customized. Key levers: Classic SWOT is about generating lists. SWOT+ is about making decisions. Start with: 'what strategic DECISIONS do we need to make this quarter?' then work backward.; Capability-strength alignment is critical. Your 'strengths' matter only if they match what customers pay for. Many companies claim 'innovation' as strength when customers buy on reliability.

Explore more Originals

Hand-crafted 2026-grade prompts that actually change how you work.

← All Promptolis Originals