theonline.mba
← Back to unit 1: How Businesses Create Value

OMBA 101 · Unit 1 · Lesson 2 of 5

Value Creation, Delivery, and Capture

How Businesses Create Value

Lesson

Why "customers like us" is not a strategy

Managers often collapse value into a single feeling: customers like the product, so the business must be healthy. That shortcut fails in boardrooms every quarter. A newspaper can create enormous reader value, deliver it reliably every morning, and still capture too little revenue when advertising shifts to platforms. A startup can build a delightful mobile app, deliver it poorly at scale, and capture nothing because unit economics never work. A manufacturer can create a superior machine, deliver it on time, and capture thin margin because five competitors offer "good enough" at lower price.

You cannot diagnose performance without naming which leg of value is broken. Lesson 1 explained why firms exist: they reduce transaction costs by coordinating inside a boundary. This lesson explains what firms must coordinate for: creating something customers want, delivering it reliably, and capturing enough of the result to survive and invest.

Value breaks into three separable activities:

  1. Creation: producing an offer customers perceive as worth more than its cost to produce
  2. Delivery: getting that value to customers consistently at acceptable cost
  3. Capture: converting delivered value into revenue and profit the firm retains

A business can excel at one corner and fail at another. Your job as a manager is to see the triangle clearly, measure each corner, and align decisions so the three do not fight each other.

Value creation: willingness to pay

Value creation is about willingness to pay (WTP): the maximum a customer would pay for your offer versus realistic alternatives, before they walk away. WTP is not a survey question about features. It is an economic ceiling anchored to outcomes, risk reduction, and alternatives.

WTP rises when you solve a painful job to be done (the real progress a customer hires your product to make): reduce risk, save time, increase revenue, or remove embarrassment. WTP rises when you differentiate on dimensions customers actually fund, not dimensions engineers love in isolation. WTP rises when you build trust and reduce uncertainty through brand, guarantees, references, and proof.

Creation is therefore economic, not aesthetic. A beautiful interface on a product that does not change a customer's P&L or personal outcome has weak WTP. A plain interface that prevents a $2 million compliance fine has strong WTP.

TermPlain meaning
WTPWillingness to pay: the highest price a customer would accept before choosing an alternative
Customer surplusWTP minus price paid: the value customers keep after the transaction
Economic impactMeasurable outcome (revenue gained, cost avoided, risk reduced) that anchors WTP
Job to be doneThe underlying progress the customer seeks, not the product category label

Consider a mid-market retailer evaluating inventory analytics. Spreadsheets "cost" little in software fees but consume analyst time and produce slow, error-prone decisions. Hiring a data analyst costs salary and recruiting risk. A specialized vendor may charge subscription fees but prevent stockouts. WTP for the vendor is anchored to stockout cost and decision speed, not to dashboard aesthetics alone.

From Lesson 1, remember that firm boundaries affect creation. If engineering is outsourced to a vendor who does not attend customer calls, learning about jobs to be done slows. Creation weakens even if delivery and pricing stay unchanged.

Value delivery: cost to serve

Value delivery is cost to serve (CTS): everything required to get created value into the customer's hands consistently after the sale. CTS includes manufacturing or service fulfillment, onboarding, customer success, logistics, uptime, returns, support, and the complexity of the sales motion.

Creation minus delivery is not profit. It is value available to split between customer surplus and firm capture. If you create $10,000 of economic value for a customer but spend $9,500 delivering it, only $500 remains to share through price and margin.

Delivery costs must often scale sub-linearly with customers for the model to work. A SaaS (software as a service, subscription software delivered over the internet) company that assigns forty hours of implementation for a $30,000 ACV (annual contract value, yearly revenue per customer contract) may create value on paper but deliver it at unsustainable CTS. That is why SaaS firms pushed product-led growth: customers activate in the product with minimal services headcount.

SymptomLikely delivery problem
High NPS during sales, low NPS after month twoOnboarding and time-to-value
Gross margin falls as revenue growsServices intensity or infrastructure cost
Support tickets rise faster than usersProduct complexity or documentation debt
Enterprise deals stall in legal and security reviewDelivery motion too heavy for segment

Managers often blame "product" when the failure is delivery. The product may create value in a demo while humans, processes, and infrastructure fail to transfer that value to the customer's daily workflow.

Value capture: pricing power and model design

Value capture is what the firm keeps after delivery: price minus variable cost, scaled by volume, sustained over time. Capture depends on pricing power (how much of created value you can charge without losing the customer), model design (subscription, usage, take rate, bundling), competitive pressure, and retention.

