Value-Based Market Sizing: Size by Value Created
Value-based market sizing estimates a market from the economic value your product creates for customers — cost saved or revenue gained — rather than the spending that already exists. You multiply the value created per customer by the number of customers, then apply a capture rate for the share you can realistically price for. Use it when your category has no budget line yet.
Quick Answer: Value-based market sizing = value created per customer × number of customers × capture rate. Estimate the economic gain your product delivers (cost saved or revenue unlocked), scale it across everyone who could realize it to get the value pool, then apply a capture rate — the fraction you convert into revenue through value-based pricing. It sizes new categories that top-down and existing-spend methods can't reach.
Most sizing methods count something that already exists: total spend in a category, or customers multiplied by a known price. That logic breaks the moment your product creates a category rather than competing in one — there is no spend to count and no price to multiply. Value-based sizing flips the question from "what do buyers spend today" to "what is this worth to them, and what slice can we charge for." It is one of several approaches you can read side by side in the complete guide to startup market sizing, and the one built for the blank-slate case. Its logic is inseparable from value-based pricing: you can only size what you can price.
Prerequisites: Quantifying the Value Created Per Customer
Before you size anything, you need a defensible annual dollar figure for the value one customer receives. That value is always one of two things — cost saved or revenue gained — and both must be measurable and credibly attributable to your product, not to everything the customer already does.
Value is cost saved or revenue gained — pick the one you can measure. Cost-saved products remove labor hours, avoid errors and rework, cut downtime, or replace paid tools. Revenue-gained products lift conversion, reduce churn, enable higher prices, or shorten time to market. Most products lean on one; lead with whichever the customer can already see in their own numbers.
Anchor the value in the customer's economics, not your ambition. The figure comes from their wage rates, their volumes, their conversion rates — gathered in discovery and pricing conversations, not assumed at a desk. A value figure you cannot trace back to the buyer's own operations is an opinion, and an opinion does not survive due diligence.
Count only the value the customer would attribute to you. Subtract the baseline — what they would achieve with a spreadsheet, an intern, or the status quo. The number that survives that subtraction is your real value created; the gap you invent by ignoring it is how value-based TAMs quietly turn into fantasy.
Express it per customer, per year. An annual, per-account figure stacks cleanly across segments and lines up with the way you will eventually price and forecast.
Different products create value in different places, and each source points to a specific number the customer already tracks. The table maps the common ones:
| Source of value | What you actually measure | Where the customer's number lives |
|---|---|---|
| Labor saved | Hours removed × loaded wage rate | Staffing levels, time-and-motion from interviews |
| Errors and rework avoided | Cost per error × reduction in error rate | Quality logs, incident and refund records |
| Revenue gained | Conversion or retention lift × deal value | The customer's funnel and pricing data |
| Downtime or risk avoided | Cost per incident × incidents prevented | Historical incident cost, SLA penalties |
| Paid tools replaced | Sum of the line items you displace | Current vendor invoices and subscriptions |
Takeaway: Every value figure should trace to a metric the customer already records, net of the baseline they would hit without you. If you cannot point to where the number lives, it is not value created — it is a hopeful assumption, and it will not survive a buyer's scrutiny or an investor's.
From Value Pool to Capturable Revenue: A Worked Example
The value pool is value created per customer multiplied by the number of customers who could realize it; capturable revenue is that pool multiplied by a capture rate. The pool is the total economic value your product could unlock across the market — but it is not your market. Customers keep most of it. Your value-based TAM is the slice pricing lets you capture.
Run it as two steps: build the pool, then take your share.
Every figure below is invented to demonstrate the method — it is not researched data, and you should never quote a teaching example as a real market size.
Picture a hypothetical product that automates a manual back-office workflow. Suppose discovery shows it saves a typical customer 500 hours a year at a loaded rate of $40 an hour — $20,000 of value created per customer, purely illustrative. Suppose 50,000 organizations could realize that gain.
| Input (illustrative) | Assumed value | How it is derived |
|---|---|---|
| Value created per customer / year | $20,000 | 500 hours saved × $40 loaded rate |
| Customers who could realize it | 50,000 | Addressable organizations |
| Value pool (total value created) | $1B | $20,000 × 50,000 |
| Capture rate | 15% | Share converted to revenue via pricing |
| Capturable revenue (value-based TAM) | $150M | $1B × 15% |
Takeaway: The $1B value pool is what the product is worth to the market; the $150M is what the market is worth to you. The gap is the surplus customers keep — their reason to buy. Notice the leverage: hold everything else fixed, swing the capture rate from 10% to 25%, and the value-based TAM moves from $100M to $250M. No other input bends the answer that hard, which is why the capture rate earns the most scrutiny.
Choosing a Defensible Capture Rate
The capture rate is the share of created value you can convert into your own revenue through pricing — and it is the single most contestable number in the model. A defensible rate reflects how much surplus a customer must keep to switch, how visible and attributable the value is, and what cheaper alternatives sit next to you.
You capture a fraction by design, never the whole. Value-based pricing works precisely because the customer keeps a clear return; price at the full value created and you have handed them no reason to buy. So the capture rate is always well under 100%, and the honest question is not whether you discount the value pool but by how much.
What moves the capture rate:
- Higher when the value is visible on the customer's own dashboard, switching costs are high, alternatives are weak, and the gain is unambiguously yours.
- Lower when attribution is fuzzy, a do-it-yourself workaround is easy, substitutes are cheap, or buyers can walk away at no cost.
Ground the rate in willingness to pay, not a round number. The fraction you can defend comes from evidence about what buyers will actually pay for a unit of value, which is exactly what willingness-to-pay research produces. Whether your defensible rate sits nearer 10% or 30% is a judgment you argue from that evidence — treat any single percentage here as illustrative until your own pricing conversations narrow it.
Sanity-check the price the rate implies. In the illustrative example above, a 15% capture rate on $20,000 of value implies a $3,000 annual price per customer; ask whether a real buyer in your market would pay that for a comparable tool. If the implied price looks absurd next to what customers spend today, your capture rate — or your value figure — is off, and the fix is to reconcile the two, not to admire the total.
When to Prefer Value-Based Sizing Over Customer-Count Sizing
Prefer value-based sizing when no existing spend or price anchors the market — a genuinely new category, a new kind of buyer, or a product that creates a budget line rather than competing for one. Prefer customer-count sizing when a price and comparable spend already exist to build from.
The two methods answer different questions, and the choice follows the evidence you actually have:
| Situation | Reach for | Why |
|---|---|---|
| New category, no budget line yet | Value-based sizing | Nothing exists to count; value is the only anchor |
| Established category with known prices | Bottom-up, customers × price | Real counts and prices exist to build up from |
| Priced market, but you are dramatically better | Both, then reconcile | Value explains the ceiling; counts ground the floor |
| Selling ROI to a skeptical buyer | Value-based framing | The sizing logic doubles as the sales narrative |
Takeaway: Value-based and customer-count sizing are not rivals. The strongest estimate runs both and reconciles them — value sets the ceiling, a bottom-up TAM calculation built from real counts and prices sets the floor — and a number that survives from both directions is far harder to dismiss than either alone. Edmired treats a value-based figure the way it treats any assumption: a hypothesis to pressure-test against the bottom-up build, not a headline to defend.
Key Takeaways
- Value-based market sizing sizes a market by the value your product creates, not the spend that already exists. It multiplies value created per customer by the number of customers, then applies a capture rate — the fraction pricing lets you keep.
- The method exists for the blank-slate case. When a category has no budget line and no established price, there is nothing to count top-down or bottom-up, so the value created becomes the only honest anchor.
- Value created is cost saved or revenue gained, sourced from the customer's own numbers. Anchor it in their wages, volumes, and conversion rates, net of the baseline they would reach without you — never in the number you wish you could charge.
- The value pool is not your market. Customers keep most of the value they receive; your addressable revenue is only the slice pricing lets you capture, which sits well below the full pool.
- The capture rate is the most contestable input, so defend it hardest. It rises with visible, attributable value and high switching costs, and falls with fuzzy attribution and cheap alternatives — ground it in willingness-to-pay evidence, not a round number.
- Cross-check the implied price against reality. Multiply value by your capture rate, read off the per-customer price, and ask whether a real buyer would pay it before trusting the total.
- Run value-based and bottom-up sizing together. Value sets the ceiling and counts set the floor; a market size that holds from both directions survives scrutiny that either one alone would not.
Frequently Asked Questions
What Is the Difference Between Value-Based and Bottom-Up Market Sizing?
Bottom-up sizing counts real customers and multiplies by a known price, so it needs an established market. Value-based sizing estimates the economic value a product creates and applies a capture rate, so it works before any price or spend exists. Use bottom-up when a category is already priced; use value-based when yours is new — and reconcile both when you can.
How Do You Calculate the Value a Product Creates for a Customer?
Measure the annual cost the customer saves or the revenue they gain because of your product, using their own numbers — wage rates, error costs, conversion lift, or displaced tools. Subtract the baseline they would achieve without you, so you count only the gain they would credibly attribute to your product. Express the result per customer, per year.
Is Value-Based Market Sizing Credible to Investors?
It is credible when every input is sourced and the capture rate is defended, and dismissed when it reads as a way to justify a huge number. Investors trust it most when you show the value evidence, state the capture rate as a challengeable assumption, and reconcile the result against a bottom-up count rather than presenting it alone.