value-proposition-canvas

What this skill does

# Value Proposition Canvas Expert

## Overview

The Value Proposition Canvas (VPC) is the canonical Strategyzer tool for designing and testing the fit between what customers care about and what your product offers. It is the "zoom-in" companion to the Business Model Canvas, focused on the two most failure-prone blocks: Customer Segments and Value Propositions. Where the Business Model Canvas asks "is this a viable business?", the VPC asks "are we building something customers actually want?"

The canvas has two sides. The **Customer Profile** describes the customer's world in their language -- jobs they are trying to do, pains they experience, and gains they aspire to. The **Value Map** describes the product's response -- the products and services offered, the pain relievers they include, and the gain creators they enable. Fit is achieved when the Value Map mirrors the Customer Profile element-by-element.

This skill walks through both sides of the canvas, defines the three levels of fit (problem-solution, product-market, business model), and provides validation checklists drawn directly from Alexander Osterwalder and Yves Pigneur's *Value Proposition Design* (2014).

### When to Use

- **Pre-PRD framing** -- Before writing requirements, validate that the value proposition is real and the customer profile is well-understood.
- **Solution refinement** -- You have a working product but unclear traction; use the VPC to diagnose whether the issue is the Customer Profile (wrong segment) or the Value Map (right segment, wrong response).
- **New segment expansion** -- Entering a new customer segment with an existing product; build a separate VPC for each segment to test fit.
- **Pricing and packaging decisions** -- Pains and gains rank-ordering informs which features go in which tier.
- **Sales enablement** -- Pain relievers and gain creators become the talking points and proof points for the sales team.

## The Two Sides of the Canvas

### Side 1: Customer Profile (the circle)

The Customer Profile describes the customer's world. It has three sections.

#### Jobs (Customer Jobs)

What is the customer trying to get done? Three flavors:

- **Functional jobs** -- A task to be completed. "Reconcile Stripe payments to QuickBooks invoices."
- **Social jobs** -- How the customer wants to be perceived. "Look competent in front of the finance director."
- **Emotional jobs** -- How the customer wants to feel. "Avoid the dread of month-end close."

Jobs are written from the customer's perspective, in their language. They are not features ("automated reconciliation tool") -- they are outcomes ("close the books in 2 days without errors").

**Job ranking:** Order jobs by *importance* to the customer. An unimportant job that is perfectly done has zero traction.

#### Pains

Bad outcomes, risks, and obstacles related to the jobs. Three flavors:

- **Undesired outcomes** -- "The reconciliation report has wrong numbers"
- **Obstacles** -- "I can't get the data out of the source system"
- **Risks** -- "If I close the books wrong, the auditor will catch it"

Pains are described concretely. "Reconciliation is hard" is weak. "Reconciliation takes 11 hours per close because I have to manually match 2,400 rows" is strong.

**Pain ranking:** Order pains by *severity* (how bad it is when it happens) and *frequency* (how often it happens). High-severity high-frequency pains are the priority.

#### Gains

Outcomes and benefits the customer wants. Four flavors:

- **Required gains** -- Without these, the solution does not work ("the report has to be accurate")
- **Expected gains** -- Customers assume these exist ("the data is encrypted in transit")
- **Desired gains** -- Customers explicitly want these ("the report exports to PDF for the auditor")
- **Unexpected gains** -- Things customers do not yet know to ask for, but love when delivered ("a Slack alert when reconciliation completes")

**Gain ranking:** Order gains by *desirability* and *relevance to the job*. Unexpected gains drive delight; required gains drive table stakes.

### Side 2: Value Map (the square)

The Value Map describes the product's response to the Customer Profile.

#### Products & Services

The bundle of things you offer. This is the *what*. Concrete listing -- a feature, a service, a subscription tier, an integration.

#### Pain Relievers

How your products and services *eliminate or reduce* the customer's pains. Each pain reliever should reference a specific pain from the Customer Profile.

Example pain: "Reconciliation takes 11 hours per close."
Pain reliever: "Automated rule-based matching that processes 2,400 rows in under 60 seconds."

#### Gain Creators

How your products and services *create* the customer's gains. Each gain creator should reference a specific gain.

Example gain: "Slack alert when reconciliation completes."
Gain creator: "Real-time Slack notifications via webhook integration; one alert per completed run."

## The Three Levels of Fit

Osterwalder defines fit as a three-stage validation process. Each stage requires evidence; do not skip.

### Level 1: Problem-Solution Fit

**Question:** Have we designed value-creating products and services that customers want?

**Test:** For each top-ranked job, pain, and gain in the Customer Profile, can you point to a specific pain reliever or gain creator that addresses it?

**Evidence required:** Customer interviews (`discovery/customer-interview-script/` + `discovery/interview-synthesis/`) confirming the jobs, pains, and gains are real. Concept tests confirming the value proposition resonates.

**Anti-pattern:** Designing pain relievers for pains that customers do not actually have. The Value Map mirrors the team's assumptions, not the Customer Profile's reality.

### Level 2: Product-Market Fit

**Question:** Have we found evidence that customers want our products and services and will pay for them?

**Test:** Are customers using the product? Are they retaining? Are they referring? Is the cost of acquisition lower than the lifetime value?

**Evidence required:** Behavioral data -- activation, retention, expansion, willingness-to-pay. The Sean Ellis test (40%+ would be "very disappointed" without the product) is one signal.

**Anti-pattern:** Confusing problem-solution fit with product-market fit. Interviews can validate problem-solution; only behavior can validate product-market.

### Level 3: Business Model Fit

**Question:** Have we found a business model that is scalable and profitable?

**Test:** Does the unit economics work? Can the channels scale? Are the costs structurally aligned with the revenue?

**Evidence required:** Cohort LTV/CAC analysis, channel economics, gross margin trends. This level lives mostly in `finance/` skills -- the VPC informs it but does not validate it alone.

## Canvas Template (Markdown Table Form)

```markdown
## Value Proposition Canvas: [Segment Name]

### Customer Profile

**Customer Jobs** (ranked by importance, 1 = most important)

| # | Job | Type | Notes |
|---|-----|------|-------|
| 1 | [Job statement in customer language] | Functional/Social/Emotional | [context] |
| 2 | [Job statement] | ... | ... |

**Pains** (ranked by severity x frequency)

| # | Pain | Severity (1-5) | Frequency (1-5) | Notes |
|---|------|----------------|------------------|-------|
| 1 | [Pain statement] | 5 | 5 | [evidence] |
| 2 | [Pain statement] | 4 | 3 | ... |

**Gains** (ranked by desirability)

| # | Gain | Type | Notes |
|---|------|------|-------|
| 1 | [Gain statement] | Required/Expected/Desired/Unexpected | [...] |
| 2 | [Gain statement] | ... | ... |

### Value Map

**Products & Services**

| # | Item | Type |
|---|------|------|
| 1 | [Feature, service, or offering] | Feature/Service/Tier |
| 2 | [...] | ... |

**Pain Relievers** (each maps to a Pain above)

| # | Pain Reliever | Addresses Pain # | How |
|---|---------------|-------------------|-----|
| 1 | [How the product reduces or eliminates a pain] | 1 | [mechanism