Capture is a stream, not a point. A single large invoice means little if churn destroys the next three years. Strong firms think in customer lifetime value (LTV, total profit expected from a customer relationship) and expansion revenue (additional sales to existing customers), not invoice size alone.

Common trap: maximizing short-term capture destroys creation. Aggressive upsells, dark patterns, or nickel-and-diming raise revenue this quarter and churn next year. Customers remember fairness. B2B buyers remember broken trust when contracts renew.

Capture also interacts with Lesson 1 boundaries. A take-rate marketplace captures value without owning inventory, but must invest in trust and dispute resolution (delivery) to keep both sides on the platform.

Capture leverRisk if overused
Price increaseChurn unless WTP justified
Reduced service levelsDelivery collapse
BundlingHidden cross-subsidy confusion
Contract lock-inCreation erodes when alternatives improve

The value triangle diagnostic

Picture a triangle with Creation, Delivery, and Capture at each corner. Sustainable businesses align all three deliberately. Misalignment produces recognizable symptoms.

SymptomLikely weak corner
Great NPS (Net Promoter Score, a survey measure of whether customers would recommend you), weak conversionCapture (price, packaging, sales motion)
Sales wins deals, customers churn in 60 daysDelivery
High churn at signup, low engagementCreation (job not solved)
Margins collapse as you scaleDelivery
Commoditized price warsCreation (undifferentiated job)
Investors love product demos, unit economics failDelivery and capture

Operating rule: Changes to one corner must be stress-tested against the other two. If you cut onboarding (delivery), model impact on activation and retention (capture). If you add features (creation), model CTS and price elasticity. If you raise prices (capture), model WTP against alternatives and churn.

Strategy fails when corners fight. Sales promises creation the product cannot deliver. Finance pushes capture through price increases while CTS rises. Operations cuts support headcount in ways that destroy WTP (long wait times erode trust).

Coherence across an industry: same triangle, different choices

Industries look different because players choose different coherent triangles. Neither choice is universally "better." Each must be internally consistent.

Premium airline carrier

  • Creation: schedule convenience, lounges, status, fewer cancellations for time-sensitive travelers
  • Delivery: complex hub network, higher crew ratios, expensive maintenance, dense airport infrastructure
  • Capture: business travelers with low price sensitivity on schedule reliability

Budget airline carrier

  • Creation: lowest fare on a route for price-sensitive travelers
  • Delivery: point-to-point routes, fast aircraft turns, unbundled fees
  • Capture: ancillary revenue for bags, seats, and priority boarding

The budget carrier does not try to win on lounge experience. The premium carrier does not try to win on lowest base fare. Each aligns corners. A premium carrier that cuts maintenance (delivery) to fund marketing (capture) may destroy the WTP that justified premium pricing.

This lesson sets up Lesson 3, where customers, employees, and owners each experience value creation, delivery, and capture differently. Employees may bear delivery cost in workload. Owners may push capture through margin targets. Customers experience creation minus price. Lesson 4 will show how marketing, sales, product, and operations own different corners of the triangle.

Measuring each corner without fooling yourself

Managers need metrics that map cleanly to creation, delivery, or capture. Mixed metrics create mixed decisions.

For creation, look for evidence that WTP is real: win rates against alternatives, customer willingness to expand usage, references that cite economic outcomes (time saved, revenue gained, risk reduced), not only "nice UI." Surveys about feature satisfaction can rise while WTP falls if a cheaper alternative becomes good enough.

For delivery, measure time-to-value, failure rates, support load per customer, and cost per successful outcome. A SaaS company should know how many onboarding hours and support tickets separate a retained account from a churned account. A manufacturer should know OTIF and warranty claims per thousand units.

For capture, track gross margin after delivery costs, net revenue retention, payback period on CAC, and cash conversion. Capture metrics that ignore CTS produce phantom success: revenue grows while contribution margin shrinks.

CornerUseful metricsMisleading proxy
CreationOutcome-based win reasons, expansion rateRaw NPS without economic anchor
DeliveryTime-to-value, cost per live customerFeature shipment count
CaptureContribution margin, NRR, CAC paybackBookings without services cost

When a metric improves on one corner but system health worsens, you are likely exporting cost to another corner. Cutting support may raise capture this quarter and destroy creation next quarter when reviews turn negative. Adding services may raise delivery cost while saving creation for complex customers who would otherwise fail. The triangle is a system, a theme Lesson 5 develops fully.

Pricing and model design as capture choices

Capture is not only "what price sticker we put on the website." It is how you design the business model: subscription versus usage, bundling versus unbundling, take rates on a marketplace, freemium with paid conversion, or hardware subsidized by consumables.

