ProjekinAja. Founder's Playbook Stage 3 · Revenue Architecture Lesson 3.2
● Stage 3 · Lesson 3.2

Value-Based Pricing — The Only Pricing That Survives

Cost-plus pricing is the default error of technical founders — here is how to anchor price on customer value and why it changes everything.

⏱ ~22 min read 💰 Pricing strategy 🔢 EVC calculator

🎯 By the end you'll understand

Why cost-plus and competitive pricing are structurally wrong for startups — not just suboptimal, but systematically wrong in a way that causes founders to leave 50–90% of value on the table. What Economic Value to Customer (EVC) means and how to compute it from discovery data. How the value capture rate works, what range is defensible, and what forces move it. And how to turn Forge's pilot interview data into a justified price range with a sensitivity table that reveals exactly which inputs matter most.

KEY INSIGHTPrice is not a number you pick — it is a claim you make

The founder who prices based on what "seems reasonable" without computing the customer's actual economic outcome will, on average, leave 50–90% of value on the table. Not occasionally — systematically, every deal, forever, until they fix the model.

Every pricing conversation starts with a founder looking inward: what did this cost to build? What are competitors charging? What feels like a fair margin? These are the wrong questions. They are the wrong questions not because margins and competition do not matter — they do — but because they anchor price to the wrong object. Price should be anchored to the value the customer receives, not the cost you incur. That shift is the entire discipline of value-based pricing, and it is harder than it sounds because it requires you to actually know what your product is worth to the customer in economic terms before you set a number.

🔑 The structural insight of Stage 3

Revenue is a design decision. The price you set today constrains every downstream decision for the life of the company: whether you can afford customer success, how much CAC you can pay, whether you can hire enterprise salespeople, and whether your unit economics close at all. A wrong price — particularly an under-price — is not just a missed opportunity. It is a structural constraint that compounds with every customer you add. Fix it early, when you have negotiating leverage and when customers have not yet anchored to a number.

CORE CONCEPTThree pricing foundations — and why two of them are wrong for startups

There are exactly three foundations a B2B startup can use to set price. Most founders intuitively reach for the first two. The third is the only one that can produce durable, defensible pricing — and it is the one that requires the most work.

1

Cost-plus pricing — start from your cost, add a margin

The logic: figure out what it costs to deliver the product or service, add a target margin, and price at that number. "Our COGS for a Forge sensor kit plus onboarding plus annual support is $14,000 per site. We want 60% gross margin. Therefore we charge $35,000." This feels disciplined. It feels like a spreadsheet. It is systematically wrong because cost has no relationship to value. If your sensor prevents a $400,000 downtime event, charging $35,000 because that is what it costs you means you captured less than 9% of the value you created. The customer just captured the other $365,000. You built that, you delivered it, and you left most of it on the table because you anchored to the wrong side of the equation. Cost-plus pricing is not conservative — it is arbitrary. It is anchoring to a number that tells you nothing about whether you are over- or undercharging.

2

Competitive pricing — start from what competitors charge

The logic: find comparable products, price at or slightly below the market rate to win deals. "Existing quality-inspection software runs $8,000–$20,000/year. We'll price at $25,000 to signal we're better, but not so much that it's shocking." This also feels reasonable. It also fails for early-stage startups in a specific way: it anchors you to your competitors' cost structures, competitive positions, and customer relationships — none of which apply to you. Your competitors priced for their unit economics, their sales motion, their customer acquisition cost, and their existing installed base. You have none of that. More importantly, competitive pricing assumes your product delivers roughly the same value as competitors. If your product is meaningfully better — if it prevents events that competitors' tools miss, or does so faster, or with less integration work — competitive pricing throws away exactly the premium your differentiation creates. You built a better product and then priced it like the worse one.

3

Value-based pricing — start from what the customer gains

The logic: figure out the full economic value the customer receives from your product, then claim a fraction of that value as your price. "This site averages 3.2 unplanned downtime events per year at $85,000 per event. Our defect escape detection reduces escapes by 40%, which translates to roughly 1.3 fewer events per year. That is $110,000 in expected annual value — plus the labor savings, plus the warranty reduction. Total EVC is approximately $180,000. We will price at $42,000, which is a 23% capture rate." This is the only pricing foundation that is tied to what you actually deliver. It is also the most defensible in a sales conversation: you are not asking a customer to accept an arbitrary number, you are asking them to share a fraction of the economic gain they are about to receive. The only way this fails is if your EVC estimate is wrong — which is why the discovery interviews in Stage 1 matter so much for pricing in Stage 3.

