The EBITDA trap is real, but it is not inescapable. The most powerful tool engineering leaders have is Labor Capitalization — reclassifying engineer salaries from OpEx to CapEx.
The Accounting Rule
GAAP (ASC 350-40) and IFRS (IAS 38) allow companies to treat software engineer salaries as CapEx when those engineers are building a new, long-lived internal asset. The logic: if a server purchase is CapEx because it creates a long-term asset, then the engineering labor that creates equivalent software should be treated the same way.
The key distinction is what the engineer is doing:
| Activity | Classification | Rationale |
|---|---|---|
| Fixing bugs / maintenance | OpEx | Restores asset to original state; creates no new value |
| Keeping systems running (on-call, ops) | OpEx | Day-to-day operations |
| Building new features / new services | CapEx | Creates a new long-term asset |
| Major enhancements that extend asset life | CapEx | Increases the asset's value or useful life |
| Research / feasibility / prototyping | OpEx | Pre-capitalization phase; outcome uncertain |
The Strategy in Practice
If your Platform Team spends 6 months building a new Internal Developer Platform (IDP), that $1M of salary cost can be reclassified from OpEx to CapEx.
- This removes $1M from the OpEx line, directly increasing EBITDA by $1M.
- The $1M is then amortized over the software's useful life (typically 3–5 years), adding only ~$250K/year back as an expense below the EBITDA line.
- Net EBITDA improvement in year one: approximately $750,000.
How FinOps Teams Execute This
FinOps and Finance teams track engineering time rigorously to maximize the amount classified as CapEx:
- Jira / Linear tagging: Engineers tag tickets as "CapEx" or "OpEx" work. Finance audits these quarterly.
- Time tracking: Engineers log hours against capitalizable projects. Even 20% of a team's time on a new feature can be capitalized.
- Project phase tracking: Finance distinguishes between the "preliminary project stage" (OpEx), "application development stage" (CapEx), and "post-implementation stage" (OpEx).
- Audit trail: Every capitalized dollar must be defensible to auditors. Vague ticket descriptions like "worked on platform stuff" will not survive scrutiny.
Engineering leaders are sometimes asked: "How does your team contribute to EBITDA improvement beyond just cutting cloud costs?" Labor capitalization is the answer most candidates miss. If your team is building new platforms or products, a significant portion of engineer salaries can be reclassified as CapEx, directly improving EBITDA without reducing headcount or cloud spend. Quantify it: "We capitalized $800K of engineering labor last year, which improved our EBITDA by approximately $600K after amortization."
Senior Insight: Labor capitalization is not a free lunch. It creates a growing intangible asset on the balance sheet that must eventually be amortized. If a capitalized project is abandoned, the entire remaining book value must be written off immediately — a painful one-time charge. This is why Finance teams require engineering leaders to honestly assess whether a project will actually deliver long-term value before capitalizing its costs. Capitalizing a failed project and then writing it off is worse than expensing it from the start.