Each model shifts who bears delivery cost and when cash arrives. Usage-based pricing aligns capture with value delivered but can scare customers who want predictable budgets. Subscriptions improve capture predictability but can undercharge heavy users who receive high creation. Take-rate models capture value without owning inventory (Lesson 1 boundary choice) but require trust and dispute resolution as delivery infrastructure.

Good capture design asks: What portion of created value can we charge for without destroying adoption? That is a judgment call, not a spreadsheet cell. It requires knowing alternatives, customer budgets, and delivery credibility. Undercharging leaves money on the table. Overcharging without delivery proof invites churn and competitor trials.


Worked example: RetailMax analytics (WTP anchored to economics)

RetailMax is a regional apparel retailer with 120 stores and $310 million in annual revenue. It evaluates InsightLoop, a B2B analytics subscription priced at $3,000 per month.

Part A: Alternatives and hidden costs

AlternativeMonthly costHidden cost
Spreadsheets plus one analyst$1,200 salary allocationSlow decisions, formula errors
Hire a data analyst$8,000+ fully loadedRecruiting risk, 90-day ramp
Competitor dashboard$2,500Less inventory-specific models

RetailMax loses roughly $50,000 per month in margin from stockouts and markdowns on key SKUs because replenishment decisions lag by a week.

Part B: WTP logic

If InsightLoop credibly prevents even half the stockout and markdown loss, economic value is $25,000 per month. WTP could approach that ceiling before the buyer chooses status quo. The $3,000 list price is low relative to impact, which suggests either weak capture by the vendor or skepticism about delivery (will the tool actually change decisions in stores?).

RetailMax's buyer asks: "Who acts on alerts, and how fast?" That is a delivery question, not a feature question.

Part C: CTS for the vendor (InsightLoop)

InsightLoop assigns 30 hours of implementation and trains district managers. If InsightLoop sells 200 accounts with a ten-person services team, delivery limits growth. CTS per customer must fall via templates and in-product onboarding, or capture (price) must rise, or churn will follow.

Part D: Managerial read

RetailMax COO: Approve pilot if time-to-first-action on alerts is under 72 hours in five stores. Measure markdown rate, not dashboard logins.

InsightLoop CEO: Price may be too low relative to WTP, but raising price without delivery proof will fail. Capture follows demonstrated creation and delivery.

Check: Economic value at stake $25,000/month vs price $3,000/month implies customer surplus $22,000/month if fully believed. Sustainable capture requires proof. ✓


Worked example: CloudMint SaaS (broken corner diagnosis)

CloudMint sells workflow software to law firms. ACV is $24,000. Gross NPS is 62. Revenue growth is 28% year over year. Yet the company burns cash and CAC (customer acquisition cost, sales and marketing spend to win one new customer) is 1.4× first-year gross profit.

Part A: Triangle assessment

CornerEvidence
CreationStrong NPS, customers praise time saved on document review
Delivery90-day implementation, 2.3 FTE customer success per $1M ARR
CaptureDiscounting to win deals; net revenue retention 94%

Part B: Unit economics sketch

LineAmount
ACV$24,000
Gross margin after hosting78% → $18,720
Allocated implementation CTS (one-time)($9,500)
First-year gross profit after implementation$9,220
CAC($12,900)
First-year net contribution($3,680)

Check: $18,720 − $9,500 − $12,900 = ($3,680) ✓

Creation is real. Capture and delivery destroy viability. CloudMint buys growth that loses money.

Part C: Intervention options

  1. Delivery: Reduce implementation to 30 days via templates; cap services hours per deal.
  2. Capture: Raise price on new segment with mandatory self-serve tier; stop discounting below $20,000 ACV.
  3. Creation: Narrow ICP (ideal customer profile, the segment where product fit is strongest) to firms with standardized workflows.

Part D: Board questions

  1. Which customer segment shows positive first-year contribution after CTS?
  2. What onboarding step drives most hours, and can product remove it?
  3. If we fix delivery, what price tests WTP without killing win rate?

Investor takeaway: High NPS does not equal a business. Diagnose the triangle before funding sales hiring.


Common mistakes beginners make

MistakeReality
Equating value creation with product featuresWTP follows economic outcomes and alternatives
Ignoring delivery when measuring successDemos create value; onboarding transfers it
Treating revenue as capture successDiscounting and services-heavy deals can destroy profit
Maximizing short-term price without retention modelCapture is a multi-year stream
Copying competitor pricing without copying their triangleDifferent delivery costs support different prices
Using NPS alone as health metricHigh NPS with negative unit economics is a delivery/capture problem
Assuming lower price always raises WTPLow price can signal low quality and shrink WTP

