Analysis Frameworks

Deep-dive reference for the three core competitive analysis frameworks: Porter's Five Forces for industry-level assessment, SWOT with strategic implications for product and company assessment, and positioning map construction for visual competitive mapping.

---

Porter's Five Forces

Porter's Five Forces is a framework for assessing the structural attractiveness of an industry and the intensity of competitive pressure a business faces. It was developed by Michael Porter at Harvard Business School and published in 1979. The model argues that long-run profitability in an industry is determined by five structural forces - not just the current rivals you face.

Use this framework when: entering a new market, evaluating a market for investment, understanding why margins are high or low in your industry, or identifying where structural advantage can be built.

---

Force 1: Threat of New Entrants

Question: How easy is it for new competitors to enter your market?

High threat (bad for incumbents): Low capital requirements, no proprietary technology, weak brand loyalty, no regulatory barriers, easy access to distribution channels.

Low threat (good for incumbents): High capital requirements, proprietary technology or patents, strong brand loyalty, regulatory licensing, exclusive distribution relationships, high switching costs for customers.

Key barriers to entry to assess:

• Economies of scale (can new entrants match your cost structure quickly?)
• Capital requirements (how much does it cost to build an MVP that competes?)
• Brand identity (how long does it take to build a trusted brand in this market?)
• Access to distribution (do incumbents lock up distribution channels?)
• Government policy / regulatory requirements
• Expected retaliation from incumbents (will incumbents fight back aggressively?)

Assessment template:

Threat of New Entrants: [Low / Medium / High]

Top barriers protecting incumbents:
1. [Barrier]
2. [Barrier]

Weakest barriers (where new entrants could attack):
1. [Weak point]

---

Force 2: Bargaining Power of Buyers

Question: How much pricing and terms leverage do customers have over you?

High buyer power (bad for you): Buyers are concentrated (few, large customers), products are commoditized, low switching costs, buyers can credibly threaten to integrate backwards, buyers have full price transparency.

Low buyer power (good for you): Many fragmented buyers, differentiated product, high switching costs, buyers depend on your product for their own revenue.

Factors that increase buyer power:

• Buyer concentration (top 10 customers = >50% of revenue is high risk)
• Commodity-like products with multiple substitutes
• Price transparency (buyers easily compare alternatives)
• Low switching costs
• Backward integration threat (buyer builds it themselves)

Assessment template:

Bargaining Power of Buyers: [Low / Medium / High]

Buyer concentration: [top N customers = X% of revenue]
Switching costs for buyers: [Low / Medium / High]
Backward integration threat: [Yes / Unlikely / No]

Implication for strategy:
[How does buyer power shape your pricing and contract strategy?]

---

Force 3: Bargaining Power of Suppliers

Question: How much leverage do your suppliers have in setting terms and prices?

High supplier power (bad for you): Few suppliers for a critical input, no substitutes, suppliers could integrate forward into your market, you are not a critical customer for them.

Low supplier power (good for you): Many competing suppliers, commodity inputs, you can switch suppliers easily, you are a significant customer for the supplier.

Common supplier categories in software markets:

• Cloud infrastructure providers (AWS, GCP, Azure) - high power, few alternatives
• AI model providers (OpenAI, Anthropic) - currently high power, growing alternatives
• Data providers - variable, depends on exclusivity
• Payment processors - moderate power (Stripe, Braintree have strong network effects)
• Distribution platforms (App Store, marketplace listings) - very high power

Assessment template:

Bargaining Power of Suppliers: [Low / Medium / High]

Critical suppliers:
- [Supplier]: [Input provided] | [Switching cost] | [Alternatives]

Highest-risk supplier dependency:
[Which supplier dependency creates the most strategic risk?]

---

Force 4: Threat of Substitute Products

Question: How easily can customers solve the same problem using a completely different category of product?

Substitutes are not direct competitors - they are different products or behaviors that serve the same customer job. They cap the price ceiling for your market because customers will switch to a substitute before paying above a threshold.

High substitute threat: The job can be accomplished with spreadsheets, manual processes, or a general-purpose tool. The substitute is "good enough" for the majority of the market.

Low substitute threat: The job requires specialized capability that only purpose- built software can provide. The cost of the substitute is high (time, error rate, specialized labor).

How to identify substitutes:

1. Start with the customer job, not the product category
2. Ask: "What would a customer do if this entire product category disappeared tomorrow?"
3. Include behavioral substitutes (hiring someone, doing it manually, not doing it at all)

Common substitutes in software:

