Competitive Strategy
Pipeline stage: CompetitorAgent | Merged from: marketing-strategy-pmm, product-strategist, startup-analyst
Frameworks and templates for competitive positioning, differentiation, market defense, go-to-market execution, and product marketing operations. Covers April Dunford positioning methodology, Value Proposition Canvas, competitive intelligence gathering, battlecard creation, SWOT analysis, Porter's Five Forces, Blue Ocean Strategy, positioning maps, win/loss analysis, ICP definition, market segmentation, GTM launch playbooks, international market entry, product launch tiers, sales enablement, and PMM operations.
When to Use
- Analyzing the competitive landscape for a startup or product
- Developing positioning and messaging strategy
- Creating competitive battlecards for sales enablement
- Running SWOT or Porter's Five Forces analysis
- Building a positioning map to visualize market placement
- Conducting win/loss analysis on closed deals
- Identifying Blue Ocean opportunities and uncontested market space
- Preparing competitive sections for pitch decks or investor materials
- Responding to a new competitor entering the market
- Defining ICP and buyer personas for B2B SaaS
- Planning market segmentation and prioritization
- Building a 90-day GTM launch plan
- Entering international markets (US, UK, DACH, France, Canada)
- Running tiered product launches (Tier 1/2/3)
- Creating sales enablement assets and training programs
- Setting up PMM KPIs, reporting, and team handoff protocols
1. Positioning Framework (April Dunford Method)
Six-step methodology for developing defensible market positioning. Work through each step sequentially -- earlier steps inform later ones.
Step 1: List Your True Competitive Alternatives
Not just direct competitors -- what would customers do if your product did not exist?
Alternatives:
1. Competitor A (direct — same category)
2. Competitor B (direct — same category)
3. Spreadsheets + email (status quo)
4. Build in-house (DIY)
5. Do nothing (ignore problem)
Key question: "If we didn't exist, what would the customer use instead?"
Step 2: Isolate Your Unique Attributes
What do you have that alternatives do not? List features, capabilities, and approaches that are genuinely differentiated.
Unique Attributes:
1. [Feature X that no one else has]
2. [Integration Y that's exclusive]
3. [Approach Z that's differentiated]
4. [Performance metric better than all]
Filter: Only include attributes that at least one alternative lacks. Table-stakes features shared by everyone are not positioning differentiators.
Step 3: Map Attributes to Value
What value do these attributes provide to customers? Connect each attribute to a measurable outcome.
Attribute: [Real-time collaboration]
-> Value: Teams can work together simultaneously
-> Outcome: 50% faster project completion
Attribute: [AI-powered automation]
-> Value: Eliminates manual data entry
-> Outcome: Save 10 hours/week per user
The outcome must matter to the buyer. If you cannot quantify it, at least make it concrete and specific.
Step 4: Define Your Best-Fit Customers
Who cares most about this value? These are the customers where you win fastest and retain longest.
Best-Fit: Mid-market SaaS companies (200-1000 employees)
Why: They have distributed teams, need real-time collaboration
Evidence: Fastest sales cycles, lowest churn, highest NPS
Validation signals for best-fit:
- Fastest sales cycles (< median time to close)
- Highest LTV (> median customer value)
- Lowest churn (< 5% annual)
- Strong product engagement (daily/weekly usage)
- Referenceable (NPS 9-10, willing to do case studies)
Step 5: Nail Your Market Category
What market do you dominate? Three strategic options:
Options:
- Head-to-head: Compete in existing category (e.g., "CRM")
When: You can credibly claim leadership or top-3 position
- Big fish, small pond: Own a niche (e.g., "CRM for agencies")
When: You dominate a specific segment but not the whole category
- Create new category: Define a new space (risky, expensive)
When: No existing category fits; you have budget to educate the market
Decision: Choose based on competitive strength and budget
Step 6: Layer on Trends
What macro trends make this the right time to buy?
Trends:
- Remote work normalization (2020-2026)
- AI/ML adoption in enterprise (2024-2026)
- Data privacy regulations (GDPR, CCPA, AI Act)
- Platform consolidation (buyers want fewer tools)
Trends add urgency. They explain why now, not just why us.
Positioning Statement Template
FOR [target customer]
WHO [statement of need/opportunity]
[Product name] IS A [product category]
THAT [key benefit/differentiator]
UNLIKE [competitive alternative]
OUR PRODUCT [primary differentiation]
One-liner template:
[Product] helps [Target Customer] [Achieve Goal] by [Unique Approach]
Example: "Acme helps mid-market SaaS teams ship 2x faster by automating project workflows with AI"
Positioning Development Timeline
Week 1: Research (10-15 customer interviews, competitive analysis, market trends) -> Week 2: Framework (Dunford exercise, unique value, best-fit) -> Week 3: Messaging (value prop, hierarchy, persona variants) -> Week 4: Validation (sales team test, A/B landing pages, customer feedback) -> Week 5-6: Rollout (website, decks, training, campaigns)
2. Messaging Architecture
Value Proposition Hierarchy
| Level | Content | Example |
|---|---|---|
| L1: Value Prop | One-liner | "[Product] helps [target] [goal] by [approach]" |
| L2: Key Benefits | 3-5 bullets | Speed (2x faster), Quality (-50% bugs), Cost (-$100k/yr) |
| L3: Features | Feature -> Benefit -> Outcome | AI automation -> no manual work -> save 10 hrs/wk |
| L4: Proof Points | Logos, stats, case studies | 10,000+ teams, 4.8/5 G2, [Customer] case study |
Messaging by Persona
| Persona | Concern | Tone | Key Message Type | Proof Type |
|---|---|---|---|---|
| Economic Buyer (VP/Dir) | ROI, outcomes | Data-driven | Revenue/cost impact | ROI calculator, case studies |
| Technical Buyer (Eng) | Fit, security, scale | Technical, objective | Architecture, uptime, compliance | Tech docs, security whitepaper |
| End User (Mgr/IC) | Ease of use, workflow | Friendly, practical | Time saved, simplicity | Demo, free trial, testimonials |
Messaging Testing & Iteration
Qualitative -- Ask 10-15 customers: "How would you describe [Product] to a colleague?", "What's the main benefit?", "Why us over [Competitor]?"
Quantitative -- A/B test headlines, ad copy, email subjects. Measure CTR, conversion rate, demo requests.
Sales Feedback -- Monthly: "Which message resonates most?", "What objections?", "How do customers compare us to [Competitor]?"
Iteration Cycle: Test (2-4 wk) -> Analyze (1 wk) -> Update docs (1 wk) -> Train sales (1 wk) -> Repeat quarterly
3. Competitive Analysis Frameworks
Competitor Tiering
Tier 1: Direct Competitors (head-to-head, same category)
- [Competitor A]: Market leader, $100M+ ARR
- [Competitor B]: Fast-growing challenger, Series B
- [Competitor C]: Open-source alternative
Tier 2: Indirect Competitors (adjacent solutions)
- [Alt Solution D]: Different approach, overlapping use case
- [Alt Solution E]: Broader platform, includes your feature
Tier 3: Status Quo (what customers do today)
- Spreadsheets + email
- Build in-house
- Do nothing
Competitive Matrix (Star Ratings)
| Factor | Us | Competitor A | Competitor B |
|---|---|---|---|
| Price | $X | $Y | $Z |
| Feature 1 | ★★★ | ★★ | ★★★★ |
| Feature 2 | ★★★★ | ★★★ | ★★ |
| UX | ★★★★ | ★★ | ★★★ |
| Support | ★★★ | ★★★★ | ★★ |
| Integration | ★★★★ | ★★★ | ★★★★ |
Rate each dimension 1-4 stars. Include yourself and all Tier 1 competitors. Additional dimensions to compare: security, performance, scalability, documentation, pricing flexibility.
Feature Comparison Matrix
Compare across: Price, core features, UX, support, integrations, security, performance. Rate each 1-4 (1=weak, 2=below avg, 3=good, 4=best-in-class). Include yourself and all Tier 1 competitors.
Threat Level Assessment
For each competitor, assess:
| Dimension | Low | Medium | High |
|---|---|---|---|
| Market overlap | < 20% same ICP | 20-60% same ICP | > 60% same ICP |
| Feature parity | Missing core features | Partial overlap | Near-complete match |
| Growth rate | < 20% YoY | 20-50% YoY | > 50% YoY |
| Funding | < $10M raised | $10-50M raised | > $50M raised |
| Brand strength | Unknown in market | Known in niche | Category leader |
| Pricing pressure | Premium pricing | Market pricing | Aggressive discounting |
Competitive Moat Types
- Network effects -- Value increases with each user (marketplaces, social)
- Switching costs -- High migration cost locks in customers (data, integrations, training)
- Economies of scale -- Lower unit costs at volume (infrastructure, procurement)
- Brand -- Trust, recognition, premium pricing power
- Data -- Proprietary data that improves product over time (AI/ML feedback loops)
- Regulatory -- Licenses, certifications, compliance advantages
- Technology -- Patents, proprietary algorithms, technical infrastructure
For each moat type, rate your strength: None | Emerging | Moderate | Strong
Competitive Intelligence Sources
Product trials, website monitoring (pricing/messaging/feature changes), customer interviews ("What alternatives did you consider?"), sales call recordings (Gong/Chorus), review sites (G2, Capterra), job postings (hiring = roadmap insights), financial filings, social media (competitor execs), partner channels, industry reports (Gartner, Forrester, IDC).
4. SWOT Analysis
Structured Template
STRENGTHS (Internal, Positive) — What do we do better than anyone else?
1. [Strength] — Evidence: [data point]
WEAKNESSES (Internal, Negative) — Where do we fall short?
1. [Weakness] — Impact: [consequence] — Mitigation: [plan]
OPPORTUNITIES (External, Positive) — What trends/gaps to exploit?
1. [Opportunity] — Size: [$ or % growth] — Timeline: [when]
THREATS (External, Negative) — What could hurt our position?
1. [Threat] — Likelihood: [H/M/L] — Severity: [H/M/L] — Response: [plan]
List 3-5 items per quadrant. Every entry needs evidence or a mitigation plan.
Industry Application Guidance
SaaS SWOT focus areas:
- Strengths: NDR, product stickiness, API ecosystem
- Weaknesses: CAC payback, feature gaps, market awareness
- Opportunities: AI integration, vertical expansion, platform play
- Threats: Open-source alternatives, platform bundling, pricing pressure
Marketplace SWOT focus areas:
- Strengths: Liquidity, network effects, take rate
- Weaknesses: Chicken-and-egg, quality control, disintermediation risk
- Opportunities: Adjacent verticals, fintech layer, international expansion
- Threats: Vertical competitors, regulatory changes, supply concentration
B2B SWOT focus areas:
- Strengths: Win rate, ACV growth, customer logos
- Weaknesses: Sales cycle length, competition at enterprise tier
- Opportunities: Upsell/cross-sell, new buyer personas, platform partnerships
- Threats: Incumbent response, budget cuts, consolidation
SWOT-to-Strategy Matrix
| Strengths | Weaknesses | |
|---|---|---|
| Opportunities | SO strategies: Use strengths to capture opportunities | WO strategies: Fix weaknesses to capture opportunities |
| Threats | ST strategies: Use strengths to defend against threats | WT strategies: Minimize weaknesses and avoid threats |
5. Porter's Five Forces
The Five Forces (Assessment Template)
Rate each force as High / Medium / Low and document evidence for each assessment.
Force 1: Threat of New Entrants
- Barriers to entry, capital requirements, brand loyalty
- Regulatory barriers, network effects, technology complexity, distribution access
Force 2: Bargaining Power of Suppliers
- Supplier concentration, switching costs, substitute availability
- Forward integration risk (could suppliers become competitors?)
- Key tech startup suppliers: cloud (AWS/GCP/Azure), AI models (OpenAI/Anthropic/Google), payments (Stripe), data (Clearbit/ZoomInfo)
Force 3: Bargaining Power of Buyers
- Buyer concentration, price sensitivity, switching costs
- Information availability, backward integration (could buyers build it?)
Force 4: Threat of Substitutes
- Substitute availability, price-performance ratio, switching costs
- Common software substitutes: spreadsheets/email, in-house dev, adjacent tools adding your feature, platform bundling
Force 5: Competitive Rivalry
- Number of competitors, industry growth rate, product differentiation
- Exit barriers, fixed cost pressure
Five Forces Summary Table
| Force | Rating | Key Driver | Strategic Response |
|---|---|---|---|
| New Entrants | [H/M/L] | [Driver] | [Response] |
| Supplier Power | [H/M/L] | [Driver] | [Response] |
| Buyer Power | [H/M/L] | [Driver] | [Response] |
| Substitutes | [H/M/L] | [Driver] | [Response] |
| Rivalry | [H/M/L] | [Driver] | [Response] |
Overall Industry Attractiveness: [High / Medium / Low]
6. Positioning Map
X/Y Axis Selection Methodology
Choose two dimensions that (a) matter most to buyers and (b) differentiate you from competitors.
Common axis pairs:
| X-Axis | Y-Axis | Best for |
|---|---|---|
| Price | Feature depth | Showing value positioning |
| Ease of use | Power/flexibility | Showing UX vs. capability tradeoff |
| SMB focus | Enterprise focus | Showing market segment targeting |
| Point solution | Platform | Showing breadth of offering |
| Self-serve | Sales-assisted | Showing GTM motion |
| Generic | Vertical-specific | Showing specialization |
Positioning Map Template
Plot on a 2x2 with labeled quadrants. Example (Price vs. Features):
- Top-left (Premium): High price, low features -- value/simplicity play
- Top-right (Luxury): High price, high features -- enterprise/status
- Bottom-left (Budget): Low price, low features -- cost focus
- Bottom-right (Value): Low price, high features -- best deal
High Price
|
Premium ----+---- Luxury
(High value) | (Status)
|
Low Feature --------+-------- High Feature
|
Budget ----+---- Value
(Cost focus) | (Best deal)
|
Low Price
Coordinate Assignment Process
List all competitors (Tiers 1-3) -> Score each on both axes (1-10) -> Plot coordinates -> Identify your current position -> Identify desired position (12-month target) -> Identify white space (unclaimed quadrants/gaps) -> Validate with customers.
Presenting to Investors
Highlight white space you occupy, show competitor clustering, draw your trajectory (current -> desired position), label quadrants clearly, limit to 5-8 competitors for readability.
7. Battlecard Template
Create one battlecard per Tier 1 competitor. Update monthly or when a competitor launches a major feature.
Full 10-Section Template
=== COMPETITIVE BATTLECARD: [Competitor Name] ===
Last Updated: [Date] | Confidence: [High/Medium/Low]
1. OVERVIEW: Company, founded, HQ, funding, size, customers, revenue est., pricing, URL
2. POSITIONING: Their tagline, reality check, category, target buyer
3. PRICING: Plans, model (per-user/seat/usage/flat), discounting, free tier, vs. ours
4. KEY STRENGTHS: 3+ strengths with why each matters to buyers
5. KEY WEAKNESSES: 3-4 weaknesses with how to exploit in sales
6. OUR ADVANTAGES: 3-4 advantages, quantified (e.g., 10x easier, 50% cheaper)
7. OBJECTION HANDLING: (see talk tracks below)
8. WIN THEMES: When we win + when we lose against this competitor
9. PROOF POINTS: Case studies, review comparisons, win rates, speed, ROI
10. RED FLAGS & QUESTIONS: Discovery questions + signs we'll lose
Objection Handling Talk Tracks
"We're already using [Competitor]" "Many of our customers came from [Competitor]. What prompted you to explore alternatives? Teams typically switch because [ease of use / cost / performance]. Would a side-by-side comparison help?"
"[Competitor] has more features" "They've been around longer with a broader feature set. What we found: most teams use only 20% of those features. Our customers love that we do [core use case] exceptionally well. What features are most critical for your team?"
"[Competitor] is cheaper" Acknowledge price, reframe to total cost of ownership, highlight hidden costs (implementation, training, support), show ROI comparison.
"[Competitor] is the market leader" Acknowledge market position, highlight innovation speed, show where leaders fall short on [specific dimension], reference customers who switched.
Discovery Questions (Uncover Competitor Weaknesses)
- "How long did implementation take with your current solution?"
- "How often do you use [competitor's advanced feature]?"
- "What's your biggest frustration with your current tool?"
- "How responsive is their support team?"
- "Have you experienced any downtime or performance issues?"
Red Flags (Signs We Will Lose)
- Prospect has personal relationship with competitor's exec team
- Already in a multi-year contract
- Evaluation is a checkbox exercise (decision already made)
- Technical buyer is a former employee of competitor
- Budget is locked to competitor's pricing tier
Battlecard Distribution
- Store in: Notion, Confluence, or sales enablement platform
- Update frequency: Monthly (or when competitor launches major feature)
- Access: Sales, CS, Product, Marketing teams
- Training: Monthly competitive update calls with sales team
8. Win/Loss Analysis
Win/Loss Interview Process
Goals: Understand why you won/lost, validate positioning, identify product gaps, track competitive trends.
Process: Identify deals closed in last 30 days -> Request interview -> Conduct (30-45 min, record) -> Analyze themes -> Share monthly insights to product/sales/marketing.
Interview Questions for Wins
- What problem were you trying to solve?
- What alternatives did you evaluate?
- Why did you choose us over [Competitor]?
- What almost made you choose someone else?
- What was the deciding factor in your decision?
- How would you describe our product to a colleague?
- What could we improve about the sales process?
- What feature or capability sealed the deal?
Interview Questions for Losses
- What problem were you trying to solve?
- Who did you choose instead? Why?
- What did we do well in the evaluation process?
- What could we have done differently?
- Was price a factor? How significant?
- Was there a specific feature gap that drove the decision?
- Would you consider us in the future? Under what circumstances?
- How would you rate our sales team's responsiveness and knowledge?
Pattern Identification
Track win/loss data in a structured format:
| Deal | Outcome | Primary Reason | Competitor | Price Factor | Product Gap | Messaging Issue |
|---|---|---|---|---|---|---|
| Acme Corp | Won | Best product fit | Competitor A | No | No | No |
| Beta Inc | Lost | Price | Competitor B | Yes | No | No |
| Gamma LLC | Lost | Missing feature X | Built in-house | No | Yes | No |
Monthly Win/Loss Report Template
Report should include: total deals analyzed (wins/losses), overall win rate, win rate per competitor, top 3 win reasons with mention counts, top 3 loss reasons with mention counts, and action items for Product (gap fixes), Sales (battlecard updates), Marketing (messaging adjustments), and Pricing (changes if needed).
Competitive Response Playbook
When a competitor makes a major move (new feature, pricing change, acquisition):
| Phase | Timeline | Actions |
|---|---|---|
| Assess | Day 1-2 | What changed? Impact on us? Which customers/prospects affected? Rate: Critical/Significant/Minor/Noise |
| Respond | Day 3-7 | Update battlecard, draft sales talking points, prep customer FAQ, identify at-risk pipeline |
| Adapt | Week 2-4 | Adjust positioning, accelerate roadmap items, create competitive content, run targeted campaign |
| Monitor | Ongoing | Track win rate changes, survey customers on perception, watch for follow-up moves |
9. Blue Ocean Strategy
Finding Uncontested Market Space
Blue Ocean Strategy focuses on creating new market space rather than competing in crowded existing markets (Red Oceans).
Red Ocean = compete in existing markets, beat competition, exploit demand, accept value-cost tradeoff. Blue Ocean = create uncontested space, make competition irrelevant, create new demand, pursue differentiation AND low cost simultaneously.
Value Innovation Framework
The cornerstone of Blue Ocean Strategy. Pursue differentiation and low cost simultaneously by asking four questions:
The Four Actions Framework:
ELIMINATE
Which factors that the industry takes for granted should be eliminated?
- [Factor 1] — Why: [Rationale]
- [Factor 2] — Why: [Rationale]
REDUCE
Which factors should be reduced well below industry standard?
- [Factor 1] — To what level: [Target]
- [Factor 2] — To what level: [Target]
RAISE
Which factors should be raised well above industry standard?
- [Factor 1] — To what level: [Target]
- [Factor 2] — To what level: [Target]
CREATE
Which factors should be created that the industry has never offered?
- [Factor 1] — Value to buyer: [Benefit]
- [Factor 2] — Value to buyer: [Benefit]
Strategy Canvas
Plot your value curve against competitors across 5-7 key competing factors (F1-F7). Rate each factor High/Med/Low for each player.
The goal: Your value curve should diverge from competitors -- not mirror them. Three qualities of a good Blue Ocean strategy: focus (don't try to compete on every factor), divergence (your curve looks different from competitors), and a compelling tagline (captures the strategic profile).
Blue Ocean Opportunity Identification
Six paths to finding Blue Oceans: (1) Alternative industries -- what do customers choose between beyond direct competitors? (2) Strategic groups -- underserved tiers within the industry? (3) Buyer chain -- target a different buyer (user vs. purchaser vs. influencer)? (4) Complementary offerings -- what happens before/during/after product use? (5) Functional-emotional appeal -- shift the basis of appeal? (6) Trends over time -- ride external trends to create new value?
Applying Blue Ocean to Startups
Early-stage companies benefit most from Blue Ocean thinking: you lack resources for head-to-head competition, but your advantage is speed and willingness to redefine the problem. Focus on noncustomers:
- Soon-to-be noncustomers -- on the edge of your market, ready to leave
- Refusing noncustomers -- consciously chose against your market
- Unexplored noncustomers -- in distant markets, never considered as customers
10. Value Proposition Canvas
Map customer needs to product value. The canvas has two sides: Customer Profile (what the customer needs) and Value Map (what you offer). Fit = your value map addresses the customer profile.
Customer Profile
CUSTOMER PROFILE VALUE MAP
+---------------------+ +---------------------+
| Customer | | Value |
| Jobs | <-----> | Proposition |
| +-------------+ | | +-------------+ |
| | Pains | | | |Pain Relievers| |
| +-------------+ | | +-------------+ |
| +-------------+ | | +-------------+ |
| | Gains | | | |Gain Creators | |
| +-------------+ | | +-------------+ |
+---------------------+ +---------------------+
Customer Jobs (what customers are trying to get done):
- Functional jobs: tasks they need to accomplish (e.g., "manage team projects")
- Social jobs: how they want to be perceived (e.g., "seen as organized leader")
- Emotional jobs: how they want to feel (e.g., "confident about delivery dates")
Customer Pains (what frustrates them):
- Undesired outcomes, risks, obstacles
- Rate each: Extreme | Severe | Moderate | Light
Customer Gains (what they want to achieve):
- Required gains (minimum expectations)
- Expected gains (standard expectations)
- Desired gains (beyond expectations)
- Unexpected gains (beyond imagination)
Value Map
Pain Relievers -- How your product eliminates or reduces specific customer pains:
Pain: Manual data entry wastes 10 hrs/week
-> Pain Reliever: AI automation eliminates 90% of manual entry
-> Outcome: Save 9 hrs/week per user
Pain: Can't collaborate in real-time (version conflicts)
-> Pain Reliever: Live multi-user editing with conflict resolution
-> Outcome: Zero version conflicts, 50% faster reviews
Gain Creators -- How your product creates specific customer gains:
Gain: Ship products faster
-> Gain Creator: Automated CI/CD pipeline with one-click deploy
-> Outcome: 2x faster release cycles
Gain: Better visibility into team progress
-> Gain Creator: Real-time dashboards with AI-powered insights
-> Outcome: 80% reduction in status meetings
Fit Assessment
Score how well your value map addresses the customer profile:
| Customer Need | Your Solution | Fit (1-5) | Gap? |
|---|---|---|---|
| [Job 1] | [Feature/capability] | 5 | No |
| [Pain 1] | [Pain reliever] | 4 | Minor |
| [Gain 1] | [Gain creator] | 2 | Major gap |
Three types of fit: (1) Problem-Solution Fit -- evidence that customers have these jobs/pains/gains. (2) Product-Market Fit -- evidence your product addresses them (paying customers). (3) Business Model Fit -- evidence you can scale profitably.
11. Market Analysis & Business Model
Market Sizing (TAM/SAM/SOM)
TAM (Total Addressable Market)
Total market demand if 100% market share
Calculation: # of potential customers x average revenue per customer
Example: 10M businesses x $1000/year = $10B
SAM (Serviceable Addressable Market)
Portion of TAM we can serve with our product
Filter by geography, segment, use case
Example: 2M businesses in our target segment = $2B
SOM (Serviceable Obtainable Market)
Realistic market share in 3-5 years
Based on competition, resources, go-to-market
Example: 5% of SAM = $100M
Market Analysis Template
# Market Analysis: [Market Name]
## Market Size
- TAM: $[X]B ([growth rate]% CAGR)
- SAM: $[X]B
- SOM: $[X]M
## Market Dynamics
### Growth Drivers
1. [Driver 1] - [Impact]
2. [Driver 2] - [Impact]
### Market Barriers
1. [Barrier 1] - [Mitigation]
2. [Barrier 2] - [Mitigation]
### Trends
- [Trend 1]: [Description]
- [Trend 2]: [Description]
## Customer Segments
| Segment | Size | Growth | Need | Willingness to Pay |
|---------|------|--------|------|-------------------|
| [Seg A] | [%] | [%] | [Need] | [$] |
| [Seg B] | [%] | [%] | [Need] | [$] |
## Key Success Factors
1. [Factor 1]
2. [Factor 2]
3. [Factor 3]
Business Model Canvas
+-------------------------------------------------------------+
| Key | Key | Value | Customer |
| Partners | Activities | Propositions | Relationships|
| | | | |
| [Who] | [What] | [Why] | [How] |
+---------------+---------------+---------------+--------------+
| Key | | | Customer |
| Resources | | | Segments |
| | | | |
| [With what] | | | [For whom] |
+---------------+---------------+---------------+--------------+
| Cost Structure | Revenue Streams |
| | |
| [How much] | [How] |
+-------------------------------+------------------------------+
Unit Economics
LTV (Lifetime Value)
= ARPU x Gross Margin x Customer Lifetime
= $100/mo x 70% x 36 months = $2,520
CAC (Customer Acquisition Cost)
= Total Sales & Marketing / New Customers
= $500,000 / 1,000 = $500
LTV:CAC Ratio
= $2,520 / $500 = 5.04:1 (Target: >3:1)
CAC Payback
= CAC / (ARPU x Gross Margin)
= $500 / ($100 x 70%) = 7.1 months
Product-Led Growth (PLG) Flywheel
+---------------------------+
| |
v |
+---------+ +-------+-----+
| Acquire | | Refer |
| Users | | Others |
+----+----+ +-------------+
| ^
v |
+---------+ +-------+-----+
| Activate| | Expand |
| Users +--------------+ Usage |
+----+----+ +-------------+
| ^
v |
+---------+ +-------+-----+
| Engage +--------------+ Monetize |
| Users | | Users |
+---------+ +-------------+
PLG Metrics Tree:
ACQUISITION
Website visitors -> Sign-ups -> Activation rate
ACTIVATION
Time to value -> Aha moment reached -> Feature adoption
RETENTION
Daily/Weekly active users -> Feature stickiness -> Churn rate
REVENUE
Conversion rate (free -> paid) -> Expansion revenue -> Net revenue retention
REFERRAL
Viral coefficient -> NPS -> Referral sign-ups
12. ICP Definition Framework
Ideal Customer Profile (ICP) definition for B2B SaaS. Four dimensions, buyer personas, validation checklist, and CRM tracking.
Four Dimensions of ICP
Dimension 1: Firmographics
- Company size: 50-5000 employees (Series A sweet spot)
- Industry: SaaS, Tech, Professional Services
- Geography: US, Canada, UK, Germany, France (prioritize by TAM)
- Revenue: $5M-$500M annual
- Funding stage: Seed to Growth (avoid pre-product)
Dimension 2: Technographics
- Tech stack: Modern (cloud-first, API-driven)
- Maturity: Growing fast, willing to adopt new tools
- Existing tools: [List competitors + complementary products]
- Integration needs: Must integrate with [Salesforce, Slack, etc.]
Dimension 3: Psychographics
- Pain level: 7-10/10 (acute pain, not nice-to-have)
- Buyer motivation: Efficiency, cost savings, revenue growth
- Decision process: 2-6 month sales cycle
- Risk tolerance: Early majority (not bleeding edge)
Dimension 4: Behavioral
- Buying signals: Actively evaluating, budget allocated, timeline defined
- Engagement: Attends webinars, downloads content, visits pricing page
- Champion exists: Internal advocate who will drive adoption
Buyer Personas (3-5 max)
Primary: Economic Buyer (signs contract)
- Title: VP, Director, Head of [Department]
- Goals: ROI, team productivity, cost reduction
- Fears: Implementation failure, team resistance, budget waste
- Messaging: Business outcomes, ROI, case studies
Secondary: Technical Buyer (evaluates product)
- Title: Senior Engineer, Architect, Tech Lead
- Goals: Solves technical problem, easy integration
- Fears: Technical debt, vendor lock-in, poor support
- Messaging: Technical capabilities, architecture, security
User/Champion (advocates internally)
- Title: Manager, Team Lead, Power User
- Goals: Makes their job easier, team loves it
- Fears: Learning curve, change management
- Messaging: UX, ease of use, quick wins
ICP Validation Checklist
- 5+ paying customers match this profile
- Fastest sales cycles (< median time to close)
- Highest LTV (> median customer value)
- Lowest churn (< 5% annual)
- Strong product engagement (daily/weekly usage)
- Referenceable (NPS 9-10, willing to do case studies)
CRM ICP Tracking
- Create "ICP Fit" property: A (perfect), B (good), C (okay), D (poor)
- Score based on firmographics, engagement, product usage
- Report: Win rate by ICP score, pipeline by ICP score
- Action: Focus acquisition on ICP A/B, nurture C, disqualify D
13. Market Segmentation Strategy
Segmentation Dimensions
By Company Size (recommend starting with one):
- SMB (10-200 employees) -- Self-serve PLG, low touch, $100-$2k ACV
- Mid-Market (200-2000 employees) -- Hybrid, inside sales, $2k-$50k ACV
- Enterprise (2000+ employees) -- Sales-led, field sales, $50k+ ACV
By Vertical (choose 2-3 focus verticals):
- Horizontal: Broad appeal (e.g., project management for any industry)
- Vertical: Industry-specific (e.g., healthcare CRM, fintech compliance)
- Approach: Start horizontal, add verticals as you scale
By Use Case (messaging varies):
- Use Case A: [e.g., Team collaboration]
- Use Case B: [e.g., Client management]
- Use Case C: [e.g., Project tracking]
- Each use case = different landing page, messaging, case studies
By Geography (Series A focus):
- US/Canada: Largest TAM, fastest sales cycles, highest willingness to pay
- UK: English-speaking, gateway to EU, similar buying behavior to US
- Germany: Largest EU economy, high data privacy standards (GDPR leader)
- France: Second largest EU market, localization critical
- Nordics: High tech adoption, English proficiency, smaller markets
Segmentation Priority Matrix
Segment: US Mid-Market SaaS Companies (200-2000 employees)
Priority: 1 (Highest)
Rationale:
- Largest TAM ($5B)
- Fastest sales cycle (60 days avg)
- Highest win rate (35%)
- Strong product fit (use cases align)
- Existing customer base (50% of customers)
Budget Allocation: 50% of marketing spend
Repeat for each segment. Rank by: TAM size, sales cycle speed, win rate, product fit, existing traction. Allocate budget proportionally to priority.
14. GTM & Launch Framework
GTM Motion Types
PLG (Product-Led Growth):
- Entry: Free trial or freemium
- Buyer: End user -> Manager -> VP
- Sales: Low touch or self-serve
- ACV: <$10k
- Example: Slack, Notion, Figma
Sales-Led Growth:
- Entry: Demo request -> Sales qualification
- Buyer: VP -> C-level
- Sales: High touch, consultative
- ACV: $25k+
- Example: Salesforce, Workday, SAP
Hybrid (PLG + Sales) -- recommended for Series A:
- Entry: Free trial for SMB, demo for Enterprise
- Buyer: End user (PLG) or Executive (Sales-Led)
- Sales: Self-serve -> Assisted -> Enterprise
- ACV: $5k-$100k
- Example: HubSpot, Atlassian, Zoom
90-Day GTM Launch Playbook
Pre-Launch (Days -90 to -30):
Week 1-4: Foundation
- Define ICP and buyer personas
- Develop positioning and messaging
- Create competitive battlecards
- Set success metrics (pipeline $, MQLs, win rate)
Week 5-8: Content & Enablement
- Build website pages (homepage, product, pricing)
- Create sales deck and demo script
- Produce launch assets (one-pager, case studies, FAQs)
- Develop email nurture sequences
- Train sales team on positioning and talk tracks
Week 9-12: Channel Setup
- Launch paid campaigns (LinkedIn, Google)
- Set up CRM tracking and attribution
- Publish SEO content (blog posts, guides)
- Activate partnerships (co-marketing plans)
- Test conversion funnels (landing page -> signup)
Launch (Days 1-30):
Week 1: Awareness
- Press release distribution
- Email announcement to existing database
- Social media campaign (LinkedIn, Twitter)
- Paid ads go live (awareness campaigns)
- Outbound sales blitz (top 100 accounts)
Week 2-4: Activation
- Monitor conversion rates (daily)
- A/B test landing pages and ad copy
- Sales follow-up on inbound leads (<4 hour SLA)
- Customer interviews (feedback on positioning)
- Adjust messaging based on early signals
Post-Launch (Days 31-90):
Week 5-8: Optimization
- Analyze win/loss data (why did we win/lose?)
- Optimize underperforming channels (pause or pivot)
- Scale winning channels (20% weekly budget increase)
- Publish post-launch case studies
- Expand content (SEO, demand gen)
Week 9-12: Scale
- Enter new market segments (vertical or geo)
- Launch partnerships (co-marketing campaigns)
- Build PLG loops (referral program, viral features)
- Sales team expansion (hire based on pipeline)
- Iterate positioning (quarterly messaging refresh)
Product Launch Tiers
Tier 1: Major Launch (quarterly, high impact)
- Scope: New product, major feature, platform expansion
- Audience: Existing customers + new prospects + press
- Effort: 6-8 weeks prep, full cross-functional launch
- Budget: $50k-$100k (Series A)
- Activities: Press release, webinar, email series, paid ads, sales blitz
Tier 2: Standard Launch (monthly, medium impact)
- Scope: Significant feature, integration, improvement
- Audience: Existing customers + select prospects
- Effort: 3-4 weeks prep, core team involvement
- Budget: $10k-$25k
- Activities: Blog post, email announcement, product update, sales enablement
Tier 3: Minor Launch (weekly, low impact)
- Scope: Small feature, bug fix, optimization
- Audience: Existing customers only
- Effort: 1 week prep, product + marketing only
- Budget: <$5k
- Activities: In-app notification, changelog, support docs
Major Launch Playbook (Tier 1 Detail)
8 Weeks Before Launch:
Week -8: Kickoff
- Kickoff meeting (Product, Marketing, Sales, CS)
- Define launch goals (pipeline $, MQLs, press coverage)
- Identify target audience (ICP, personas)
- Create positioning and messaging
- Assign roles and responsibilities
Week -7: Strategy
- Develop GTM strategy (channels, tactics, budget)
- Create sales enablement (deck, demo script, FAQs)
- Plan content (blog posts, case studies, videos)
- Design creative assets (ads, social graphics, emails)
Week -6: Build
- Build landing pages (product page, demo request)
- Set up CRM campaigns and tracking
- Write press release and pitch media
- Create email nurture sequences
- Produce demo video
Week -5: Enable
- Beta test with select customers (feedback)
- Train sales team (positioning, demo, objection handling)
- Train CS team (onboarding, support docs)
- Finalize launch timeline and channel mix
- Prepare customer case studies
4 Weeks Before Launch:
Week -4: Activate channels
- Launch paid ad campaigns (LinkedIn, Google)
- Publish teaser content (blog, social)
- Send pre-launch email to customer base
- Pitch press and influencers
- Set up webinar registration
Week -3: Ramp
- A/B test landing pages and ad copy
- Ramp up content production (blog posts, videos)
- Sales prospecting (outbound to target accounts)
- Finalize webinar content and speakers
- Prepare launch day checklist
Week -2: Test
- Send reminder emails (webinar, launch countdown)
- Increase paid ad spend (ramp up)
- Sales follow-up on warmed leads
- Dry run: Test all systems (website, forms, CRM)
- Prepare launch day assets (social posts, emails)
Week -1: Final prep
- Final review: All assets approved
- Pre-launch email to VIP customers and partners
- Sales team ready (trained, motivated, quotas set)
- CS team ready (docs updated,
…(truncated)