Startup Canvas
Apply the Startup Canvas framework to evaluate, structure, and iterate product strategies and business models. Explicitly divide corporate operational modeling from strategic product positioning, document business assumptions, map customer jobs-to-be-done, and verify defensibility moats.
When to Use
- Drafting initial startup plans — mapping vision, segments, value proposition, and trade-offs from scratch.
- Refactoring existing product strategies due to market shifts, new competitive entrants, or pricing model changes.
- Defining strategic trade-offs for product roadmaps — explicitly documenting what the team will not build.
- Evaluating competitive defensibility — running the "Can't/Won't" alignment loop against named competitors.
- Defining North Star Metrics — selecting outcome-based metrics that track value delivery, not vanity counts.
- Separating product strategy from business model costs — ensuring unit economics are mapped alongside strategic positioning.
Trigger keywords: startup canvas, product strategy, defensibility moat, north star metric, trade-offs, JTBD, jobs to be done, business model, value proposition, competitive moat, relative costs, growth loop.
Route elsewhere:
saas-mvp-launcher — to scaffold Next.js repositories.
startup-business-analyst-financial-projections — to model P&L spreadsheets and detailed financial projections.
Prerequisites
- Inputs required before starting: Product name, version, target segments, value propositions, non-goals, cost items, and pricing structures.
- User research: At least 15 target user interviews should be completed (or planned) to document primary JTBD before finalizing market segments.
- Competitor data: Top 3 competitors profiled for relative cost strategy construction.
- Framework contrast (BMC / Lean Canvas): BMC's nine boxes mix operating model for an ongoing firm. Lean Canvas is problem/solution/unfair-advantage for early teams but is light on relative-cost posture and mandatory non-goals. Startup Canvas splits product strategy from unit economics and requires explicit trade-offs plus Can't/Won't.
- Schema and YAML: use the JSON Schema excerpt and YAML Strategic Choice Configuration in Examples. If the team keeps a project-local schema file, validate against that file.
Procedure
Step 1 — Establish Vision
- State the long-term, aspirational purpose of the product team in one to two sentences.
- Confirm the founding team is aligned on this vision before proceeding.
- Record the vision in the canvas metadata (top-level
vision field).
Step 2 — Define Market Segments via JTBD
- Interview at least 15 target users to document their primary needs and problems.
- Define customer cohorts based on shared problems and Jobs-to-be-Done (JTBD) — not broad demographics.
- For each segment, record:
segmentName: A concise label.
jobsToBeDone: Array of job statements (e.g., "Secure customer logins quickly without custom coding").
Step 3 — Establish Relative Cost Posture
- Profile the top 3 competitors to understand their cost structures.
- Select one of two postures:
- Low-Cost: Optimizing for minimal operational cost, competing on price efficiency.
- Unique-Value: Delivering premium value that justifies higher costs.
- Record the posture in
relativeCosts as either "Low-Cost" or "Unique-Value".
Step 4 — Draft the Value Proposition
Map the customer transformation across three states:
- What Before: Describe the problematic customer state before the product exists.
- How: List the product features and mechanics that resolve this pain.
- What After: Describe the improved, successful customer state after using the product.
Graph your feature offerings against alternatives to map unique value (value curve analysis).
Step 5 — Declare Trade-offs (Non-Goals)
- Document at least 5 features or market segments the team will deliberately ignore.
- Each trade-off must be specific and actionable (e.g., "No custom on-premises deployments (Cloud only)").
- HARD RULE: Every Startup Canvas must contain at least 3 strategic trade-offs detailing what the team will not build or target. Fewer than 3 is a quality failure.
Step 6 — Define Key Metrics
- Select a North Star Metric (NSM) that directly tracks value delivery to the customer.
- HARD RULE: NSM must track outcomes, not operational inputs or vanity registration counts. Examples of valid NSMs: "Weekly Active Authentications (WAA)", "Successful automated query completions". Invalid: "Total registered users", "Page views".
- Select a One Metric That Matters (OMTM) for the current planning period.
- Record both in
keyMetrics.
Step 7 — Map the Growth Loop
- Map customer acquisition, referral, and retention channels.
- Identify the primary channel (e.g., organic SEO, product-led growth, partnerships).
- Outline backup channels in case the primary channel saturates.
Step 8 — Document Capabilities
- List internal capabilities needed to execute the strategy.
- Categorize each capability as Build, Buy, or Partner.
- Record in the
capabilities array.
Step 9 — Conduct the "Can't/Won't" Defense Test
- Identify the primary competitor(s) for the target segment.
- Run simulations showing how a legacy competitor would react to your positioning.
- Apply the Moat Strategy Selection decision rule:
- If competitor is a legacy incumbent: Focus the moat on "Won't" — leverage their innovator's dilemma. Show why offering your value proposition would conflict with their core revenue model (e.g., incumbent won't lower prices because it undercuts their legacy base).
- If competitor is a venture-backed startup: Focus the moat on "Can't" — leverage proprietary data loops, custom enterprise workflows, hardware integrations, or patents. Show why they lack the resources or positioning to replicate.
- HARD RULE — AI-Era Defensibility: Traditional technical execution is no longer a sustainable moat due to AI code generation reducing development costs to near zero. Focus the "Can't/Won't" defense on proprietary data loops, custom enterprise workflows, hardware integrations, or strategic misalignments with competitors' business models.
- HARD RULE — Weak Moat Warning: If the "Can't/Won't" analysis does not yield a clear competitive barrier, flag this as a critical business risk and suspend feature roadmap development until resolved.
Step 10 — Map Business Model (Financial Mechanics)
- Cost Structure: Detail fixed and variable expenses (e.g., hosting, API limits, salaries, CAC).
- Revenue Streams: Establish pricing tiers, billing models, and outline expansion revenue paths.
- Project the cost structure and revenue channels onto a spreadsheet.
- HARD RULE: Never build product strategies without mapping unit economics — this leads to negative margins at scale.
Step 11 — Identify Risky Hypotheses and Design Validations
- Highlight the top 3 assumptions that must be true for the business to survive.
- Design low-cost validations: landing page tests, clickable prototypes, or concierge MVPs to validate customer demand.
- Launch validations before committing to full build.
Step 12 — Output the Canvas
- Generate the final canvas as GFM Markdown containing Mermaid diagram assets.
- Ensure the output is optimized for direct integration into pitch decks and board presentations.
- Include the strategic feedback loop diagram:
graph TD
A[1. Vision] --> B[2. Market Segments]
B --> C[3. Relative Costs]
C --> D[4. Value Proposition]
D --> E[5. Trade-offs]
E --> F[6. Key Metrics]
F --> G[7. Growth Loop]
G --> H[8. Capabilities]
H --> I[9. Can't/Won't Defense]
- Optionally validate a project-local JSON config against the schema excerpt in Examples (or the team's own schema file).
Examples
YAML Strategic Choice Configuration
# startup_canvas_config.yaml
metadata:
product_name: "AuthSentinel"
revision: "v2.1"
owner: "product-strategy-team"
strategy:
vision: "To eliminate authentication friction and security leaks globally."
relative_cost_posture: "Unique-Value"
target_segments:
- name: "Early-stage SaaS Teams"
jtbd: "Secure customer logins quickly without custom coding."
trade_offs:
- "No custom on-premises deployments (Cloud only)"
- "No integration support for non-standard SAML databases"
- "No free tier — paid plans only to maintain unit economics"
key_metrics:
north_star_metric: "Weekly Active Authentications (WAA)"
omtm_q2: "Active integrations per tenant"
cant_wont:
competitors_cant: "Replicate our zero-knowledge validation latency."
competitors_wont: "Offer free basic tiers, as it undercuts their enterprise models."
JSON Configuration Schema (Excerpt)
Validate and store Startup Canvas configurations programmatically. Keep a project-local schema if automation needs a file; the excerpt below is the contract:
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"title": "StartupCanvas",
"type": "object",
"properties": {
"productName": { "type": "string" },
"version": { "type": "string" },
"lastUpdated": { "type": "string", "format": "date-time" },
"part1_productStrategy": {
"type": "object",
"properties": {
"vision": { "type": "string" },
"marketSegments": {
"type": "array",
"items": {
"type": "object",
"properties": {
"segmentName": { "type": "string" },
"jobsToBeDone": { "type": "array", "items": { "type": "string" } }
},
"required": ["segmentName", "jobsToBeDone"]
}
},
"relativeCosts": { "type": "string", "enum": ["Low-Cost", "Unique-Value"] },
"valueProposition": {
"type": "object",
"properties": {
"beforeState": { "type": "string" },
"solutionMechanisms": { "type": "array", "items": { "type": "string" } },
"afterState": { "type": "string" }
},
"required": ["beforeState", "solutionMechanisms", "afterState"]
},
"tradeOffs": { "type": "array", "items": { "type": "string" } },
"keyMetrics": {
"type": "object",
"properties": {
"northStarMetric": { "type": "string" },
"oneMetricThatMatters": { "type": "string" }
},
"required": ["northStarMetric", "oneMetricThatMatters"]
},
"growth": { "type": "string" },
"capabilities": { "type": "array", "items": { "type": "string" } },
"cantWontDefensibility": { "type": "string" }
},
"required": ["vision", "marketSegments", "relativeCosts", "valueProposition", "tradeOffs", "keyMetrics", "growth", "capabilities", "cantWontDefensibility"]
},
"part2_businessModel": {
"type": "object",
"properties": {
"costStructure": { "type": "array", "items": { "type": "string" } },
"revenueStreams": { "type": "array", "items": { "type": "string" } }
},
"required": ["costStructure", "revenueStreams"]
}
},
"required": ["productName", "version", "lastUpdated", "part1_productStrategy", "part2_businessModel"]
}
Pitfalls
- Feature Chasing: Violating documented strategic trade-offs by building custom features for individual clients. This dilutes product focus and turns a product company into a services agency. Prevention: Reference trade-offs before every roadmap decision; reject features that violate non-goals.
- Single-Feature Moats: Relying on a single feature for defensibility. Competitors can replicate features quickly; sustainable defensibility requires a system of strategic choices. Prevention: The "Can't/Won't" defense must cite at least two reinforcing barriers.
- Vanity Metrics as North Star: Using metrics like total registered users as the NSM. Prevention: NSM must measure active value delivery (e.g., successful system queries, weekly active authentications), not registration counts or seat usage.
- Separation of Strategy and Finance: Building product strategies without mapping unit economics, leading to negative margins at scale. Prevention: Always complete Step 10 (Business Model) before finalizing the canvas.
- Demographic Segmentation: Basing market segments on demographics instead of JTBD. Prevention: Every segment must have at least one documented job statement derived from user interviews.
- AI-Era Moat Illusion: Believing technical execution speed or code quality is a defensible moat. AI code generation has reduced development costs to near zero. Prevention: Focus moats on proprietary data, workflows, hardware, or business model misalignments — never on "we build faster."
- Weak Moat Not Flagged: Proceeding with roadmap development when the "Can't/Won't" analysis yields no clear barrier. Prevention: Suspend feature roadmap development until a defensible moat is identified.
Verification
Run these checks on every completed Startup Canvas:
Trade-off count: Confirm at least 3 strategic trade-offs are documented.
- Check:
grep -c "trade_offs" startup_canvas_config.yaml or count items in the tradeOffs JSON array. Must be ≥ 3.
North Star Metric quality: Confirm the NSM tracks value delivery, not vanity.
- Check: Does the NSM measure an outcome (e.g., "successful authentications") rather than an input (e.g., "signups")? If it contains words like "registered", "total", or "page views", reject and revise.
JTBD presence: Confirm every market segment has at least one job statement.
- Check: In the JSON/YAML, verify each item in
marketSegments / target_segments has a non-empty jobsToBeDone / jtbd array.
Moat strength: Confirm the "Can't/Won't" defense cites at least one barrier that is NOT pure technical execution.
- Check: Read
cantWontDefensibility. If it only references code quality, speed, or engineering talent, flag as weak moat and trigger the Weak Moat Warning.
Business model completeness: Confirm both costStructure and revenueStreams are populated.
- Check: Both arrays in
part2_businessModel must be non-empty.
JSON schema validation (if using JSON config):
# Point -s at a project-local schema that matches the excerpt in Examples
npx ajv validate -s startup_canvas.schema.json -d startup_canvas_config.json
Expected output: startup_canvas_config.json valid
Mermaid diagram renders: Confirm the strategic feedback loop diagram renders correctly in GFM Markdown preview.
Related Skills
saas-mvp-launcher — Scaffold Next.js repositories after strategy is finalized.
startup-business-analyst-financial-projections — Model detailed P&L spreadsheets from the business model section.
Source Anchors
Changelog
2026-05-30: Initial modernization pass. Converted to active voice, updated YAML metadata, removed boilerplate sections, and updated defensibility criteria to account for AI-assisted development cost reductions.
2026-05-31: Production-grade rewrite. Added explicit procedure steps, hard rules, verification checks, reference file loading instructions, and decision rules for moat strategy selection.
1---
2name: startup-canvas
3description: "Structures a Startup Canvas that splits product strategy (JTBD segments, trade-offs, North Star, Can't/Won't moats) from unit-economics lines. Use for early strategy drafts or defensibility reviews after competitor cost profiles exist. Not a Next.js MVP scaffold (saas-mvp-launcher) and not a P&L projection workbook."
4version: 1.0.1
5domain: Business-Strategy
6risk: safe
7last_verified: '2026-05-30'
8self_updating: true
9metadata:
10 source: https://skillmd.com/skills/kayforkind/startup-canvas
11---
12
13# Startup Canvas
14
15Apply the Startup Canvas framework to evaluate, structure, and iterate product strategies and business models. Explicitly divide corporate operational modeling from strategic product positioning, document business assumptions, map customer jobs-to-be-done, and verify defensibility moats.
16
17## When to Use
18
19- **Drafting initial startup plans** — mapping vision, segments, value proposition, and trade-offs from scratch.
20- **Refactoring existing product strategies** due to market shifts, new competitive entrants, or pricing model changes.
21- **Defining strategic trade-offs** for product roadmaps — explicitly documenting what the team will *not* build.
22- **Evaluating competitive defensibility** — running the "Can't/Won't" alignment loop against named competitors.
23- **Defining North Star Metrics** — selecting outcome-based metrics that track value delivery, not vanity counts.
24- **Separating product strategy from business model costs** — ensuring unit economics are mapped alongside strategic positioning.
25
26**Trigger keywords**: startup canvas, product strategy, defensibility moat, north star metric, trade-offs, JTBD, jobs to be done, business model, value proposition, competitive moat, relative costs, growth loop.
27
28**Route elsewhere**:
29- `saas-mvp-launcher` — to scaffold Next.js repositories.
30- `startup-business-analyst-financial-projections` — to model P&L spreadsheets and detailed financial projections.
31
32## Prerequisites
33
34- **Inputs required before starting**: Product name, version, target segments, value propositions, non-goals, cost items, and pricing structures.
35- **User research**: At least 15 target user interviews should be completed (or planned) to document primary JTBD before finalizing market segments.
36- **Competitor data**: Top 3 competitors profiled for relative cost strategy construction.
37- **Framework contrast (BMC / Lean Canvas)**: BMC's nine boxes mix operating model for an ongoing firm. Lean Canvas is problem/solution/unfair-advantage for early teams but is light on relative-cost posture and mandatory non-goals. Startup Canvas splits product strategy from unit economics and requires explicit trade-offs plus Can't/Won't.
38- **Schema and YAML**: use the JSON Schema excerpt and YAML Strategic Choice Configuration in Examples. If the team keeps a project-local schema file, validate against that file.
39
40## Procedure
41
42### Step 1 — Establish Vision
43
441. State the long-term, aspirational purpose of the product team in one to two sentences.
452. Confirm the founding team is aligned on this vision before proceeding.
463. Record the vision in the canvas metadata (top-level `vision` field).
47
48### Step 2 — Define Market Segments via JTBD
49
501. Interview at least 15 target users to document their primary needs and problems.
512. Define customer cohorts based on shared problems and Jobs-to-be-Done (JTBD) — **not** broad demographics.
523. For each segment, record:
53 - `segmentName`: A concise label.
54 - `jobsToBeDone`: Array of job statements (e.g., "Secure customer logins quickly without custom coding").
55
56### Step 3 — Establish Relative Cost Posture
57
581. Profile the top 3 competitors to understand their cost structures.
592. Select one of two postures:
60 - **Low-Cost**: Optimizing for minimal operational cost, competing on price efficiency.
61 - **Unique-Value**: Delivering premium value that justifies higher costs.
623. Record the posture in `relativeCosts` as either `"Low-Cost"` or `"Unique-Value"`.
63
64### Step 4 — Draft the Value Proposition
65
66Map the customer transformation across three states:
67
681. **What Before**: Describe the problematic customer state before the product exists.
692. **How**: List the product features and mechanics that resolve this pain.
703. **What After**: Describe the improved, successful customer state after using the product.
71
72Graph your feature offerings against alternatives to map unique value (value curve analysis).
73
74### Step 5 — Declare Trade-offs (Non-Goals)
75
761. Document at least **5 features or market segments** the team will deliberately ignore.
772. Each trade-off must be specific and actionable (e.g., "No custom on-premises deployments (Cloud only)").
783. **HARD RULE**: Every Startup Canvas must contain at least **3 strategic trade-offs** detailing what the team will *not* build or target. Fewer than 3 is a quality failure.
79
80### Step 6 — Define Key Metrics
81
821. Select a **North Star Metric (NSM)** that directly tracks value delivery to the customer.
83 - **HARD RULE**: NSM must track outcomes, not operational inputs or vanity registration counts. Examples of valid NSMs: "Weekly Active Authentications (WAA)", "Successful automated query completions". Invalid: "Total registered users", "Page views".
842. Select a **One Metric That Matters (OMTM)** for the current planning period.
853. Record both in `keyMetrics`.
86
87### Step 7 — Map the Growth Loop
88
891. Map customer acquisition, referral, and retention channels.
902. Identify the primary channel (e.g., organic SEO, product-led growth, partnerships).
913. Outline backup channels in case the primary channel saturates.
92
93### Step 8 — Document Capabilities
94
951. List internal capabilities needed to execute the strategy.
962. Categorize each capability as **Build**, **Buy**, or **Partner**.
973. Record in the `capabilities` array.
98
99### Step 9 — Conduct the "Can't/Won't" Defense Test
100
1011. Identify the primary competitor(s) for the target segment.
1022. Run simulations showing how a legacy competitor would react to your positioning.
1033. Apply the **Moat Strategy Selection** decision rule:
104 - **If competitor is a legacy incumbent**: Focus the moat on **"Won't"** — leverage their innovator's dilemma. Show why offering your value proposition would conflict with their core revenue model (e.g., incumbent won't lower prices because it undercuts their legacy base).
105 - **If competitor is a venture-backed startup**: Focus the moat on **"Can't"** — leverage proprietary data loops, custom enterprise workflows, hardware integrations, or patents. Show why they lack the resources or positioning to replicate.
1064. **HARD RULE — AI-Era Defensibility**: Traditional technical execution is no longer a sustainable moat due to AI code generation reducing development costs to near zero. Focus the "Can't/Won't" defense on proprietary data loops, custom enterprise workflows, hardware integrations, or strategic misalignments with competitors' business models.
1075. **HARD RULE — Weak Moat Warning**: If the "Can't/Won't" analysis does not yield a clear competitive barrier, flag this as a **critical business risk** and suspend feature roadmap development until resolved.
108
109### Step 10 — Map Business Model (Financial Mechanics)
110
1111. **Cost Structure**: Detail fixed and variable expenses (e.g., hosting, API limits, salaries, CAC).
1122. **Revenue Streams**: Establish pricing tiers, billing models, and outline expansion revenue paths.
1133. Project the cost structure and revenue channels onto a spreadsheet.
1144. **HARD RULE**: Never build product strategies without mapping unit economics — this leads to negative margins at scale.
115
116### Step 11 — Identify Risky Hypotheses and Design Validations
117
1181. Highlight the top **3 assumptions** that must be true for the business to survive.
1192. Design low-cost validations: landing page tests, clickable prototypes, or concierge MVPs to validate customer demand.
1203. Launch validations before committing to full build.
121
122### Step 12 — Output the Canvas
123
1241. Generate the final canvas as **GFM Markdown** containing Mermaid diagram assets.
1252. Ensure the output is optimized for direct integration into pitch decks and board presentations.
1263. Include the strategic feedback loop diagram:
127
128```mermaid
129graph TD
130 A[1. Vision] --> B[2. Market Segments]
131 B --> C[3. Relative Costs]
132 C --> D[4. Value Proposition]
133 D --> E[5. Trade-offs]
134 E --> F[6. Key Metrics]
135 F --> G[7. Growth Loop]
136 G --> H[8. Capabilities]
137 H --> I[9. Can't/Won't Defense]
138```
139
1404. Optionally validate a project-local JSON config against the schema excerpt in Examples (or the team's own schema file).
141
142## Examples
143
144### YAML Strategic Choice Configuration
145
146```yaml
147# startup_canvas_config.yaml
148metadata:
149 product_name: "AuthSentinel"
150 revision: "v2.1"
151 owner: "product-strategy-team"
152
153strategy:
154 vision: "To eliminate authentication friction and security leaks globally."
155 relative_cost_posture: "Unique-Value"
156 target_segments:
157 - name: "Early-stage SaaS Teams"
158 jtbd: "Secure customer logins quickly without custom coding."
159 trade_offs:
160 - "No custom on-premises deployments (Cloud only)"
161 - "No integration support for non-standard SAML databases"
162 - "No free tier — paid plans only to maintain unit economics"
163 key_metrics:
164 north_star_metric: "Weekly Active Authentications (WAA)"
165 omtm_q2: "Active integrations per tenant"
166 cant_wont:
167 competitors_cant: "Replicate our zero-knowledge validation latency."
168 competitors_wont: "Offer free basic tiers, as it undercuts their enterprise models."
169```
170
171### JSON Configuration Schema (Excerpt)
172
173Validate and store Startup Canvas configurations programmatically. Keep a project-local schema if automation needs a file; the excerpt below is the contract:
174
175```json
176{
177 "$schema": "https://json-schema.org/draft/2020-12/schema",
178 "title": "StartupCanvas",
179 "type": "object",
180 "properties": {
181 "productName": { "type": "string" },
182 "version": { "type": "string" },
183 "lastUpdated": { "type": "string", "format": "date-time" },
184 "part1_productStrategy": {
185 "type": "object",
186 "properties": {
187 "vision": { "type": "string" },
188 "marketSegments": {
189 "type": "array",
190 "items": {
191 "type": "object",
192 "properties": {
193 "segmentName": { "type": "string" },
194 "jobsToBeDone": { "type": "array", "items": { "type": "string" } }
195 },
196 "required": ["segmentName", "jobsToBeDone"]
197 }
198 },
199 "relativeCosts": { "type": "string", "enum": ["Low-Cost", "Unique-Value"] },
200 "valueProposition": {
201 "type": "object",
202 "properties": {
203 "beforeState": { "type": "string" },
204 "solutionMechanisms": { "type": "array", "items": { "type": "string" } },
205 "afterState": { "type": "string" }
206 },
207 "required": ["beforeState", "solutionMechanisms", "afterState"]
208 },
209 "tradeOffs": { "type": "array", "items": { "type": "string" } },
210 "keyMetrics": {
211 "type": "object",
212 "properties": {
213 "northStarMetric": { "type": "string" },
214 "oneMetricThatMatters": { "type": "string" }
215 },
216 "required": ["northStarMetric", "oneMetricThatMatters"]
217 },
218 "growth": { "type": "string" },
219 "capabilities": { "type": "array", "items": { "type": "string" } },
220 "cantWontDefensibility": { "type": "string" }
221 },
222 "required": ["vision", "marketSegments", "relativeCosts", "valueProposition", "tradeOffs", "keyMetrics", "growth", "capabilities", "cantWontDefensibility"]
223 },
224 "part2_businessModel": {
225 "type": "object",
226 "properties": {
227 "costStructure": { "type": "array", "items": { "type": "string" } },
228 "revenueStreams": { "type": "array", "items": { "type": "string" } }
229 },
230 "required": ["costStructure", "revenueStreams"]
231 }
232 },
233 "required": ["productName", "version", "lastUpdated", "part1_productStrategy", "part2_businessModel"]
234}
235```
236
237## Pitfalls
238
239- **Feature Chasing**: Violating documented strategic trade-offs by building custom features for individual clients. This dilutes product focus and turns a product company into a services agency. **Prevention**: Reference trade-offs before every roadmap decision; reject features that violate non-goals.
240- **Single-Feature Moats**: Relying on a single feature for defensibility. Competitors can replicate features quickly; sustainable defensibility requires a *system* of strategic choices. **Prevention**: The "Can't/Won't" defense must cite at least two reinforcing barriers.
241- **Vanity Metrics as North Star**: Using metrics like total registered users as the NSM. **Prevention**: NSM must measure active value delivery (e.g., successful system queries, weekly active authentications), not registration counts or seat usage.
242- **Separation of Strategy and Finance**: Building product strategies without mapping unit economics, leading to negative margins at scale. **Prevention**: Always complete Step 10 (Business Model) before finalizing the canvas.
243- **Demographic Segmentation**: Basing market segments on demographics instead of JTBD. **Prevention**: Every segment must have at least one documented job statement derived from user interviews.
244- **AI-Era Moat Illusion**: Believing technical execution speed or code quality is a defensible moat. AI code generation has reduced development costs to near zero. **Prevention**: Focus moats on proprietary data, workflows, hardware, or business model misalignments — never on "we build faster."
245- **Weak Moat Not Flagged**: Proceeding with roadmap development when the "Can't/Won't" analysis yields no clear barrier. **Prevention**: Suspend feature roadmap development until a defensible moat is identified.
246
247## Verification
248
249Run these checks on every completed Startup Canvas:
250
2511. **Trade-off count**: Confirm at least 3 strategic trade-offs are documented.
252 - Check: `grep -c "trade_offs" startup_canvas_config.yaml` or count items in the `tradeOffs` JSON array. Must be ≥ 3.
253
2542. **North Star Metric quality**: Confirm the NSM tracks value delivery, not vanity.
255 - Check: Does the NSM measure an outcome (e.g., "successful authentications") rather than an input (e.g., "signups")? If it contains words like "registered", "total", or "page views", reject and revise.
256
2573. **JTBD presence**: Confirm every market segment has at least one job statement.
258 - Check: In the JSON/YAML, verify each item in `marketSegments` / `target_segments` has a non-empty `jobsToBeDone` / `jtbd` array.
259
2604. **Moat strength**: Confirm the "Can't/Won't" defense cites at least one barrier that is NOT pure technical execution.
261 - Check: Read `cantWontDefensibility`. If it only references code quality, speed, or engineering talent, flag as weak moat and trigger the Weak Moat Warning.
262
2635. **Business model completeness**: Confirm both `costStructure` and `revenueStreams` are populated.
264 - Check: Both arrays in `part2_businessModel` must be non-empty.
265
2666. **JSON schema validation** (if using JSON config):
267 ```powershell
268 # Point -s at a project-local schema that matches the excerpt in Examples
269 npx ajv validate -s startup_canvas.schema.json -d startup_canvas_config.json
270 ```
271 Expected output: `startup_canvas_config.json valid`
272
2737. **Mermaid diagram renders**: Confirm the strategic feedback loop diagram renders correctly in GFM Markdown preview.
274
275## Related Skills
276
277- `saas-mvp-launcher` — Scaffold Next.js repositories after strategy is finalized.
278- `startup-business-analyst-financial-projections` — Model detailed P&L spreadsheets from the business model section.
279
280## Source Anchors
281
282- [The Product Compass Strategic Canvas Guides](https://www.productcompass.pm/p/product-strategy-canvas)
283- [BVP SaaS Growth Benchmarks](https://www.bvp.com/atlas)
284
285## Changelog
286
287- `2026-05-30`: Initial modernization pass. Converted to active voice, updated YAML metadata, removed boilerplate sections, and updated defensibility criteria to account for AI-assisted development cost reductions.
288- `2026-05-31`: Production-grade rewrite. Added explicit procedure steps, hard rules, verification checks, reference file loading instructions, and decision rules for moat strategy selection.