The Treasury Blind Spot: When Your Board Doesn't Know Your Runway

The question that should be easy

Pick any board member at a venture-backed startup and ask them: "What is the company's current cash balance?"

At a well-run company, this number is known within hours. It's on the weekly finance report. It's on the dashboard the CFO updates every Monday. It comes up in every board meeting without being prompted, because everyone in that room understands that runway is the company's most important operational metric.

At a surprising number of companies, the honest answer is: "I'm not sure. Let me ask the CEO. Actually, let me ask whoever does our books."

Over the past year-end cycle, working through the audit data collection process for a fund portfolio, I encountered multiple companies that could not produce a verified December 31 cash balance on short notice. Not because they were hiding something — but because no one in the organization had ownership of that number in a form that was reliable enough to share.

This is the treasury blind spot. And it's more common than anyone wants to admit.

Cash is not the same as treasury

The first problem is conceptual. Many early-stage companies, particularly in the crypto and Web3 space, conflate "treasury" with "cash in the operating account." These are not the same thing — and treating them as equivalent creates dangerous distortions in how runway is calculated and communicated.

Consider a company holding $5 million in Bitcoin and $500,000 in cash — illustrative numbers, but a shape we see constantly. On a spreadsheet, the treasury looks healthy: $5.5 million in assets, easily 18 months of runway at reasonable burn rates. But here's what that balance sheet is actually saying: roughly 90% of the company's operating liquidity is in an asset whose 30-day realized volatility has run 30-35% through 2025-2026 — compressed from the 50%-plus of earlier cycles, but still several times that of broad equities.

That $5 million Bitcoin position can shed a seven-figure slice in a single bad month — and add one back in a good one. The company's actual runway fluctuates by millions of dollars without any operational change. The board may think they have 18 months of runway. In a sharp market drawdown, they have eight.

Under ASU 2023-08, effective for fiscal years beginning after December 15, 2024, Bitcoin and other qualifying cryptocurrencies held as assets must be remeasured to fair value at each reporting period, with gains and losses flowing through the income statement. This isn't just a disclosure change — it means that a company holding significant crypto as treasury will report volatile earnings driven entirely by asset price movements, not operating performance.

The board needs to understand this dynamic explicitly. "We have $5M in treasury" is not a useful statement if the composition isn't disclosed along with it.

How runway calculations go wrong

The standard runway formula is deceptively simple: cash divided by monthly burn equals months of runway. Every investor knows it. Every founder can recite it.

The problems start when the inputs are wrong or stale.

Monthly burn as a single number obscures the trajectory. A company burning $400K per month is very different from one that was burning $400K six months ago and is now burning $550K — even though both would report the same "burn rate" if the calculation uses a trailing average. If headcount has grown, if vendor contracts have renewed, if the sales team just hit quota and triggered a commission cycle — these events change the cash consumption rate immediately, before they show up in a trailing average.

Cash position as of a reporting date is only as accurate as the last reconciliation. For many early-stage companies, the cash balance in the finance system is a week or two behind reality. It doesn't include transactions that haven't been coded. It may include items in transit. It may not reflect all the wallets and accounts the company actually uses.

When the board asks "what's our runway?" and the CFO says "fourteen months," that number has a margin of error attached to it. The board should understand what that margin is. Usually, they don't.

Then there's the crypto complication. If any portion of the treasury is in digital assets, the cash position as of a specific date requires marking those positions to market as of that date. If the finance function is doing this monthly, or quarterly, or whenever someone remembers — the runway calculation is inherently imprecise.

The dissolution problem

On the far end of the spectrum from "imprecise runway" is a scenario that is harder to explain: the company that dissolves without informing its investors.

This is not a hypothetical. A company in a portfolio we were auditing had dissolved months before anyone noticed. The discovery came through routine audit data collection: the email address on file bounced. There was no notification, no winding-up correspondence, no communication of any kind.

The fund had been carrying a position on the books. Because the dissolution predated the December 31 balance sheet date, ASC 855 treats it as a recognized — Type 1 — subsequent event: the fund had to adjust the year-end statements and write the position off as of December 31, not merely disclose it.

The issue here isn't just financial. It's governance. If a company reaches the point of dissolution — a legal, operational, and financial event that affects every stakeholder — and the investors aren't notified, something has broken down well before the final decision was made. Either the board wasn't meeting. Or the founder had checked out. Or the communication infrastructure was so thin that there was literally no mechanism for investor notifications to go out.

Treasury management and investor communication are not separate disciplines. They're downstream of the same organizational capacity: does the company have the infrastructure to know what's happening, and the discipline to communicate it?

Real-time dashboards vs. quarterly spreadsheets

There's a spectrum of treasury visibility infrastructure, and most early-stage companies are at the wrong end of it.

At the bottom: a shared spreadsheet that someone updates manually when they remember. The cash balance is whatever number was entered the last time someone looked at the bank portal. The burn calculation is a formula that may or may not be current. The spreadsheet may have multiple versions across multiple people's laptops.

In the middle: an accounting system (Xero, QuickBooks) with bank feeds connected. Transactions post in near real-time. The cash balance is accurate within a day or two. Monthly close takes a few days instead of weeks. A basic cash report can be produced on short notice.

At the top: a treasury dashboard that integrates the accounting system with exchange APIs, on-chain wallet monitoring, and automated reporting. Cash is verified against bank statements daily. Crypto holdings are marked to market at every reporting period. Runway is calculated automatically using actual burn rates, not trailing averages. Alerts fire when cash drops below defined thresholds.

The difference in cost between the bottom and the middle is roughly the time cost of the person maintaining the spreadsheet — which, when priced at an opportunity cost for a founder or early employee, is already more expensive than a basic accounting setup. The difference between the middle and the top is a fractional CFO with the right tooling.

What changes when you move up this spectrum is not just accuracy. It's the board's ability to govern. A board that receives a real-time cash dashboard every Monday can make decisions — about hiring, about spend, about fundraising timing — with current information. A board that receives a quarterly spreadsheet is making decisions based on data that may be ninety days stale.

In a volatile market environment, ninety days is an eternity.

3 questions every board member should ask about treasury management

These aren't trick questions. They're the minimum bar for responsible oversight of a company's financial position.

1. What is our current cash balance — verified against our bank and exchange statements — as of the most recent business day? Not an estimate. Not "approximately." A number that someone with access to the accounts confirmed this week. If no one on the call can answer this within thirty seconds, the board has a governance gap, not just an accounting gap.

2. What percentage of our total liquid assets are in non-stablecoin, non-cash instruments — and what does our runway look like if those assets decline 40% in value? This question directly surfaces the crypto treasury risk. It also tests whether the finance function is stress-testing runway or simply reporting a base-case number.

3. How often do we receive a formal treasury report, and who owns the accuracy of that report? The answer should be: at minimum monthly, and there should be a named individual — not a role, a name — who is personally responsible for the accuracy of the figures in that report.

If the answers to these questions are vague, or if the question about ownership produces a moment of silence while board members look at each other, that's the signal. The company has a treasury blind spot. The cost of that blind spot isn't always visible in the next quarter's financial statements — but it tends to materialize at the worst possible time, when a fundraise is in progress, when a key customer is asking for financial references, or when the market turns and the board suddenly needs accurate numbers fast.

The fix is not complicated. It's a monthly close. A single owner. A dashboard that reflects reality. The discipline to update it consistently.

That's all it takes to not be surprised by your own company's financial position.