Volatility is a feature: duration, drawdowns, and the board

The meeting after a 40% drawdown

Every Bitcoin treasury eventually has the meeting. The asset is down. A director asks whether the thesis changed. The correct answer is almost always no — if the policy was written for duration. Bitcoin is a twenty-year duration instrument stuffed into a market that still prices it like a software stock. That mismatch produces volatility. It also produces the opportunity: patient balance sheets can harvest coins from impatient ones.

The error is to import hedge-fund language into a reserve conversation. VaR, stop-losses, and “de-risking into strength” are tools for books that must mark to a redemption gate. A corporate treasury with a going-concern horizon can instead publish a drawdown protocol: no discretionary selling, continued DCA inside pre-agreed bands, and a liquidity sleeve in cash that covers 18–24 months of obligations.

Communication as risk management

Price is not the only volatility. Narrative volatility — analysts, activists, employees with 401(k) dashboards — can force a sale even when the policy forbids it. The antidote is cadence. A monthly board pack that reports BTC held, BTC per share, cost basis, and scenario NAV at ±50% does more than a heroic letter after a crash.

We also recommend a single sentence that every officer can repeat: “We hold Bitcoin as digital property; we do not trade it.” Repetition is not marketing. It is liability management. When the transcript is read years later, the company should sound like it knew what it owned.

Designing for the worst year

Policy should be written for the worst year in the sample, not the last twelve months. That means custody diversified before it is fashionable, insurance conversations held while premiums are boring, and a prohibition on pledging BTC as collateral for operating debt. Leverage converts a volatility feature into a survival risk. The treasuries that endure are the ones that can go dark for two years and still make payroll.