Solution Value Proposition Testing SOP

Solution value proposition testing tells you which promise about your solution makes target customers understand it and want it, and it takes one to two weeks. The product stays the same in every variant. Only the promise changes: time saved, money saved, risk removed or a better feeling. The words you lead with decide who clicks, who signs up and who never reads the second line, so picking them by gut is an expensive guess.

What is solution value proposition testing and when should you use it?

This SOP compares three to five short statements that each describe the main benefit of the same solution from a different angle. You run them through three cheap tests in a row: a five-second test for comprehension, a preference poll for appeal and a small ad split for behaviour. A statement has to win at least two of the three to become your lead message.

Use this SOP:

• After customer interviews, when you heard several frustrations and don't know which one to lead with.
• Before a landing page test, so the page tests demand with the strongest promise instead of a random one.
• When your team or co-founders disagree about how to describe the product.
• When your landing page converts poorly and you suspect the headline.

Two neighbours cover related ground. The concept testing SOP checks whether the solution idea itself appeals. Marketing message testing comes later, at go-to-market, and tunes copy for each channel and audience at scale. This SOP sits between them: one solution, a handful of promises, one winner.

What do you need before you start?

• Notes or recordings from 10+ customer interviews. Every statement should borrow words customers used. The customer interview SOP shows how to collect them.
• One target segment you can reach on a research panel or with ads.
• Accounts on Lyssna or PickFu for five-second and preference tests with screened panels.
• An ad budget of $100 to $300 and a simple page on Carrd for clicks to land on.
• A scoring sheet with one row per statement.

How do you run it, step by step?

1. Write three to five statements with different angles

Use Geoffrey Moore's positioning template from Crossing the Chasm as a starting frame, then cut each version down to a headline of 10 words or fewer. Give each statement a different angle: speed, money, risk, control or feeling. Strategyzer's canvas by Alexander Osterwalder helps here: each angle maps to a different customer pain or gain.

2. Check each statement against customer words

Hold every statement next to your interview notes. If no customer ever described the problem that way, rewrite it or drop it. Statements built from real quotes beat clever ones you invented at your desk.

3. Run a five-second comprehension test

Show each statement as a simple hero section for five seconds to 20 panel members from your segment. Then ask: "What does this product do?" and "Who is it for?" Count the answers that match your intent. A promise people misread in five seconds will be misread on your homepage too.

4. Run a preference poll

Show all statements side by side, in random order, to 50 or more screened respondents. Ask which one they would click and why. The "why" answers are gold: they tell you which words carried the choice.

5. Run a small ad split

Create one ad per statement with identical images, audience and budget. Only the headline changes. Send clicks to a Carrd page with the same headline and an email signup. Run until each variant has at least 30 clicks.

6. Talk to five people about the winner

Show the leading statement to five target customers in short calls. Ask what they expect the product to do, what it would replace and what they would pay. This catches promises that win clicks but set the wrong expectations.

7. Pick the winner and write it down

Score each statement on the three tests. Write the winner as your official headline, plus one supporting line, and use it on your landing page, pitch and outreach until new data says otherwise.

Template you can copy

STATEMENT WORKSHEET (Moore's template, one per angle)
For [target customer]
who [frustration in their words],
[product name] is a [category]
that [main benefit].
Unlike [current alternative], it [difference].

Headline version (max 10 words): ______
Angle: speed / money / risk / control / feeling
Customer quote it came from: "______"

SCORING SHEET
Statement | Angle | 5-sec test: correct answers out of 20 |
Preference poll: share picking it first | Ad CTR | Signups | Cost per signup |
Wins (out of 3) | Notes from "why" answers

Worked example: an app for small landlords

This example is illustrative. A founder builds an app that collects tenant repair requests and books local trades for landlords who own one to five flats. She tests four headlines.

Statement B won all three tests. The "why" answers explained it: landlords feared liability for a missed report more than they cared about saving minutes. She made B the headline, moved C's money angle into the second line and ran her landing page test with that pair.

What should you measure, and when do you stop?

Stop when one statement wins two of the three tests. If no statement wins, the problem sits upstream, in how you describe the frustration or in a segment that is too broad. Go back to your notes, or map the fit between problem and solution with the problem-solution fit canvas SOP.

Which mistakes should you avoid?

• Testing near-identical statements. "Save time on repairs" versus "Save hours on repairs" teaches you nothing. Change the angle.
• Changing images along with headlines. You no longer know which one made the difference.
• Trusting the poll alone. People pick the statement that sounds nice; ads show what they click.
• Promising what you can't deliver. A winning promise that the product breaks creates churn later.
• Testing with the wrong panel. A general consumer panel judging a landlord tool gives you random data. Screen respondents.

How can AI speed this up?

Paste your interview quotes into an AI assistant and ask for one statement per angle, using only words that appear in the quotes. The free F/MS generator for benefit statements does a similar first draft. AI can also summarize the "why" answers from the preference poll into themes. The human check: you remove any statement that overpromises, and you read the poll answers yourself, because the surprising ones are the useful ones. Once you have a winner, the elevator pitch generator turns it into a 30-second pitch.

Where does this SOP fit in your validation plan?

Solution value proposition testing sits early in Solution Validation, right after the problem is clear.

1. Before: collect the customer words with the customer interview SOP and check the idea with concept testing.
2. Next: put the winning statement on a page and measure demand with the landing page test SOP.
3. Later: position against competitors with brand positioning validation and tune channel copy with marketing message testing.

Find the rest of the Solution Validation SOPs in one place.

FAQ

How many promises should I test at once?

Three to five. Fewer than three gives you little to compare, and more than five splits a small budget into variants that never reach enough clicks.

Do I need ads for this test?

No, but they help. The five-second test and the poll show comprehension and appeal. Ads add real behaviour from people who don't know they are in a test.

How many responses do I need for a five-second test?

20 per statement shows clear misunderstandings. Use 50 or more for the preference poll, because you compare shares across all statements.

What if two statements tie?

Lead with the one that people understood best in five seconds and use the other as the supporting line. Then let the landing page test settle it with signups.