The most common executive error is celebrating creation metrics (engagement, NPS, awards) while delivery CTS and capture mechanics leak cash. The second is cutting delivery cost in ways that silently reduce WTP, such as support waits that erode trust.


Practice problem

HarborDesk sells customer support software to e-commerce merchants. Facts:

ItemValue
Average ACV$18,000
Gross margin80%
Monthly stockout-style downtime cost for merchant (if product fails)$40,000
HarborDesk prevents an estimated 70% of that downtime
Implementation labor cost to HarborDesk$6,000 one-time
Ongoing support cost to HarborDesk$2,400/year
Proposed price increasefrom $1,500/month to $1,800/month

Tasks:

  1. Estimate merchant economic value created per month if claims are believed.
  2. Compute HarborDesk first-year gross profit per customer after implementation and ongoing support.
  3. Will a $300/month price increase likely destroy WTP? Explain using customer surplus.
  4. Name one delivery improvement and one capture improvement HarborDesk should test.

Solution

1. Monthly economic value created

Downtime cost $40,000 × 70% prevented = $28,000 per month economic value if credible.

2. First-year gross profit per customer

Revenue Year 1 at current price: $18,000
Gross profit at 80%: $14,400
Less implementation: ($6,000)
Less ongoing support: ($2,400)
First-year contribution: $6,000

Check: $14,400 − $6,000 − $2,400 = $6,000 ✓

3. Price increase and WTP

Increase adds $3,600 per year ($300 × 12). Customer surplus before increase at full belief: ($28,000 × 12) − $18,000 = $336,000 − $18,000 = $318,000 annually (illustrative ceiling if merchant values all prevented downtime). After increase: $336,000 − $21,600 = $314,400. Surplus remains large if trust is high.

A $300/month increase likely does not destroy WTP if HarborDesk proves prevention credibly. If proof is weak, WTP collapses regardless of list price because merchants revert to status quo risk.

4. Improvements

Delivery: Publish uptime dashboards and incident root-cause reports to reduce buyer skepticism; reduce implementation below $6,000 with automated connectors.

Capture: Introduce usage-tier pricing for high-volume merchants who receive disproportionate value, capturing more WTP without raising base price for small merchants.


Practice problem 2 (conceptual)

Classify each scenario as primarily a creation, delivery, or capture problem:

  1. Customers love the demo but cancel during onboarding.
  2. Product is unique but sales keeps discounting 30% to hit quota.
  3. Churn is low but prospects say "your competitor is good enough at half the price."
  4. Gross margin falls as revenue rises because each new customer needs heavy services.

Explain one cross-corner interaction in scenario 4.

Solution

  1. Delivery (time-to-value and onboarding failure).
  2. Capture (pricing discipline and sales incentives); may also signal weak creation proof if discounts are needed to close.
  3. Creation (differentiation and WTP vs alternatives); competitor "good enough" compresses WTP ceiling.
  4. Delivery (services intensity); drives capture failure because margin available to the firm shrinks even when price holds.

Cross-corner interaction in 4: Heavy services (delivery) reduce gross margin available for reinvestment in product (creation), which eventually weakens WTP and forces price cuts (capture). The triangle degrades in sequence.


Key takeaways

  • Creation, delivery, and capture are distinct; conflating them blinds diagnosis.
  • WTP is economic, anchored to alternatives and measurable outcomes.
  • Cost to serve must scale for the business model to work at volume.
  • Sustainable strategy aligns all three corners; misalignment shows up in unit economics.
  • From Lesson 1, firm boundaries shape delivery cost and learning speed for creation.

After this lesson

  1. For your current company, which corner of the value triangle is strongest? Which is weakest? Name one metric that proves your answer.
  2. Find one customer complaint that maps to delivery, not product features.
  3. Continue to Lesson 3: Customers, Employees, Owners, and Other Stakeholders.

Lesson exercise

40 min

Apply: Value Creation, Delivery, and Capture

Using your anchor company (or Business Foundations and Managerial Thinking default), complete a focused exercise on **Value Creation, Delivery, and Capture**. 1. Write the decision frame (choice, owner, date, constraints). 2. Apply the lesson framework with at least one table and one explicit assumption. 3. Add a downside scenario and a guardrail metric. 4. Conclude with a recommendation and what would change your mind.

Deliverable

One-page workbook entry or memo section filed under OMBA 101 Unit materials.

Rubric

  • Decision frame is specific and time-bound
  • Framework applied with auditable steps
  • Downside case is plausible, not strawman
  • Guardrail metric defined with owner
  • Recommendation links to evidence quality label