Cost-Plus COGS margin price = cost + % actual value (unknown, uncaptured) Arbitrary anchor Competitive your price Competitor's anchor, not yours Value-Based EVC captured ~20-30% customer keeps 70-80% Anchored to what you deliver
The three pricing foundations. Cost-plus anchors to the wrong side of the equation — internal cost. Competitive anchors to a number someone else set for reasons unrelated to your business. Value-based anchors to the economic outcome you produce for the customer. Only the third model reveals whether your price is defensible.
⚠ "But we're a startup — we need to be affordable"

This is the rationalization that keeps founders under-priced for years. "Affordable" relative to what? If your product delivers $200,000 in annual value, a $40,000 price is already 80% affordable — the customer keeps four times what they pay. The real issue is usually that the founder has not done the math, and so "affordable" becomes a vague heuristic that defaults to whatever feels non-threatening in the conversation. Value-based pricing is not about charging maximum price — it is about charging a justified price. Unjustified low prices are not a competitive advantage; they are a liability that makes you unprofitable at the customer acquisition costs required to grow.

CORE CONCEPTEconomic Value to Customer — the number that anchors everything

Economic Value to Customer (EVC) is the total economic gain a specific customer receives from your product over a defined time period, net of the cost of their next-best alternative. It is not the maximum they would ever pay. It is not a vague sense of "value." It is a specific, computable number — and for B2B products, it can almost always be computed from data you gather in discovery interviews.

EVC has a precise structure:

Component What it measures Forge example (per site/year)
Reference value The value of the customer's next-best alternative (incumbent solution) Value of existing manual inspection + current defect escape cost they already manage
Positive differentiation value Economic gains your product delivers that the alternative does not Downtime events prevented × avg cost per event; labor hours saved × labor rate; warranty claims avoided
Negative differentiation value Costs your product imposes that the alternative does not Integration labor, training time, hardware maintenance overhead
EVC = Reference value + Positive differentiation − Negative differentiation The total justified economic premium over the alternative

For Forge, the relevant positive differentiation value comes from three sources that discovery interviews can quantify: (1) the cost per unplanned downtime event, times the reduction in events that Forge's defect detection enables; (2) the reduction in defect escape rate, which drives warranty and recall costs down; and (3) the direct labor saved by automating inspection tasks that inspectors currently do manually. Each of these is a number a manufacturing operations manager either knows or can estimate — and the quality of your EVC computation is determined entirely by the quality of those estimates.

💡 The EVC interview technique

In discovery interviews, you do not ask "what would you pay for this?" — that activates anchoring effects and produces unreliable answers. Instead: "Walk me through the last unplanned downtime event. How long was the line down? What does an hour of downtime cost the facility?" and "How many inspectors do you have on this line? What percentage of their time is inspection versus other tasks?" These behavioral questions about existing economic reality — not hypothetical willingness to pay — are what let you compute EVC from the outside in.

Downtime prevented +$119K Defect escape reduction +$45K Inspection labor saved +$22.5K Integration overhead −$8K EVC = $178.5K price ~$42K (24%)
A simplified EVC waterfall for Forge — one site, one year (4 events × $85K × 35% reduction = $119K downtime component). Downtime events prevented is typically the largest component for predictive-maintenance products. Negative differentiation (integration overhead) shrinks EVC slightly. Price ($42K) captures approximately 24% of the total economic value created ($178.5K). The customer retains ~$136.5K.

CORE CONCEPTThe value capture rate — what fraction is yours to keep

Once you have computed EVC, the next question is: what fraction of it should you capture as price? This is the value capture rate, and it is not arbitrary — it is constrained by several forces.

