Skip to content

borghei/Claude-Skills / project-management/discovery/value-proposition-canvas

value-proposition-canvas

Verified

Maps one segment's jobs, pains and gains against your product's relievers and creators and checks fit. Use when testing whether an offer matches what customers care about, or positioning a product for one segment.

assets/fit_validation_checklist.md

View on GitHub
# Fit Validation Checklist

Three levels of fit to validate, in order. Each level has evidence requirements; do not claim a level without the evidence.

---

## Level 1: Problem-Solution Fit

**Definition:** We have designed value-creating products and services that customers want.

**Evidence requirements (all must be met):**

- [ ] **Customer Profile validated.** Jobs, pains, and gains populated from >=5 customer interviews per segment, with verbatim quotes attached.
- [ ] **Top 3 jobs identified.** Importance + frequency scoring complete; team aligned.
- [ ] **Top 3 pains identified.** Severity x frequency scoring complete; current workarounds documented.
- [ ] **Top 3 gains identified.** Including at least 1 Unexpected (delighter) gain.
- [ ] **Value Map mirrors top items.** Every top-3 job, pain, and gain has a corresponding pain reliever or gain creator.
- [ ] **Concept tests passed.** At least 5 customers reviewed the value proposition statement and confirmed it resonates with their actual problem (not "sounds interesting" -- "this is what I'm dealing with").
- [ ] **Willingness-to-pay signal.** At least 3 prospects have signaled intent to pay (LOI, prepayment, paid pilot) -- not "interested in seeing more".
- [ ] **No forced-fit mapping.** Items with no genuine pain reliever or gain creator are explicitly listed as uncovered.

**Conclusion:**

- [ ] Problem-Solution Fit ACHIEVED -- proceed to validate Product-Market Fit
- [ ] Problem-Solution Fit PARTIAL -- list specific gaps and a plan to close them
- [ ] Problem-Solution Fit NOT YET -- return to discovery (`discovery/customer-interview-script/`)

**Date validated:** [YYYY-MM-DD]
**Validated by:** [Names]

---

## Level 2: Product-Market Fit

**Definition:** We have evidence that customers want our products and services and will pay for them.

**Evidence requirements (most must be met; weight depends on stage):**

- [ ] **Sean Ellis test.** Survey existing users with: "How would you feel if you could no longer use [product]?" -- at least 40% answer "Very disappointed".
- [ ] **Retention curve flattens.** Cohort retention does not approach zero; segment-appropriate plateau reached (e.g., B2B SaaS: >70% retention at 90 days).
- [ ] **Net Revenue Retention.** > 100% on a trailing 12-month basis (B2B SaaS).
- [ ] **Organic growth signal.** Net new MRR from referrals/word-of-mouth > 0 when paid acquisition is zeroed.
- [ ] **Willingness-to-pay confirmed.** Customers are paying at or above the target ACV/ARPU; price increases tested and accepted.
- [ ] **Customer NPS.** > 30 (B2B) or > 50 (B2C consumer).
- [ ] **Expansion revenue.** Customers are upgrading tiers, adding seats, or buying add-ons within 12 months.
- [ ] **Win rate.** > 25% on qualified opportunities.

**Conclusion:**

- [ ] Product-Market Fit ACHIEVED -- proceed to validate Business Model Fit; consider scaling
- [ ] Product-Market Fit PARTIAL -- specific signals missing; targeted experiments to close
- [ ] Product-Market Fit NOT YET -- return to problem-solution validation; pivot may be needed

**Date validated:** [YYYY-MM-DD]
**Validated by:** [Names]

---

## Level 3: Business Model Fit

**Definition:** We have a scalable, profitable business model.

**Evidence requirements (all must be met for sustainable scale):**

- [ ] **LTV / CAC.** > 3 on a fully-loaded basis (CAC includes sales + marketing + onboarding).
- [ ] **CAC Payback Period.** < 18 months (B2B SaaS); < 12 months (PLG); < 3 months (B2C subscription).
- [ ] **Gross Margin.** > 70% (B2B SaaS); appropriate to business model.
- [ ] **Channel economics scale.** Cost per acquired customer does not balloon as the channel scales 2-3x.
- [ ] **Operating model sustainable.** Burn multiple < 2 (Series A); < 1 (Series B+); positive contribution margin per customer.
- [ ] **Unit economics by segment.** LTV/CAC holds across at least 2 distinct segments (no single-segment dependency).
- [ ] **Pricing tested at multiple price points.** Customers retained after a price increase or willing to upgrade tiers.

**Conclusion:**

- [ ] Business Model Fit ACHIEVED -- scale with confidence
- [ ] Business Model Fit PARTIAL -- identify economic gaps and address before scaling spend
- [ ] Business Model Fit NOT YET -- defer scaling; reduce burn; revisit pricing and unit economics

**Date validated:** [YYYY-MM-DD]
**Validated by:** [Names]

---

## Anti-Pattern Checklist

Things that look like fit but are not. If any of these are true, downgrade the fit claim by one level.

- [ ] We are claiming PMF based on interview enthusiasm rather than behavior.
- [ ] We have growth but it is bought, not retained (LTV < CAC).
- [ ] We have retention but only in one segment that does not scale.
- [ ] We have revenue but margins are unworkable.
- [ ] We have a strong Value Map but the Customer Profile is written in team language, not customer language.
- [ ] We have an "all customers" canvas instead of segment-specific canvases.
- [ ] Our roadmap targets fix items that are NOT in the top 3 pains or gains.
- [ ] We assumed problem-solution fit transferred to a new segment without re-validating.

---

## Quarterly Review Cadence

Fit is not a one-time achievement. Schedule:

- **Monthly:** Behavioral signals (retention, NRR, NPS)
- **Quarterly:** Full canvas review, including Customer Profile drift and uncovered items
- **Annually:** Business model fit review, including unit economics by segment

**Triggers for early review:**

- Retention drop > 5pp month-over-month
- Major competitor move
- Segment entry (new market, new role)
- Pricing change
- Product line expansion or sunset
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall