0 to 1 Product Development
0 of 9
Workbook
Module 4 · Steps 7 and 8 · about 60 min

What it does for them: product spec and quantified value

By the end of this moduleA benefit-first product specification, a one-page visual of the product, and a quantified value proposition: the as-is number, the to-be number, and the metric that connects them.

Benefits first. Features are how you deliver them.

A high-level product specification is three columns. The customer's problem, need or job. The benefit your product creates for it. The feature that delivers the benefit. Founders fill the third column first and then reverse-engineer the other two. Do it in order. If a feature has no row in column one, it is a feature you like.

Then make it visual. A landing page or a one-screen mock does two things: it forces you to say the value in one headline, and it gives interviewees something to react to, which they are good at.

Quantify the value proposition

Pick the one value your customer actually measures: money saved, hours saved, errors reduced, downtime cut. Measure the as-is state from your interviews and journey map. Then estimate the to-be state with your product. The gap is your quantified value proposition, and it is the most reused number in your company: pricing, sales, investors, roadmap.

Compare it against the substitutes too. Customers do not compare you to nothing. They compare you to the spreadsheet, the accountant and the intern.

If you cannot write the as-is number, you did not finish Module 2. Go back and ask how much time it takes each week.

The value exchange loop

To capture value you have to deliver it first. Customer gets value, company gets paid, company reinvests, customer gets more value. Every product that lasts runs this loop. The quantified value proposition is the first half. The Business Modeling course is the second half. Get the first half right or the second half has nothing to price.

Worked example

From feature to benefit at UX Pilot

UX Pilot had a feature called Deep Design, a higher-fidelity generation mode. As a feature it was one toggle among many. As a benefit it was polished first drafts instead of rough ones, for a first-time user deciding in the first seven days whether the tool was worth paying for. Same code. Different row in the spec. That reframing is what made it worth testing in Module 6.

Exercise · 45 min

Product spec and QVP

Fill the spec left to right. Then the value proposition with real numbers from your interviews.

Saved in this browser
Customer problem, need or jobBenefit your product createsFeature that delivers it
1
2
3
4
5
The benefit, in the customer's words, under 12 words.
Hours per week, euro per month, errors per payroll run.
From interviews. With source.
Your honest estimate. Say how you got it.
What the spreadsheet, the agency or the intern delivers on the same metric, and what they cost.
Feeds your pitch deck: Solution slide
Checkpoint

Tick only what is true. Nobody is grading this. The next module assumes it.