Framework
The debt that builds as you grow:Value Debt
Everyone knows technical debt. The debt nobody sees builds up from the promises you make to users, and its interest is paid in churn.
Author: Alp SuleimanPublished
Definition
The gap between promise and delivery
Value debt is the gap that builds up, as you grow, between the value you promise users and the value you actually deliver.
Borrowing isn't wrong. Taking a shortcut to grab a market, make a funding round or settle in before a competitor is sometimes a smart choice. The problem is not knowing you borrowed, and never paying it back.
This page is the named, measurable version of the idea in the article of the same name. I turn what I described there into a framework here.
Value debt hides inside the growth chart. As the chart climbs, the debt grows, and because the two move in the same direction for a while, nobody notices.
Analogy
Technical debt's cousin
Both are taken on to move fast and both charge interest. The difference is that one sits in front of engineers and the other sits off the balance sheet.
- How it's taken
Technical debtShortcut code to ship faster.
Value debtPromising users more to grow faster.
- Who sees it
Technical debtEngineers. They like to complain.
Value debtNobody. It disappears into the growth chart.
- Interest
Technical debtEvery change gets a little slower.
Value debtEvery new cohort leaves a little earlier.
- Payment
Technical debtBy slowing down or rewriting.
Value debtIn churn, discounts or lost trust.
- Ledger
Technical debtMost teams keep one.
Value debtMost companies never do.
Sources
How the debt builds up
The routes I see in the field are few and familiar. Usually nobody acts in bad faith; each one looks reasonable that quarter.
- 01
Overpromising
Sales says something the product doesn't do yet to fill a quota. Marketing describes the product's best day as every day. The customer arrives with one expectation and meets another reality.
- 02
Features that never realize value
Features shipped for the roadmap that change nothing in the user's life. They launch, get announced, go unused. The product grows; the value doesn't.
- 03
Pricing above delivered value
Price rises faster than the value users receive. Year one is fine; at renewal the user redoes the math.
- 04
Onboarding gaps
A setup that never shows first value. The promise is made, but the user gives up or quietly stops using the product before seeing it kept.
- 05
Short-term tactics and neglected maintenance
Discounts, campaigns that inflate metrics, dark patterns; meanwhile slow flows stay unfixed. For existing users the product slowly gets worse.
Course
From principal to default
Like any debt, value debt moves through stages. Early on it is cheap; late it costs the whole company.
Principal
A promise is made, a gap opens
The first distance appears between promise and delivery. Nobody keeps a ledger. Metrics are still fine because users haven't started comparing yet.
Interest
The gap compounds daily
New cohorts retain worse than old ones. Support tickets fill with "why is it like this?" and "you told me this." Each renewal needs a little more discount.
Default
The debt is called in
Users leave in waves, renewals collapse, referrals stop. Paying it off now costs far more than what you borrowed.
Symptoms
Early signals
The bad thing about value debt is that it's noticed late. The good thing is that it signals early if you look carefully.
- 01
New cohorts leave sooner
If each wave stays shorter than the last, the distance between promise and delivery may be widening.
- 02
The kind of support ticket changes
"How do I do this?" gives way to "why is it like this?" The user came with an expectation and didn't find it met.
- 03
Discount dependence
If every renewal needs a bigger discount to hold, it isn't the price being questioned, it's the value.
- 04
Satisfaction and behavior split
Surveys are fine while depth of use drops. Satisfaction is a feeling, value is an outcome; when they diverge, believe the outcome.
Self-check
Value debt check
Ten statements. Answer yes or no honestly for your own company. The result is not a measurement, it is a qualitative reading of where you stand.
We don't write down the promises sales makes that the product doesn't yet keep.
Answers stay on this page: they are not written to the link, and no separate request is made to send them. This is not a diagnosis; it is a mirror to start a conversation.
Repayment
How to pay it down
- 01
Make the debt visible
Teams that manage technical debt keep a ledger. Do the same for value debt: promises sales made that product doesn't keep, inflated metrics, deferred maintenance. Debt you don't write down is debt you forget to pay.
- 02
Set a repayment rhythm
Each quarter, give a share of capacity to work that ships nothing new but repairs existing value. It brings no announcement; it brings retention.
- 03
Ask before you borrow
Before saying yes to a tactic, campaign or promise, one question: does this really change something in the user's life, or just this quarter's chart? If it's the latter you can still do it, but you know you borrowed.
- 04
Name the owner
No single team can pay value debt. It needs everyone from sales to product, which means a place that meets regularly and can decide.
- 05
Watch behavior, not surveys
Time to first value, depth of use and cohort retention. Surveys are polite; behavior isn't.
Frequently asked
What is value debt?
The gap that builds up, as you grow, between the value you promise users and the value you actually deliver. Its interest is paid quietly, in churn.
How is value debt different from technical debt?
Both are taken to move fast and both charge interest. Engineers see and discuss technical debt. Value debt disappears into the growth chart, so most of the time nobody tracks it.
Is borrowing always wrong?
No. Taking a shortcut to grab a market or make a funding round can be smart. The problem is not knowing you borrowed, not recording it and never paying it back.
How do I measure value debt?
There is no single number. Read new-cohort retention, time to first value, the type of support tickets and the discount needed at renewal together. The check above turns that view into a rough reading.
Let's look together
Let's work out how much debt you carry
I read the gap between promise and delivery through cohorts, pricing and onboarding. We start with a short exchange.