Problem definition
Value proposition map
Value proposition map is licensed CC BY 4.0. Attribution: Katafacts (katafacts.com).
Customise with AISkill file ↓1 · What it is
What it is
A value proposition map is a one-page, two-sided picture: the customer's jobs, problems, and hoped-for benefits on one side, and your products & services, problem fixes, and benefit claims on the other — each problem fix and benefit claim naming exactly which problem or benefit it addresses, not a generic list of features. Real strength shows up as a tight match between the two sides; real weakness shows up as a problem or benefit with nothing genuinely addressing it, or a feature with no real customer problem or benefit underneath it to justify it.
2 · When to use it
When to use it — and when not to
Use it when
- You have real, evidenced customer jobs, problems, and hoped-for benefits (a value hypothesis or CTQ tree is the natural upstream input) and want to check how tightly your actual offering maps onto them.
- You want a second, complementary view of the same evidence a message architecture already organized as a tree — this one built to expose feature-market fit gaps a tree's own shape doesn't surface as directly.
- You want to see honestly which problem fixes and benefit claims are backed by real proof and which are still a hope.
Not when
- You don't have real evidence of the customer's actual jobs, problems, and hoped-for benefits yet — a value hypothesis or discovery work first, then a map built from what it actually shows.
- You already have a message architecture built from the same evidence and just need the standing message, not a second diagnostic view — use that directly instead of duplicating the exercise.
3 · How to fill it in
How to fill it in
- Customer jobs
- What is the buyer actually trying to get done?
- Customer problems
- What's getting in the way, or making it worse? Grounded in real evidence, not a guess.
- Hoped-for benefits
- What outcome would make this a clear win for the buyer?
- Products & services
- What do you actually offer that touches these jobs?
- Problem fixes
- How specifically does what you offer remove or ease a named pain? Name the pain it addresses, not a generic benefit.
- Benefit claims
- How specifically does what you offer produce a named gain? Name the gain it addresses, and whether it's actually proven yet.
4 · What good looks like
What good looks like
The example below organizes the exact same evidence the message architecture and value hypothesis worked examples already established for Beacon Analytics — the same three needs, the same 48-hour and $310K figures — as a two-sided map instead of a tree, and is honest that the weakest column (spreadsheet trust) still has no real benefit claim behind it.
Same example, as a downloadable xlsx workbook.
Scoping canvas
Beacon Analytics — value proposition map
Priya Anand, RevOps · 2027-03-05
Customer jobs
- Forecast pipeline accurately enough that leadership isn't surprised at the QBR.
- Build a business case for a new tool that survives budget scrutiny without help.
- Keep the team's trust in whatever system they're actually using day to day.
Customer problems
- Stalled deals surface at the QBR, weeks after they went quiet — Northline Freight's VP RevOps described finding out this way, not from a live signal.
- A budget champion has no defensible number to bring to their own approval chain — Beacon Analytics' own Q1 deal A3 traced $40K of stalled pipeline directly to this.
- A new tool has to earn trust away from a spreadsheet the team already relies on and understands.
Hoped-for benefits
- Deals flagged at-risk with enough lead time to actually intervene.
- A quantified, defensible number the champion can carry into a budget conversation alone.
- Confidence in the numbers without re-learning how the team already works.
Products & services
- Automated deal-risk scoring against real CRM activity, not a stale manual tag.
- A one-click, buyer-specific business-case calculator built from the buyer's own historical deal data.
- CRM-native integration — no separate system for reps to learn or trust.
Problem fixes
- Deal-risk scoring flags a stalled deal within 48 hours, replacing a ~3-week QBR-cycle discovery.
- The business-case calculator replaces a $40K-a-quarter blind spot with a real, computed number.
- CRM-native means no new login, no separate data entry, no second system to trust.
Benefit claims
- Early flags give reps and managers real lead time to intervene before a deal is unrecoverable.
- A self-serve, defensible number — $310K in Northline Freight's own trial cohort — the champion doesn't need Beacon Analytics in the room to defend.
- Nothing to migrate away from — the team's existing habits stay intact while the blind spot closes.
Narrative
The first two problems map to problem fixes and benefit claims with real, already-proven numbers behind them — the same 48-hour visibility target and $310K reference figure the message architecture and value hypothesis both cite. The third problem, spreadsheet trust, is honestly the thinnest column here: its problem fix ("nothing to migrate away from") is a real product fact, but the benefit claim underneath it hasn't been tested with a real buyer yet, the same gap the message architecture already flags rather than papering over with an unproven claim.
5 · Common mistakes
Common mistakes
Listing a problem fix or benefit claim that doesn't actually name which problem or benefit it addresses.
A feature floating with no named pain or gain underneath it is exactly the mismatch this map exists to expose — every entry on the value-map side should trace to a specific entry on the customer side.
Writing benefit claims as aspirations rather than proven results.
The whole value of this map is seeing which parts of the offer are actually proven — treating a hope as a proven benefit hides the exact gap a consistency audit would later need to catch.
Filling in the value-map side before the customer side is grounded in real evidence.
A map built from an assumed persona's jobs and pains produces a confident-looking match that isn't actually testing anything real — start from real discovery or a value hypothesis, not a guess.
6 · What it connects to
What it connects to
upstream
The same needs and proof points a message architecture organizes as a tree are what this map maps as jobs, problems and hoped-for benefits versus problem fixes and benefit claims — two views of one set of evidence, not two separate sources of truth.
A deal-specific value hypothesis that's actually worked is real evidence for this map's customer-side entries — not invented from an assumed persona.
downstream
7 · Where AI helps
Where AI helps
Judgement — stays yours
- Deciding whether a problem fix genuinely addresses the problem it's paired with, or just sounds related
- Deciding whether a benefit claim is actually proven or still an unproven hope
Analysis — AI helps
- Drafting each section's bullets from a rough description or real deal evidence
- Flagging a section that's too thin to mean anything yet, rather than padding it
Drudgery — automated
- Formatting the map and keeping every section on one page
- Exporting to xlsx in the house format
9 · Rate this kata