Force Effect on capture rate Typical range
Competitive alternatives More alternatives → lower capture rate (customer has options). First mover with no alternatives → higher capture possible. Strong competition: 5–15%. Weak/no competition: 25–40%.
Switching cost for customer High switching cost to adopt your product → lower rate (risk premium). High switching cost to leave your product later → higher rate (lock-in). Adoption switching cost narrows range. Post-adoption lock-in expands ceiling.
Proof / track record First customer with zero proof → lower rate (risk adjustment). Proven ROI with references → higher rate. Pilot/first customer: 10–20%. Established product: 20–35%.
Customer's budget process Must pass 3-level approval and ROI threshold → rate constrained by internal hurdle. Direct purchase authority → rate reflects pure value negotiation. Enterprise approval cycles: cap around 20–25% of EVC unless champion can show clear ROI.
Your gross margin requirement Your minimum capture rate is set by the economics you need to be viable — not a ceiling, but a floor. Below this you are not building a business. SaaS target: ≥70% GM. Hardware+SaaS hybrid: ≥55–60% blended GM. Sets price floor.

For an early-stage B2B startup with limited proof and real integration costs, a defensible starting range is typically 15–25% of EVC. Below 15%, you are likely leaving money on the table and the unit economics may not close. Above 30–35%, you are typically asking customers to accept more risk than they are willing to take on a first-generation product from an unknown vendor. The sweet spot for Forge's first contracts — with two pilot customers and documented outcomes — is around 20–25%.

📐 The capture rate floor: gross margin discipline

There is a hard floor on capture rate that is not about competition or customer psychology — it is about your own economics. If your COGS per customer is $18,000/year and your target gross margin is 60%, your minimum price is $45,000/year. If EVC is $172,000, this translates to a minimum capture rate of about 26%. If the market will only bear 20%, you either need to cut costs or accept that your gross margin will miss target. Both of those are real choices, but you cannot make them if you have not done the EVC math.

SEE ITValue-Based Price Calculator — compute Forge's justified price range

⚙ Interactive · Value-Based Price Calculator

Enter Forge-specific value data from discovery interviews: cost per downtime event, defect escape rate improvement, and annual inspection labor saved. The widget computes total annual Economic Value to Customer (EVC), then lets you set a capture rate and outputs a justified price with a sensitivity table. Try low and high scenarios to see which inputs move the price the most.

Forge context: Two pilot sites completed. Both are mid-size automotive Tier-1 plants. You have interview data on downtime costs, defect escape rates, and labor allocation. Set the sliders to match your best estimate from the interviews, then explore the capture rate options.

Customer Value Inputs (per site, per year)
$85,000 $/event
4 events/yr
35% % reduction
$45,000 $/yr
$22,500 $/yr
$8,000 $/yr equiv
Defensible range for an early-stage B2B startup with 2 pilots: 10–30%. Select a rate to see the resulting price and sensitivity table.
Total Annual EVC (this site)
—
—
—
Downtime value
—
Defect escape value
—
Labor value
—
Integration cost
—
Sensitivity table — price at each capture rate
Capture rate Justified price Customer keeps Customer ROI Notes
📊 Pricing verdict

Adjust the sliders to match your discovery interview data, then select a capture rate to see a justified price range.

A few things to notice from working the calculator. First, the downtime cost per event slider is almost always the dominant driver — a small change in that number (from $85K to $120K) moves your justified price by more than the entire labor component. This tells you that downtime cost estimation is the highest-priority interview topic in your discovery process. If you do not have a reliable number from the customer, your EVC is unstable. Second, notice the sensitivity table: at low EVC, the 10% capture rate may produce a price that does not cover your COGS — the EVC math reveals that you have a business model problem, not a pricing problem. Third, notice that even a conservative 20% capture rate typically produces a price meaningfully above what most technical founders would have set using cost-plus or competitive anchors.

FORGEHow Forge priced its first two annual contracts

By the end of Stage 3, Forge converted both pilot customers to annual contracts at $42,000 ACV each. Here is how the EVC math drove that number.

Discovery interviews across 20 Tier-1 manufacturing plants (Stage 1) produced reliable estimates for three value components. The median downtime event cost was $85,000, with a range of $55,000–$140,000 across sites. Sites averaged 3–5 unplanned downtime events per year. Forge's defect detection reduced events attributable to quality escapes by 30–40% in pilot data (not 100% — Forge only prevents defects it can detect in the sensor's line of sight; other causes remain). The defect escape and warranty reduction was harder to quantify but pilots showed an average $40,000–$55,000 in avoided warranty claims. Inspection labor was the smallest component: about $18,000–$28,000 per site per year.

