whether you are building a wasting asset or a compounding one
Your engineering team pitches two projects, each requiring $200K in salary and three months of work. Project A: build a custom integration with a third-party vendor's reporting API. Project B: build an internal data pipeline that structures every customer interaction in a format you control. Both ship on time. Eighteen months later, Project A costs $5K/month to maintain against a deprecated API and delivers less value every quarter. Project B powers your Pricing engine, feeds your Scoring Model, and gets more valuable with every new customer. Same investment. Opposite trajectories. The difference: one was a Wasting Asset, the other was a Compounder.
A Wasting Asset is an Asset that loses economic value over time regardless of how well it was built. The single most important Capital Allocation question an Operator faces is whether each dollar builds something that decays or something that compounds.
A Wasting Asset is any Asset whose economic value declines over time, eventually reaching zero or near-zero. The decline is structural - it happens because of how the world changes around the Asset, not because you built it badly.
This is different from Depreciation, which is an accounting method for spreading the cost of a Capital Asset across multiple periods on your P&L. Depreciation is a Ledger entry. Wasting is an economic reality. A server you Depreciate over 3 years on your Balance Sheet might actually be worthless in 18 months if the software it runs becomes Obsolete. Or it might still be productive at year 5. The accounting schedule and the actual value trajectory are independent.
The classic examples outside of business: options lose value as they approach expiration, oil wells deplete, patents expire. Inside a business, the examples that matter to Operators are subtler - custom integrations, vendor-locked workflows, Marketing Spend with no lasting Asset, and software built on assumptions that will change.
Every dollar you allocate either builds something that compounds or something that decays. Over a long enough Time Horizon, this distinction dominates every other Capital Allocation decision.
Consider two Operators who each control a $2M annual Budget for technology investments. Operator A spends 70% on projects that compound - internal Knowledge Capital, proprietary data systems, reusable platforms. Operator B spends 70% on projects that waste - custom vendor integrations, one-off client builds, quick fixes that become permanent. After three years, Operator A's cumulative investment generates increasing Returns. Operator B spends just to maintain what already exists.
For PE-Backed businesses, the impact is amplified. Valuation multiples are applied to EBITDA, and EBITDA reflects ongoing costs. If your technology Portfolio is dominated by Wasting Assets, your maintenance costs grow every year - dragging EBITDA down right when you want it climbing toward an exit. A Portfolio of compounding Assets does the opposite: the initial Capital Investment is behind you, and the value keeps delivering with lower incremental cost.
The P&L tells you what you spent. Whether that spend built a Wasting Asset or a Compounder - that only becomes visible with time.
Three forces turn Assets into Wasting Assets:
1. Obsolescence
The world moves and your Asset does not. A vendor changes their API. A platform sunsets a feature you depend on. A regulation shifts. The Asset was valuable in the context that existed when you built it, and that context no longer exists. For software, Obsolescence is the dominant force - the technology ecosystem changes fast enough that anything tightly coupled to external dependencies has a limited window of value.
2. Competitive Erosion
What was once a Competitive Advantage becomes a Commodity. You built a feature that differentiated you in 2024. By 2026, every competitor has it. The Asset still works, but it no longer generates outsized Revenue or justifies premium Pricing. Its market value has fallen even though its Book Value on the Balance Sheet has not.
3. Knowledge decay
The people who built and understood the Asset leave. Documentation was thin. Tribal Knowledge walks out the door. The Asset technically still functions, but nobody can safely modify, extend, or debug it. Maintenance costs rise, reliability drops, and eventually it becomes cheaper to rebuild than to sustain.
Contrast these with compounding Assets - things like a Data Moat (more data makes the system smarter, attracting more users who generate more data), Knowledge Capital embedded in well-documented systems, or a platform architecture where each new capability makes every existing capability more valuable. Compounding Assets create a Feedback Loop: usage increases value, which increases usage.
The practical test is simple: will this Asset be worth more or less in 18 months if we do nothing beyond basic maintenance? If less, it is wasting. If more, it is compounding. If roughly the same, it is neither - just a standard Depreciating Asset, which is fine, but should not be confused with a strategic investment.
Apply the wasting-vs-compounding lens whenever you are making a Capital Allocation decision about where to invest engineering time, Marketing Spend, or operational effort.
Build decisions: Before greenlighting a project, ask what happens to its value over time. If the answer is "it decays unless we keep investing," you are signing up for ongoing costs. That might be acceptable if the near-term ROI justifies it - but you need to account for the full lifecycle cost, not just the build cost.
Build, Buy, or Hire decisions: Buying a SaaS tool is explicitly renting - you pay monthly, you get monthly value, nothing compounds. That is honest and sometimes correct. The trap is building a custom solution that feels like ownership but behaves like renting because it wastes just as fast.
Portfolio review: At least quarterly, look at your technology investments as a Portfolio. What fraction is compounding? What fraction is wasting? If most of your engineering capacity goes to maintaining Wasting Assets, you have a structural problem - your Cost Structure is rising while your Competitive Advantage is not.
Hiring and team resource allocation: Engineers maintaining Wasting Assets are not building future value. This is the opportunity cost that does not show up on any Financial Statement but determines whether your business compounds or treads water.
Your business allocates $200K (two senior engineers for five months) to build a custom integration with a third-party analytics vendor. The integration automates reporting that currently costs $8K/month in manual Labor. A competing proposal asks for the same $200K to build an internal data pipeline that captures every customer interaction in a structured format you control.
Year 1 - Vendor integration: Manual Labor eliminated. Savings = $96K/year. ROI looks strong: $96K return on $200K investment. Net position: -$104K (still paying back the build cost).
Year 1 - Internal pipeline: Saves only $40K in direct Labor (less immediate payoff). But every new customer adds data that improves your Scoring Model accuracy. Net position: -$160K. Looks worse.
Year 2 - Vendor integration: Vendor deprecates the API version you built on. Rebuild cost: $60K. Vendor raises Pricing 30%. Net savings drop to $50K/year after maintenance. Cumulative return: ($96K + $50K - $60K) = $86K on a $200K investment over 2 years.
Year 2 - Internal pipeline: 12,000 new customers have flowed through. The Scoring Model now drives a Pricing tier that generates $180K in incremental Revenue. Maintenance: $20K/year. Cumulative return: ($40K + $180K - $20K) = $200K over 2 years - and accelerating.
Year 3 - Vendor integration: Vendor announces end-of-life for the product. You need $150K to migrate or lose the automation entirely. The Asset's market value is effectively zero.
Year 3 - Internal pipeline: Now powering three downstream capabilities (Pricing, customer segmentation, Churn prediction). Incremental Revenue contribution: $300K/year. The Asset is worth more than the day you built it.
Insight: The vendor integration had a better Year 1 ROI but was a Wasting Asset - its value depended on external factors you did not control. The internal pipeline had a worse Year 1 ROI but was a Compounder - its value grew with usage. Over a 3-year Time Horizon, the compounding Asset returned roughly 2.5x more cumulative value on the same initial investment.
You have $50K per quarter allocated to customer acquisition. Option A: spend it on paid ad slots ($50K/quarter, generating leads only while you pay). Option B: invest in a content library - technical articles, guides, and tools ($50K/quarter in engineering and writing time). Evaluate over 4 quarters, then stop all spending and observe.
Quarter 1 - Paid ads: $50K generates 500 leads at $100 Cost Per Unit. Stop spending, leads go to zero immediately.
Quarter 1 - Content library: $50K produces 12 articles. They generate 80 leads in Q1 (still being indexed, low traffic). Cost Per Unit: $625/lead. Looks terrible.
Quarter 4 - Paid ads: You have spent $200K total. You generated 2,000 leads total (500/quarter, consistent). If you stop spending today, future leads = 0. The $200K produced no lasting Asset.
Quarter 4 - Content library: You have 48 articles. The early ones now rank well and generate steady traffic. Total leads to date: 80 + 140 + 180 + 200 = 600. Fewer than ads so far, but the trend is upward.
Quarter 8 (zero additional spend in either channel): Paid ads have generated zero leads since Q4. Content library has generated an additional ~800 leads at zero marginal cost over Q5-Q8. Total content leads (1,400) now exceed total paid leads (2,000 and frozen). By Quarter 10, content will have generated more total leads on half the lifetime investment.
Insight: Paid ads are a Wasting Asset by design - value exists only while you are spending. A content library is a compounding Asset - it builds on itself and generates Returns long after the investment stops. Most Operators need a mix of both, but you must know which dollar is renting and which is building.
The test for a Wasting Asset is straightforward: will it be worth more or less in 18 months with only basic maintenance? If less, it is wasting. If more, it is compounding.
Accounting Depreciation and actual value decay are independent. An Asset can be fully Depreciated on the Balance Sheet but still productive, or carried at full Book Value but economically worthless.
The compounding-vs-wasting distinction is the highest-Leverage question in Capital Allocation because it determines whether your past investments help future performance or drag it down.
Judging investments only on Year 1 ROI. Wasting Assets often look better in the short term because they deliver immediate value with a clean payback story. The decay only becomes visible in Year 2 or 3 - by which point you have already committed the Budget and the team.
Treating all Capital Investments as equivalent on the Balance Sheet. Two Assets with the same Book Value can have wildly different economic trajectories. One is compounding, the other is heading toward zero. The Balance Sheet does not distinguish between them - only your judgment as an Operator does.
Classify each of the following engineering investments as Wasting Asset, Compounder, or neither (a standard Depreciating Asset): (1) A custom Slack bot that automates internal approval workflows, (2) A machine learning model trained on 3 years of customer behavior data, (3) A laptop for a new hire, (4) A white-label integration built for a single enterprise client's proprietary system.
Hint: For each one, ask: does its value increase with usage or time? Does it depend on external factors you do not control? Is it generic infrastructure or strategically differentiating?
(1) Neither - standard Depreciating Asset. It saves time but does not compound or erode quickly. It needs occasional updates but is relatively stable and internally controlled. (2) Compounder - more data over time improves the model, which drives better decisions, which attracts more customers who generate more data. Classic Feedback Loop. (3) Neither - standard Depreciating Asset. Predictable decline, no strategic value, easy to replace. (4) Wasting Asset - its value depends entirely on that one client and their proprietary system. If the client churns or changes their system, the integration is worthless. High Obsolescence risk and zero reuse value.
Your team maintains 14 internal tools. Total annual maintenance cost: $420K ($30K average per tool). You suspect most are Wasting Assets consuming engineering capacity that could go toward compounding investments. Design a process to audit the Portfolio and decide which tools to sunset, rebuild, or keep. What data would you collect for each tool?
Hint: Think about what drives value decay: external dependencies, usage trends, Tribal Knowledge concentration, and the gap between Book Value and actual economic value.
For each tool, collect five data points: (1) Usage trend - monthly active users or API calls over the last 12 months. Declining usage signals wasting. (2) Dependency risk - count external API dependencies and check their deprecation status. More external dependencies = higher Obsolescence risk. (3) Knowledge concentration - how many engineers can safely modify this tool? If the answer is 1 or 2, Tribal Knowledge decay is a critical risk. (4) Maintenance cost trajectory - is annual maintenance rising or falling? Rising costs on declining usage is the signature pattern of a Wasting Asset. (5) Revenue or cost-saving attribution - what Revenue or Cost Reduction does this tool enable? Then apply decision rules: Sunset tools with declining usage + rising maintenance + high dependency risk. Rebuild tools with high value attribution but high decay risk (rebuild on internal, controlled foundations so the replacement compounds). Keep tools with stable usage, low maintenance, and low dependency risk.
You are an Operator at a PE-Backed SaaS company. The CFO asks you to cut $500K from your $3M engineering Budget. You can cut from two areas: (A) a team maintaining legacy integrations that currently serve 15% of Revenue ($1.8M ARR), or (B) a team building a new internal platform that has generated zero Revenue so far but creates a growing Data Moat. The PE firm plans to exit in 24 months. Which do you cut and why?
Hint: Think about Time Horizon and what drives Valuation at exit. Consider what happens to Revenue if you cut the legacy team vs. what happens to long-term Valuation if you cut the compounding investment. Run Expected Value on both scenarios.
This is a genuine tension. Cutting the legacy team (A) saves $500K but risks $1.8M in ARR. If even half those customers Churn without integration support, you lose $900K/year in Revenue. At a 10x EBITDA multiple, that could reduce Enterprise Value by $9M. You would need a migration plan to move those customers to alternatives before cutting. Cutting the platform team (B) preserves current Revenue but kills the compounding Asset. With only 24 months to exit, the Data Moat may not mature enough to measurably impact Valuation. The Operator's framework: Calculate the Expected Value of each option. For (B), estimate: what is the probability the platform demonstrably improves EBITDA (through Throughput gains or Churn reduction) within 12 months, and by how much? If there is a 40% chance it adds $300K/year to EBITDA, the Expected Value of its Valuation impact at 10x is 0.4 x $3M = $1.2M - exceeding the $500K cost. Keep it. If the probability is lower or the timeline is longer than the exit window allows, the rational move is to cut (B) and protect the Revenue-generating Asset, even though it is wasting. Time Horizon changes which side of the wasting-vs-compounding tradeoff wins.
This concept builds directly on Asset - you already know that Assets are durable stores of future economic value recorded on the Balance Sheet, and that the distinction between capitalizing and expensing affects EBITDA. Wasting Asset adds a critical dimension: not all Assets are equal over time. Some decay toward zero (Wasting Assets), some hold steady (standard Depreciating Assets like equipment), and some grow in value (Compounders). This distinction connects forward to Obsolescence (the primary force that makes technology Assets waste), Competitive Erosion (the market force that turns differentiation into Commodity), Knowledge Capital and Data Moat (two of the strongest compounding Assets an Operator can build), and Capital Allocation (the discipline of deciding where each dollar goes). When you later encounter EBITDA Optimization, you will see how a Portfolio dominated by Wasting Assets creates a rising Cost Structure that drags down the metric PE firms use to price your business - while a Portfolio of compounding Assets does the opposite, generating increasing Returns on a fixed or declining cost base.
Disclaimer: This content is for educational and informational purposes only and does not constitute financial, investment, tax, or legal advice. It is not a recommendation to buy, sell, or hold any security or financial product. You should consult a qualified financial advisor, tax professional, or attorney before making financial decisions. Past performance is not indicative of future results. The author is not a registered investment advisor, broker-dealer, or financial planner.