The Startup Runway Dashboard
Your runway should not live in a forgotten spreadsheet. Here's the simple dashboard founders use to track burn, cash, and decisions.
Published , updated · 8 min read
Most founders can tell you their product roadmap, their next launch, and the investor they want to meet next.
Fewer can answer the one question that quietly controls all of those things:
How many months do we have before cash forces the next major decision?
Not the optimistic number from the fundraising deck. Not the number from a model built three months ago. The real number, using current cash, current burn, committed spend, and realistic revenue.
That number belongs in a runway dashboard.
A runway dashboard is not a finance vanity panel. It is the early-warning system for the company. It tells you when to hire, when to pause, when to fundraise, when to cut, when to raise prices, and when a strategic bet is too expensive for the cash you have left.
Why Runway Gets Mismanaged
Runway gets mismanaged because it lives in the wrong places.
It lives in a spreadsheet only one founder opens. It lives in the accountant's monthly report. It lives in a mental estimate that has not been updated since the last wire hit. It lives in a pitch deck where the assumptions were rounded for storytelling.
The problem is not that founders do not care about cash. They care deeply. The problem is that cash data is often disconnected from the operating cadence where decisions happen.
If runway is not visible when you discuss hiring, roadmap, sales targets, pricing, and fundraising, it is not really part of the decision.
The test is simple: if the dashboard changes but no decision changes with it, you built reporting, not an operating tool.
The Seven Numbers Your Dashboard Needs
A good runway dashboard can be simple. Start with seven numbers.
| Metric | Why it matters |
|---|---|
| Cash in bank | The actual starting point, not a forecast |
| Gross burn | Total cash leaving each month |
| Cash receipts | Revenue, grants, investment, or other cash in |
| Net burn | Gross burn minus cash receipts |
| Committed spend | Future spend you have already promised |
| Runway months | Cash divided by net burn, adjusted for commitments |
| Default-dead date | The calendar month cash reaches zero |
The last one matters most. "Nine months of runway" sounds abstract. "Cash runs out in April 2027" changes behavior.
This is the same practical discipline behind building your first financial model: the model should help you make decisions, not just impress someone else.
Use Trailing Burn, Not Vibes
Founders often calculate burn from memory:
We spend about $40K a month.
Maybe. But "about" hides reality.
Use trailing three-month average net burn as your default view. Then show last month separately.
Why both?
- The three-month average smooths weird timing issues.
- Last month catches recent changes quickly.
If your three-month average net burn is $38K but last month was $54K, the dashboard should make that visible. Something changed. Maybe you paid annual software bills. Maybe contractors increased. Maybe revenue slipped. Maybe hiring started showing up in payroll.
Runway conversations get better when the number is grounded in actual cash movement.
Separate Fixed and Variable Burn
Not all burn is equally flexible.
Fixed burn includes payroll, rent, baseline infrastructure, and signed contracts. Variable burn includes contractors, ads, tools, travel, experiments, and discretionary services.
Why this matters:
| Burn type | Decision implication |
|---|---|
| Fixed burn | Harder to cut, slower to change, needs earlier warning |
| Variable burn | Easier to adjust, useful for conservation plans |
A founder who only knows total burn may think they can cut quickly. Then they learn most spend is locked into people and contracts. A dashboard that separates fixed and variable burn prevents fake confidence.
Show Three Runway Scenarios
One runway number is not enough because the future is sensitive.
Your dashboard should show:
Base Case
The honest plan. Current hiring, expected revenue, current spend, realistic conversion. This is not the investor story. It is what you actually believe.
Downside Case
Revenue grows slower, a customer churns, fundraising takes longer, or a hire starts earlier than expected. This is the case that tells you whether you are fragile.
Conservation Case
What happens if you freeze hiring, cut discretionary spend, delay contractors, and reduce tool costs? This is not necessarily the plan. It is the emergency brake.
The difference between these cases is often the difference between calm decision-making and panic.
Add Decision Triggers
The dashboard becomes powerful when it contains thresholds.
For example:
| Trigger | Decision |
|---|---|
| 12 months runway | Start investor relationship warming |
| 9 months runway | Begin formal fundraise prep |
| 6 months runway | Freeze non-critical hiring |
| 4 months runway | Cut discretionary spend and revisit strategy |
| 3 months runway | Survival mode: default to cash preservation |
Your thresholds may differ, but they should be written before you are under pressure. Cash stress makes founders over-optimistic and over-reactive at the same time. Written triggers protect the team from both.
These triggers should connect directly to your monthly investor update. Investors do not need drama. They need a founder who sees cash clearly and acts early.
Connect Runway to Hiring
Hiring is usually the biggest runway decision.
Every open role should show its runway impact:
- Monthly fully loaded cost
- Start date
- One-time recruiting or equipment cost
- Expected business outcome
- Runway impact in months
This does not mean you stop hiring. It means every hire competes against the cash reality honestly.
If hiring a senior engineer reduces runway by 1.8 months but accelerates a revenue-critical product milestone, that may be the right decision. If hiring a generalist reduces runway by 1.2 months with no clear milestone, that is a different conversation.
The dashboard should make the tradeoff visible.
Connect Runway to Revenue Targets
Revenue targets are more useful when they show runway impact.
Instead of:
We want to hit $20K MRR.
Ask:
If we hit $20K MRR by October, how many runway months do we gain?
That turns revenue goals into operating consequences. It also helps founders see which targets matter. Some revenue goals look exciting but barely move runway because gross burn is too high. Others change the financing timeline entirely.
This is where pricing, churn, sales velocity, and cash planning meet.
Review It Weekly, Update It Monthly
The dashboard should be reviewed weekly and reconciled monthly.
Weekly review:
- Has cash changed materially?
- Did any large expense hit?
- Did revenue or churn change the forecast?
- Did any hiring or vendor decision affect runway?
- Are we approaching a trigger?
Monthly reconciliation:
- Replace forecast with actuals.
- Update burn averages.
- Refresh scenario assumptions.
- Record what changed and why.
The weekly review keeps runway in decisions. The monthly update keeps the numbers honest.
The Founder Test
A founder with a useful runway dashboard can answer these questions without opening five tabs:
- How much cash do we have today?
- What is our trailing three-month net burn?
- What is our default-dead date?
- What happens if revenue is 30% below plan?
- What hiring decisions are already baked into the forecast?
- When do we need to start fundraising?
- What cuts would extend runway by three months?
If those answers are scattered, your financial model is not operating the company. It is just a spreadsheet.
What This Looks Like in 1tab.ai
1tab.ai includes a founder finance workspace where runway, burn, revenue, hiring plans, financial models, tasks, investor updates, and weekly reviews stay connected. The point is not just seeing the number. It is turning runway into earlier, calmer decisions.