1

Anchor EVC to the pilot data — not to optimistic projections

Forge used conservative figures: $85,000 per event × 4 events × 35% reduction = $119,000 downtime component. Plus $45,000 warranty reduction. Plus $22,500 labor savings. Less $8,000 integration overhead. Total EVC: approximately $178,500. The temptation is to use the high end of every range — that produces an EVC of $280,000+ that no procurement team will believe. Using documented pilot data produces a credible, auditable number.

2

Set capture rate based on proof level and competitive position

With two pilots and documented outcomes, Forge is out of the "no proof" bucket but not yet in the "proven at scale" category. Competitive alternatives (legacy quality management systems, manual inspection, consultants) exist but none deliver real-time edge detection. Forge settled on 23–24% — $42,000 — as the right point: above the gross margin floor ($30,000 platform + $12,000 hardware = $42,000 ACV total, with the hardware cost as a separate one-time line item per site), below the threshold that triggers multi-level procurement approval in the customer organizations.

3

Present the math to the customer — do not hide it

In the contract negotiation, Forge walked both customers through the EVC calculation using the customer's own data from the pilot. "Your line was down 4 times last year at an average of $85,000 per event. We reduced that by 1.4 events in the pilot. That is $119,000 in direct value. Our price is $42,000 — you keep $136,000, or 3.2x what you pay us." When customers see the math with their own numbers, the price becomes a ratio, not a number. Ratios are much easier to approve internally.

🔑 Forge Stage 3 milestone pricing math

Two annual contracts at $42,000 ACV each = $84,000 ARR. Business model: $30,000 annual SaaS platform fee + $12,000 one-time hardware fee per site (amortized into year-1 ACV for simplicity; hardware is a separate line item). Gross margin on first contracts: 61% blended ($30K software at ~80% GM + $12K hardware at ~25% GM). CAC: $18,000 (discovery + pilot + conversion sales effort). LTV at current churn estimate: approximately $165,000 (5-year implied retention at early churn assumptions). Payback: approximately 8.5 months on blended first-year economics (CAC $18K ÷ monthly gross profit of ~$2.1K). This unit economics profile — particularly the 61% gross margin and sub-12-month payback — is only achievable because the price was anchored to EVC, not to cost.

WEAKNESSWhere this bites

✗ The "reasonable-seeming" anchor — pricing without computing EVC

The most common failure mode is the founder who sets a price by intuition — "around $20,000 seems fair, it's a meaningful number but not scary" — without ever computing what the product is actually worth to the customer. This is not conservatism. It is an information failure. A $20,000 price on a product with $180,000 EVC is not cautious pricing — it is an 11% capture rate that forces your unit economics to fail (you cannot afford a salesperson, a customer success function, or meaningful R&D reinvestment at that margin). The "reasonable" price almost always anchors to what the founder can imagine charging, not what the customer gains. Those are almost never the same number, and the gap between them is systematically in the same direction: founders underprice by 3–10x.

✗ Confusing willingness-to-pay with EVC

Willingness to pay (WTP) is what a customer will pay in a negotiation. EVC is what your product is actually worth to them. These are not the same number, and using WTP as a proxy for EVC produces systematically wrong pricing. WTP is influenced by budget cycles, procurement authority, the customer's negotiating behavior, anchoring effects from your initial quote, and the alternatives they have considered. EVC is determined by the actual economic outcomes your product delivers. If a customer says "we have $25,000 budgeted for this kind of tool," that tells you about their budget process — it tells you nothing about whether their EVC is $80,000 or $800,000. Pricing to WTP without computing EVC leaves you with no basis to push back when a customer tries to negotiate you down — you cannot defend a number you arrived at by intuition.

✗ Overestimating EVC with unaudited assumptions

