EBITDA and valuation consequences
Where token spend lands changes EBITDA and how the business is valued. Capitalizing moves cost below the EBITDA line into amortization; expensing keeps it in operating cost; COGS sits in gross margin. Mis-coding rented intelligence as pure OpEx, or capitalizing too aggressively, distorts both margin and earnings quality, and auditors and investors read the choice closely ASC 350-40-25.
How the coding moves EBITDA
Capitalized development is excluded from EBITDA and recovered as amortization, flattering operating margin in the build period. Expensed spend reduces EBITDA now. COGS sits inside gross margin, so routing inference there rather than to OpEx lowers gross margin but not EBITDA. Each choice tells investors a different story about unit economics.
The valuation risk of getting it wrong
Aggressive capitalization inflates near-term earnings and builds a balance sheet of assets that may impair fast, an earnings-quality red flag. Under-capitalizing genuine development understates asset value and depresses reported margin. Both invite restatement risk and a valuation discount once diligence uncovers the pattern.
Posts to
Primary sources
- [S4] Weaver: Navigating internally developed software costs: U.S. GAAP vs tax treatment (US GAAP)
- [S1] KPMG: Hot Topic: Accounting for internal-use software (ASC 350-40) (US GAAP)
Ledger current as of 2026-07-24. A position and a citation, not accounting advice. See how we cite.