Accurate, and Beside the Point
A dashboard says growing. A thirteen-week cash forecast says payroll fails on the 25th. The metrics are not wrong — they were built to answer a question that has changed.

"I decided not to pay myself this month."
He said it the way you would say you had skipped lunch. No drama, no tremor. We were fifteen minutes into a review of his quarterly numbers, and he mentioned it as context, almost an aside, before walking the room through the cash position. The calmness was the alarming part. This was not a founder in crisis. This was a founder who had metabolized the crisis privately, weeks earlier, and was now presenting its consequences as operational decisions.
His dashboard, for what it is worth, was fine. NRR, Gross margin, CAC payback, the lot. If you had seen the slides without hearing the conversation you would have said: reasonable company, a few adjustments, nothing structural. The metrics described a business with a future. The decision to stop taking a salary described a business where the future had become a week-by-week question.
The metrics were not wrong. They were accurate. They had simply stopped being what the company was about. The question a company runs on can change without warning, from how do we grow to how do we survive until something changes, and when it does the founder who used to wake up thinking about pipeline wakes up thinking about the bank balance. Not as a general worry. As the first thought of the day. Nobody announces the shift. There is no meeting where survival mode is declared. It happens in one person's head, and by the time anyone else notices, the founder has been living there for weeks.
What the shift does, before it does anything else, is change the founder's job into one no playbook prepared them for. The person who spent their days on product and sales coaching now spends mornings on cash. Not the quarterly kind that goes in the board deck. The daily kind. Which invoices land this week. Which suppliers will tolerate sixty days instead of thirty. Whether the CIR reimbursement arrives before the URSSAF payment is due. Whether two enterprise invoices at ninety days, 180,000 euros between them, clear before or after payroll. This is treasury, and it is a different discipline from running a tech company, granular and unsentimental and hour by hour, and most founders learn it on the job, where the mistakes are immediate.
The founders lucky enough to be in a portfolio that has seen this before get shifted onto a different document early: a rolling thirteen-week cash forecast, updated every Friday, every inflow and outflow tracked by day. It becomes the most important document in the company, more important than the board deck or the roadmap. The ones who are not, either never learn to build it, or build it quietly and never show it, because no one ever asks. The board asks about the dashboard. Two documents describing the same company, telling entirely different stories, shown to entirely different audiences. The dashboard says: growing, retention solid, unit economics reasonable. The thirteen-week says: if Client X does not pay by the 20th, payroll fails on the 25th.
And the founder is carrying the second document while still running the company off the first. Still doing one-on-ones. Still closing deals. Still presenting at the all-hands as though the trajectory were intact. The load is immense and entirely private. They check the bank balance at odd hours. They get good at compartmentalizing, strategic optimism in the morning meeting, cash realism after the room empties. "I decided not to pay myself this month" was the first time this founder had said any part of it out loud to anyone outside the company. Not to the board. Not to the other investors. Not to the co-founder. It came out sideways, in a meeting nominally about quarterly metrics.
The companies that come through this, and some do, do not make it because they found the right metric. They make it because someone finally says the thing out loud.
The metrics do not stop being useful because they turn inaccurate. They stop being useful because the question changed, and they were built to answer the old one.
There is no metric that tells a founder when to stop paying themselves. There is no playbook for what it costs to carry that alone, in the odd hours, while the all-hands runs as though nothing has changed. There is no benchmark for the morning the question quietly turns from how do we grow into how long do we have. Those things live in the space between what the numbers can measure and what running a company actually asks, and that space is where the outcome gets decided. What decides it is rarely the severity of the problem. It is how long the founder stays alone with it.