Chapter 14: Go-to-Market Strategy | The Modern MBA Toolkit

1. GTM Strategy Canvas

Overview

The GTM strategy canvas is an author-created hypothesis set connecting a target customer and buying unit to a problem, differentiated proof, channel, pricing/value metric, economics, capacity, onboarding, retention, and learning. Value-proposition/customer-profile concepts are bounded by the registered source; a completed canvas is not evidence of fit. ^[1]

How to Apply

Fill each field with an assumption, evidence owner, uncertainty, and next test. Compare alternatives, customer harm, access, channel capacity, contract/privacy constraints, margin, cash timing, and service burden before treating the canvas as a launch recommendation.

Constructed-example boundary: The customer descriptions, counts, prices, percentages, targets, and operating values in the examples below are invented teaching inputs. They are not benchmarks, forecasts, observed company results, or evidence of causality.

Purpose: Reconcile a set of GTM hypotheses in one view. The canvas is an author synthesis; customer-profile/value-proposition concepts are supported by the registered source, but a completed canvas is not evidence of fit. ^[1]

Canvas Components:

A. Target Customer (WHO)

Definition: Who are you selling to?
Examples:
- B2B: "Mid-market SaaS companies ($5M-50M revenue)"
- B2C: "Young professionals aged 25-35, city-based, $75K+ income"
- B2B2C: "Retailers who sell to fashion-conscious women 18-35"
Specificity: More specific = better (not "any company")

B. Customer Problem (WHAT)

Definition: What painful problem does your customer have?
Avoid vagueness: Not "marketing is hard" but "marketing teams spend 20 percent time on manual data entry"
Validation: Have you interviewed 20+ customers confirming this is a top-3 problem?
Urgency: Is this a "nice to have" or "urgent problem threatening business"?

C. Unique Value Prop (WHY US)

Definition: Why us vs. alternatives (competitor, DIY, do nothing)?
Format: "[Quantified benefit] vs. [clear alternative]"
Examples:
- "Reduce onboarding from 3 weeks to 3 days vs. legacy system approach"
- "Save marketing teams 10 hours/week vs. manual data entry"
- "Deploy AI model in 2 weeks vs. 6-month custom build"
Test: Can customer understand it in 1 sentence?

D. Go-to-Market Channel (HOW)

Definition: How will customers find you?
Options:
- Direct sales: Test when explanation, procurement, implementation, or relationship needs may justify sales capacity.
- Self-service: Test when users can understand, buy, onboard, and obtain value with limited assisted service.
- Partnerships: Test when partner reach, capability, incentives, control, economics, and customer ownership align.
- Digital marketing: Test when targeting, consent, claims, attribution, conversion, economics, and service capacity are acceptable.
- Mixed: Define channel roles and conflict rather than assuming a combination is superior. This is an author-created design caution.

E. Pricing Model (HOW MUCH)

Definition: How do you make money?
Common models:
- Per user/month: A constructed SaaS model can charge by active seat; scalability depends on service, support, infrastructure, and acquisition economics.
- Percentage of transaction: Marketplace fee; determine the basis and rate from value, cost, risk, competition, contract, and willingness-to-pay evidence. ^[2]
- Per feature: A constructed tiered model can separate basic, professional, and enterprise capabilities.
- One-time license: A software vendor may quote a license for a defined scope, term, maintenance arrangement, and usage right.
- Freemium: Free + premium (free-to-paid conversion)

F. Unit Economics (FINANCES)

Definition: The math at one customer level
Key metrics:
- Customer Acquisition Cost (CAC): Define which sales and marketing cash, labor, incentives, and overhead are included and which acquired cohort is the denominator.
- Lifetime value (LTV): Model expected gross-margin contribution or another explicit contribution measure by cohort, retention, expansion, service cost, and time—not revenue alone.
- Payback period: Divide CAC by the relevant periodic contribution, not ARPU without margin and service-cost adjustments.
- LTV:CAC ratio: State definitions, uncertainty, cash timing, and sensitivity; no universal ratio proves sustainability.
Example:
- CAC: $500 (sales + marketing to get one customer)
- ARPU: $100/month
- Revenue proxy: $100/month × 24 months = $2,400; this is not LTV until margin, retention, service cost, and discounting assumptions are defined.
- Revenue-proxy/CAC = 4.8:1; do not label it healthy without the missing assumptions.

G. Growth Assumption (TRAJECTORY)

Definition: How will you scale?
Year 1 Targets:
- Revenue: $1M
- Customers: 100
- CAC efficiency: $5K per customer
Constraints: What's the limiting factor? (Sales team size, ad spend, product capacity)

Template:

TARGET: Mid-market SaaS companies, $5M-50M revenue
PROBLEM: Data pipeline takes 3 weeks, costs 15 percent of revenue
VALUE PROP: Deploy in 3 days, save $500K/year vs. custom build
CHANNEL: Direct sales (complex sales) + Partnerships with data infrastructure companies
PRICING: $50K per-year subscription (enterprise focused)
ECONOMICS: CAC $30K, LTV $250K (5-year avg), Payback 7 months
GROWTH: Year 1: 20 customers ($1M ARR), Year 2: 60 customers ($3M ARR)

Usage:

Draft by founders
Validate with 20+ customer conversations (iterate canvas 2-3 times)
Use to guide product decisions (features that support GTM strategy)
Update quarterly as you learn

Figure 14.1. GTM evidence and readiness loop (constructed). Customer, product, economics, channel capacity, and launch readiness iterate together; an explicit decision gate can test, launch, pause, pivot, or stop.

Text equivalent: Define the segment and buying unit, investigate the problem and alternatives, develop differentiated proof, compare channels and capacity, test pricing and cohort economics, and assess product/service readiness. At the gate, launch a bounded cohort only when evidence and controls are sufficient; otherwise run another test, revise the GTM design, pause, or stop. Onboarding, retention, churn, complaints, expansion, and closed-lost evidence feed the next decision.

flowchart LR
    A[Define ICP] --> B[Validate problem]
    B --> C[Test value proposition and proof]
    C --> D[Compare channels and capacity]
    D --> E[Test price, packaging, and contract]
    E --> F[Model cohort economics and cash]
    F --> R[Assess product, service, legal, and operational readiness]
    R --> G{Launch gate}
    G -->|Bounded launch| H[Onboard and observe retention, churn, expansion, complaints, and harm]
    G -->|Test or pivot| A
    G -->|Pause or stop| X[Preserve evidence and close responsibly]
    H --> A

So What for Managers

Use the canvas to expose dependencies between segment, proof, channel, price, delivery, and cash.
Treat every value, target, and customer description as a hypothesis until defined evidence supports the next decision.
Make launch, pause, pivot, stop, and responsible-close options visible before increasing exposure.

Limits and Critiques

A canvas can create false coherence when the fields are guesses, the buying unit is wrong, or the customer evidence is selected for confirmation.
Firmographics, a value proposition, or a favorable ratio do not establish demand, willingness to pay, causal lift, or retention.
A launch decision also depends on product quality, privacy, accessibility, contracts, service capacity, legal review, and affected-party outcomes.

Connections

Customer and segment: Use Framework 2 and Chapter 5 for jobs, segmentation, alternatives, and measurement.
Channels and pricing: Use Frameworks 4 and 5 for channel tests, value metrics, contracts, and unit economics.
Product and evidence: Use Chapters 13, 21, and 22 for venture tests, product readiness, cohorts, and analysis.

2. Ideal Customer Profile (ICP) Framework

Overview

The ideal customer profile (ICP) is a constructed segmentation and buying-unit hypothesis that adds job, alternatives, access, urgency, economics, service fit, and decision rights to firmographic description. Jobs-to-be-Done can deepen the problem lens; Moore’s beachhead lens is a bounded practitioner aid, not a universal adoption sequence. ^[3] ^[4]

How to Apply

Define inclusion, exclusion, evidence, disqualifiers, fairness/privacy constraints, and a local decision rule. Use the score to prioritize a test or allocate attention; do not use it to infer worth, authorize exclusion, or prove fit.

Constructed-example boundary: The firms, budgets, scores, segment sizes, win rates, ratios, and other values below are invented teaching inputs. They are not market estimates, permission to exclude, or evidence of willingness to pay.

Purpose: Define a testable segment and buying unit whose job, alternatives, access, economics, and service fit support focused learning. Jobs-to-be-Done can deepen the problem lens beyond firmographics. ^[3]

For some disruptive-technology contexts, Moore's early-market/mainstream and beachhead-market framing can prompt questions about reference customers and adoption barriers. It is a practitioner lens, not a universal adoption sequence. ^[4]

S03 is used only for the jobs-to-be-done/problem lens; the ICP dimensions, score, anti-priority rule, fairness checks, and prioritization decision are author-created and must be tested locally.

ICP Dimensions:

Firmographic (Company Characteristics)

Industry: e.g., "SaaS B2B" (not insurance or nonprofits)
Company size: e.g., "$5M-50M revenue" or "20-200 employees"
Geography: e.g., "US + Canada, tech hubs" (not all geographies)
Growth stage: e.g., "Series A-C funded" (not pre-seed bootstraps)
Decision budget: e.g., "Has a documented budget process" (an access or buying-process signal to test, not evidence of willingness to pay)

Behavioral (How They Operate)

Technology stack: e.g., "Uses Salesforce" (integration point)
Process maturity: e.g., "Has formalized marketing ops team" (can execute)
Pain urgency: e.g., "Recently had hiring surge creating data chaos" (trigger)
Buying cycle: e.g., "Contracts in Q1" (budget planning cycle)

Psychographic (Values/Priorities)

Growth mindset: e.g., "Looking to optimize; willing to invest"
Technology affinity: e.g., "Early adopters of new tools"
Decision style: e.g., "Data-driven, requires clear ROI" (vs. gut-feel driven)

ICP Profile Template:

COMPANY: MarketCo (example)
- Revenue: $20M (in our $5-50M range ✓)
- Employees: 150 (fits 50-300 profile ✓)
- Industry: Marketing SaaS (target industry ✓)
- Stage: Series B funded (growth-stage ✓)
- Tech stack: Salesforce + HubSpot (integration ready ✓)
- Problem: Manual data sync between systems (top pain ✓)
- Budget: $500K annual marketing operations (sufficient budget ✓)
- Decision timeline: Q1 annual budget planning (quarterly cycle)
- Decision maker: VP Marketing + IT director (multi-stakeholder)

SCORE: 9/10 ICP fit ✓ (pursue aggressively)

Constructed scoring system: Define criteria, weights, evidence, disqualifiers, fairness/privacy constraints, and decision thresholds locally. A high score prioritizes a test; it does not prove fit or authorize exclusion.

Anti-ICP (Who to Deprioritize):

"We'll work with anyone" can spread resources thin; define prioritization signals and review them for unfair effects.
Example anti-priority: An account whose documented product, service, payment, security, legal, or capacity requirements cannot be met under the approved offer; organization type or budget alone is not a disqualifier.
Possible outcome: Lower contribution, higher support cost, or poor retention under the defined model; measure rather than assume.

Usage:

Sales team uses to qualify leads (ICP score)
Marketing uses to target ads, content
Product uses to prioritize feature requests (from ICP customers only)
Revise quarterly based on actual sales data

Table 14.1: Constructed segment-prioritization illustration. The figures are invented teaching inputs, not market benchmarks, forecasts, or evidence of fit.

Segment	Size	Avg Deal	Win Rate	LTV:CAC	Priority
ICP (perfect fit)	500 companies	$50K	25 percent	5:1	1 (focus here)
Good fit	2000 companies	$30K	15 percent	3:1	2
Possible fit	5000 companies	$20K	5 percent	1.5:1	3 (if inbound)

So What for Managers

Define who buys, who uses, who is affected, who can block, and what alternatives are available.
Treat segment size, win rate, deal size, and ratio values as locally measured or constructed, not market facts.
Reassess the ICP when evidence, access, economics, service burden, or harm patterns differ across cohorts.

Limits and Critiques

Firmographics and an ICP score can hide jobs, power, accessibility, nonbuyers, affected people, and distributional harm.
A narrow segment may improve learning while reducing reachable market, resilience, or ethical fit; a broad segment may be necessary for a different model.
Segment evidence is vulnerable to selection, survivorship, response, attribution, and privacy errors.

Connections

Problem evidence: Use Chapter 13 and Framework 1 to connect venture hypotheses, jobs, alternatives, and proof.
Channel: Use Framework 4 to test whether the selected segment is reachable and serviceable.
Product and analytics: Use Chapter 21 for product discovery and Chapter 22 for cohort, uncertainty, and causal analysis.

3. Sales Funnel Metrics Dashboard

Overview

The sales funnel metrics dashboard is an author-created measurement aid for defining stages, cohorts, owners, entry/exit rules, closed-lost reasons, onboarding, retention, expansion, churn, complaints, and harm. It is not a standard funnel, benchmark, or causal model. ^[5]

How to Apply

Define the stage, unit, denominator, observation window, data quality, and decision use before comparing conversion. Separate attribution from incremental lift and include closed-lost and post-close outcomes in the learning loop.

Purpose: This author-created dashboard illustrates how a team might define acquisition stages, cohort transitions, losses, onboarding, and post-close outcomes. It is not a standard funnel, benchmark, causal model, or prescribed stage taxonomy; use local definitions and validated data to investigate—not merely label—bottlenecks.

Constructed funnel example:

AWARENESS: 1000 leads (potential customers who know you exist)
    ↓ (60 percent conversion = 600)
CONSIDERATION: 600 leads (evaluating you vs. alternatives)
    ↓ (40 percent conversion = 240)
