The bank balance is a symptom. The artifact is the runway.

01The bank-balance trap.

Sunday, 8 p.m. You open the bank app. The number is fine. You close it. Twenty minutes later you open it again. Same number, same fine, but you feel worse, not better, because you have now checked twice for no reason and the second check taught you nothing.

This is the trap. The bank balance is a real number, but it answers a question you are not actually asking. What you want to know is how many weeks of expenses that balance covers at your current burn. That is runway. It is a derived number. And it is an artifact, something you compute once, write down, and reference, not a lookup you keep re-checking.

The check does not produce a decision. It produces a feeling. And the feeling swings hard on numbers that mean nothing without context. A big AR receipt lands and the balance jumps 40%, but nothing about the business has actually improved. A payroll run lands and the balance drops 60%, but nothing has gotten worse.

The bank balance is a photograph. Runway is the film. If you keep re-photographing the same frame you will never see the movie you are actually in.

02What runway actually measures.

Runway is a ratio, not a lookup. It is the number of months of expenses your current bank balance covers at your current burn. That means you need two inputs: the balance and the burn. And it means the derivative is only as good as the burn number underneath it.

03Deriving runway in ten minutes.

Three inputs. Ten minutes. Once a week. Do it Sunday if you want; do it Friday if you would rather not touch it on the weekend. What matters is that it is derived, written, and referenced, not looked up on demand.

04Three signs it is broken.

The ritual does not scale forever. Somewhere between $2M and $10M ARR it starts to strain. Here is what starting to strain looks like:

1. 01
   Sign · Cash · High impact

   You checked the derived number and it disagreed with your gut.

   Almost always means one big AR line skewed the trailing 90. Look for a single invoice larger than 2× the median, recompute without it and see if the runway shifts. If yes, you do not have a runway problem, you have a concentration problem.

2. 02
   Sign · Burn · Medium impact

   Two months in a row, monthly burn jumped 15%+ vs. the trailing average.

   Not a fire, but a smoke alarm. Something got hired, subscribed, or renewed. Track down which line moved and decide if it is structural or seasonal. Runway is only as good as the burn number underneath it.

3. 03
   Sign · Process · Low impact

   You skipped the derivation two weeks in a row.

   Not because the number is bad, because the ritual is soft. The moment the derivation feels optional, the balance-check reflex comes back. Re-anchor the ritual to a calendar event you cannot skip.

05What to do Monday.

Here is the thing about writing runway down: the number matters less than the fact that you touched the inputs at all. Ten minutes on Sunday means you cannot be surprised on Wednesday when a vendor asks about renewals or a hire wants an updated offer.

The Monday version of this article, delivered against your own numbers, is what Cohesion Insight ships. But the ritual works without us. Steal it, the artifact is the point¹.