• Spreadsheets (analytics, project management, CRM for small teams)
• Email + calendar (scheduling, communication)
• Manual processes (anything pre-software in regulated industries)
• Outsourced services (legal, accounting, design, compliance)
• General-purpose AI assistants (replacing point solutions)

Assessment template:

Threat of Substitutes: [Low / Medium / High]

Primary substitutes:
- [Substitute]: [Jobs it addresses] | [Why customers use it] | [Its ceiling/limitation]

Price ceiling implication:
[At what price do customers substitute away from your category?]

---

Force 5: Rivalry Among Existing Competitors

Question: How intense is the competition among current players in the market?

High rivalry (bad for margins): Many similarly sized competitors, slow market growth, high fixed costs, low differentiation, high exit barriers.

Low rivalry (good for margins): Few players, fast market growth, high differentiation, niche focus, low exit barriers.

Factors that drive rivalry intensity:

• Number and balance of competitors (many equal-sized players = high rivalry)
• Market growth rate (slow growth means share must be taken from rivals)
• Product differentiation (commodity = price war; differentiated = less direct rivalry)
• Switching costs (low switching = competitors constantly poach each other's customers)
• Exit barriers (high sunk costs keep weak competitors fighting instead of exiting)

Assessment template:

Rivalry Among Competitors: [Low / Medium / High]

Number of significant competitors: [N]
Market growth rate: [Declining / Slow / Fast / Hypergrowth]
Differentiation level: [Commodity / Low / Moderate / High]
Key dynamics:
[What drives the most competitive pressure right now?]

---

Five Forces Summary Template

PORTER'S FIVE FORCES ASSESSMENT
Market: [name]
Date: [YYYY-MM-DD]

Force                          | Rating | Key Driver
-------------------------------|--------|------------------------------------------
Threat of New Entrants         | [L/M/H]| [One sentence]
Bargaining Power of Buyers     | [L/M/H]| [One sentence]
Bargaining Power of Suppliers  | [L/M/H]| [One sentence]
Threat of Substitutes          | [L/M/H]| [One sentence]
Rivalry Among Competitors      | [L/M/H]| [One sentence]

Overall Industry Attractiveness: [Low / Medium / High]

Strategic implication:
[2-3 sentences on what this means for competitive strategy and where to build moats]

---

SWOT Analysis - Full Template

SWOT is a four-quadrant framework for structured assessment. Its value is not the grid itself but the strategic options that emerge from crossing quadrants. The TOWS matrix (SO, ST, WO, WT) is where the actionable strategy lives.

Gathering inputs before filling the grid

SWOT degraded to a brainstorm produces garbage. Require evidence for every cell:

Strengths sources: NPS verbatims, win reasons from CRM, product metrics, competitive win rates by segment, analyst reports, customer advisory board feedback.

Weaknesses sources: Lost deal reasons, support ticket themes, churned customer exit surveys, product areas with low feature adoption, sales objection logs.

Opportunities sources: Market research reports, competitor weaknesses (their negative reviews), technology shifts enabling new capabilities, regulatory changes opening new segments, underserved customer jobs.

Threats sources: Competitor funding announcements, hiring signals from competitors (job posts reveal roadmap direction), technology shifts enabling substitutes, platform dependency risks, macro trends reducing demand.

---

SWOT Grid Template

SWOT ANALYSIS
Subject: [Product / Company / Business Unit / Competitor]
Date: [YYYY-MM-DD]
Prepared by: [Name / Team]

STRENGTHS (internal, positive)
  Evidence required for each item
  S1: [Strength] - Evidence: [metric, quote, data point]
  S2: [Strength] - Evidence: [metric, quote, data point]
  S3: [Strength] - Evidence: [metric, quote, data point]

WEAKNESSES (internal, negative)
  Evidence required for each item
  W1: [Weakness] - Evidence: [metric, quote, data point]
  W2: [Weakness] - Evidence: [metric, quote, data point]
  W3: [Weakness] - Evidence: [metric, quote, data point]

OPPORTUNITIES (external, positive)
  Evidence required for each item
  O1: [Opportunity] - Source: [report, signal, data point]
  O2: [Opportunity] - Source: [report, signal, data point]
  O3: [Opportunity] - Source: [report, signal, data point]

THREATS (external, negative)
  Evidence required for each item
  T1: [Threat] - Source: [competitor action, trend, signal]
  T2: [Threat] - Source: [competitor action, trend, signal]
  T3: [Threat] - Source: [competitor action, trend, signal]

---

TOWS Matrix - Strategic Options

The TOWS matrix crosses the four SWOT quadrants to generate four types of strategic options. This is the "so what?" layer that makes SWOT actionable.

TOWS MATRIX

                  | OPPORTUNITIES (O)       | THREATS (T)
------------------|-------------------------|-------------------------
STRENGTHS (S)     | SO - Maxi/Maxi          | ST - Maxi/Mini
                  | Use strengths to pursue | Use strengths to reduce
                  | opportunities           | impact of threats
                  |                         |
                  | SO1: [S? + O?] = [action]| ST1: [S? + T?] = [action]
                  | SO2: [S? + O?] = [action]| ST2: [S? + T?] = [action]
------------------|-------------------------|-------------------------
WEAKNESSES (W)    | WO - Mini/Maxi          | WT - Mini/Mini
                  | Fix weaknesses to       | Minimize weaknesses and
                  | capture opportunities   | avoid threats (defensive)
                  |                         |
                  | WO1: [W? + O?] = [action]| WT1: [W? + T?] = [action]
                  | WO2: [W? + O?] = [action]| WT2: [W? + T?] = [action]

Action item quality rules:

• Each action must be specific: who does what, by when, with what success metric
• SO actions are offensive growth moves - prioritize these
• ST actions are defensive moat-building - critical for market leaders
• WO actions are investment/build priorities - typically roadmap items
• WT actions are risk mitigation - often process or partnership plays

---

Worked SWOT example (condensed)

Subject: Acme Deploy (deployment automation tool)
Date: 2025-Q1

S1: One-click rollback - fastest in market (NPS drivers: "rollback saved us" x34)
S2: Multi-cloud support (AWS + GCP + Azure natively)
W1: No on-premise support - blocks 30% of enterprise deals (source: CRM lost reasons)
W2: Dashboard UX rated poor (G2 average: 3.2/5 for "ease of use")
O1: Enterprise compliance wave - SOC2 automation demand up 3x (Gartner 2024)
O2: AI-generated deployment configs trend - 60% of teams trialing AI assist
T1: AWS CodeDeploy native expansion (AWS ecosystem lock-in risk)
T2: New entrant DeployAI raised $20M targeting our SMB base (TechCrunch Jan 2025)

SO: S2 + O1 = Launch multi-cloud SOC2 compliance bundle before AWS adds it
ST: S1 + T2 = Lead with rollback safety in DeployAI competitive messaging
WO: W1 + O1 = Build on-premise beta for 3 reference enterprise customers by Q3
WT: W2 + T2 = Accelerate UX redesign before DeployAI targets our SMB churners

---

Positioning Map Construction Guide

A positioning map (perceptual map) is a 2x2 grid that plots competitors visually on two strategically meaningful axes. The goal is to reveal clusters (contested space) and gaps (open space) in the market.

Step 1 - Choose the right axes

The axes make or break the map. Bad axes produce a map where everyone clusters in one quadrant and the picture is meaningless.

Good axis criteria:

1. Customer decision criteria - The axis must represent something customers actually weigh when choosing. If customers do not think about it, it is not useful.
2. Real variance - Competitors must actually differ on this dimension. If everyone scores "high" on ease of use, ease of use is not a good axis.
3. Orthogonality - The two axes should be independent (not correlated). Testing: "If I moved a product along Axis 1, would its Axis 2 position automatically change?" If yes, the axes are correlated.

Axis discovery process:

• List the top 5-7 reasons customers choose or reject products in this market
• Identify the two that create the most meaningful segmentation
• Validate against win/loss data: do these dimensions predict outcomes?

---

Step 2 - Score each competitor

Score each competitor on each axis using a consistent method:

Option A - Evidence-based scoring: Use G2/Capterra review themes, hands-on trial notes, customer interviews. Score 1-10 on each axis. Document the rationale for each score.

Option B - Qualitative placement: Place each competitor in a quadrant (high/high, high/low, low/high, low/low) based on their primary positioning and target customer.

---

Step 3 - Draw and interpret the map

Full template:

POSITIONING MAP
Market: [name]
Axes: [Y axis label] (vertical) vs [X axis label] (horizontal)
Date: [YYYY-MM-DD]

                    High [Y Axis Label]
                           |
  [Competitor C]           |      [Competitor A]
                           |
  Low [X Axis Label] ------+------ High [X Axis Label]
                           |
                           |  [Competitor B]  [Competitor D]
                    Low [Y Axis Label]

Quadrant interpretation:
- Top-left  ([Low X, High Y]): [What this position means for buyers]
- Top-right ([High X, High Y]): [What this position means for buyers]
- Bot-left  ([Low X, Low Y]): [What this position means for buyers]
- Bot-right ([High X, Low Y]): [What this position means for buyers]

Where we are: [Your product position and why it is strategically defensible]

Open space identified: [Any quadrant with high customer demand but no strong competitor]

Strategic implication: [What this map tells us about where to position or invest]

---

Common positioning map pitfalls

Pitfall	What happens	Fix
Axes chosen to make you look good	Map is dishonest; strategy built on it fails	Choose axes based on customer decision criteria, not self-flattery
Too many competitors plotted	Map is unreadable; message is lost	Limit to 6-8 competitors; group others into "others" cluster
Map never updated	Competitors reposition; map becomes misleading	Rebuild every 6 months or after major competitor moves
Axes with no variance	Everyone clusters; no insight generated	Test axis: if 3+ competitors share the same score, choose a different axis
Open space assumed to mean opportunity	White space may exist because there is no demand there	Validate open space with customer research before repositioning

Market Landscape - Deep Dive

Porter's Five Forces

Use Porter's Five Forces to assess the structural attractiveness of a market before entering or when evaluating competitive intensity.

1. Threat of New Entrants

How easy is it for new competitors to enter this market?

Factors that raise barriers (good for incumbents):

• High capital requirements (hardware, infrastructure)
• Strong network effects (marketplace, social platform)
• Regulatory requirements (fintech, healthcare)
• Proprietary technology or patents
• High switching costs for customers
• Brand loyalty and trust built over years

Factors that lower barriers (bad for incumbents):

• Open-source alternatives reduce build cost
• Cloud infrastructure eliminates hardware investment
• API-first platforms enable fast assembly of competing products
• Low switching costs (export data easily, no lock-in)

Assessment template:

Threat of New Entrants: [High / Medium / Low]
Key barriers: [list top 3]
Key enablers: [list top 2]
Implication: [one sentence on what this means for your strategy]

2. Bargaining Power of Suppliers

Who supplies the critical inputs to your product, and can they squeeze you?

For software companies, "suppliers" include:

• Cloud infrastructure providers (AWS, GCP, Azure)
• AI model providers (OpenAI, Anthropic, Google)
• Key open-source projects (if a critical dependency)
• Data providers (if your product depends on third-party data)
• Distribution platforms (App Store, Chrome Web Store)

High supplier power indicators:

• Few alternatives (one dominant AI model provider)
• High switching cost (deep integration with one cloud)
• Supplier could forward-integrate (AWS building competing products)

3. Bargaining Power of Buyers

How much leverage do your customers have?

High buyer power indicators:

• Few large customers account for most revenue
• Low switching costs (easy data export, standard formats)
• Buyers are price-sensitive (commodity market)
• Buyers have full information on alternatives
• The product is a small part of the buyer's total spend

Low buyer power indicators:

• Fragmented customer base (no single customer is >5% of revenue)
• High switching costs (data lock-in, workflow integration)
• Product is mission-critical with few alternatives

4. Threat of Substitutes

What completely different approaches could replace your product category?

Substitutes are not direct competitors - they are different solutions to the same problem. Examples:

• Video conferencing substitutes for business travel
• AI code generation substitutes for hiring junior developers
• No-code tools substitute for custom software development
• Outsourcing substitutes for internal tool building

Assessment: For each substitute, evaluate:

• Performance trade-off: does the substitute do the job well enough?
• Price trade-off: is the substitute meaningfully cheaper?
• Switching cost: how hard is it for buyers to move to the substitute?

5. Competitive Rivalry

How intense is competition among existing players?

High rivalry indicators:

• Many competitors of similar size
• Slow market growth (fighting for share, not growth)
• Low differentiation (commodity features)
• High fixed costs (pressure to fill capacity)
• High exit barriers (can't easily leave the market)

Low rivalry indicators:

• Clear market leader with >40% share
• Fast market growth (enough for everyone)
• Strong differentiation between players
• High switching costs reduce churn between competitors

---

Strategic Group Mapping

Strategic groups are clusters of competitors that follow similar strategies. Mapping them reveals who you really compete against (not everyone in the market).

How to build a strategic group map:

1. Choose two strategic dimensions that separate competitors:

   • Price level (low/mid/high)
   • Product scope (point solution vs platform)
   • Target segment (SMB vs mid-market vs enterprise)
   • Geographic focus (regional vs global)
   • Go-to-market (self-serve vs sales-led vs channel)
   • Technology approach (cloud-native vs on-premise)

2. Plot competitors as circles on a 2D grid. Circle size = relative market share or revenue.

3. Draw boundaries around clusters. Competitors within a cluster are your direct strategic rivals. Competitors in other clusters compete differently.

Example:

Strategic Group Map: Project Management Tools

                    Enterprise
                         |
           [MS Project]  |  [ServiceNow]
           [Smartsheet]  |  [Jira]
                         |
  Point Solution --------+-------- Platform
                         |
           [Todoist]     |  [Notion]
           [Things]      |  [Monday.com]
                         |
                      SMB

Mobility barriers: The factors that make it hard to move between strategic groups. A point solution cannot easily become a platform (requires years of development). A sales-led enterprise tool cannot easily become self-serve (requires product rebuild). These barriers protect your strategic group from invasion.

---

TAM / SAM / SOM Analysis

Use TAM/SAM/SOM to size the market opportunity and set realistic targets.

Definitions:

• TAM (Total Addressable Market): Total revenue opportunity if you captured 100% of the market. Every possible customer, globally.
• SAM (Serviceable Addressable Market): The portion of TAM you can realistically reach with your current product, geography, and go-to-market.
• SOM (Serviceable Obtainable Market): The portion of SAM you can realistically capture in the next 1-3 years given competition and resources.

Calculation methods:

Top-down (quick, less accurate):

TAM = [Total # of potential customers] x [Average annual contract value]
SAM = TAM x [% in your target segment and geography]
SOM = SAM x [Realistic market share % in 1-3 years]

Bottom-up (slower, more accurate):

SOM = [# of customers you can reach with current sales capacity]
      x [Expected win rate]
      x [Average deal size]
SAM = SOM / [Your expected market share in reachable segment]
TAM = SAM / [% of total market your segment represents]

Rules of thumb:

• Always present both top-down and bottom-up. If they differ by >5x, your assumptions are wrong somewhere.
• Investors care about SAM more than TAM. A $100B TAM means nothing if your SAM is $50M.
• SOM should be achievable - tie it to your sales headcount, pipeline, and conversion rates.
• Update annually as the market evolves.

---

Market Segmentation for Competitive Analysis

Segment the market to identify where you can win, not just where the market is big.

Segmentation criteria:

• Company size: SMB (<100 employees), Mid-market (100-1000), Enterprise (1000+)
• Industry vertical: Each vertical has different needs, budgets, and buying processes
• Use case: What specific job they hire your product for
• Technical maturity: Early adopters vs mainstream vs laggards
• Current solution: What they use today (competitor, spreadsheet, nothing)

Competitive heat map:

| Segment           | Your Strength | Comp A | Comp B | Status Quo | Priority |
|-------------------|---------------|--------|--------|------------|----------|
| SMB / SaaS        | Strong        | Strong | Weak   | Medium     | Defend   |
| Mid-market / SaaS | Medium        | Strong | Strong | Low        | Invest   |
| Enterprise / Fin  | Weak          | Medium | Strong | Low        | Monitor  |
| SMB / Ecommerce   | Medium        | Weak   | Weak   | Strong     | Attack   |

Priority definitions:

• Defend: You are strong here; protect the position
• Invest: Opportunity to gain share; allocate resources
• Attack: Competitors are weak; offensive opportunity
• Monitor: Not worth investing now; watch for changes
• Abandon: Low opportunity, strong competition; redirect resources

Positioning Frameworks - Deep Dive

April Dunford's Obviously Awesome Framework

The most practical positioning methodology for B2B products. Based on the book "Obviously Awesome" by April Dunford. Use this when positioning feels unclear or when your product is misunderstood by the market.

The Five Components of Positioning

Every positioning exercise must answer these five questions in this exact order:

1. Competitive Alternatives What would customers do if your product did not exist?

• Not just direct competitors - include spreadsheets, manual processes, hiring an intern, using a different category of tool
• Interview recent customers: "What were you doing before you found us?"
• List all alternatives, then rank by frequency

2. Unique Attributes What features or capabilities do you have that the alternatives lack?

• Must be objectively true and verifiable
• Focus on what is genuinely unique, not what is merely "better"
• Technical capabilities, integrations, data advantages, UX innovations

3. Value (and proof) What value do those unique attributes deliver to customers?

• Translate features into outcomes: "real-time sync" becomes "your team never works on stale data"
• Attach proof points: customer metrics, case studies, third-party validation
• Value must be measurable or at least observable

4. Target Customer Characteristics Who cares most about the value you deliver?

• Not a demographic - describe the characteristics that make them a great fit
• Example: "Engineering teams that deploy more than 10 times per day" (not "mid-market SaaS companies")
• The best target customer segment is the one where your unique attributes matter most

5. Market Category What market category makes your value obvious?

• The category sets buyer expectations for features, pricing, and competitors
• Three options: existing category, sub-category, or new category
• Choose the category that gives you an unfair advantage

Positioning Canvas

+-------------------------------------------------------------------+
| POSITIONING CANVAS                                                |
+-------------------------------------------------------------------+
| Competitive Alternatives:                                         |
| 1. [Alternative 1]                                                |
| 2. [Alternative 2]                                                |
| 3. [Alternative 3 - often "do nothing" or "use spreadsheet"]      |
+-------------------------------------------------------------------+
| Unique Attributes:            | Value (with proof):               |
| - [Attribute 1]               | - [Value 1] ([proof])             |
| - [Attribute 2]               | - [Value 2] ([proof])             |
| - [Attribute 3]               | - [Value 3] ([proof])             |
+-------------------------------------------------------------------+
| Target Customer:              | Market Category:                  |
| [Characteristics that make    | [Category that makes the value    |
|  them a perfect fit]          |  obvious to the buyer]            |
+-------------------------------------------------------------------+

Common mistakes with the Dunford framework

• Starting with the market category instead of competitive alternatives
• Listing features as "unique attributes" without verifying competitors lack them
• Defining target customers by demographics instead of behavioral characteristics
• Choosing a category to sound impressive rather than to clarify value

---

Category Design

Sometimes the right positioning move is to create a new category rather than compete in an existing one. Use this approach sparingly - it is expensive and high-risk but can produce outsized returns.

When to create a new category

Create a new category only if ALL of these are true:

1. Existing categories actively confuse buyers about what you do
2. Your product combines capabilities from multiple existing categories
3. You have the budget and patience for 18-24 months of category education
4. The new category name is intuitive - a first-time hearer should roughly understand what it means

When NOT to create a new category

• You are a startup with limited marketing budget
• Your product fits neatly into an existing category where you can win
• You are creating a category just to avoid competing with an incumbent
• The category name requires a paragraph of explanation

Category design framework

Step 1 - Name the problem, not the product: The category name should describe the problem space, not your solution.

• Good: "Revenue Intelligence" (Gong)
• Good: "Conversational AI" (a whole space)
• Bad: "Smart CRM" (sounds like a feature, not a category)

Step 2 - Define the category with a POV: Write a "Point of View" document that explains:

• Why the old way of doing things is broken
• What has changed in the world that makes a new approach necessary
• What the new approach looks like (your category)
• Who benefits and how

Step 3 - Lightning strike: Launch the category with concentrated effort:

• Analyst briefings (Gartner, Forrester)
• Thought leadership content (not product content)
• Industry event or launch moment
• Community building around the category (not your product)

---

Messaging Architecture

Positioning lives in a strategy document. Messaging is how positioning shows up in actual customer-facing materials. Build a messaging architecture that translates positioning into consistent language across all channels.

Messaging hierarchy

LEVEL 1: Positioning statement (internal only)
  "For [target] who [need], [product] is the [category] that [differentiator]"

LEVEL 2: Value proposition (homepage hero, elevator pitch)
  One sentence that communicates the primary benefit
  Example: "Ship features 10x faster without breaking production"

LEVEL 3: Three pillars (landing pages, sales decks)
  Three supporting messages, each with:
  - Pillar headline (benefit-oriented)
  - Supporting copy (2-3 sentences)
  - Proof point (metric, customer quote, or demo)

LEVEL 4: Proof points (throughout all materials)
  - Customer logos and case studies
  - Metrics and benchmarks
  - Awards and analyst recognition
  - Integration partnerships

Messaging template

VALUE PROPOSITION:
[One sentence - the primary benefit for your target customer]

PILLAR 1: [Benefit headline]
[2-3 sentences explaining how you deliver this benefit]
Proof: [Customer name] achieved [metric] using [product]

PILLAR 2: [Benefit headline]
[2-3 sentences explaining how you deliver this benefit]
Proof: [Third-party validation or benchmark]

PILLAR 3: [Benefit headline]
[2-3 sentences explaining how you deliver this benefit]
Proof: [Demo or technical proof point]

Messaging consistency checklist

• All customer-facing pages use the same value proposition language
• Sales deck pillars match website pillars
• Customer success uses the same terminology as marketing
• Product UI labels align with external messaging (no internal jargon)
• Competitive claims are substantiated with proof points

---

Positioning Against Specific Competitor Types

Against the market leader

• Do not fight them on their terms (more features, broader platform)
• Find a niche where you are 10x better and own it completely
• Position their strength as a weakness: "They are built for everyone, we are built for [your specific audience]"
• Lead with speed, focus, or modern architecture as differentiators

Against a well-funded startup

• Emphasize stability, track record, and customer base
• Highlight the risk of betting on an unproven vendor
• Compete on depth rather than breadth of features
• Build switching costs through integrations and workflows

Against open-source alternatives

• Position around total cost of ownership, not license cost
• Lead with support, security, compliance, and uptime guarantees
• Emphasize time-to-value and managed experience
• Offer a free tier that captures users before they self-host

Against "do nothing" / status quo

• Quantify the cost of the current approach (hours, errors, missed revenue)
• Show a before/after comparison with specific metrics
• Reduce perceived risk of change (free trial, migration support, rollback)
• Find an internal champion who feels the pain most acutely

Advanced SWOT Techniques

TOWS Matrix

The TOWS matrix is the action-oriented extension of SWOT. While SWOT identifies factors, TOWS crosses them to generate strategies. This is where the actual value of the exercise lives.

How to build a TOWS matrix

Take the completed SWOT grid and systematically cross each quadrant pair:

                    | Strengths (S)              | Weaknesses (W)             |
                    | S1: [strength]             | W1: [weakness]             |
                    | S2: [strength]             | W2: [weakness]             |
                    | S3: [strength]             | W3: [weakness]             |
--------------------|----------------------------|----------------------------|
Opportunities (O)   | SO Strategies              | WO Strategies              |
O1: [opportunity]   | Use S to maximize O        | Overcome W to exploit O    |
O2: [opportunity]   |                            |                            |
--------------------|----------------------------|----------------------------|
Threats (T)         | ST Strategies              | WT Strategies              |
T1: [threat]        | Use S to minimize T        | Minimize W to avoid T      |
T2: [threat]        |                            |                            |
--------------------|----------------------------|----------------------------|

Strategy types explained

SO Strategies (Strength-Opportunity) - PURSUE AGGRESSIVELY These are your best plays. You have an internal advantage aligned with an external opportunity. Examples:

• "Use our superior data pipeline (S) to capture the growing demand for real-time analytics (O)"
• "Leverage our strong brand in SMB (S) to expand into the adjacent mid-market segment (O)"

WO Strategies (Weakness-Opportunity) - INVEST TO FIX You see an opportunity but have a weakness blocking you. Decide whether to invest in fixing the weakness or partner around it. Examples:

• "Our lack of enterprise SSO (W) blocks us from the enterprise segment (O) - build SSO in Q2 to unlock enterprise deals"
• "We lack a mobile app (W) but mobile usage is growing 40% YoY (O) - partner with a mobile-first platform or acquire"

ST Strategies (Strength-Threat) - DEFEND AND LEVERAGE An external threat exists but you have strengths to counter it. Examples:

• "A new competitor entered with lower pricing (T) but our deep integrations create high switching costs (S) - emphasize integration ecosystem in messaging"
• "AI-generated content threatens our writing tool (T) but our editorial workflow and brand trust are strong (S) - position as 'AI + human editorial'"

WT Strategies (Weakness-Threat) - MITIGATE OR EXIT Your weakest position. An external threat targets an internal weakness. Be honest about whether to defend or retreat. Examples:

• "Our legacy codebase (W) makes it hard to match the competitor's release speed (T) - start platform rewrite or consider acquisition"
• "We lack regulatory compliance (W) as new regulations approach (T) - hire compliance team immediately or exit the regulated segment"

---

Weighted SWOT Scoring

Simple SWOT lists treat all items as equal. Weighted scoring forces prioritization and makes the output actionable.

Scoring methodology

For each SWOT item, score on two dimensions:

For Strengths and Weaknesses:

• Importance to the customer (1-5 scale)
• Your relative performance vs competitors (1-5 scale)
• Score = Importance x Performance

For Opportunities and Threats:

• Probability of occurring (1-5 scale)
• Impact if it occurs (1-5 scale)
• Score = Probability x Impact

Scoring template

STRENGTHS
| Item                        | Importance | Performance | Score | Priority |
|-----------------------------|------------|-------------|-------|----------|
| [Strength 1]                | 5          | 4           | 20    | High     |
| [Strength 2]                | 3          | 5           | 15    | Medium   |
| [Strength 3]                | 4          | 3           | 12    | Medium   |

WEAKNESSES
| Item                        | Importance | Performance | Score | Priority |
|-----------------------------|------------|-------------|-------|----------|
| [Weakness 1]                | 5          | 2           | 10    | Critical |
| [Weakness 2]                | 3          | 1           | 3     | Low      |

OPPORTUNITIES
| Item                        | Probability | Impact | Score | Priority |
|-----------------------------|-------------|--------|-------|----------|
| [Opportunity 1]             | 4           | 5      | 20    | High     |
| [Opportunity 2]             | 2           | 5      | 10    | Medium   |

THREATS
| Item                        | Probability | Impact | Score | Priority |
|-----------------------------|-------------|--------|-------|----------|
| [Threat 1]                  | 4           | 4      | 16    | High     |
| [Threat 2]                  | 2           | 3      | 6     | Low      |

Priority thresholds:

• Score 15-25: High priority - address immediately
• Score 8-14: Medium priority - plan for next quarter
• Score 1-7: Low priority - monitor but do not invest

---

Competitive Response Modeling

Predict how competitors will react to your moves before you make them.

Response matrix

For each strategic move you are considering, model the likely competitive response:

YOUR MOVE: [Describe your planned action]

| Competitor | Most Likely Response    | Response Time | Your Counter-move      |
|------------|-------------------------|---------------|------------------------|
| Comp A     | [What they will do]     | [Days/weeks]  | [How you respond]      |
| Comp B     | [What they will do]     | [Days/weeks]  | [How you respond]      |
| Comp C     | [What they will do]     | [Days/weeks]  | [How you respond]      |

Competitor response archetypes

The Fast Follower: Copies your features within 1-3 months. Counter by continuously shipping and building switching costs before they catch up.

The Price Warrior: Responds to your moves by cutting prices. Counter by competing on value, not price. Raise switching costs through integrations.

The Platform Player: Responds by bundling your feature into their larger platform. Counter by being 10x better at the specific job and building a specialist brand.

The Indifferent Incumbent: Does not respond at all (too big, too slow, or does not perceive you as a threat). Exploit the window aggressively before they wake up.

The Legal Challenger: Responds with patent claims, cease-and-desist, or regulatory complaints. Counter by ensuring your IP is clean and having legal counsel review competitive claims.

Modeling guidelines

1. Base predictions on past behavior - how did this competitor respond to the last market entrant or price change?
2. Consider their incentives and constraints - a public company may not cut prices due to margin pressure
3. Factor in response time - if it takes them 6 months to ship a feature, you have a 6-month window
4. Plan two moves ahead - what do you do after they respond?

---

Scenario Planning

Use scenario planning when the competitive landscape is uncertain and multiple futures are plausible.

Four-scenario framework

1. Choose two critical uncertainties about the market (things that could go either way and would significantly change the landscape)
2. Cross them to create four scenarios
3. Name each scenario memorably
4. Develop strategy implications for each

Template:

Uncertainty 1: [e.g., "AI adoption speed" - fast vs slow]
Uncertainty 2: [e.g., "Regulatory environment" - permissive vs restrictive]

                    Fast AI Adoption
                         |
  "AI Gold Rush"         |         "Regulated AI Boom"
  (Fast + Permissive)    |         (Fast + Restrictive)
                         |
  Permissive ------------+------------ Restrictive
                         |
  "Slow Burn"            |         "Locked Down"
  (Slow + Permissive)    |         (Slow + Restrictive)
                         |
                    Slow AI Adoption

For each scenario, document:

SCENARIO: [Name]
Assumptions: [What must be true for this to happen]
Probability: [Low / Medium / High]
Competitive implications:
  - Winner: [Who benefits most]
  - Loser: [Who suffers most]
  - Our position: [Where we stand]
Strategy:
  - If this scenario unfolds: [What we do]
  - Early warning signals: [What to watch for]
  - Hedging move (do now regardless): [Low-cost action that helps in this scenario]

Hedging strategies

The most valuable output of scenario planning is identifying "no-regret moves" - actions that help regardless of which scenario unfolds:

• Building platform flexibility (helps in all scenarios)
• Investing in customer relationships (always valuable)
• Maintaining financial reserves (optionality)
• Building data assets (competitive moat in any future)

And "option-creating moves" - small investments that give you the right (but not obligation) to pursue a strategy if a specific scenario unfolds:

• Proof-of-concept with a new technology (option on that technology)
• Partnership discussion with a potential acquirer (option on exit)
• Pilot in a new segment (option on expansion)