PROPOSAL: 240 leads (you've proposed solution)
    ↓ (50 percent conversion = 120)
NEGOTIATION: 120 leads (in final discussion)
    ↓ (60 percent conversion = 72)
CLOSED WON: 72 customers

Figure 14.2. Acquisition, loss, and post-close learning loops (constructed). Every stage needs a definition, owner, entry/exit rule, cohort, and loss reason. Closed-won is the start of onboarding and retention evidence, while closed-lost evidence returns separately.

Text equivalent: Prospects move from awareness to consideration, proposal, negotiation, and either closed-won or closed-lost. Closed-won proceeds through onboarding to retained use, expansion, churn, complaint, or other outcomes. Closed-lost and post-close evidence return to segment, message, price, channel, product, service, and capacity decisions for the next cohort.

flowchart LR
    A[Awareness] --> B[Consideration]
    B --> C[Proposal]
    C --> D[Negotiation]
    D --> E{Decision}
    E -->|Closed won| F[Onboarding and time to value]
    E -->|Closed lost| L[Record reason, alternative, and evidence]
    F --> G{Post-close outcome}
    G -->|Retained or expanded| R[Measure value, service burden, and economics]
    G -->|Churn, complaint, or harm| Q[Investigate cause and remedy]
    L --> H[Refine segment, proof, price, channel, or product]
    R --> H
    Q --> H
    H --> A

Key Metrics by Stage:

AWARENESS

Metric: Lead volume
Target: 1000 qualified leads/month (depends on your target market size)
Drivers:
- Paid ads: $10K/month budget → 500 leads
- Content marketing: 10,000 monthly blog visitors → 300 leads
- Partnerships: Referral program → 200 leads
Health: Increasing month-over-month

CONSIDERATION

Metric: Lead response rate, meeting booking rate
Target: 60 percent of leads book a call (60 percent conversion rate)
Drivers:
- Email quality (personalized > blast)
- Response time (within 2 hours > next day)
- Value prop clarity (clear why they should talk)
Health: Declining conversion suggests bad leads or weak messaging

PROPOSAL

Metric: Proposal win rate
Target: 40-50 percent of meetings lead to proposal
Drivers:
- Meeting quality (talked to actual decision maker?)
- Problem confirmation (did they confirm the problem?)
- Fit assessment (is your solution right for them?)
Health: Low conversion suggests selling too early

NEGOTIATION

Metric: Discount rate, term length, close rate
Target: 50-60 percent of proposals close
Drivers:
- Value understood (did you quantify ROI?)
- Competition (did they consider alternatives?)
- Urgency (do they have budget/decision timeline?)
Health: Low close rate suggests price too high or weak negotiation

POST-CLOSE

Metric: Onboarding success, support load, and a defined customer-experience measure; if NPS is used, collect the 0–10 recommendation item and calculate promoters minus detractors under the approved instrument
Target: 90 percent or more timely onboarding, below 2 percent churn
Drivers:
- Expectation management (did you over-promise?)
- Ramp time (how long to value?)
- Support quality (responsive team?)

Table 14.2: Constructed funnel dashboard for one sample month. Stage definitions, targets, actuals, and health labels require local cohort and data-quality rules.

Stage	Target	Actual	Conv Rate	Health
Awareness	1000	950	-	✓ Good
Consideration	600	520	54 percent	⚠ Slight dip
Proposal	240	180	35 percent	🔴 Below target
Negotiation	120	90	50 percent	✓ Good
Closed Won	72	54	60 percent	⚠ Below target

Diagnosis: Proposal conversion low (35 percent vs 40 percent target). Action: Review 5 recent proposals (messaging? fit? timing?).

Typical Funnel Economics:

To close 100 customers/year:

Need ~200 proposals (assuming 50 percent close rate)
Need ~400 meetings (assuming 50 percent proposal rate)
Need ~1000 qualified leads (assuming 40 percent meeting rate)

Table 14.3: Constructed channel-funnel comparison. Conversion values are illustrative and are not channel benchmarks.

Channel	Awareness	Consideration	Proposal	Close	Efficiency
Direct sales	High touch	70 percent conv	60 percent conv	70 percent conv	High deal size, low volume
Self-serve	High volume	30 percent conv	20 percent conv	40 percent conv	High volume, small deals
Partnerships	Medium	80 percent conv	50 percent conv	60 percent conv	Medium, high trust

So What for Managers

Ask where evidence is lost, not merely where volume falls.
Pair acquisition metrics with onboarding, retention, support, complaints, refunds, accessibility, and customer outcomes.
Use randomized or justified quasi-experimental designs when a channel or intervention decision requires causal lift.

Limits and Critiques

Funnels are definitions and measurement conventions; they do not prove causality, value, or customer satisfaction.
Stage conversion can be distorted by cohort mix, attribution, selection, seasonality, sales capacity, and inconsistent loss coding.
Optimizing top-of-funnel volume can increase spam, harm, service load, or low-quality demand.

Connections

Channel: Use Framework 4 to compare reach, control, capacity, incentives, and economics.
Pricing: Use Framework 5 to connect conversion and price tests to contribution and cash.
Analytics and product: Use Framework 7 and Chapters 21–22 for experiments, cohorts, causal methods, and product outcomes.

4. Channel Strategy Matrix

Overview

The channel strategy matrix is a constructed comparison of reach, control, explanation, access, capacity, partner incentives, service burden, risk, contribution, and cash. Bullseye supports brainstorming, ranking, small parallel tests, and focus based on evidence; the values below are not channel benchmarks. ^[5]

How to Apply

Compare a small portfolio of channels using defined segment evidence, buying behavior, incremental lift, cost, capacity, customer experience, privacy, partner rights, and exit options. Choose, combine, defer, or stop channels according to the decision and downside rule.

Purpose: Decide which sales/marketing channels to invest in.

All volume, deal-size, cycle, margin, investment, CAC, LTV, and maturity values in this section are constructed hypotheses, not channel benchmarks. Weinberg describes Bullseye as brainstorming across acquisition channels, ranking candidates, running small parallel tests, and then focusing based on evidence; the specific outcomes below are not sourced. ^[5]

Table 14.4: Constructed channel-evaluation matrix. Volume, deal-size, cycle, margin, investment, and maturity values are hypotheses for teaching, not benchmarks.

Channel	Volume Potential	Deal Size	Sales Cycle	Margin	Investment	Notes
Direct Sales	Medium (1-2 deals/rep/month)	High ($50K+)	Long (3-6 mo)	High (70 percent or more)	High (salary, travel)	Best for enterprise
Inside Sales	Medium-High (2-5 deals/month)	Medium ($10-50K)	Medium (1-3 mo)	High (60 percent or more)	Medium (salary)	Best for mid-market
Self-Serve	High (unlimited)	Low ($0-1K)	Short (<1 week)	Low (30-40 percent)	Medium (product, ads)	Best for SMB
Partnerships	Medium (depends on partner)	Variable	Variable	Medium (40-50 percent)	Low (commission only)	Best for reach
Content Marketing	High (inbound)	Variable	Long (passive)	High (organic)	Medium (content team)	Best for brand building
Paid Ads	High	Variable	Short (immediate)	Low (30 percent or more)	High (ad spend)	Best for quick scaling

Channel Selection Framework:

Step 1: Current evidence and constraints

Compare buying behavior, explanation and implementation burden, channel access, partner incentives, sales capacity, cash, service quality, privacy, attribution, and control. Stage labels do not determine the channel.

Step 2: Economics Assessment

Calculate Unit Economics for Each Channel:

Example - SaaS company, $300 ARPU, 2-year revenue scenario:

Table 14.5: Constructed channel-economics hypothesis. The figures below illustrate a comparison method; they are not observed LTV, CAC, or channel performance.

Channel	CAC	LTV	LTV:CAC	Status
Direct sales	$8K	$7.2K	0.9:1	Contribution does not recover acquisition cost under these assumptions
Inside sales	$3K	$7.2K	2.4:1	Positive modeled spread; test retention, margin, and cash timing
Self-serve	$500	$7.2K	14.4:1	Large modeled spread; validate attribution and service costs
Partnerships	$1K	$7.2K	7.2:1	Positive modeled spread; validate partner economics

Illustrative decision: Investigate self-service and partnerships further because the constructed model gives them more favorable contribution-to-acquisition scenarios. Validate demand, margin, support, retention, partner behavior, and capacity before scaling.

Step 3: Learning sequence

Choose the smallest channel portfolio that can answer the decision without creating unmanaged conflict or service burden. Add, remove, or combine channels when incremental evidence and capacity justify it; no universal month sequence applies.

Common Mistakes:

Spreading across 5 channels too early (excellence diluted)
Ignoring low-LTV:CAC channels (drains cash)
Not measuring channel quality (volume ≠ good customers)

So What for Managers

Choose channels that the team can operate, measure, support, and govern for the selected customer and buying process.
Separate reach and attribution from incremental demand, contribution, retention, service load, and cash timing.
Make partner incentives, customer ownership, data rights, exclusivity, and exit terms explicit.

Limits and Critiques

Channel performance depends on segment, product maturity, buying process, competition, capacity, and measurement quality.
A high modeled LTV:CAC or low CAC can reflect definitions, selection, delayed costs, or missing service and support burden.
Parallel tests can create channel conflict, brand inconsistency, customer confusion, or privacy and consent risk.

Connections

ICP and funnel: Use Frameworks 2 and 3 to define who each channel reaches and how evidence is recorded.
Pricing and growth: Use Frameworks 5 and 7 to connect economics, experiments, incentives, and guardrails.
International entry: Use Framework 10 and Chapter 2 for regulatory, contract, partner, privacy, and non-market constraints.

5. Pricing Model Comparison

Overview

The pricing model comparison is a constructed decision aid for testing value metrics, packages, willingness-to-pay evidence, economics, fairness, competition, tax, contract, procurement, and operating consequences. The cited source supports bounded value-based pricing concepts; sample prices, capture percentages, and evolution paths are constructed. ^[2]

How to Apply

Define the customer value metric, cost-to-serve, contribution, alternatives, willingness-to-pay evidence, price sensitivity, contract, tax, fairness, and billing controls. Test a package or price with a defined cohort and stop rule rather than treating a model as inherently superior.

Purpose: Compare value metric, package, willingness-to-pay evidence, economics, fairness, competition, tax, contract, procurement, and operating consequences. Value-based pricing is a supported concept; the sample prices, capture percentages, and evolution are constructed. ^[2]

The S05 record is used only for the bounded value-based-pricing and pricing-model concepts. Fairness, competition, tax, procurement, contract, billing, service, and operating checks are author-created prompts that require the applicable specialist review.

Four Main Models:

Model 1: Per-Unit Pricing

Mechanics: Fixed price per customer/seat/transaction
Example: $99/user/month for SaaS
Ideal for: Scalable products where value is per user
Pros:
- Easy to understand (no complexity)
- Scales with value (more users = more revenue)
- Easy to forecast (predictable ARR)
Cons:
- Leaves money on table (big companies get same price as small)
- "Sprawl" (companies avoid adding users to save cost)
Optimization: Tiered pricing (Starter $99, Pro $299, Enterprise $999)

Model 2: Value-Based Pricing

Mechanics: Price based on ROI/value customer receives
Example:
- If a use case is estimated to save $500K annually, test alternative packages and prices rather than applying a universal share-of-value percentage.
- If a product may contribute to new revenue, separate attribution, risk, implementation effort, and customer alternatives before using the estimate in pricing.
Ideal for: Enterprise, quantifiable ROI
Potential advantages:
- Can connect price to a value metric customers recognize
- Can align incentives when measurement, attribution, risk, and contracts support the design
Cons:
- Hard to quantify (negotiations required)
- Requires trust (customer might low-ball)
- Complex to administer
Usage: Enterprise sales; RFP responses include ROI calculator

Model 3: Freemium

Mechanics: Free basic version; premium paid tier
Example:
- Free: Up to 10K API calls/month
- Pro: $99/month for unlimited
Ideal for: High-volume, low-touch, developer products
Pros:
- Removes purchase friction (try before buy)
- Network effects (more free users = more value)
- Viral potential (easy to share)
Cons:
- Free tier is expensive (server, support, churn)
- Conversion can be low without a clear upgrade path
- Cannibalization (some paying customers downgrade to free)
Success factors:
- Free tier hits a real limitation (not just arbitrary)
- Clear upgrade path (customer hits free limit and converts)

Model 4: Usage-Based / Consumption Pricing

Mechanics: Pay for what you use (like utilities)
Example:
- Computing capacity priced by measured use
- Transaction service priced by a percentage and/or fixed fee
Ideal for: Infrastructure, platform products
Pros:
- Aligns with customer value (use more = benefit more = pay more)
- Low barrier to entry (start cheap, scale naturally)
- Predictable revenue (scales with customer success)
Cons:
- Revenue unpredictability (customer might not scale)
- Billing complexity
- Customer frustration (surprise bills if usage spikes)
Mitigation: Usage caps, annual commitments, committed tiers

Table 14.6: Constructed pricing-model comparison. The dimensions are decision prompts, not universal model attributes.

Model	Predictability	Scalability	Customer Friction	Enterprise	SMB
Per-Unit (seats)	High	High	Low	Medium	High ✓
Value-Based	Low	High	High	High ✓	Low
Freemium	Medium	High	Very Low	Low	High ✓
Usage-Based	Medium	High	Medium	Medium	Medium
Hybrid	Medium	High	Medium	High ✓	Medium

Hybrid Example (Common for SaaS):

Base: $99/month (per seat, includes 10K API calls)
Plus: $0.10 per API call above 10K
Result: Per-seat predictability + usage upside

Pricing evolution: Revisit the value metric, package, fairness, economics, customer predictability, billing controls, and contract as evidence changes. A product need not progress from seat to tier to usage to value-based pricing on a fixed timeline.

So What for Managers

Price the value metric the customer can understand and the firm can measure, deliver, support, and govern.
Separate revenue, contribution margin, cash payback, willingness to pay, and customer fairness.
Record who approved the price, what evidence supports it, what assumptions remain, and what would trigger revision.

Limits and Critiques

Value-based pricing is not permission to claim or capture an arbitrary share of customer value.
A price test can be confounded by segment, packaging, sales effort, trust, timing, competition, procurement, and service capacity.
Freemium, usage, tier, and hybrid models can create privacy, fairness, billing, lock-in, and surprise-cost risks.

Connections

Customer: Use Framework 2 to define the buying unit, alternatives, and value evidence.
Funnel and channel: Use Frameworks 3 and 4 to link price to conversion, service, capacity, and contribution.
Finance and law: Use Chapters 4 and 15 plus qualified legal/tax owners for margin, contracts, tax, disclosure, and competition constraints.

6. Product Launch Checklist

7. Growth Experimentation Framework

Overview

The growth experimentation framework is an author-created sequence for testing whether an acquisition mechanism produces incremental, economically acceptable, and customer-safe growth. Bullseye supports channel brainstorming, ranking, small tests, and evidence-based focus; the broader experiment contract is author synthesis. ^[5]

How to Apply

Define the mechanism, eligible population, unit, time window, counterfactual, primary outcome, guardrails, cost basis, data rights, and stop rule before exposure. Record attribution separately from incremental lift and review retention, service load, complaints, accessibility, privacy, and harm.

Purpose: Test whether a channel, product mechanism, or referral process produces incremental, economically and ethically acceptable growth. Bullseye directly supports structured acquisition-channel testing; the broader experiment checklist here is author-created. ^[5] Fast experimentation does not waive consent, consumer-protection, competition, accessibility, platform, security, or data-governance obligations.

5-Step Framework:

Step 1: Identify Growth Levers

Definition: What action by customer leads to more customers?
Examples:
- Referral: Existing customer refers friend → new customer
- Referral: a retained customer voluntarily recommends the product to another eligible prospect
- Product-mediated diffusion: collaboration or sharing exposes an invited non-user to the product
- Network effect: utility changes with participation, subject to congestion, governance, and multi-homing
- Content: useful, substantiated material attracts qualified demand
- Product-led: a product experience creates evidence for a later purchase decision

Step 2: Quantify the Lever

Descriptive growth coefficient: Conversions attributed to the mechanism during a defined window ÷ eligible or exposed population during that same window. Report the cohort, unit, generation, time basis, overlap, retention, cost, uncertainty, and attribution limits.
Example - Referral:
- 100 current customers
- Each refers 0.2 new customers on average
- Referral contribution proxy = 0.2 new sign-ups per current customer for the measured window; this is not a monthly growth rate unless the cohort, time basis, retention, overlap, and denominator support that interpretation.

Step 3: Optimize the Top Lever

Identify: Which lever has highest potential impact?
Optimize: A/B test to increase conversion
Example - Referral Optimization:
- Control: "Refer a friend, get 1 month free"
- Test A: "Refer a friend, get 1 month free (AND they get 1 month free)"
- Test B: "Refer 3 friends, get lifetime discount"
- Measure: Which increases referral rate most?

Step 4: Automate the Lever

Definition: Make it happen without manual effort
Example - Referral Automation:
- Trigger: Customer reaches a predefined retained-activation condition appropriate to the product
- Action: Auto-send referral incentive email
- Tool: Built into product (share button, dashboard link)

Step 5: Invest in Winning Levers

Scale: Increase exposure only after incremental lift, retention, contribution, customer outcomes, and capacity are credible
Budget: Allocate sales/marketing dollars to top levers
Example: If referral drives 20 percent growth, incentivize it; if content drives 10 percent, invest less

Diffusion measure: See the next section. A product-generated invitation is not automatically causal acquisition, a network effect, or valuable retention.

Experiment discipline:

State the mechanism, eligible population, unit of analysis, window, counterfactual, cost, and guardrails before launch.
Separate attribution from incremental lift and test for novelty, cannibalization, selection, spillover, and survivor bias.
Prohibit deceptive interfaces, forced invitations, contact scraping, undisclosed incentives, unauthorized testimonials, discriminatory targeting, and retaliation against non-participants.
Monitor complaint, unsubscribe, deletion, refund, security, accessibility, service-load, and vulnerable-customer indicators alongside acquisition.
Scale, revise, pause, or stop from predeclared evidence and harm rules; do not optimize only a top-of-funnel metric.

So What for Managers

Require a decision-specific experiment contract before scaling exposure, budget, incentives, or automated outreach.
Compare incremental acquisition, retained value, contribution, service load, and customer-harm indicators rather than a single growth metric.
Make pause, stop, remedy, and responsible-close paths operational before the test begins.

Limits and Critiques

Observational attribution, short windows, selection, spillover, novelty, and survivor bias can overstate a mechanism's effect.
A statistically detectable lift may still be uneconomic, operationally infeasible, unfair, or harmful to customers or nonparticipants.
A result from one segment, product, channel, or platform does not automatically transfer to another context.

Connections

Funnel and channel: Use Frameworks 3 and 4 to define stages, reach, capacity, cost, and attribution boundaries.
Diffusion: Use Framework 8 for invitation-cycle measurement and its limits; do not treat K as a viability threshold.
Analytics and product: Use Chapters 21 and 22 for experiment design, cohorts, causal inference, privacy, and guardrail analysis.

8. Product-mediated diffusion measure

Overview

The product-mediated diffusion measure summarizes invitations and observed conversion for a defined cohort and generation. It is a descriptive local metric, not proof of causality, retention, network effects, profitability, or self-sustaining growth. ^[6]

How to Apply

Define the included user, invitation, conversion, generation, eligibility, observation window, overlap, retention, cost, and data-quality rules. Report the measure with confidence intervals or uncertainty ranges where appropriate, and use an experiment or credible quasi-experimental design when a causal decision warrants it.

Purpose: Summarize invitations and observed conversion for a defined cohort and generation. This is a local descriptive measure, not proof of causality, retention, network effects, profitability, or self-sustaining growth. Empirical work shows that diffusion is heterogeneous and sensitive to network structure and adoption dynamics. ^[6]

The Formula:

Viral Coefficient (K) = (Invites sent per user) × (% Invites converted to users)

Example Calculation:

Average user sends 5 invites
20 percent of invites convert (1 in 5 friends actually signs up)
K = 5 × 0.20 = 1.0

Interpretation: Within one consistently defined and observed generation, K > 1 means more than one converted invite per included user on average. It does not establish exponential or self-sustaining growth. The next generation can differ because of retention, cycle time, saturation, invitation overlap, incentives, fraud, channel quality, eligibility, service capacity, or changed product behavior. K = 1 is not financial break-even, and K < 1 does not imply that the business is shrinking.

Improving Viral Coefficient:

Increase Invites Sent

Method 1: Make sharing easy (prominent share button)
Method 2: Test a disclosed, consent-based incentive only after legal, fraud, fairness, and economic review
Method 3: Make sharing natural (product naturally involves non-users)
Guardrail: Do not force contact uploads, preselect consent, obscure sponsorship, or make core use contingent on recruiting others

Increase Conversion Rate

Method 1: Make sign-up fast (1-click with existing email)
Method 2: Show value immediately (demo or instant usefulness)
Method 3: Social proof ("Your friend is using this")
Example: Team collaboration tools can show which colleagues are already active

Decision view: Report K with invitation-cycle time, retained activated users, duplication, acquisition source, contribution, incentive and service cost, complaint/unsubscribe rates, and cohort confidence intervals. Use an experiment or credible quasi-experimental design to estimate causal lift where the decision warrants it. A high K paired with weak retention, poor customer outcomes, or high harm is a stop signal, not a reason to scale.

So What for Managers

Treat K as a cohort-and-window diagnostic that informs a test; do not use it as a universal growth, profitability, or product-market-fit gate.
Pair diffusion with retained activation, contribution, fraud, service capacity, consent, complaints, accessibility, and customer-outcome measures.
Set invitation, incentive, privacy, and harm limits before expanding the mechanism.

Limits and Critiques

Invitation overlap, eligibility changes, incentives, fraud, saturation, and selective retention can make K unstable or misleading.
Observed conversion does not identify the conversions caused by the product-mediated mechanism without a credible counterfactual.
Network structure and adoption dynamics differ across products, cohorts, generations, and contexts; source findings do not provide a company-specific forecast.

Connections

Experimentation: Use Framework 7 for mechanism, counterfactual, guardrail, and stop-rule design.
Funnel and economics: Use Frameworks 3–5 to connect conversion to onboarding, service cost, contribution, pricing, and cash.
Product and analysis: Use Chapters 21 and 22 for activation, retention, cohort definitions, uncertainty, and causal analysis.

9. Partnership Evaluation Matrix

Overview

The partnership evaluation matrix is an author-created comparison of partnership hypotheses across reach, customer fit, incentives, economics, execution, data/IP/security, competition, dependency, reversibility, and exit. Its categories and sample values are not benchmarks or predictions.

How to Apply

Define the partner role, customer permission, incremental contribution, enablement and support cost, data and IP rights, incentive alignment, attribution, governance, dependency, audit, and termination conditions. Use a bounded pilot and staged commitment where the risks and evidence justify it.

Purpose: This author-created matrix illustrates questions for comparing partnership hypotheses; its categories, weights, values, timing, and priorities are not benchmarks or predictions. Confirm authority, incentives, economics, customer effects, data/IP/security requirements, competition rules, dependencies, reversibility, and exit terms before acting.

Partnership Types:

Distribution: Partner sells your product (e.g., reseller, channel partner)
Integration: Partner's product integrates with yours (e.g., API connection)
Co-marketing: Partner co-brands/promotes with you (e.g., joint webinar)
OEM: Partner embeds your solution in theirs (e.g., white-label)
Strategic: Partner with shared customer base (e.g., non-competing SaaS)

Table 14.7: Constructed partnership-evaluation illustration. Company names, revenue potential, timing, and priorities are invented teaching inputs, not forecasts.

Partnership	Revenue Potential	Ease of Execution	Strategic Fit	Timeline	Priority
Company A (Reseller)	High ($500K yr 1)	Hard (needs sales training)	High (same customer)	6 months	1
Company B (Integration)	Medium ($100K yr 1)	Easy (API connector)	High (customers need integration)	2 months	2
Company C (Co-marketing)	Low ($20K yr 1)	Easy (webinar, email)	Medium (complementary not integrated)	1 month	3
Company D (OEM)	High potential ($1M)	Very hard (custom build)	Medium (different use case)	12 months	4 (future)

Scoring Methodology:

Revenue Potential: Low (< $50K), Medium ($50-200K), High ($200K+)
Ease: Hard (custom build, sales training), Medium (some requirements), Easy (standard)
Strategic Fit: How aligned with your core customer?
Timeline: Realistic time to generate first revenue?

Key Evaluation Questions:

Do they have access to your target customer?
- Example: SaaS company with 100 accountants = good partner for accounting software
- Example: Random B2B tool = weak fit
Is the economics fair?
- Reseller: negotiated margin split that leaves both parties economically motivated
- Integration: Negotiate a documented share or fee from incremental contribution, enablement, support, risk, control, and customer value; no fixed split is universal
- Co-marketing: Often reciprocal (both benefit equally)
Can they actually execute?
- Do they have sales team to sell?
- Do they have support team to support?
- Or are you doing all the work (not a partnership)?
What are success metrics?
- First year target: $X in revenue
- Quarterly check-in: Are we on track?
- Exit clause: If not working, how do we end partnership?

Common Partnership Mistakes:

Pursuing partnerships instead of direct sales (less capital efficient)
Weak partners who don't deliver
Misaligned incentives (partner doesn't care about your success)
Over-investment in relationship building without revenue traction

Partnership Strategy by Stage:

Earlier evidence stage: Test only the partner roles needed to learn, with explicit customer, incentive, support, control, and exit conditions.
Repeatability stage: Add integration or distribution commitments when incremental contribution, capability, governance, and capacity are evidenced.
Portfolio stage: Stage strategic or OEM relationships only when dependency, data/IP, customer ownership, service, competition, and exit risks are approved.

So What for Managers

Compare partner reach and credibility with enablement, integration, support, control, attribution, dependency, and exit cost.
Require documented customer, data, IP, security, competition, sanctions, and contract approvals before irreversible commitment.
Start with a bounded pilot and predeclared evidence, remedy, renewal, and termination rules.

Limits and Critiques

Partner-reported reach, revenue potential, and strategic fit may not translate into incremental demand or contribution.
Revenue share and stage labels are not universal rules; economics depend on effort, incentives, support, risk, control, and customer ownership.
A partner can increase concentration, operational, privacy, security, reputational, competition, and exit risk.

Connections

Channel: Use Framework 4 to compare direct, self-service, and partner routes using the same cost and capacity definitions.
Pricing and launch: Use Frameworks 5 and 6 for commercial terms, billing, readiness, support, and customer communication.
International and governance: Use Framework 11 and qualified legal, privacy, security, trade-control, tax, and competition owners for diligence.

10. Market Entry Strategy Decision Tree

Overview

The market-entry strategy decision tree is a constructed decision aid for comparing a new category, existing competitive market, or adjacency. It organizes evidence questions; it does not predict entry success or make a one-year commitment rule.

How to Apply

Classify the entry context, define the first segment and job, test alternatives and incumbent response, assess channel access and service capacity, model contribution and cash, map legal and policy constraints, and choose test, adapt, partner, defer, pause, stop, or exit. State what evidence would reverse the choice.

Context: This constructed decision aid compares strategic questions; it does not predict entry success. Define the market and substitutes, test demand, examine incumbent response and channel access, model cash and service capacity, and identify regulatory, competition, IP, privacy, and contract constraints before selecting an option.

Figure 14.3: Evidence-gated market-entry choice (constructed). This is a decision aid, not a prediction model.

flowchart TD
  S{"Which entry context best fits the evidence?"}
  S --> A["New or poorly defined category"]
  S --> B["Existing market with many competitors"]
  S --> C["Adjacent segment, use case, or geography"]
  A --> A1{"Valuable reachable job and viable first segment?"}
  A1 -->|"Yes"| A2["Test focused entry and category-education cost"]
  A1 -->|"No"| A3["Continue discovery, reframe, pause, or stop"]
  B --> B1{"Differentiation valuable, provable, defensible, and deliverable?"}
  B1 -->|"Yes"| B2["Test position through an operable channel"]
  B1 -->|"No"| B3["Test a narrower segment, different job, partnership, or no entry"]
  C --> C1{"Capabilities, permissions, brand, channel, and service model transfer?"}
  C1 -->|"Yes"| C2["Test expansion with cannibalization and outcome guardrails"]
  C1 -->|"No"| C3["Adapt, partner, acquire capability, defer, or stop"]

Text equivalent: Classify the entry as a new category, an existing competitive market, or an adjacency. For a new category, test whether the customer job and first segment are viable. For an existing market, test whether differentiation is valuable, supportable, defensible, and deliverable. For an adjacency, test whether capabilities and permissions transfer. Each branch permits further testing, adaptation, partnership, deferral, or no entry.

Strategy Definitions:

Focused category entry or new-market development

Goal: Test a defensible position when credible demand and operating readiness justify entry
Approach:
- Bounded customer acquisition with evidence and capacity controls
- Pricing and packaging supported by customer evidence and sustainable economics
- Test category-education cost and whether the job is understood and valuable
- Investigate switching, complements, network structure, and incumbent response rather than assuming a moat
Risk: The firm can spend heavily educating a category that lacks demand or that better-resourced competitors later enter

Differentiation (Existing Market)

Goal: Win on unique value, not price
Approach:
- Clearly articulate difference (not just "better")
- Focus on specific use case (don't try to be everything)
- Test whether willingness to pay supports the differentiated value and delivery cost
- Match assisted sales, self-service, or partners to buying complexity and firm capacity
Risk: Price erosion as competitors copy features

Niche (White Space)

Goal: Own specific segment nobody else serves well
Approach:
- Identify underserved customer segment (e.g., "left-handed designers")
- Build product specifically for their needs when evidence and capacity justify the investment
- Become thought leader in niche
- Test adjacent niches only when transferability, economics, capacity, and customer protections are evidenced
Risk: Niche too small; outgrow it quickly and need new markets

Land-and-Expand (Existing Customer)

Goal: Deepen relationships with existing customers
Approach:
- Introduce new product/service to existing customers (lower friction)
- Focus on account growth over new customer acquisition
- Cross-sell, upsell, usage expansion
Risk: Cannibalization (customer uses new product instead of old)

Choosing Strategy:

Table 14.8: Author-created market-entry comparison. Each row states evidence to obtain before commitment; the strategy labels do not predict success.

Situation	Candidate strategy	Evidence required before commitment
New or weakly defined category	Focused category entry	Valuable job, first segment, alternatives, education cost, complements, cash, and incumbent response
Existing market with provable difference	Differentiation	Comparative proof, willingness to pay, switching path, channel capacity, service quality, and contribution
Existing market without broad differentiation	Niche	Segment need, reachability, viable economics, competitive response, and credible expansion or durable-focus logic
Existing customer relationship or capability	Land-and-expand	Permission, incremental customer value, retention effects, cannibalization, capacity, and channel conflict

Decision rule: Concentration can reduce learning noise and capacity strain, but no strategy deserves a fixed one-year commitment. Define evidence, harm, cash, and authority gates, then continue, revise, pause, or stop.

So What for Managers

Make the no-entry, defer, partner, adapt, bounded-pilot, and exit options visible alongside the preferred entry strategy.
Require evidence about reachability, willingness to pay, delivery, contribution, cash, incumbent response, customer protection, and reversibility.
Recheck the decision as market, policy, channel, capacity, and customer-outcome evidence changes.

Limits and Critiques

Category, differentiation, niche, and land-and-expand labels simplify markets and can hide substitutes, power, regulation, and execution burden.
A decision tree cannot establish demand, defensibility, causal impact, or durable advantage from assumptions alone.
“Dominant,” “moat,” and fixed sequencing language can create overconfidence; entry may remain local, staged, reversible, or unattractive.

Connections

ICP and channels: Use Frameworks 2 and 4 to define the segment, route, capacity, and learning test.
Pricing and finance: Use Framework 5 and Chapter 4 for willingness to pay, contribution, currency, cash, and downside scenarios.
International gate: Use Framework 11 for country, institutional, data, trade, partner, service, and exit constraints.

11. International and Non-Market GTM Gate

Overview

The international and non-market GTM gate is a constructed governance screen for country-, sector-, product-, channel-, entity-, and date-specific entry decisions. It highlights evidence and accountable owners; it is not a country score, legal opinion, or substitute for local advice. ^[7] ^[8]

How to Apply

Define the exact entry scope and date, then map local demand, institutions, currency, tax, data, trade controls, labor, product standards, partners, service capacity, rights, and exit obligations. Treat non-compensable gates as gates; obtain documented specialist approval before transfer, launch, or irreversible investment. ^[9] ^[10] ^[11]

International entry is not domestic GTM with a translated website. Demand, institutions, public policy, currency, tax, data movement, product standards, trade controls, partner incentives, labor, service capacity, and exit feasibility can change the business model. Country-level indicators are a screening lens, not a substitute for country-, sector-, and transaction-specific evidence: the World Bank expressly cautions that its governance aggregates are too coarse to design specific reforms and reports uncertainty around estimates. ^[7]

Country and institution matrix

Table 14.9: International and non-market entry gate. This author-created matrix assigns evidence and accountable approval; official-source markers support only their narrow rows.

Decision lane	Evidence required before commitment	Gate or trigger
Customer and competition	Local jobs, alternatives, purchasing authority, willingness to pay, switching, channel access, incumbent response	Pilot only when the first segment and buying process are evidenced
Institutions and policy	Applicable national and subnational rules, licensing, procurement, competition, ownership, labor, consumer, product, tax, customs, IP, dispute resolution, corruption and human-rights exposure	Local counsel and accountable specialist approve the issue map; a country score never substitutes for law
Currency and cash	Transaction, translation, and economic exposure; invoicing currency; convertibility; repatriation; tax; collections; inflation; hedge availability and cost	Finance sets exposure limits, downside rates, liquidity needs, and stop-loss or repricing rules; see Chapter 4
Data and technology	Data categories and subjects, hosting, cross-border transfers, localization, security, access, retention, export-control classification and end use	Privacy, security, and trade-control owners approve the architecture before transfer or release; EU transfers, for example, require an applicable GDPR transfer mechanism or condition. ^[9]
Partner and route to market	Beneficial ownership, competence, reputation, incentives, rights, exclusivity, subagents, audit, training, support, sanctions/export screening and termination	Diligence is risk-based and continuing; partner status is not a compliance shield. ^[10] ^[11]
Operations and service	Lead time, inventory, returns, warranties, accessibility, language, local support, supplier continuity and crisis response	Capacity and customer-outcome tests pass under downside demand and disruption
Exit and reversibility	Contract termination, employee and customer obligations, data return/deletion, inventory, licenses, asset recovery, repatriation, communications and stranded cost	Exit plan is approved before irreversible investment; trigger owners and evidence cadence are named

The S09, S10, and S11 markers support only the narrow transfer, sanctions-control, and responsible-conduct points identified in their rows. The remaining institution, tax, labor, product, partner, service, and exit questions are author-created governance prompts requiring applicable local and specialist review.

The U.S. International Trade Administration's Country Commercial Guides provide current starting points for market conditions, regulations, business customs, channels, trade rules, and due diligence across more than 125 countries. They are not legal opinions or proof that a market is attractive. ^[8]

Figure 14.4: International-entry evidence and exit loop (constructed).

flowchart LR
  A["Define country, segment, product, entity, channel, and date"] --> B["Test demand and local economics"]
  B --> C["Map institutions, policy, data, trade, tax, labor, and rights"]
  C --> D["Diligence partners and operating capacity"]
  D --> E{"All non-compensable gates passed?"}
  E -->|"No"| F["Redesign, partner differently, defer, or stop"]
  E -->|"Yes"| G["Run bounded pilot with currency and outcome guardrails"]
  G --> H{"Scale, revise, pause, or exit?"}
  H -->|"Learn and revise"| B
  H -->|"Exit trigger"| I["Protect people, customers, data, contracts, cash, and evidence"]
  H -->|"Scale with approval"| J["Stage investment and recheck policy and assumptions"]

Text equivalent: Define the exact country, segment, product, entity, channel, and decision date; test demand and economics; map institutional, policy, data, trade, tax, labor, and rights constraints; and diligence partners and capacity. If a mandatory gate fails, redesign, defer, or stop. If gates pass, run a bounded pilot with currency and customer guardrails, then scale, revise, pause, or execute the preplanned exit.

Constructed country-comparison exercise

Compare two candidate countries using the matrix above. Supply a dated local-demand exhibit, two official regulatory sources per country, a currency downside scenario, a partner-diligence packet, a data-flow map, and a service-capacity plan. Recommend direct entry, distributor, licensing, joint venture, acquisition, remote service, further research, or no entry. State which evidence is missing, which criteria are non-compensable, what would reverse the choice, and how the firm exits without abandoning customers, workers, data, or legal obligations.

So What for Managers

Assign accountable owners for demand, institutional, finance, privacy, security, trade, labor, partner, service, rights, and exit decisions.
Treat non-compensable legal, safety, rights, privacy, trade, customer, and reversibility conditions as gates rather than offsetting them with market size.
Stage investment and recheck dated assumptions, policy, currency, partner, service, and customer-outcome evidence before scaling.

Limits and Critiques

Country indicators and commercial guides are screening inputs, not transaction-specific law, permissions, forecasts, or approvals.
A complete issue map cannot remove uncertainty about enforcement, political change, currency, partners, customers, or operational disruption.
International entry can create obligations to customers, workers, communities, counterparties, and data subjects that a revenue model does not capture.

Connections

Entry choice: Use Framework 10 to compare local, adjacent, partner, defer, and no-entry options.
Partner route: Use Framework 9 for ownership, incentives, customer rights, data/IP/security, audit, and exit.
Finance, product, and evidence: Use Chapter 4 for exposure and cash, Chapter 21 for product and data decisions, and Chapter 22 for dated evidence and uncertainty; obtain qualified local review.

Summary: GTM Strategy Frameworks

Table 14.10: Constructed framework-use summary. Timing is a planning aid, not a universal sequence or readiness gate.

Framework	When to Use	Time Required
GTM Canvas	Before any customer conversations	2-3 hours
ICP Framework	Before sales/marketing investments	1-2 days
Funnel Metrics	After first 10 customers	Ongoing (weekly review)
Channel Strategy	When deciding sales/marketing mix	1-2 weeks
Pricing	Before launch	1-2 weeks
Launch Checklist	4 weeks before launch	Ongoing coordination
Growth experimentation	When a mechanism can be tested safely	Duration set by decision and measurement design
Product-mediated diffusion	When invitations or sharing are observable	Ongoing cohort analysis
Partnership Matrix	When partnership inquiries arrive	1-2 days per opportunity
Market Entry Decision	Before GTM strategy	1 day

How To Get Started

Go-to-market strategy often feels overwhelming - there are 10+ frameworks, hundreds of decisions, and pressure to launch fast. This section provides two practical paths: a Quick Version (2-3 weeks) focused on validating your GTM Canvas and refining your ICP, and a Detailed Version (8-12 weeks) for a comprehensive GTM launch from strategy through early scale.

Constructed-template boundary: Every day, week, interview count, score, target-account count, conversion rate, price, budget, workload, and decision threshold in both paths is illustrative. Managers must set a decision-specific sample and cadence from risk, heterogeneity, access, precision, capacity, cash, and legal constraints. Interviews reveal accounts and hypotheses; they do not by themselves validate demand or establish causal effects.

Version 1: Quick GTM Validation (2-3 Weeks)

Goal: Validate your GTM assumptions with real customers, refine your ICP, and prepare for launch with confidence.

Timeline: 15-20 Business Days

Days 1-2: GTM Canvas Workshop

What: Complete the GTM Strategy Canvas (Framework #1)
How:
- Gather founding team + any advisors (2-3 hour workshop)
- Fill out each component:
  - TARGET: Who is the customer? (Be specific: industry, size, geography)
  - PROBLEM: What painful problem do they have? (Quantified if possible)
  - VALUE PROP: Why us vs. alternatives? (1 sentence, clear benefit)
  - CHANNEL: How will they find us? (Pick 1-2 primary channels)
  - PRICING: How much will they pay? (Ballpark pricing model)
  - ECONOMICS: What's the unit economics? (CAC estimate, LTV estimate)
  - GROWTH: What's Year 1 target? (Revenue, customer count)
- Output: Draft GTM Canvas (1 page)
Pitfall to Avoid: Being too broad ("anyone who needs X" → narrow to specific segment)

Days 3-10: Customer Validation Interviews

What: Talk to 20 potential customers to validate GTM assumptions
How:
- Identify 50 target prospects matching your TARGET profile
- Reach out via email/LinkedIn (personalized: "Can I get 20 minutes of feedback?")
- Schedule 20 conversations (15-20 minutes each, 2-3 per day)
- Interview script:
  - "Tell me about [problem we think they have]" (validate problem exists)
  - "How do you solve this today?" (understand alternatives)
  - "What would make a solution worth paying for?" (validate value prop)
  - "How do you typically evaluate/buy tools like this?" (validate channel)
  - "What would you expect pricing to be?" (validate pricing)
- Track responses in spreadsheet:
  - Prospect name, company, role
  - Problem confirmed? (Yes/No/Partial)
  - Current solution (DIY, competitor, nothing)
  - Interest level (High/Medium/Low)
  - Pricing feedback
Output: 20 completed interviews, pattern analysis
Review signal: If the locally defined evidence share does not support urgency, revisit the PROBLEM definition; the percentage in the earlier draft was illustrative, not a universal threshold.

What: Analyze interviews to identify "who succeeds best"
How:
- Review interview notes and identify patterns:
  - Which companies expressed highest urgency?
  - Which had budget/decision authority?
  - Which understood value prop immediately?
- Create ICP profile using Framework #2:
  - Firmographic: Industry, company size, revenue range, geography
  - Behavioral: Tech stack, buying cycle, decision process
  - Psychographic: Values (data-driven? risk-averse? early adopter?)
- Score each interviewed company (1-10 ICP fit)
- Identify top 10 best-fit prospects (your launch targets)
Output: 1-page ICP profile, scored prospect list
Pitfall to Avoid: Keeping ICP too broad ("we can sell to anyone") - narrow to best fit

Days 16-20: Pricing/Channel Decision + Launch Prep (Week 3)

What: Finalize pricing and channel strategy based on validation
How:
- Pricing decision:
  - Review feedback from 20 interviews
  - Model unit economics (Framework #5):
    - Estimated CAC (based on channel choice)
    - Estimated contribution/value scenario (not observed LTV)
    - Target: A locally approved contribution and payback scenario with explicit margin, service cost, cash timing, and uncertainty
  - Pick pricing model (per-seat, value-based, freemium, usage-based)
  - Set initial price (can adjust later, but start somewhere)
- Channel decision:
  - Based on ICP and interviews, which channel makes sense? (Framework #4)
  - Direct sales (if high-touch, complex sale)
  - Self-serve (if simple, low price point)
  - Partnerships (if need distribution help)
  - Pick 1-2 primary channels (focus > spreading thin)
- Launch prep:
  - Set launch date (30-60 days out)
  - Draft 1-page launch plan (key activities, timeline)
  - Identify first 10 target customers (from ICP list)
Output: Pricing decision, channel strategy, launch date set

Final Deliverable (End of Week 3):

1-page GTM Canvas (validated with 20 customers)
1-page ICP profile (scored, with top 10 target accounts)
Pricing model decided (with unit economics modeled)
Launch date set (30-60 days out)
Confidence level: High (based on customer validation)

Measurement Framework:

Daily: Customer conversations completed (target: 2-3/day during Week 1-2)
Weekly: GTM Canvas confidence (1-10 scale, target: 7+ by end of Week 3)
End of Week 3: Number of "high interest" prospects (target: 10+ out of 20 interviewed)

Version 2: Detailed GTM Launch (8-12 Weeks)

Goal: Comprehensive GTM strategy from canvas through launch and early optimization.

Timeline: 8-12 Weeks (4 Phases)

Detailed-path Phase 1: GTM Canvas Development & Validation (Weeks 1-2)

Week 1: Draft GTM Canvas

Monday-Tuesday: GTM Canvas workshop (same as Quick Version Days 1-2)
Wednesday-Friday: Research & preparation
- Identify 100 target prospects (will narrow to 50 for interviews)
- Draft customer interview script
- Research competitors (what's their GTM? pricing? positioning?)
- Create competitor matrix (us vs. top 3 alternatives)
Output: Draft GTM Canvas, competitor analysis, interview script

Week 2: Customer Validation

Monday-Friday: 20 customer interviews (4 per day)
- Same interview approach as Quick Version
- Focus on problem validation, alternative analysis, pricing feedback
Weekend/End of Week: Synthesize findings
- Problem validation: % who confirmed urgent problem
- Value prop resonance: % who understood benefit immediately
- Pricing feedback: Range of acceptable pricing
- Channel insights: How do they discover/evaluate tools?
Output: 20 completed interviews, synthesis memo

Detailed-path Phase 2: ICP Deep Dive & Positioning (Weeks 3-4)

Week 3: ICP Refinement

Monday-Tuesday: Analyze interview patterns (same as Quick Version)
- Create firmographic, behavioral, psychographic profile
- Score all 20 interviewed companies (1-10 ICP fit)
Wednesday-Thursday: Expand ICP analysis
- Identify 3-5 customer segments (if patterns emerge)
- For each segment, calculate:
  - Size (how many companies fit this profile?)
  - Avg deal size (based on pricing feedback)
  - Win rate estimate (based on urgency/fit)
  - LTV:CAC estimate
- Pick primary segment (best economics + best fit)
Friday: Create target account list
- List 200 companies matching ICP (prioritized by fit score)
- Segment into tiers: Tier 1 (top 50), Tier 2 (next 100), Tier 3 (rest)
Output: ICP profile, segmentation analysis, target account list (200 companies)

Week 4: Positioning & Messaging

Monday-Tuesday: Define positioning
- Value proposition (1 sentence, quantified)
- Key differentiators (vs. competitors, DIY, do nothing)
- Positioning statement: "For [TARGET], who [PROBLEM], our product [SOLUTION], unlike [ALTERNATIVE]"
- Example: "For mid-market SaaS companies who spend 3 weeks building data pipelines, DataFlow deploys in 3 days and saves $500K/year, unlike custom builds that take 6 months"
Wednesday-Thursday: Create messaging framework
- Homepage headline (7 words or less)
- Value prop statement (1 sentence)
- 3 key benefits (with quantified outcomes)
- Customer testimonials (if available from interviews)
- Objection handling (common concerns + responses)
Friday: Validate messaging
- Send positioning/messaging to 5 interviewed customers (get feedback)
- Iterate based on feedback (clarity, resonance)
Output: Positioning statement, messaging framework (validated)

Detailed-path Phase 3: Channel & Pricing Strategy (Weeks 5-6)

Week 5: Channel Strategy

Monday-Tuesday: Channel evaluation (Framework #4)
- Evaluate 3-5 potential channels:
  - Direct sales: Calculate (# reps needed × cost per rep × ramp time)
  - Inside sales: Calculate (# SDRs + AEs × cost × productivity)
  - Self-serve: Calculate (website build + ad spend + conversion rate)
  - Partnerships: Identify 10 potential partners (fit, reach, feasibility)
  - Content marketing: Estimate (content team cost + SEO timeline)
- For each channel, model:
  - Upfront investment (time + money)
  - CAC estimate (based on industry reference points)
  - Timeline to first customer
  - Scalability (can this channel get to 100 customers?)
Wednesday-Thursday: Pick 1-2 primary channels
- Criteria: Best LTV:CAC ratio + fastest time to revenue + team capability
- Create channel plan:
  - Month 1-3: Activities, budget, expected output
  - Month 4-6: Scale plan (if working)
  - Success metrics (CAC, conversion rate, payback period)
Friday: Channel partnerships (if relevant)
- If partnerships is a channel, identify 5 target partners
- Draft partnership proposal (1-pager: value to partner, economics, timeline)
Output: Channel strategy (1-2 primary channels), channel plan, partnership targets

Week 6: Pricing & Unit Economics

Monday-Tuesday: Pricing model selection (Framework #5)
- Review pricing feedback from interviews
- Evaluate pricing models:
  - Per-user: Pros/cons, pricing range
  - Value-based: ROI calculation, pricing approach
  - Freemium: Free tier limits, conversion rate estimate
  - Usage-based: Pricing per unit, predictability concerns
- Pick pricing model based on:
  - Customer preference (from interviews)
  - Revenue predictability
  - Sales complexity
Wednesday-Thursday: Unit economics modeling
- Build spreadsheet model:
  - Inputs: Pricing, CAC (by channel), churn rate, sales cycle length
  - Outputs: LTV, CAC, LTV:CAC ratio, payback period, break-even timeline
- Model 3 scenarios:
  - Base case (realistic assumptions)
  - Optimistic (20 percent better on all metrics)
  - Pessimistic (20 percent worse on all metrics)
- Validate: Does the base-case contribution and payback scenario meet the locally approved threshold? (if not, adjust pricing or channel)
Friday: Finalize pricing
- Set initial pricing (can iterate post-launch)
- Create pricing page copy (tiers, features, pricing)
- Draft pricing FAQ (common questions + answers)
Output: Pricing model decided, unit economics model, pricing page draft

Detailed-path Phase 4: Launch Preparation & Execution (Weeks 7-12)

Week 7-8: Launch Preparation

Week 7: Marketing assets
- Website/landing page (value prop, product screenshots, pricing, CTA)
- Sales deck (5 slides: problem, solution, differentiation, pricing, case example/testimonial)
- Email templates (outreach, follow-up, launch announcement)
- Product demo (recorded or live demo script)
- FAQ / Help documentation (1-page "How to Get Started")
Week 8: Sales & partnerships
- Sales process documentation (qualification, pitch, objection handling, close)
- CRM setup (track leads, pipeline stages, conversion rates)
- Partnership agreements (if relevant, finalize terms with 1-2 partners)
- Launch target list (50 Tier 1 accounts for launch outreach)
Output: Marketing assets, sales process, partnerships finalized, launch readiness

Week 9: Launch

Pre-launch (Days 1-3):
- Send "coming soon" email to target list (50 Tier 1 accounts + interviewed prospects)
- Finalize product (QA testing, performance testing)
- Coordinate team (everyone knows launch plan, responsibilities)
Launch Day (Day 4):
- Announce launch (email, social, website live)
- Outreach to Tier 1 accounts (personalized emails from sales team)
- Monitor product stability (check error rates, performance, support volume)
- Respond to inquiries in real-time (<1 hour response time)
Post-launch (Days 5-7):
- Follow up with interested leads (book meetings, send demos)
- Collect early feedback (questionnaire or 1-on-1 conversations)
- Fix critical bugs (if any identified)
- Publish launch recap (metrics, wins, learnings)
Output: Launch executed, early customer feedback, first customers (target: 5-10)

Weeks 10-12: Optimization & Iteration

Week 10: Measure & analyze
- Track funnel metrics (Framework #3):
  - Awareness: Lead volume (from launch activities)
  - Consideration: Meeting booking rate
  - Proposal: Proposal submission rate
  - Close: Win rate
- Calculate actual CAC (launch spend / customers acquired)
- Calculate early LTV (based on pricing + estimated retention)
- Compare to model (actual vs. projected unit economics)
Week 11: Iterate based on learnings
- If low conversion: Revisit messaging (not resonating?) or ICP (wrong target?)
- If high CAC: Optimize channel (reduce spend, improve targeting)
- If low LTV: Revisit pricing (too low?) or retention (churn too high?)
- Make 2-3 key changes based on data
Week 12: Scale preparation
- Document playbook (what's working? how to replicate?)
- Set Month 4-6 goals (revenue, customers, metrics)
- Identify constraints (sales team capacity? product readiness? budget?)
- Plan next phase (hire sales rep? expand channel? new partnerships?)
Output: GTM playbook, Month 4-6 plan, scale readiness

Weekly GTM Cadences (Weeks 9-12):

Sales Cadence (Weekly):

Monday: Pipeline review (where are deals? stuck? moving forward?)
Wednesday: Prospect outreach (add 20 new leads to pipeline)
Friday: Deal reviews (close deals, negotiate terms, move to next stage)

Marketing Cadence (Weekly):

Tuesday: Content publish (blog post, social update, email newsletter)
Thursday: Campaign review (ad performance, email open/click rates, website traffic)
Friday: Lead handoff to sales (qualified leads from marketing → sales pipeline)

Partnership Cadence (Bi-weekly):

Every other Monday: Partner check-in (leads generated? support needed? co-marketing opportunities?)

Measurement Framework (Weeks 9-12):

Weekly Metrics:

Customer conversations count (target: 10+ conversations/week with prospects)
Feedback patterns (are objections consistent? is messaging resonating?)
GTM Canvas confidence (1-10 scale, should be 8+ by Week 12)

Launch Metrics (Weeks 9-10):

CAC (Customer Acquisition Cost): Launch spend / customers acquired, with the inclusion rule and cohort stated; compare with the approved scenario rather than a universal target.
Early value scenario: Report the contribution formula, margin, retention evidence, service cost, cohort, and uncertainty; pricing × estimated retention is not observed LTV.
Conversion rate: Leads → Meetings → Proposals → Closed (track each stage)
Retention by cohort: Are customers retained and receiving value in the defined observation window? Set the target from the decision and customer-outcome context.

Monthly Metrics (Months 3-4):

Growth rate: Month-over-month revenue growth (target: 20 percent or more MoM)
Customer acquisition trend: Are we acquiring customers faster each month?
Unit economics trending: Is CAC decreasing? Is LTV increasing? (both indicate improving efficiency)

Final Deliverable (End of Week 12):

GTM strategy fully executed (Canvas → ICP → Channel → Launch)
First 10-20 customers acquired
Unit economics validated (actual vs. projected)
Funnel metrics tracked (know conversion rates at each stage)
GTM playbook documented (repeatable process for next quarter)
Scale plan ready (Month 4-6 roadmap)

Common Pitfalls

Even with a solid plan, GTM strategies fail for predictable reasons. Watch out for these five common pitfalls:

1. Vague Target Customer ("Everyone is NOT the customer")

Symptom: GTM Canvas says "any company that needs X" or "B2B companies"
Why it's a problem: Marketing becomes generic, sales wastes time on bad-fit prospects, product tries to serve everyone (serves no one well)
Fix: Force specificity in ICP
- Example: Change "SaaS companies" → "Series A-C SaaS companies, $5-50M ARR, 50-300 employees, US-based"
- Test: Can you list 50 companies that fit this profile? If not, too vague.
Warning sign: Conversion rates are low across all prospects (no clear "perfect fit" segment emerging)

2. Misaligned Channel Choice (Channel doesn't match customer buying behavior)

Symptom: You choose self-serve, but customers need demos. Or you choose direct sales, but customers want to "try before buy."
Why it's a problem: Friction between how you sell and how customers want to buy = lost deals
Fix: During interviews, ask "How do you typically evaluate and buy tools like this?"
- If they say "we need to see ROI analysis, talk to multiple stakeholders" → Direct sales (high-touch)
- If they say "we just try it, if it works we buy" → Self-serve (low-friction)
Warning sign: High lead volume but low conversion (channel mismatch)

3. Pricing Too High or Too Low (No unit economics analysis)

Symptom - Too high: Prospects say "interested but too expensive" OR long negotiation cycles with heavy discounting
Symptom - Too low: You're acquiring customers fast but unit economics are negative (CAC > LTV)
Why it's a problem:
- Too high: Kills deals, slows growth
- Too low: Grows fast but burns cash (unsustainable)
Fix: Model unit economics BEFORE launch (Framework #5)
- Calculate: CAC by channel and a contribution-based value scenario with margin, retention, service cost, cash timing, and uncertainty.
- If ratio is too low, raise prices OR reduce CAC (improve conversion)
- Test pricing with 5 customers (pilot program) before scaling
Warning sign: The value-to-acquisition relationship is below the approved decision threshold or discounting exceeds the approved policy.

4. Launch Without Measurement (No funnel metrics tracked)

Symptom: You launch, get some customers, but don't know which channel worked, what conversion rates are, or where prospects drop off
Why it's a problem: Can't optimize what you don't measure. You'll scale inefficient channels, miss bottlenecks, waste budget.
Fix: Set up funnel tracking BEFORE launch (Framework #3)
- Track: Awareness (leads), Consideration (meetings booked), Proposal (proposals sent), Close (deals won)
- Use CRM or simple spreadsheet to track every prospect through funnel
- Weekly review: Where are prospects getting stuck? What's the bottleneck?
Warning sign: Can't answer "What's our CAC?" or "What's our lead → customer conversion rate?"

5. Ignoring Competition (No positioning against alternatives)

Symptom: Prospects say "we'll think about it" but never close (considering alternatives)
Why it's a problem: If you don't differentiate, you're commoditized (price becomes only decision factor)
Fix: Build competitive positioning (Framework #1, Value Prop section)
- Identify top 3 alternatives (competitor, DIY, do nothing)
- For each, articulate: "Unlike [alternative], we [specific benefit]"
- Example: "Unlike custom builds that take 6 months, we deploy in 3 days"
- Validate with customers: "Why did you choose us vs. [competitor]?"
Warning sign: Long sales cycles with no clear reason for delay (customer is comparison shopping)

How to Avoid Pitfalls:

Use frameworks (GTM Canvas, ICP, Funnel Metrics = built-in structure to catch these)
Validate early (20 customer conversations = surface issues before launch)
Measure constantly (weekly funnel review = catch problems fast)

Red Flags: When GTM is Failing

Even with a plan, GTM strategies can fail. Here are red flags that indicate you need to revisit your strategy:

Red Flag #1: Low Conversion Rates

Metric: Lead → Customer conversion materially below your modeled target
Diagnosis:
- Wrong ICP (talking to companies that aren't good fit)
- Weak value prop (not compelling enough)
- Misaligned channel (friction in buying process)
Action: Re-interview 10 lost deals (why didn't they buy?), revisit ICP and messaging

Red Flag #2: High CAC

Metric: Acquisition cost exceeds the contribution and cash threshold approved for the defined cohort.
Diagnosis:
- Inefficient channel (high cost, low conversion)
- Pricing too low (not capturing enough value)
- Long sales cycle (high time/cost to close)
Action: Model unit economics again, consider raising prices OR switching channels

Red Flag #3: No Word-of-Mouth / Referrals

Metric: low share of new customers from referrals after the initial customer cohort
Diagnosis:
- Product not sticky (customers don't love it enough to refer)
- No incentive to refer (not easy/rewarding to share)
- Wrong ICP (customers aren't networked)
Action: Customer interviews (why aren't they referring?), implement referral program, improve product experience

Red Flag #4: High Early Churn

Metric: excessive early churn in the first customer cohort
Diagnosis:
- Over-promised during sales (expectations not met)
- Poor onboarding (customers don't get value fast)
- Wrong ICP (customers aren't right fit)
Action: Interview churned customers (why did they leave?), improve onboarding, tighten ICP

Red Flag #5: Stalled Growth

Metric: growth materially below the plan after the first operating quarter
Diagnosis:
- Market too small (ran out of ICP targets)
- Channel saturated (exhausted initial leads)
- Competition caught up (differentiation eroded)
Action: Expand ICP (adjacent segments?), add new channel, revisit differentiation

What to Do When You See Red Flags:

Stop scaling (don't pour money into broken GTM)
Diagnose root cause (talk to customers, analyze data)
Fix core issue (adjust ICP, messaging, pricing, channel)
Validate fix (test with 5-10 customers before scaling again)
Resume growth (once unit economics and conversion rates are healthy)

Why This Matters: Mental Models & GTM Wisdom

Go-to-market strategy is a system of interconnected decisions about how a firm creates, captures, and delivers value. The arithmetic, cases, channel ranges, stage bands, and outcomes in this section are constructed teaching examples or composites, not observed company histories, causal estimates, or benchmarks. They surface hypotheses and trade-offs that a manager must test against local evidence.

Mental Models: Why GTM Strategy Works

1. GTM Canvas: Holistic Customer View Across Acquisition, Activation, Retention

The Systems Thinking: Most founders treat acquisition, product, and pricing as separate problems. The GTM Canvas forces holistic thinking: every component affects every other component. Your pricing model affects which customers you can acquire profitably. Your ICP determines which channels work. Your channel determines what unit economics are possible. The canvas prevents the common failure mode: optimizing one part while breaking the whole.

The Psychology: A GTM plan is a system: changing one variable can alter the economics of the others. A canvas can make those dependencies discussable. In a constructed example, placing "CAC: $5K" and "ARPU: $100/month" on the same page prompts the team to calculate a simple 50-month revenue payback before margin, retention, or cash-timing adjustments.

Why It Works:

Supports trade-off visibility: A constructed high-touch-sales case with $30K CAC and $99 monthly pricing exposes a mismatch that requires full margin, retention, and cash analysis.
Supports scenario iteration: Changing a constructed price assumption from $99 to $299 shows how one input affects modeled unit economics; it does not establish willingness to pay.
Prevents silo optimization: Marketing can't optimize for volume if sales can't handle the leads
Creates alignment: When whole team sees the canvas, everyone understands how their work fits together

The Failure Mode: Teams can optimize local metrics while degrading the overall system. A constructed example is marketing celebrating 10,000 leads while sales lacks capacity, or sales celebrating 100 customers while finance estimates that CAC exceeds LTV. A canvas can surface the disagreement, but it cannot prevent local optimization without shared definitions, incentives, governance, and decision rights.

The Economic Principle: The GTM Canvas operationalizes strategic fit - Porter's concept that competitive advantage comes from how activities reinforce each other. Your channel choice reinforces your pricing, which reinforces your ICP, which reinforces your product positioning. When these elements fit together, you have a defensible business. When they don't, you have a pile of disconnected tactics.

2. ICP Focus: Concentration of Resources on Highest-Value Customers

The Strategic Insight: The counter-intuitive truth about customer acquisition: narrowing your target increases your success rate. Most founders fear narrowing: "But we're leaving money on the table!" The opposite is true. Trying to sell to everyone means your message resonates with no one, your product serves no one excellently, and your resources scatter across hundreds of mediocre opportunities.

The Math: Consider two strategies:

Broad: Target 1,000 companies, 5 percent win rate, $50K deal size, $10K CAC → 50 customers, $2.5M revenue, $500K CAC spend
Narrow ICP: Target 200 companies (perfect fit), 25 percent win rate, $50K deal size, $8K CAC → 50 customers, $2.5M revenue, $400K CAC spend

Same revenue, but the narrow approach has:

Lower modeled CAC ($8K vs $10K in this constructed comparison): Investigate whether the difference reflects message fit, lead mix, sales-cycle length, attribution, exclusions, or random variation.
Higher win rate (25 percent vs 5 percent): Sales team focuses on qualified leads
Better retention: Perfect-fit customers stay longer (higher LTV)

Why It Works:

Message clarity: "For mid-market SaaS companies" resonates more than "for any company"
Product focus: Build features perfect-fit customers need, ignore edge cases
Sales efficiency: Reps become experts in one customer type, learn objections, iterate playbook
Retention: Customers who perfectly fit your ICP get more value, churn less

The Psychological Trap: Founders resist narrowing because it feels like artificial constraint. "Why would I say no to a customer?" The answer: opportunity cost. Every hour spent on a mediocre-fit customer is an hour not spent on a perfect-fit customer. The narrow ICP isn't about saying no to customers - it's about saying yes to the strategy that produces the most customers.

The Failure Mode: "Spray and pray" GTM: Sales targets 5,000 companies with generic messaging. Win rate is 2 percent. Sales team blames product or marketing. Real problem: No ICP discipline. The solution isn't better messaging - it's narrower targeting so messaging can actually be specific.

3. Channel Strategy: Matching Customer Behaviors to Go-to-Market Approaches

The Core Principle: Channels are not interchangeable distribution pipes. Each has acquisition, enablement, support, control, and margin implications. Low-touch selling can fit some simple, lower-stakes purchases; complex or high-stakes purchases may require more assisted evaluation. Match the channel to observed buying behavior and economics rather than treating price as a deterministic selector.

The Economics: Each channel has a natural CAC range and customer expectation:

Table 14.11: Constructed channel-model comparison. Values are illustrative ranges and descriptive expectations to test locally, not natural channel properties.

Channel	Natural CAC	Customer Expectation	Works For
Self-serve	$50-500	Try immediately, low assisted-sales burden	$10-100/month, simple products
Inside sales	$1K-5K	Personalized demo and assisted evaluation	$100-500/month, some complexity
Direct sales	$10K-50K	Multi-stakeholder, custom solution	$50K+/year, high complexity

The Mismatch Failure Mode:

Self-serve for complex product: Customers bounce (too confusing without help)
Direct sales for simple product: CAC too high (spending $20K to acquire $500/year customer)
Inside sales for tiny deals: Sales team drowns in small deals, can't hit quota

Why It Works When Matched:

Self-serve + Simple product: Customer can try immediately, get value, convert
Direct sales + Complex product: Sales guides customer through evaluation, justifies ROI (Salesforce, SAP)
Inside sales + Mid-market: Balance of touch (phone/video calls) and efficiency (no travel)

The Strategic Insight: Channel design influences unit economics but does not determine them alone. Direct sales can add acquisition and service cost, so test whether observed contract value, margin, retention, sales-cycle length, and cash timing support it. Customer segment, product, channel, and economics should be modeled jointly rather than derived from a universal CAC, ACV, or LTV:CAC rule.

4. Pricing Psychology: Value Perception vs. Cost Basis

The Counterintuitive Truth: Value-based pricing treats the customer's perceived economic value and credible alternatives as central inputs, while cost, capacity, risk, competition, and required return constrain what is viable. A constructed cost-plus example—"It costs us $20 to deliver, so we'll charge $30"—does not establish willingness to pay. If an offer may create large annual savings, quantify and validate that value before using it in pricing. ^[2]

The Psychology of Price: Customers don't buy products - they buy outcomes. Your price should reflect the value of the outcome, not the cost of your inputs. Consider:

Payment processors charge per transaction: The price reflects payment reliability and business value, not only processing cost.
Constructed enterprise-software case: Assume a $100K annual price and a customer-estimated $1M annual benefit, then test implementation cost, adoption, realized benefit, alternatives, risk, and willingness to pay.

The Three Pricing Failures:

Too low: Based on costs, not value. Customers assume low price = low quality. You leave money on table.
Too high: Based on wishful thinking, not value. Customers can't justify ROI. You get no customers.
Wrong model: Per-seat when usage-based fits better (or vice versa). Customers confused or feel cheated.

Why Value-Based Pricing Works:

Tests differentiated value: If enterprise users report materially greater value than smaller buyers, test differentiated packaging and willingness to pay rather than applying a fixed multiple.
Tests shared economics: In a constructed case, compare a customer's estimated $1M benefit with a proposed $200K price, implementation cost, uncertainty, and alternatives.
Makes assumptions explicit: A claim such as "estimated $500K annual benefit for a $100K investment" still requires a documented baseline, causal logic, sensitivity range, and later benefit realization.
Potential retention mechanism: Clear, realized value may support retention, but churn also depends on product quality, alternatives, switching, service, contracts, price, and customer conditions.

The Failure Mode: Founders who never ask "What's this worth to the customer?" end up either:

Underpriced: Growing fast but unit economics broken (every customer loses money)
Overpriced: No sales because customers can't justify ROI

The Strategy: During customer discovery, ask what the problem costs today and what evidence supports that estimate. Treat stated willingness to pay as a hypothesis, not a binding boundary. Combine it with observed purchase behavior, alternatives, implementation burden, cost-to-serve, and controlled price tests before selecting a price.

Constructed Failure Composites: Which GTM Assumptions Could Fail

Composite 1: Consumer File-Sync Platform — GTM Conflict

What Happened: A consumer file-syncing platform grew through a freemium model, then tried to move upmarket into enterprise accounts. The shift created GTM confusion because the original consumer motion and the enterprise motion required different pricing, product, and sales systems.

The GTM Confusion: The company tried to run two completely different GTM motions simultaneously:

Consumer GTM: Self-serve freemium, viral growth, low monthly subscription, no sales team
Enterprise GTM: Direct sales, complex deals, annual contracts, dedicated sales team

What Failed:

Channel Conflict: Free users in enterprises blocked paid enterprise deals ("Why pay when we can use free?")
Sales Complexity: Sales reps struggled to sell against free product their own company offered
Product Fragmentation: Enterprise needed security, admin controls, compliance (different product from consumer)
Brand Confusion: Was the product a consumer utility or enterprise tool? Market couldn't tell.
Economics Mismatch: Consumer and enterprise unit economics required different strategies

What The GTM Should Have Shown:

ICP Clarity: The company should have chosen: consumer OR enterprise, not both
Channel Fit: Can't run self-serve freemium AND direct sales (they cannibalize each other)
Pricing Strategy: Freemium works for consumer, not for enterprise (CFOs don't want "free trial" culture)

What Actually Happened: The company spent years trying to bridge consumer and enterprise GTM. Result:

Slow enterprise growth: Sales team struggled against free product
Consumer revenue stagnation: Free users never converted to paid at high rates
Investor narrative complexity: The market struggled to understand whether the company was a consumer utility or enterprise platform

What Could Have Saved Them:

Separate Brands: Create a business product as a clearly distinct offer
Kill Freemium for Enterprise: No free tier for business email domains (force paid from Day 1)
Choose One Lane: Double down on consumer OR pivot fully to enterprise (don't straddle)
Pricing Confidence: Charge enterprise pricing that reflects security, administration, and compliance value

The Learning: You can't run two conflicting GTM strategies simultaneously. Consumer GTM (freemium, viral, self-serve) and enterprise GTM (direct sales, paid, high-touch) have opposite requirements. Trying to do both created friction, confusion, and missed opportunity. Pick one GTM, execute excellently, then (maybe) expand to the other.

Composite 2: Team Collaboration Platform — GTM Evolution

What Happened: A team collaboration platform launched with a freemium, viral, self-serve GTM. The model worked well for small teams, but stopped working at enterprise scale, forcing a GTM transformation toward direct sales and enterprise controls.

The Original GTM:

Freemium: Free for small teams, paid for advanced features
Viral: Every person invited to the workspace could invite others
Self-serve: No sales team, customers signed up via website
Economics: Low-touch acquisition economics were strong while teams bought on their own

Why It Stopped Working:

Enterprise adoption hit wall: Free teams inside F500 companies grew, but companies didn't centrally adopt
Security/Compliance concerns: IT departments blocked adoption when enterprise controls were insufficient
Revenue leakage: Large companies could use free workspaces instead of central paid deployments
Competition: Bundled enterprise alternatives changed the buying conversation

The Forced Pivot: The company had to add:

Direct sales team: Enterprise reps to sell into large accounts
Enterprise features: SSO, compliance, admin controls, data residency
New pricing: Enterprise packages for large deployments
Marketing shift: From "fun" consumer brand to "secure" enterprise brand

The GTM Cost:

Sales team expense: A major new operating cost
CAC expansion: Enterprise selling costs were structurally higher than self-serve acquisition
Slower growth: Viral growth stalled; sales-led growth is slower
Lower margins: Direct sales adds operating cost and reduces contribution margin

What The GTM Evolution Taught:

Viral GTM doesn't scale to enterprise: F500 companies don't adopt via bottom-up viral; they require top-down sales
Free users aren't revenue: Large free-user populations still need conversion into paid company accounts
Competitive response required GTM shift: Bundled alternatives forced the product to prove enterprise value through sales
Stage dependency: Viral GTM works early (low CAC, high growth), but mature markets require sales-led GTM

What Could Have Prevented Crisis:

Earlier enterprise investment: Build security/compliance features before enterprise demand forced the issue
Hybrid GTM from start: Viral for SMB, sales-led for enterprise (not "flip the switch" later)
Kill free tier for large companies: Force companies >100 people to pay from Day 1
Pricing power: Charge for enterprise value and invest in enterprise sales earlier

The Learning: Your GTM must evolve with market maturity. What works in early revenue stages (viral, freemium, self-serve) often doesn't work at enterprise scale (sales-led, paid, high-touch). Founders must anticipate this evolution, not react in crisis mode.

Composite 3: Enterprise Analytics Vendor — Mid-Market Mismatch

What Happened: An enterprise analytics vendor built an enterprise-focused GTM: direct sales, long sales cycles, large contracts, and dedicated implementation teams. When the company tried to expand to mid-market companies with the same GTM, the motion did not fit the segment economics.

The Enterprise GTM (What Worked):

ICP: Large enterprises and government agencies
Deal Size: Large multi-year contracts
Sales Cycle: 12-24 months (complex procurement)
Channel: Direct sales, C-suite relationships, multi-year contracts
CAC: High acquisition cost, justified only by large deal size

The Mid-Market Disaster (What Failed): The vendor assumed: "We can take our proven GTM and apply it to smaller companies." They were wrong.

Why It Failed:

CAC Mismatch: Enterprise acquisition costs do not work for mid-market budgets
Sales Cycle Too Long: Mid-market companies can't afford 12-month evaluation (need revenue faster)
Product Complexity: The product required dedicated implementation teams; mid-market customers could not afford that burden
Buying Process: F500 has procurement departments; mid-market has VP who needs quick decision
Pricing: Enterprise minimums were too large for mid-market revenue bases

What The Pattern Showed:

Win Rate: Mid-market prospects did not convert at enterprise rates
Deal Size: Average contract value could not support enterprise CAC
Sales Cycle: Evaluation stayed too long for the segment
Churn: Product fit was weaker outside the enterprise segment

What The GTM Should Have Revealed:

Channel: Mid-market needs lower-touch sales, not enterprise field sales
Product: Mid-market needs self-serve onboarding, not 6-month implementations
Pricing: Mid-market needs a package sized to its budget and buying process

What They Did Instead: Doubled down on enterprise GTM and abandoned the mid-market motion. The lesson was expensive but clear.

What Could Have Prevented Failure:

Different GTM for Different Segment: Build mid-market GTM from scratch (inside sales, lower-touch, simpler product)
Unit Economics Modeling: Before investing, model: "Can we acquire mid-market customers at a CAC the deal size supports?"
Product Simplification: Build a simpler version with self-serve setup
Test Before Scale: Pilot with 10 mid-market companies using new GTM, prove it works before hiring 50 sales reps

The Learning: Enterprise GTM doesn't translate to SMB/mid-market. The channels, economics, sales cycles, and product requirements are fundamentally different. Founders often assume: "We can sell to anyone!" False. Each customer segment requires a different GTM system. Applying the wrong GTM to the wrong segment burns money fast.

Competing Schools: Different GTM Philosophies

Understanding competing GTM philosophies helps founders choose the right approach for their market, product, and stage. Each school of thought has fierce advocates, clear strengths, and predictable failure modes.

Comparison boundary: The categories are simplified design options. All CAC, deal-size, margin, speed, sustainability, and stage claims are illustrative hypotheses; channel performance depends on definitions, segment, capacity, competition, product, service, cash timing, and causal evidence.

1. Direct vs. Indirect Sales (Margin vs. Channel Scale)

Direct Sales Philosophy:

Core Belief: Own the customer relationship; highest margin, best customer insight
Method: Build internal sales team, control entire sales process
Economics: High margin, but high CAC per customer
Possible fit: Complex, high-stakes purchases that require assisted evaluation; validate the economics and buyer process.

Indirect Sales (Channel Partner) Philosophy:

Core Belief: Scale faster by leveraging partners' existing customer relationships
Method: Recruit resellers, VARs (Value-Added Resellers), system integrators
Economics: Lower margin because partners take a share, but lower CAC because partners invest in sales
Possible fit: Offers that partners can credibly sell or implement where reach, enablement, control, and margin sharing are acceptable.

The Trade-offs:

Table 14.12: Direct and indirect route trade-offs. The comparison is an author-created decision aid; performance depends on segment, capacity, economics, governance, and customer ownership.

Dimension	Direct Sales	Indirect Sales
Margin	High	Lower because partners take a share
CAC	Often higher because the seller bears the sales motion; measure it	May be lower for the vendor but must include enablement, incentives, and channel support
Control	High (you train, manage reps)	Low (partners do what they want)
Scale Speed	Slow (hiring, ramping reps)	Fast (partners already have customers)
Customer Insight	High (direct relationship)	Low (partner is intermediary)

When Direct Sales Wins:

High-value, complex products: Assisted sales may be justified when contribution margin, retention, implementation, sales-cycle length, and risk support the acquisition cost.
Product differentiation: You need to explain unique value (partners won't learn complex pitch)
Early stage: Before PMF, founders need direct customer feedback (can't outsource learning)
Enterprise: Large deals require C-suite relationships (partners don't have this access)

When Indirect Sales Wins:

Commodity/known products: "We sell CRM" doesn't need complex explanation; partners can sell
Geographic scale: Expanding to 50 countries; partners provide local presence cheaply
Lower-value deals: Direct sales may be uneconomic when acquisition and service costs exceed risk-adjusted contribution; partner cost is not automatically lower and must be measured.
Existing relationships: Partners already sell to your ICP (instant distribution)

The Hybrid Mistake: Many companies try both simultaneously. Result: Channel conflict (partners and internal reps compete for same customers), confusion (who owns the customer?), margin erosion (partners demand bigger cut to compensate for competition). Choose one, execute excellently, then (maybe) add the other with clear rules.

The Synthesis: Direct, indirect, and hybrid routes can each be appropriate. A direct motion may improve early customer learning in some contexts; a partner route may add reach or capability in others. Choose from observed buying behavior, incremental economics, service capacity, governance, customer ownership, and reversibility, then test the selected route rather than treating stage or product-market-fit labels as universal sequencing rules.

2. Product-Mediated, Earned, and Paid Acquisition

Acquisition mechanisms are hypotheses about how exposure, adoption, and retention occur. Weinberg's Bullseye method treats acquisition-channel choice as testable: brainstorm across possible channels, rank candidates, run small tests, focus on evidence, and repeat when the current channel plateaus. ^[5] The taxonomy below and the cautions that “organic” is not free, “viral” is not automatic, and paid growth is not inherently predictable are author synthesis. Diffusion dynamics provide context, not a company-specific forecast.

Table 14.13: Author-created acquisition-mechanism questions. Use the table to define evidence and guardrails; it is not a taxonomy or performance ranking.

Dimension	Questions to test
Causal incrementality	Which conversions would not have occurred without the mechanism? Use holdouts or credible counterfactuals where feasible.
Retention and customer quality	Do acquired cohorts retain, expand, support, and refer at economically meaningful rates?
Cost	Include creative, product, incentive, agency, sales, tooling, discount, fraud, support, and opportunity costs—not media spend alone.
Saturation and dependence	How do marginal response, auction prices, platform rules, network density, and channel concentration change with scale?
Consent and brand	Are referral, tracking, targeting, and messaging lawful, accessible, non-deceptive, and consistent with customer expectations?
Cash and reversibility	What working capital, commitment, learning speed, and downside exposure does the mechanism create?

Run channel tests with pre-specified primary and guardrail measures, segment and cohort reporting, attribution limits, and stop/scale rules. A product-mediated loop may work for one use case and fail in another; paid acquisition may add incremental demand, cannibalize existing demand, or attract lower-retention cohorts. Do not rank a channel until the evidence and full economics support the decision. ^[5]

3. Horizontal and Vertical GTM as Design Choices

“Horizontal” and “vertical” are positioning and operating choices, not fixed performance laws. A horizontal design can address a broadly shared job but may face generic positioning, integration breadth, and varied workflows. A vertical design can encode segment-specific workflow, language, regulation, and channel knowledge but may face concentration, bespoke service, or expansion limits.

Compare observed segment value, workflow commonality, compliance, channel access, service capacity, contribution economics, concentration risk, and transferability. Expansion from one vertical, use case, or geography is one option; starting horizontal, remaining focused, partnering, or not entering can also be rational. The prior named-company and categorical win-rate, moat, speed, and value claims were removed because no adjacent source established them.

Stage-Dependent GTM Tailoring

Stage labels can organize questions, but ARR, customer count, channel count, staffing, CAC/LTV, and cadence do not define universal maturity gates. Assess the venture's evidence, product, buying process, service model, regulation, cash, capacity, and strategic options directly.

Earlier evidence stage

Define a bounded segment, buying unit, job, alternatives, proof, and customer-harm guardrails.
Compare a small set of channels only to the degree needed to learn; simultaneous tests can be appropriate when attribution, capacity, and cash permit them.
Founder contact can improve learning, but founders need not perform every sale or delay all specialist hiring.
Estimate economics as ranges with explicit missing data; no ratio or customer count proves product-market fit.

Repeatability and expansion stage

Test whether acquisition, onboarding, retained value, service quality, and contribution transfer across comparable cohorts.
Add channels, segments, and staff when evidence, capacity, governance, and cash justify the added complexity.
Document decision-relevant processes without assuming one playbook, revenue band, or founder/recruit transition defines readiness.
Treat brand, profitability, risk controls, and customer success as context-dependent—not concerns that automatically wait for a later stage.

Portfolio stage

Different segments may require different assisted, self-service, partner, service, pricing, and contract designs.
Portfolio complexity requires stable definitions, capacity, channel-conflict rules, customer-outcome controls, and segment-level contribution and cash evidence.
Forecast accuracy is one planning diagnostic, not proof of a mature GTM system.
Continue, adapt, pause, or retire motions from evidence; scale is not an automatic progression.

Key takeaway: Match GTM design to the decision and evidence rather than to a rigid startup ladder. A single segment/channel can improve focus in some contexts; multiple motions can improve learning or coverage in others.

Case Example: B2B SaaS Launch

Constructed case: DataFlow is fictional. Every company attribute, partner, price, funnel value, result, and causal interpretation below is illustrative and must not be attributed to a real company or treated as a benchmark.

Company: DataFlow (fictional data-pipeline software venture)

Application:

GTM Canvas:
- Target: SMB data teams ($5M-50M revenue)
- Problem: 3-week data pipeline setup
- Value prop: Deploy in 3 days, $500K/year savings
- Channel: Direct sales + partnerships
- Pricing: $50K/year subscription
- Unit economics hypothesis: $5K CAC and $250K five-year revenue proxy produce a 50:1 revenue-proxy/CAC ratio, not LTV:CAC. A decision-grade LTV requires retention, gross-margin contribution, service cost, discounting, and cohort uncertainty.
ICP: Mid-market SaaS companies with 10+ engineers, $500K annual IT budget
Sales Funnel: Target 300 leads → 180 meetings → 72 proposals → 36 closes (20 percent conversion)
Channel Strategy: 70 percent direct sales (high-touch), 30 percent partnerships (with data infrastructure vendors)
Pricing: $50K/year ($5K/month minimum), plus usage overage for high-volume companies
Launch Plan:
- Week 1: Test two integration or distribution partnerships
- Week 2: Launch product + press + email to 500 target customers
- Week 3-4: Sales team outreach to top 100 ICP companies
- Month 2: Referral program (existing customer = $10K credit for referral)
Growth experimentation: Product-led trial and integration hypotheses with causal, retention, service, and customer-harm guardrails
Partnerships: Model three hypothetical integration partners and test their access, incentives, control, support burden, and incremental contribution

Constructed scenario results:

Launch month: 50 signups (15 percent from press, 60 percent from partnerships, 25 percent from direct)
Month 3: 20 closed customers ($1M ARR annualized)
Growth: 25 percent MoM on track to $3M ARR by end of year

Interpretation: The figures demonstrate internal consistency checks; they do not establish that focus or execution caused the result. A real evaluation would compare cohorts or use a credible counterfactual and would examine retention, contribution, cash, capacity, and harm.

Operating Manual: Your 10-Week GTM Launch

This operating manual translates the GTM Strategy frameworks into a week-by-week execution plan. Use this when you have a product ready to launch and need a structured approach to acquire your first 20-50 customers through validated channels, positioning, and pricing.

Constructed operating-template boundary: The ten-week cadence, hours, counts, budgets, ratios, conversion targets, prices, and decision triggers below are worked assumptions, not evidence-based benchmarks. Adapt or reject them through the responsible owner, qualified legal/finance/privacy review, customer risk, measurement design, capacity, cash, and the actual approval path. Passing a numeric gate does not validate demand, product-market fit, causality, or legal readiness.

Timeline Overview: 10 weeks from GTM canvas workshop to first revenue and optimization

Prerequisites:

Product is built (MVP or beyond)
You have validated problem-solution fit with at least 10 customer interviews
Founding team can dedicate 50-60 hours/week to GTM execution

Outcome Targets:

Week 10: 10-20 paying customers acquired
Validated ICP profile (scored, documented)
Proven acquisition channel with known unit economics
Pricing model validated through actual sales
Documented sales playbook for replication

Operating-template Phase 1: GTM Strategy Development (Weeks 1-2)

Week 1: GTM Canvas & Competitive Positioning

Day 1-2: GTM Canvas Workshop (16 hours total)

Monday Morning (4h): Assemble founding team + any advisors
- Complete GTM Strategy Canvas (Framework #1):
  - TARGET: Define specific customer segment (industry, size, geography, growth stage)
  - PROBLEM: Quantify the painful problem (hours lost, revenue impact, cost burden)
  - VALUE PROP: Draft 1-sentence differentiation vs. alternatives
  - CHANNEL: Identify 2-3 potential acquisition channels
  - PRICING: Ballpark pricing model and price point
  - ECONOMICS: Estimate CAC and LTV based on channel/pricing assumptions
  - GROWTH: Set Year 1 targets (revenue, customer count)
- Output: Draft GTM Canvas (1 page document)
Monday Afternoon (4h): Pressure-test each component
- TARGET: Can you list 100 companies that fit this profile?
- PROBLEM: Have you interviewed 10+ customers who confirm this is top-3 problem?
- VALUE PROP: Can customer understand benefit in one sentence?
- CHANNEL: Do you have access to this channel (network, budget, expertise)?
- PRICING: Does the defined pricing and contribution scenario meet the locally approved threshold?
- Output: Revised GTM Canvas with confidence scores (1-10) for each component
Tuesday Morning (4h): Competitive analysis
- Identify top 3 alternatives (competitors, DIY solutions, "do nothing")
- For each alternative, document:
  - Pricing model and price point
  - Target customer (who uses them?)
  - Strengths (what do they do well?)
  - Weaknesses (where do they fail customers?)
  - GTM approach (how do they acquire customers?)
- Output: Competitive matrix (you vs. 3 alternatives)
Tuesday Afternoon (4h): Positioning workshop
- Draft positioning statement: "For [TARGET], who [PROBLEM], our product [SOLUTION], unlike [ALTERNATIVE]"
- Refine value proposition with quantified benefits
- Identify 3 key differentiators (vs. each alternative)
- Test messaging clarity: Can someone outside your team understand it?
- Output: Positioning statement + messaging framework (1 page)

Week 1 Outputs:

GTM Canvas with confidence scores
Competitive matrix (you vs. 3 alternatives)
Positioning statement and messaging framework
Target prospect list (100 companies matching ICP)

Week 2: Customer Validation & ICP Refinement

Day 1-2: Interview Preparation (8 hours)

Monday Morning (4h): Build target prospect list
- Identify 50 companies matching your TARGET profile
- Prioritize by fit score (firmographic, behavioral, psychographic alignment)
- Research each company: pain signals, recent news, tech stack, decision makers
- Output: Prioritized prospect list (50 companies with research notes)
Monday Afternoon (4h): Create interview materials
- Draft interview script (15-20 minute conversation):
  - "Tell me about [problem we think they have]" (validate problem urgency)
  - "How do you solve this today?" (understand alternatives + switching cost)
  - "What would make a solution worth paying for?" (validate value prop)
  - "How do you evaluate and buy tools like this?" (validate channel fit)
  - "What would you expect pricing to be?" (validate pricing assumptions)
- Prepare tracking spreadsheet:
  - Columns: Prospect name, company, role, problem confirmed (Y/N/Partial), current solution, interest level (High/Med/Low), pricing feedback, ICP fit score (1-10)
- Output: Interview script + tracking spreadsheet

Day 3-5: Customer Interviews (20+ hours, 4 interviews per day)

Tuesday-Thursday (6-7h per day): Execute 20 customer interviews
- Outreach: Personalized emails/LinkedIn messages ("Can I get 20 minutes of feedback on [problem area]?")
- Schedule: 4 interviews per day (15-20 min each + 10 min for notes)
- During interview: Follow script, probe for specifics, avoid pitching product
- After interview: Score ICP fit (1-10), note key quotes, identify patterns
- Output: 20 completed interviews with detailed notes

Week 2 Outputs:

20 customer interviews completed
Interview synthesis: % who confirmed urgent problem, common objections, pricing range
ICP refinement: Patterns in "high interest" vs "low interest" prospects
Updated GTM Canvas based on validation learnings

Decision review #1 (End of Week 2): Problem and evidence review

Illustrative review prompts (not universal GO criteria):

A locally defined share of the interviewed or otherwise eligible population supports urgency under a documented coding rule; the percentage shown in the earlier draft was illustrative, not a universal threshold.
A locally defined share expresses interest under a documented sampling and interpretation rule; stated interest is not purchase or causal evidence.
Pricing feedback is consistent with the defined value, contribution, cash, fairness, and service-cost scenario; willingness to pay remains a hypothesis.
Clear pattern emerges in ICP (you can describe "who succeeds best")

Possible review or stop signals (define locally):

If the local urgency evidence rule is not met → Revisit the PROBLEM definition in the GTM Canvas.
If the local interest evidence rule is not met → Revisit the VALUE PROP; stated interest alone is not demand evidence.
Pricing feedback too low → Rethink pricing model or target different ICP
No clear ICP pattern → Target too broad; need to narrow

Contingency if the local evidence rule is not met: Pause the launch, revise the ICP or value proposition, and set the next evidence review from the decision's risk and access constraints.

Proceed only with accountable approval: Move to Phase 2 (ICP Deep Dive & Positioning) when the locally defined evidence, customer-outcome, capacity, cash, and legal controls are adequate.

Operating-template Phase 2: ICP Deep Dive & Positioning (Weeks 3-4)

Week 3: ICP Segmentation & Target Account List

Day 1-2: ICP Profile Development (16 hours)

Monday Morning (4h): Analyze interview patterns
- Review all 20 interviews and identify characteristics of "high interest" prospects:
  - Firmographic: Industry, company size, revenue, geography, growth stage
  - Behavioral: Tech stack, process maturity, pain urgency, buying cycle
  - Psychographic: Growth mindset, technology affinity, decision style
- Calculate correlation: Which characteristics predict high interest?
- Output: ICP dimensions with weights (which matter most?)
Monday Afternoon (4h): Create ICP scoring framework
- Define 8-10 ICP criteria with point values (e.g., "Series A-C funded" = 2 points, "Uses Salesforce" = 1 point)
- Score all 20 interviewed companies using framework
- Validate: Do high-scoring companies match "high interest" prospects? (If not, revise criteria)
- Output: ICP scoring framework (8-10 criteria, point system)
Tuesday Morning (4h): Build target account list
- Use LinkedIn Sales Navigator, Crunchbase, or industry databases
- Identify 200 companies matching ICP criteria
- Score each company using ICP framework
- Segment into tiers: Tier 1 (ICP score 8-10, top 50 companies), Tier 2 (score 6-7, next 100), Tier 3 (score 4-5, remaining 50)
- Output: Target account list (200 companies, scored and tiered)
Tuesday Afternoon (4h): Anti-ICP definition
- Identify characteristics of "low interest" prospects from interviews
- Define Anti-ICP: Who to avoid? (e.g., "Nonprofits with <$1M budget, need heavy customization")
- Document why: Low price potential, high support cost, poor retention risk
- Output: Anti-ICP profile (who to disqualify)

Day 3-5: Segmentation Analysis (16 hours)

Wednesday Morning (4h): Identify potential customer segments
- Review ICP data: Do multiple distinct segments emerge? (e.g., "Early-stage SaaS" vs "Growth-stage SaaS")
- For each potential segment (2-4 segments max):
  - Size: How many companies fit this profile?
  - Avg deal size: Based on pricing feedback
  - Win rate estimate: Based on interview interest levels
  - CAC estimate: Based on channel requirements
  - LTV estimate: Pricing × estimated retention
- Output: Segmentation analysis (2-4 segments with economics)
Wednesday Afternoon (4h): Select primary segment
- Compare segments on: Market size, win rate, LTV:CAC ratio, sales cycle
- Pick primary segment: Best economics + best product fit + fastest time to revenue
- Document rationale: Why this segment first?
- Identify expansion path: Which segment next? (After primary is proven)
- Output: Primary segment selection with expansion roadmap
Thursday-Friday (8h): Tier 1 account deep research
- For top 50 Tier 1 accounts:
  - Identify decision maker (name, title, LinkedIn profile)
  - Research pain signals (recent hiring, funding, tech stack changes)
  - Find connection path (mutual contacts, investors, advisors)
  - Draft personalized outreach angle (specific to their situation)
- Output: Tier 1 account research dossier (50 companies with personalized notes)

Week 3 Outputs:

ICP profile (1 page) with scoring framework
Target account list (200 companies, scored and tiered)
Anti-ICP profile (disqualification criteria)
Segmentation analysis with primary segment selected
Tier 1 account research dossier (50 companies)

Week 4: Messaging & Positioning Validation

Day 1-2: Messaging Framework Development (16 hours)

Monday Morning (4h): Homepage messaging
- Headline (7 words or less): Core benefit in plain language
- Subheadline (1 sentence): Value proposition with quantified outcome
- 3 key benefits: Specific outcomes customer achieves (with numbers if possible)
- Social proof: Customer testimonials or case example snippets (if available from interviews)
- Call-to-action: What do you want prospect to do? (Book demo, start trial, etc.)
- Output: Homepage messaging framework
Monday Afternoon (4h): Sales messaging
- Elevator pitch (30 seconds): Who you help, what problem you solve, unique approach
- Discovery questions: 5-7 questions to qualify prospect and uncover pain
- Value prop by persona: How benefit differs for CEO vs VP vs Manager
- ROI calculator: Simple model to quantify customer savings/gains
- Output: Sales messaging toolkit
Tuesday Morning (4h): Objection handling framework
- Review interview feedback: What concerns/objections came up repeatedly?
- For each objection, draft response:
  - Acknowledge: "I understand the concern about [X]"
  - Reframe: "Here's how we think about that..."
  - Proof: Customer testimonial, data, or case example
- Common objections: Price too high, switching cost, competitor comparison, "not urgent"
- Output: Objection handling guide (5-8 common objections with responses)
Tuesday Afternoon (4h): Competitive positioning
- For each top alternative (competitor, DIY, do nothing):
  - Draft "Unlike [alternative], we [specific benefit]" statement
  - Quantify difference: "3 days vs 3 weeks," "$500K savings vs $100K"
  - Prepare comparison matrix: Feature-by-feature or outcome-by-outcome
- Output: Competitive positioning statements + comparison matrices

Day 3-5: Messaging Validation (16 hours)

Wednesday-Thursday (12h): Validation interviews
- Reach out to 5-10 interviewed customers (high interest prospects)
- Share positioning/messaging: "Does this resonate? Is it clear? Compelling?"
- Test headline, value prop, key benefits, pricing messaging
- A/B test variants: Try 2 different headlines or value props, see which resonates more
- Iterate based on feedback: Clarity issues? Jargon? Missing key benefit?
- Output: Validated messaging framework (iterated based on feedback)
Friday (4h): Create messaging assets
- 1-pager: Overview of product, problem, solution, benefits, pricing (sales leave-behind)
- Email templates: Outreach, follow-up, demo invite (personalized but repeatable)
- Pitch deck (5 slides): Problem, solution, differentiation, pricing, case example/testimonial
- Output: Core messaging assets ready for launch

Week 4 Outputs:

Homepage messaging framework (headline, subheadline, benefits, CTA)
Sales messaging toolkit (pitch, discovery questions, ROI calculator)
Objection handling guide (5-8 objections with responses)
Competitive positioning statements
Messaging assets (1-pager, email templates, pitch deck)

Decision review #2 (End of Week 4): Messaging resonance

Illustrative review prompts (not universal GO criteria):

A locally defined share of validation participants says messaging is clear and compelling under a documented sampling and coding rule; the percentage is illustrative, not a universal threshold.
Value proposition resonates (prospects immediately understand benefit)
Competitive positioning is defensible (you can articulate unique value vs alternatives)
Messaging assets are ready (1-pager, email templates, pitch deck)

Possible review or stop signals (define locally):

Messaging confusing or generic → Iterate on clarity, specificity
Value prop doesn't resonate → Revisit customer pain points, quantify benefits more clearly
Can't differentiate from alternatives → Identify unique angle or narrow ICP further

Contingency if the local evidence rule is not met: Iterate the message with additional customer feedback and reset the launch timing from the evidence and operating constraints.

Proceed only with accountable approval: Move to Phase 3 (Channel & Pricing Strategy) when the locally defined evidence and controls are adequate.

Operating-template Phase 3: Channel Selection & Pricing (Weeks 5-6)

Week 5: Channel Strategy & Economics

Day 1-2: Channel Evaluation (16 hours)

Monday Morning (4h): Evaluate potential channels
- Based on ICP and interviews, assess 3-5 channels:
  - Direct sales: # reps needed, cost per rep, ramp time, CAC estimate
  - Inside sales: # SDRs + AEs, cost, productivity per rep, CAC estimate
  - Self-serve: Website build cost, ad spend, conversion rate estimate, CAC estimate
  - Partnerships: Identify 10 potential partners (fit, reach, revenue share)
  - Content marketing: Content team cost, SEO timeline, organic lead volume estimate
- For each channel, model:
  - Upfront investment (time + money for first 90 days)
  - CAC estimate (based on industry reference points or similar companies)
  - Timeline to first customer
  - Scalability potential (can this get to 100 customers? 1,000?)
- Output: Channel evaluation matrix (3-5 channels with economics)
Monday Afternoon (4h): Interview insights on buying behavior
- Review customer interviews: "How do you typically evaluate and buy tools like this?"
- Patterns to identify:
  - Self-serve indicators: "We just try it, if it works we buy"
  - Inside sales indicators: "We need a demo and ROI analysis"
  - Direct sales indicators: "Multiple stakeholders, formal evaluation process"
- Match buying behavior to channel type
- Output: Buying behavior analysis (which channel fits customer expectations?)
Tuesday Morning (4h): Channel economics modeling
- Build spreadsheet model for top 2 channels:
  - Inputs: Channel investment, expected conversion rates, deal size, sales cycle
  - Outputs: CAC, number of customers in 90 days, payback period
- Compare channels on: CAC, speed to revenue, LTV:CAC ratio
- Sensitivity analysis: What if conversion rate is 50 percent worse? CAC doubles?
- Output: Channel economics model (comparing top 2 channels)
Tuesday Afternoon (4h): Select primary channel(s)
- Criteria: Best LTV:CAC ratio + fastest time to revenue + team capability
- Pick 1-2 primary channels (not 5 - focus is critical)
- Document rationale: Why this channel? What are the risks?
- Create 90-day channel plan:
  - Month 1: Activities, budget, expected leads/customers
  - Month 2: Scale plan (if Month 1 works)
  - Month 3: Optimization (improve conversion, reduce CAC)
- Output: Primary channel selection + 90-day plan

Day 3-5: Partnership Development (if relevant) (16 hours)

Wednesday Morning (4h): Identify target partners (if partnerships is a channel)
- Criteria: Access to your ICP, complementary product, no direct competition
- Evaluate 10 potential partners:
  - Customer overlap: Do they sell to your ICP?
  - Reach: How many customers do they have?
  - Engagement: Active community, events, content?
  - Feasibility: Will they partner with early-stage startup?
- Prioritize top 5 partners
- Output: Target partner list (5 partners with fit scores)
Wednesday Afternoon-Friday (12h): Partnership outreach & proposals
- Draft partnership proposal (1-pager):
  - Value to partner: How does partnering benefit them? (revenue share, customer value, co-marketing)
  - Economics: Revenue split, referral fees, co-marketing investment
  - Timeline: Pilot period (90 days), success metrics, expansion plan
- Outreach to top 5 partners: Email + LinkedIn + mutual intro (if available)
- Goal: Book exploratory calls with 3-5 partners
- Initial conversations: Validate interest, discuss terms, explore pilot
- Output: 3-5 partnership exploratory calls booked + draft agreements

Week 5 Outputs:

Channel evaluation matrix (3-5 channels assessed)
Channel economics model (top 2 channels compared)
Primary channel selection + 90-day plan
Partnership target list (if relevant) + outreach initiated

Week 6: Pricing Model & Unit Economics

Day 1-2: Pricing Model Selection (16 hours)

Monday Morning (4h): Review pricing feedback
- Analyze interview data: What did customers say about pricing?
- Acceptable range: $X to $Y (based on "what would you expect to pay?")
- Pricing model preferences: Did they mention per-user, per-transaction, flat fee?
- Budget constraints: What's typical budget for this type of tool?
- Output: Pricing feedback synthesis
Monday Afternoon (4h): Evaluate pricing models (Framework #5)
- Consider 3-4 pricing models:
  - Per-user/seat: $X per user per month (e.g., $99/user/month)
  - Tiered: Basic ($X), Pro ($Y), Enterprise ($Z) with feature differentiation
  - Value-based: % of savings or revenue generated (e.g., 20 percent of $500K savings = $100K/year)
  - Usage-based: Pay per API call, transaction, GB processed, etc.
  - Hybrid: Base fee + usage overage (e.g., $99/month + $0.10 per API call above 10K)
- For each model, assess:
  - Customer preference: Does this match how they think about value?
  - Revenue predictability: Can you forecast monthly/annual revenue?
  - Sales complexity: Easy to explain and sell?
- Output: Pricing model comparison (3-4 models evaluated)
Tuesday Morning (4h): Unit economics modeling
- Build detailed spreadsheet model:
  - Inputs: Pricing, CAC (by channel), monthly churn rate, gross margin, sales cycle length
  - Outputs: Monthly recurring revenue (MRR), annual recurring revenue (ARR), LTV, CAC, LTV:CAC ratio, payback period, break-even timeline
- Model 3 scenarios:
  - Base case: Realistic assumptions based on interviews and reference points
  - Optimistic: 20 percent better on pricing, conversion, retention
  - Pessimistic: 20 percent worse on all metrics
- Validate: Does the base-case contribution and payback scenario meet the locally approved threshold, with uncertainty and cash timing stated?
- Output: Unit economics model (3 scenarios)
Tuesday Afternoon (4h): Price point selection
- Based on model, select initial pricing:
  - If per-user: $X/user/month
  - If tiered: Define 3 tiers with feature breakdown
  - If value-based: % of customer savings/revenue + minimum fee
  - If usage-based: Price per unit + committed tiers
- Justify pricing: ROI for customer (they save/earn $Y, we charge $X)
- Plan for iteration: "We'll test this price, adjust after 10 customers if needed"
- Output: Pricing decision (model + price point)

Day 3-5: Pricing Page & Sales Toolkit (16 hours)

Wednesday Morning (4h): Create pricing page
- For each tier/plan:
  - Plan name (Basic, Pro, Enterprise)
  - Price point ($99/month, $299/month, Custom)
  - Key features included (3-5 most important)
  - CTA (Start trial, Book demo, Contact sales)
- Add: FAQ section (common pricing questions)
- Add: ROI calculator or savings estimate
- Output: Pricing page copy (ready for website)
Wednesday Afternoon (4h): Sales pricing toolkit
- Pricing justification: How to explain pricing in sales conversation
- Discount policy: When can reps discount? (e.g., annual commitment = 10 percent off, never more than 20 percent discount)
- Negotiation guidelines: How to handle "it's too expensive" objection
- Contract terms: Month-to-month vs annual, payment terms, cancellation policy
- Output: Sales pricing guide
Thursday-Friday (8h): Pricing validation
- Share pricing with 5 high-interest prospects from interviews
- Ask: "Does this pricing make sense? Is it in line with value?"
- Test objection handling: If they say "too expensive," test your response
- Iterate if needed: Adjust price point or packaging based on feedback
- Output: Validated pricing (adjusted based on feedback if necessary)

Week 6 Outputs:

Pricing model selected (per-user, tiered, value-based, usage, hybrid)
Unit economics model (3 scenarios: base, optimistic, pessimistic)
Pricing decision (specific price points and tiers)
Pricing page copy (ready for website)
Sales pricing guide (justification, discounts, objection handling)

Decision review #3 (End of Week 6): Unit-economics review

Illustrative review prompts (not universal GO criteria):

Base-case contribution and payback scenario meets the locally approved threshold, with margin, service cost, cash timing, and uncertainty stated.
Payback period is acceptable for the venture's liquidity, risk, customer, and operating context; no universal month threshold applies.
Pricing resonates with validation customers (no major objections)
Channel strategy yields a realistic path to the locally defined evidence and customer-outcome objective within the approved cash and capacity window.

Possible review or stop signals (define locally):

Contribution below the approved threshold → Revisit pricing, channel, service cost, retention, or the target segment.
Payback outside the approved liquidity window → Revisit pricing, cash terms, retention, channel, or exposure before scaling.
Pricing objections → Lower price OR better justify value (improve ROI articulation)

Contingency if the local evidence rule is not met: Revise pricing or channel strategy, re-model contribution and cash, and delay or reduce exposure until the responsible owner approves the economics.

Proceed only with accountable approval: Move to Phase 4 (Launch Preparation & Execution) when the local contribution, cash, capacity, customer-outcome, and governance rules are satisfied.

Operating-template Phase 4: Launch Preparation (Week 7-8)

Week 7: Marketing Assets & Sales Process

Day 1-2: Website/Landing Page (16 hours)

Monday-Tuesday (16h): Build launch landing page
- Core sections:
  - Hero: Headline, subheadline, CTA, hero image/screenshot
  - Problem: Describe customer pain (quantified)
  - Solution: How your product solves it (key features + benefits)
  - Differentiation: Why you vs alternatives (comparison or unique approach)
  - Social proof: Customer testimonials, logos, case examples (if available)
  - Pricing: Clear pricing table or "Contact sales" CTA
  - FAQ: 5-10 common questions answered
- Technical: Use Webflow, WordPress, Framer, or similar (no-code preferred for speed)
- Mobile-responsive, fast load time, clear CTAs
- Output: Live landing page (ready to drive traffic)

Day 3-5: Sales Assets & Process (16 hours)

Wednesday Morning (4h): Sales deck (5 slides)
- Slide 1: Problem (customer pain with data/quotes)
- Slide 2: Solution (your product, how it works)
- Slide 3: Differentiation (you vs alternatives)
- Slide 4: Pricing & ROI (tiers, ROI calculator, payback period)
- Slide 5: Social proof (testimonials, case examples, logos)
- Keep it visual, minimal text, clear narrative
- Output: Sales pitch deck (PDF + editable version)
Wednesday Afternoon (4h): Product demo preparation
- Recorded demo: 5-10 minute walkthrough of product (Loom or similar)
- Live demo script: Step-by-step flow for live calls
- Demo environment: Sandbox account with realistic data
- Demo customization: How to tailor demo to prospect's use case
- Output: Demo assets (recorded demo + live demo script)
Thursday Morning (4h): Sales process documentation
- Define sales stages:
  - Stage 1: Outreach (email, LinkedIn)
  - Stage 2: Discovery call (qualify, understand pain)
  - Stage 3: Demo (show solution, tailor to their use case)
  - Stage 4: Proposal (send pricing, ROI, terms)
  - Stage 5: Negotiation (handle objections, finalize terms)
  - Stage 6: Close (sign contract, onboard)
- For each stage:
  - Objective: What are you trying to achieve?
  - Duration: How long does this stage typically take?
  - Exit criteria: When do you move to next stage?
  - Disqualification: When do you disqualify prospect?
- Output: Sales process playbook (6 stages documented)
Thursday Afternoon-Friday (8h): CRM setup & email sequences
- Set up CRM: HubSpot, Pipedrive, or spreadsheet (track leads through funnel)
- Create email sequences:
  - Outreach sequence: Initial email + 2 follow-ups
  - Post-demo sequence: Thank you + proposal + follow-ups
  - Nurture sequence: For "not ready now" prospects
- Templates: Personalized but repeatable (merge fields for company, name, pain point)
- Output: CRM configured + email sequences ready

Week 7 Outputs:

Live landing page (hero, problem, solution, pricing, CTAs)
Sales pitch deck (5 slides)
Product demo assets (recorded demo + live script)
Sales process playbook (6 stages with objectives, duration, exit criteria)
CRM setup + email sequences

Week 8: Launch Coordination & Partnerships

Day 1-2: Launch Campaign Assets (16 hours)

Monday Morning (4h): Press & media outreach
- Identify 10-15 journalists/bloggers covering your industry
- Draft press release: Who, what, why now, customer benefit, quote from founder
- Personalized pitches: Why this journalist's audience cares
- Schedule outreach: 1 week before launch (embargoed), launch day (public)
- Output: Press list + press release + pitch emails
Monday Afternoon (4h): Social media launch plan
- Pre-write social posts for launch day:
  - LinkedIn: Founder post (personal story, why we built this, CTA)
  - Twitter: Product launch thread (problem, solution, features, pricing, link)
  - Company accounts: Coordinated announcement
- Prepare assets: Screenshots, GIFs, short demo video
- Identify amplifiers: Advisors, early customers, partners (ask them to share)
- Schedule posts: Coordinate timing (all go live at same time)
- Output: Social media launch plan + pre-written posts
Tuesday Morning (4h): Email launch sequence
- Segment email list:
  - Warm leads: Interviewed customers, high interest prospects
  - Waitlist: Anyone who signed up for early access
  - Network: Friends, family, advisors (ask for intros/shares)
- Create email sequence:
  - Pre-launch (1 week before): "We're launching soon, here's what to expect"
  - Launch day: "We're live! Here's how it works, special launch offer"
  - Post-launch (1 week after): "Early results, case example, last chance for launch offer"
- Output: Email launch sequence (3 emails, segmented lists)
Tuesday Afternoon (4h): Launch day operations plan
- Assign responsibilities:
  - Who monitors product stability? (error rates, performance)
  - Who handles customer support? (email, chat, social DMs)
  - Who manages social amplification? (retweets, reshares, engagement)
  - Who tracks metrics? (signups, demos booked, revenue)
- Set up monitoring:
  - Product analytics: Track signups, feature usage, errors
  - Marketing analytics: Track website traffic, email opens/clicks, social reach
  - Sales pipeline: Track demos booked, proposals sent, deals closed
- Contingency plan: What if servers crash? What if no one signs up?
- Output: Launch day operations plan (roles, monitoring, contingencies)

Day 3-5: Partnership Finalization & Target Outreach (16 hours)

Wednesday (8h): Finalize partnership agreements (if relevant)
- Negotiate terms with 1-2 partners:
  - Revenue share or referral fee
  - Co-marketing commitments (webinar, email to their list, blog post)
  - Integration or product collaboration
  - Success metrics (# referrals, revenue target)
- Use counsel-approved agreement or term-sheet templates; an LOI or MOU can create binding obligations and is not a substitute for legal review
- Coordinate launch timing: Partner announcements on launch day
- Output: 1-2 partnership agreements signed
Thursday-Friday (8h): Tier 1 target outreach preparation
- Review Tier 1 account list (top 50 companies)
- For each account:
  - Verify decision maker contact info (email, LinkedIn)
  - Draft personalized outreach email (reference their specific pain, recent news, mutual connection)
  - Plan outreach timing: Launch week
- Set outreach targets:
  - Week 8: 20 personalized emails sent
  - Week 9: 30 more emails + follow-ups
- Output: Tier 1 outreach plan (50 personalized emails drafted, send schedule)

Week 8 Outputs:

Press release + media outreach list (10-15 journalists)
Social media launch plan (posts pre-written, amplifiers identified)
Email launch sequence (3 emails for warm leads, waitlist, network)
Launch day operations plan (roles, monitoring, contingencies)
Partnership agreements signed (1-2 partners)
Tier 1 outreach plan (50 personalized emails ready)

Decision review #4 (End of Week 8): Launch readiness

Illustrative review prompts (not universal GO criteria):

Landing page is live and functional (loads fast, CTAs work)
Sales assets complete (deck, demo, email sequences)
Launch campaign ready (press, social, email pre-written)
Product is stable (QA tested, no critical bugs)
Team is aligned (everyone knows their launch day role)

Possible review or stop signals (define locally):

Landing page not ready → Delay launch 1 week, prioritize page completion
Critical product bugs → Fix bugs before launch (unstable product kills momentum)
Sales process unclear → Document process, test with mock sales calls

Contingency if the local evidence rule is not met: Delay or narrow the launch and use the available time to close critical evidence, product, service, or approval gaps.

Proceed only with accountable approval: Move to Phase 5 (Launch & Early Traction) when product, service, customer, evidence, capacity, and governance controls are ready.

Operating-template Phase 5: Launch & Optimization (Weeks 9-10)

Week 9: Launch Execution

Day 1-3: Launch Week (24 hours)

Monday (Pre-launch Day, 8h):
- Final QA: Test every feature as new customer (signup, onboarding, core workflow, payment)
- Send pre-launch email to waitlist: "We launch tomorrow, here's what to expect"
- Confirm partnerships: Partners ready to announce on launch day
- Brief team: Final check on roles, responsibilities, communication plan
- Output: Everything ready for launch day
Tuesday (Launch Day, 12h):
- 9am: Launch announcement goes live
  - Publish landing page (if not already live)
  - Send launch email to warm leads, waitlist, network
  - Post social announcements (LinkedIn, Twitter, company accounts)
  - Reach out to press (send press release, personalized pitches)
  - Partner announcements (coordinated timing)
- 9am-6pm: Monitor and respond
  - Track signups against the locally defined qualified-reach and learning objective for launch day.
  - Respond to inquiries in real-time (<1 hour response time)
  - Engage on social (reply to comments, reshare mentions)
  - Monitor product stability (check error logs, performance)
- 6pm-9pm: Celebrate and debrief
  - Share launch day metrics with team (signups, traffic, social reach)
  - Identify what worked, what didn't
  - Plan Day 2 activities (follow-ups, momentum maintenance)
- Output: Launch executed, metrics tracked, team debriefed
Wednesday (Post-launch Day 1, 4h):
- Follow up with launch day signups: Welcome email, onboarding support
- Send thank you notes to amplifiers (partners, advisors who shared)
- Publish "launch recap" post: Metrics, wins, learnings (builds momentum)
- Continue Tier 1 outreach: 10 personalized emails to target accounts
- Output: Launch momentum maintained

Day 4-5: Early Customer Engagement (16 hours)

Thursday-Friday (16h): Convert interest to demos
- Reach out to all signups: Book discovery calls or demos
- Prioritize high-fit prospects (Tier 1 accounts, high ICP scores)
- Conduct 5-10 discovery calls/demos:
  - Discovery: Qualify prospect, understand pain, assess fit
  - Demo: Show product, tailor to their use case, handle objections
  - Next steps: Send proposal or offer trial
- Track conversion: Signup → Demo → Proposal → Close
- Output: 5-10 demos completed, proposals sent

Week 9 Outputs:

Launch executed (press, social, email sent)
Launch day metrics (signups, traffic, social reach)
Qualified reach and signups measured against the locally defined launch objective.
5-10 demos completed
Proposals sent to high-fit prospects

Week 10: Optimization & Early Revenue

Day 1-2: Close First Customers (16 hours)

Monday-Tuesday (16h): Sales follow-up & closing
- Follow up on proposals sent in Week 9:
  - Answer questions, handle objections
  - Negotiate terms (within discount policy limits)
  - Send contract, process payment
  - Onboard customers (setup, training, success plan)
- Goal: Close a locally defined amount of paid evidence by the end of Week 10
- Track: Close rate (proposals → closed customers)
- Output: Paid evidence recorded against the locally defined customer and quality objective.

Day 3-4: Metrics Analysis & Funnel Optimization (16 hours)

Wednesday Morning (4h): Measure funnel conversion rates
- Calculate conversion at each stage (Framework #3):
  - Awareness: How many leads generated? (launch signups + outreach responses)
  - Consideration: % who booked demo
  - Proposal: % of demos that led to proposal
  - Close: % of proposals that closed
- Identify bottlenecks: Where are prospects dropping off?
- Output: Funnel metrics dashboard
Wednesday Afternoon (4h): Calculate unit economics (actual)
- Actual CAC: Launch spend (ads, tools, time) / customers acquired
- Early value scenario: Do not call pricing × estimated retention actual LTV; report the contribution basis, retention evidence, service cost, cohort, uncertainty, and cash timing.
- Compare to model: Actual vs projected CAC and LTV
- Identify variance: Why is actual different from model?
- Output: Actual unit economics vs model
Thursday (8h): Customer feedback & iteration
- Interview first 5-10 customers:
  - What almost prevented you from buying?
  - What convinced you to buy?
  - What's missing in the product?
  - Would you refer us? Why or why not?
- Identify patterns: Common objections, feature requests, pricing feedback
- Prioritize 2-3 quick wins: Changes that would improve conversion or retention
- Output: Customer feedback synthesis + iteration priorities

Day 5: Playbook Documentation & Scale Planning (8 hours)

Friday Morning (4h): Document GTM playbook
- What worked:
  - Which channel drove most qualified leads?
  - Which messaging resonated best?
  - What objection handling worked?
- What didn't work:
  - Which channels underperformed?
  - Where did prospects drop off?
  - What objections couldn't we overcome?
- Repeatable process:
  - Step-by-step: How to acquire next customer using what worked
  - Templates: Email, pitch, demo script that converted
  - Metrics: Reference Points for "good" conversion at each stage
- Output: GTM playbook (1-2 page doc)
Friday Afternoon (4h): Plan Weeks 11-14 (next 30 days)
- Set Month 2 goals:
  - Revenue target: $X MRR or ARR
  - Customer target: Y new customers
  - Funnel target: Z demos, proposals
- Identify constraints:
  - Team capacity: Can founders handle sales volume?
  - Product readiness: Are there critical features needed?
  - Budget: Do we need more ad spend or tools?
- Plan next phase:
  - If working: Scale what's working (more of same channel, outreach)
  - If not working: Iterate (change messaging, try different channel, adjust pricing)
- Output: Month 2 plan (goals, activities, budget)

Week 10 Outputs:

Paid evidence recorded against the locally defined customer and quality objective.
Funnel metrics dashboard (conversion rates at each stage)
Actual unit economics (CAC, LTV, LTV:CAC ratio)
Customer feedback synthesis
GTM playbook documented
Month 2 scale plan

Decision review #5 (End of Week 10): GTM evidence and scale review

Illustrative review prompts (not universal GO criteria):

A locally defined amount and quality of paid evidence supports the next decision; customer count alone does not validate GTM.
Contribution and payback meet the locally approved threshold, or the owner documents a bounded, evidence-backed path with downside controls.
Repeatable process documented (playbook shows how to replicate success)
Positive customer feedback under a defined measure; a single 0–10 recommendation rating is not itself NPS

Possible review or stop signals (define locally):

Insufficient paid evidence → Extend or redesign the test; do not pursue a universal customer-count target.
Contribution below the approved threshold with no credible fix → Revisit pricing, channel, service cost, segment, or exposure.
No repeatable process → Continue experimenting, document what works
Negative customer feedback → Fix product issues before scaling (retention risk)

Contingency if the local evidence rule is not met:

If paid evidence is insufficient: Extend or redesign the test from the approved evidence and capacity plan.
If unit economics broken: Pause scaling, fix pricing or channel strategy
If churn is high: Fix product/onboarding before acquiring more customers

Proceed only with accountable approval: Increase exposure gradually only when the locally defined incremental-economics, capacity, retention, customer-outcome, and governance rules are satisfied.

Resource Requirements

Human Resources:

Founding Team (Weeks 1-10):

Founder/CEO: 50-60h/week (GTM strategy, customer interviews, partnerships, sales)
Co-founder/CTO (or technical lead): 20-30h/week (product stability, demo prep, analytics setup, tech integration)
Marketing/Sales (if exists): 40-50h/week (messaging, launch campaign, sales execution)
- If no dedicated marketing/sales, founder takes this on (60-70h/week total)

External Resources (Optional):

Freelance designer: 10-20h (landing page design, pitch deck design)
Copywriter: 5-10h (messaging polish, email copywriting)
Advisor/Mentor: 2-4h/month (GTM strategy review, objection handling coaching)

Financial Resources:

The following budget is a constructed worksheet, not a current price guide. Replace every amount with dated quotes, internal fully loaded costs, applicable taxes, compliance needs, and a contingency justified by the actual plan.

Weeks 1-2 (Strategy Development): $500-$1,500

Tools: LinkedIn Sales Navigator ($100/month), questionnaire tools ($50), misc research tools ($200-500)

Weeks 3-4 (ICP & Messaging): $500-$1,000

Tools: CRM setup ($100-200), design assets ($300-500), misc tools ($100-300)

Weeks 5-6 (Channel & Pricing): $1,000-$3,000

Freelance help: Designer for landing page ($500-1,500)
Tools: Website hosting ($20-50), email tool ($50-100)
Partnership development: Travel or meeting costs ($200-500)
Misc: $200-500

Weeks 7-8 (Launch Prep): $2,000-$5,000

Website/landing page: Build or template ($500-2,000)
Marketing tools: Email platform, analytics, CRM ($200-500)
Freelance: Copywriter, designer, video editor ($500-1,500)
Press outreach: PR service (optional, $500-1,000)
Misc: $300-1,000

Weeks 9-10 (Launch & Traction): $3,000-$10,000

Paid ads (if using): Google Ads, LinkedIn Ads ($1,000-5,000)
Partnership costs: Revenue share, co-marketing investment ($500-2,000)
Sales tools: Contracts, payment processing setup ($200-500)
Customer onboarding: Tools, support, misc ($300-1,000)
Misc/buffer: $1,000-1,500

Total Budget (10 Weeks): $7,000-$20,500

Constructed Scenario A: $7,000-10,000 (minimal paid ads, DIY landing page, no freelancers)
Constructed Scenario B: $12,000-15,000 (moderate paid ads, freelance help, selected tools)
Constructed Scenario C: $15,000-20,500 (higher paid-ad exposure, additional tools, PR support)

Red Flags & Warning Signals

Week 1-2 Red Flags:

Local urgency evidence rule is not met → Revisit the PROBLEM definition, sampling, coding, or ICP before scaling.
Customers can't articulate the problem clearly → You're solving a "nice to have," not urgent pain
Wide variance in ICP fit scores → Target is too broad; need to narrow to specific segment

Week 3-4 Red Flags:

Messaging doesn't resonate in validation → Value prop is unclear or not compelling; iterate on specificity and quantified benefits
Can't differentiate from alternatives → Competitive positioning is weak; find unique angle or narrow to underserved niche
ICP scoring doesn't predict interest → Scoring criteria are wrong; reassess which firmographic/behavioral traits matter

Week 5-6 Red Flags:

Contribution below the approved threshold in the base case → Revisit pricing, channel, service cost, retention, or exposure.
Payback outside the approved liquidity window → Revisit pricing, cash terms, retention, channel, or exposure before scaling.
Channel doesn't match customer buying behavior → Mismatch (e.g., self-serve for complex product); switch channel strategy

Week 7-8 Red Flags:

Landing page unclear or confusing → Messaging not distilled enough; simplify value prop and CTAs
Partnership negotiations stall → Partners see no value; reassess partnership value prop or find different partners
No clear sales process → Founders don't know how to sell; need to document discovery, demo, close steps

Week 9-10 Red Flags:

Launch reach below the locally defined evidence level → Diagnose awareness, distribution, consent, targeting, message, or product fit.
Demo booking below the locally defined evidence level → Diagnose qualification, customer expectations, accessibility, or message/product alignment.
High drop-off after demo → Product doesn't match expectations, or objections not handled; improve demo or product
Paid evidence below the locally defined decision level by the review date → Diagnose awareness, conversion, pricing, product, service, or access.
Early churn or harm above the locally defined guardrail → Pause or narrow acquisition, investigate causes, and remedy product or onboarding issues before scaling.

Contingency Triggers

Trigger 1: Problem-Market Fit Failure (Week 2)

Condition: The locally defined urgency evidence rule is not met.
Action: Pause the GTM launch, revise the ICP or problem statement, and set the next evidence review from risk, access, and capacity.
Timeline impact: Re-estimate from the evidence plan; no fixed extension is universal.

Trigger 2: Unit Economics Failure (Week 6)

Condition: Contribution or payback is below the approved threshold with no credible, bounded improvement path.
Action: Revise pricing, channel, service cost, retention, segment, or exposure; re-model economics before proceeding.
Timeline impact: Re-estimate from the remediation and measurement plan.

Trigger 3: Launch Failure (Week 9)

Condition: Launch reach or qualified engagement is below the locally defined evidence level.
Action: Diagnose awareness, consent, message, distribution, access, product, and service readiness before relaunching.
Timeline impact: Re-estimate from the revised launch plan.

Trigger 4: Conversion Failure (Week 10)

Condition: Paid evidence is insufficient for the defined decision despite qualified reach.
Action: Deep-dive on the conversion bottleneck, interview lost prospects, and fix objection handling, pricing, product, access, or service gaps before expanding.
Timeline impact: Re-estimate from the evidence and remediation plan.

Trigger 5: Early Churn Crisis (Week 10)

Condition: Early churn, non-retention, complaints, or harm exceeds the locally defined guardrail.
Action: Pause or narrow new acquisition, fix product/onboarding issues, interview affected customers, and resume only when the responsible owner approves the evidence and controls.
Timeline impact: Re-estimate from the remediation and validation plan.

Timeline Variance

Rapid Mode (6-8 Weeks):

Use when: Product-market fit is validated, clear ICP, experienced founder in GTM
Compress: Combine Weeks 1-2 (GTM Canvas + Interviews in 1 week), Weeks 3-4 (ICP + Messaging in 1 week), Weeks 7-8 (Launch prep in 1 week)
Risk: Less validation, higher chance of GTM missteps
Outcome: Launch in 6 weeks, first customers by Week 7-8

Standard Mode (10 Weeks):

Use when: First-time GTM launch, need validation, moderate urgency
Timeline: As described in this operating manual
Balance: Adequate validation with reasonable speed
Outcome: Launch in Week 9, first customers by Week 10

Thorough Mode (14-16 Weeks):

Use when: Complex product, enterprise sales, need deep customer validation
Expand: +1 week for customer interviews (40 instead of 20), +1 week for messaging validation, +2 weeks for partnership negotiation
Benefit: Higher confidence, better positioning, stronger partnerships
Outcome: Launch in Week 13-15, first customers by Week 14-16

Measurement Dashboard

Weekly Tracker (Weeks 1-10):

Table 14.14: Constructed ten-week operating-template tracker. Targets and thresholds are illustrative prompts; set them from the defined decision, cohort, risk, capacity, cash, and approval context.

Week	Key Metric	Target	Actual	Status
1	GTM Canvas confidence (1-10)	7+	___	___
2	Customer interviews completed	20	___	___
2	Share confirming urgent problem	Local evidence rule	___	___
3	ICP profile confidence (1-10)	8+	___	___
3	Target accounts identified	200	___	___
4	Messaging validation (% positive)	Local evidence rule	___	___
5	Primary channel selected	Yes	___	___
6	Contribution/payback scenario	Approved local threshold	___	___
7	Landing page live	Yes	___	___
8	Launch campaign ready	Yes	___	___
9	Launch day signups	20-50	___	___
9	Demos booked	5-10	___	___
10	Paying customers acquired	5-10	___	___
10	Actual CAC	Compare with approved scenario	___	___

End-of-Week-10 Milestone Metrics:

Customer Acquisition:

Paying customers: Report the locally defined quantity and quality of paid evidence; no universal customer-count gate applies.
Pipeline (qualified leads): 20-30
Conversion rate (signup → customer): measured against your modeled target

Unit Economics:

CAC (actual): Compare with the forecast, explain attribution and inclusion rules, and investigate material variance; no universal SMB or enterprise cutoff applies.
LTV:CAC (estimated): Report the formula, margin basis, cohort, confidence range, and sensitivity cases rather than applying a universal pass threshold.
Payback period: Compare with the approved liquidity and risk window; no universal month threshold applies.

GTM Validation:

Repeatable process documented: Yes (playbook exists)
Primary channel validated: CAC known, conversion rates measured
Messaging resonance: strong customer agreement that the value prop was clear and compelling
ICP accuracy: most customers match the ICP profile

Product-Market Fit Indicators:

Customer recommendation item: illustrative local range on a 0–10 scale; calculate NPS separately only with the approved instrument and full response distribution
Referral willingness: meaningful share say they would refer
Early retention: strong retained usage after 30 days

Success vs Struggling: How to Know

You're succeeding if (Week 10):

Paid evidence meets the locally defined quantity and quality requirement through a repeatable process.
Contribution and payback meet the locally approved threshold with sensitivity, service cost, cash timing, and customer outcomes stated.
Conversion rates above reference points:
- Signup → Demo: above modeled target
- Demo → Proposal: above modeled target
- Proposal → Close: above modeled target
Customer evidence: defined recommendation responses, referrals, retained use, complaints, outcomes, and feature requests; no single item rating proves that customers “love” the product
Clear winning channel: One channel drives most customers with known economics
Founders confident: "We know how to get next 10 customers"

Next steps (conditional success): Increase exposure gradually only after the channel's incremental economics, capacity, retention, customer outcomes, and operational risks hold under a pre-specified test. Set the next revenue milestone from the venture's cash plan rather than a generic MRR target.

You're struggling if (Week 10):

Paid evidence remains below the locally defined requirement despite outreach and launch efforts.
Contribution or payback remains below the approved threshold (economics require redesign before scaling).
Low conversion rates:
- Signup → Demo: below modeled target
- Demo → Close: below modeled target
High early churn: too many customers cancel within 30 days
No clear pattern: Can't identify what's working vs what's not
Founders unsure: "We don't know how to get the next customer"

Next steps (Struggling):

Diagnose bottleneck: Is it awareness (too few signups)? Conversion (signups don't convert)? Retention (customers churn)?
Customer interviews: Talk to lost prospects and churned customers to understand why
Iterate one variable: Fix messaging OR pricing OR channel (not all at once)
Extend timeline: Give yourself 4 more weeks to diagnose and fix
Consider pivot: If fundamentals are wrong (no urgent problem, bad economics), may need to revisit product or ICP

What matters.

Vocabulary

Related chapters

1. GTM Strategy Canvas

Overview

How to Apply

A. Target Customer (WHO)

B. Customer Problem (WHAT)

C. Unique Value Prop (WHY US)

D. Go-to-Market Channel (HOW)

E. Pricing Model (HOW MUCH)

F. Unit Economics (FINANCES)

G. Growth Assumption (TRAJECTORY)

So What for Managers

Limits and Critiques

Connections

2. Ideal Customer Profile (ICP) Framework

Overview

How to Apply

Firmographic (Company Characteristics)

Behavioral (How They Operate)

Psychographic (Values/Priorities)

So What for Managers

Limits and Critiques

Connections

3. Sales Funnel Metrics Dashboard

Overview

How to Apply

AWARENESS

CONSIDERATION

PROPOSAL

NEGOTIATION

POST-CLOSE

So What for Managers

Limits and Critiques

Connections

4. Channel Strategy Matrix

Overview

How to Apply

Step 1: Current evidence and constraints

Step 2: Economics Assessment

Step 3: Learning sequence

So What for Managers

Limits and Critiques

Connections

5. Pricing Model Comparison

Overview

How to Apply

Model 1: Per-Unit Pricing

Model 2: Value-Based Pricing

Model 3: Freemium

Model 4: Usage-Based / Consumption Pricing

So What for Managers

Limits and Critiques

Connections

6. Product Launch Checklist

Overview

How to Apply

Marketing & Communications (Week -4 to -1)

Sales & Partnership (Week -4 to -1)

Product & Operations (Week -4 to -2)

Launch Day (Day 0)

Post-Launch (Days 1-7)

So What for Managers

Limits and Critiques

Connections

7. Growth Experimentation Framework

Overview

How to Apply

Step 1: Identify Growth Levers

Step 2: Quantify the Lever

Step 3: Optimize the Top Lever

Step 4: Automate the Lever

Step 5: Invest in Winning Levers

So What for Managers

Limits and Critiques

Connections

8. Product-mediated diffusion measure

Overview

How to Apply