The opposite failure mode is inflating EVC by using optimistic inputs the customer did not actually provide. "Downtime events probably cost them $200,000 each" when your interview data has one person mentioning $85,000 and you rounded up because it felt conservative. Every component of EVC should trace to a specific customer statement, documented in your discovery interview notes. If a component is estimated rather than measured, flag it as such and use the low end of the range. An overinflated EVC that a customer can challenge line by line destroys the credibility of the entire pricing conversation. The EVC argument is only as strong as the weakest link in the data chain. If that link is your own guess, the customer will find it.

KEY INSIGHTHow this connects

  • 1.6 — Reading Signal: Real Pain vs. Polite Interest — the quantified pain data from Stage 1 interviews is the raw material for EVC computation. The distinction between "they mentioned the problem" and "they gave you a specific dollar figure for a downtime event" is the difference between an EVC estimate you can defend and one you invented. Lesson 1.6's framework for distinguishing real pain from polite interest tells you exactly which data points are strong enough to use in a pricing conversation.
  • 3.1 — Business Model Archetypes: What You Are and What You're Not — the business model you chose in Lesson 3.1 constrains both your gross margin target and the pricing motion available to you. Annual SaaS contracts require a different EVC argument than usage-based pricing or professional services. The EVC framework in this lesson is the next step after locking business model: you now know the structural form of your revenue, and this lesson tells you how to compute the number that goes into that structure.
  • 3.3 — Pricing Architecture: Tiers, Metrics, and Anchors → — once you have the base EVC and justified price range from this lesson, Lesson 3.3 shows how to architect it into a tier structure, select a pricing metric (per site, per seat, per inspection, per event), and create anchoring options that make the middle-tier selection feel like the obvious choice. EVC is the foundation; tier architecture is the packaging.

Value-based pricing is not a Stage 3 concept you apply once and move on. Every time you expand to a new customer segment — different industry, different size, different geography — EVC changes because the economic outcomes change. A mid-size plant and a mega-facility have radically different downtime costs and labor structures. The discipline of computing EVC per segment is how you build a defensible price structure rather than a single price that is wrong for half your customers.

GLOSSARYKey terms introduced

Economic Value to Customer (EVC)
The total economic gain a specific customer receives from your product over a defined period, net of the cost of their next-best alternative. Computed from positive differentiation value (gains from your product) minus negative differentiation value (adoption costs), anchored against the reference value (what the alternative delivers). EVC is the ceiling on defensible price.
Value capture rate
The fraction of EVC that the seller claims as price. Computed as price ÷ EVC. Typical early-stage B2B range: 10–30%. Constrained by competitive alternatives, proof level, customer switching costs, and gross margin requirements. The remaining fraction (1 − capture rate) stays with the customer as economic surplus — this is what makes the product worth buying.
Cost-plus pricing
Setting price by adding a target margin to the cost of delivery. Structurally wrong for startups because cost has no relationship to value created. Produces arbitrary prices that systematically underprice high-value products and may overprice low-value ones. The dominant default error of technical founders.
Competitive pricing
Setting price by benchmarking against comparable products in the market. Appropriate for commodity markets where products are substitutes; wrong for differentiated startups because it anchors to competitors' cost structures and value delivery, not yours. If your product is better, competitive pricing throws away the premium your differentiation creates.
Positive differentiation value
The incremental economic gains your product delivers relative to the customer's next-best alternative. Includes cost reductions (downtime prevented, defects avoided), revenue gains (throughput improvements, faster time to market), and risk reductions (warranty exposure, compliance risk). The largest component of EVC for most B2B products.
Negative differentiation value
The incremental costs and burdens your product imposes relative to the alternative. Includes integration labor, training, change management, SLA risk, and ongoing maintenance overhead. Subtracted from EVC. High negative differentiation reduces the defensible price ceiling and is the main reason enterprise buyers discount initial EVC claims.
Reference value
The value of the customer's next-best alternative — what they are currently using or would use if your product did not exist. Sets the baseline from which positive and negative differentiation are computed. A product that replaces a $40,000/year incumbent has a higher reference value than one that replaces a manual process that costs nothing to maintain.
Willingness-to-pay (WTP)
The maximum price a customer will accept in a negotiation, influenced by budget cycles, anchoring effects, procurement authority, and alternatives considered. Distinct from EVC, which is the actual economic value. WTP is almost always lower than EVC — the gap represents negotiation dynamics, risk adjustment, and information asymmetry. Using WTP as a proxy for EVC produces systematically wrong pricing.

