Three-Part Monetization Roadmap
Find the value unit, rank paid features, then set a tested price.
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 7
- Confidence
- 99%
The Three-Part Monetization Roadmap separates first-time monetization into value, features, and price. First identify the core product variable customers are willing to pay to unlock, such as recording duration or volume rather than peripheral organization tools. Second, prototype candidate features and run a MaxDiff survey, repeatedly asking users to choose the most and least valuable items from small sets. Combine responses with user data to compare roles, company sizes, and stages, then decide whether the offer should be horizontal or persona-specific. Third, run a Van Westendorp price analysis using four perceptions: suspiciously cheap, a bargain, expensive but still possible, and too expensive to consider. Select an intersection consistent with the growth strategy. Together, these outputs become the product's initial packaging, feature roadmap, and price point.
Origin
The approach was learned through a Reforge monetization program and described by Joe Thomas on The Foundr Podcast.
Core principles
- 01Start with the core variable customers pay to unlock
- 02Feature priorities should come from forced trade-offs
- 03Segment survey results with real user attributes
- 04Price research should distinguish cheap, acceptable, expensive, and prohibitive
- 05Pricing and packaging should protect the chosen growth model
How to run it
- 1
Find the paid value variable
Determine the central limit or capability customers care enough to pay to remove. Separate it from features they merely appreciate.
Pro tip Test usage volume, duration, access, and outcome limits before assuming advanced features drive payment.
Watch out Do not confuse frequently requested organization features with the core reason to upgrade.
- 2
Prototype candidate features
Create a varied list of plausible paid capabilities and make each concrete enough for users to compare. Include enhancements, analytics, and integrations where relevant.
Pro tip Use lightweight prototypes so respondents judge an understandable experience rather than a label.
- 3
Run forced feature trade-offs
Show small sets of candidate features and require each respondent to select the most and least valuable. Repeat with different combinations across roughly ten to twelve cycles.
Pro tip Forced choices reveal relative preference better than rating every feature as important.
Watch out Do not treat one permutation as enough evidence.
- 4
Segment the preference data
Join responses with user attributes such as role, company size, and stage. Compare whether value is broad or concentrated in a particular persona.
Watch out A global average can hide a strong vertical opportunity.
- 5
Map price perceptions
Ask when the product feels so cheap that quality is questionable, a bargain, expensive but still possible, and too expensive to consider. Plot the responses as four curves.
Pro tip Keep the product and package definition constant while asking all four questions.
- 6
Choose the strategic intersection
Select a price intersection that fits the intended customer breadth and growth motion. A broad viral product may favor a lower viable point to reduce adoption friction.
Watch out The statistically available price points do not remove the need for a strategic choice.
- 7
Build the monetization roadmap
Combine the paid value variable, feature ranking, segment analysis, and price into the initial package. Measure adoption and revise with real purchasing behavior.
Pro tip Treat survey evidence as the starting hypothesis, then compare it with actual conversion and retention.
Watch out Stated willingness to pay is not the same as a completed purchase.
In the wild
Loom's team identified longer recordings and unlimited recording volume as the core paid value. It used MaxDiff comparisons to rank possible additions across user segments, then applied Van Westendorp price analysis. Because Loom wanted a broad horizontal offer without damaging virality, it selected the lower relevant price intersection.
→ The research produced a $10-per-user monthly starting price and a monetization roadmap, according to Thomas.
A reporting product finds that users will pay to remove the monthly report limit. It compares alerts, exports, team permissions, and integrations through repeated forced choices, segments the results by company size, and asks the four price-perception questions for a defined paid package.
→ The team launches a package tied to the core usage limit at a price consistent with its self-serve strategy.
Common mistakes
Pricing before finding the value unit
A price is difficult to interpret when the team has not established what customers are actually paying to unlock.
Letting users mark everything important
Independent ratings produce weak priorities when respondents are not required to make trade-offs.
Treating surveys as purchase proof
Preference and price research guide the launch, but actual conversion and retention must validate the package.
Is it for you?
Best for
It is best for a used but unmonetized SaaS product preparing its first paid offering.
Not ideal for
It is not ideal before enough active users exist to provide informed product and pricing responses.
From the transcript
“Three core components one is um like core value proposition of the platform”
“you have to pick what is the most valuable and what is the least valuable”
“that became our monetization road map”
From the episode
506: I Ignored Investors and Built a $975M Company
Joe Thomas