ACTIVE RECALLCheck your understanding

Answer in your own words first, then reveal.

1A technical founder says: "Our cloud competitors charge $15,000/year so we priced at $18,000 to signal we're better." What is wrong with this reasoning, and what would the value-based approach require instead?›

The competitive anchor is wrong for two reasons. First, the competitor priced for their own cost structure, sales motion, and customer base — none of which apply to this founder. Second, if their product genuinely delivers more value than the competitor, they have thrown away the economic premium their differentiation creates. The value-based approach requires: (1) computing EVC from discovery interview data — what does the customer gain from this product that the competitor's product does not deliver? (2) expressing that incremental gain in dollars. (3) setting price as a fraction of total EVC. If the additional value over the competitor is $60,000/year, the price premium justified by differentiation is $12,000–$18,000 (at 20–30% capture), producing a price of $27,000–$33,000 — not $18,000. The founder used competitive pricing and systematically underpriced by 50%+.

2What is the difference between EVC and willingness-to-pay, and why does using WTP as a proxy for EVC produce systematically wrong pricing?›

EVC is what the product is actually worth in economic terms — the dollars saved, earned, or protected. WTP is what the customer will accept in a negotiation, shaped by budget processes, anchoring, procurement authority, and alternatives they have considered. WTP is almost always lower than EVC because it reflects the customer's information state and negotiating behavior, not the underlying value. Using WTP as a proxy for EVC produces systematically wrong pricing because: (a) if you anchor your initial ask to WTP, you start the negotiation too low and get negotiated down from there; (b) you have no basis to push back when customers try to reduce the price, because you have no independent calculation to defend; (c) WTP varies by prospect based on their budget cycle timing, not on the value your product delivers — so you will charge the same customer different amounts in different quarters, which is incoherent. EVC gives you an anchor that is independent of the negotiation — you compute it from their data, and then negotiate the capture rate, not the total.

3Forge's EVC calculator shows a total of $172,000 per site per year. A prospect says their budget cap for this category is $25,000. How should Forge respond, and what does this reveal about either the prospect or the pricing?›

First, distinguish between a budget constraint and a budget ceiling. "$25,000 is our budget for this category" may mean: (a) their procurement category has a low ceiling — in which case, the product is mis-categorized and the right response is to help re-categorize it as capex/safety/quality budget rather than IT software; (b) they genuinely believe the product is worth $25,000 — in which case, walk through the EVC calculation with their own data and ask them to identify which component is wrong; (c) it is a negotiating opener — in which case, hold the price and offer to reduce scope. What this situation reveals: if the prospect cannot challenge any specific component of the EVC calculation, the $25,000 budget constraint is either a categorization problem or a negotiating tactic. Forge should respond by presenting the EVC math ("you told us your downtime events cost $85K each and you had 4 last year — which of those numbers should we use a different estimate for?") and letting the customer either correct the math or acknowledge the constraint is structural rather than value-based. A budget constraint is not the same as a value argument.

4What is the capture rate floor set by gross margin requirements, and how does it differ from the competitive ceiling on capture rate?›

The gross margin floor is the minimum price you need to charge to hit your target gross margin given your actual COGS. If COGS per customer is $18,000 and you need 60% gross margin, minimum price is $45,000. As a fraction of EVC ($172,000), that is a 26% minimum capture rate. Below 26%, you are making a business model decision to accept lower gross margins — not a pricing strategy choice. The competitive ceiling is different: it is the maximum capture rate defensible given competitive alternatives, proof level, and customer switching costs. For an early-stage B2B startup, this is typically around 25–35%. When the gross margin floor is close to or exceeds the competitive ceiling, you have a structural problem: your cost structure prevents you from pricing at the level the market will accept. The only solutions are to reduce COGS (hardware cost, delivery efficiency, automation) or to find a customer segment with higher EVC that allows higher absolute price at the same capture rate. The EVC framework reveals this structural mismatch before you have scaled — when you can still fix it.

Next: turn your justified price range into a tier architecture that makes the right choice obvious →