Tactical insights for first-time founders to outsmart the burn, the churn & the breakdown.
Hey Founder,
We made it to issue #40. That’s about 100,000 words of me yelling (lovingly) about running a company like an adult.
If you’re still here, you’re serious. So let’s get serious again.
You don’t have a runway problem. You have a “how this place actually runs” problem.
Your 12–18 months of runway only exist if your company behaves the way your financial model assumes it does.
On paper, your projections rely on clear ownership, disciplined execution, reliable reporting, and aligned teams.
In reality, many companies run on founder intervention, loosely defined accountability, and metrics that are debated more than they are trusted.
The gap between the company in your spreadsheet and the one you are actually operating is your “operational runway”: how long your current backbone (structure and decision cadence) can sustain growth before friction turns into underperformance.
This issue is about that backbone. Not more meetings. Not more dashboards.
Just seeing how many cycles your current way of working can actually carry.
The Margin
Your Plan Assumes a Stronger Backbone Than You Have
Every serious growth plan assumes an organisational backbone that often does not exist.
Under ten people, chaos works. As David Sacks described the early PayPal days, you solve problems by turning your chair and shouting across the room. Alignment is informal, decisions are fast, and proximity replaces process.
Past a couple of dozen people, the same chaos turns into drag. Metrics multiply, priorities fragment, and meaningful decisions circle back to the founder because no real decision architecture was built.
Claire Hughes Johnson saw this at Stripe while scaling from roughly 160 to 6,000 employees: without a simple company operating system that defines who decides what, which meetings matter, and which numbers actually drive action, senior hires stall, decisions get revisited, and teams hit goals that do not compound.
Headcount scales, expectations scale, but the backbone - your operational discipline - often does not.
Operational runway is how many ninety-day cycles a mismatch can survive before it shows up as stalled growth, missed forecasts, or leaders quietly burning out.
How it feels when your operational runway is short
You do not need a new dashboard to know your backbone is under strain. You feel it in how your weeks unfold.
You remain the spine of every meaningful initiative. Integrations, launches, and cross-team projects move only when you push, and stall the moment you step back.
Problems repeat in slightly different forms. The same launch slips for familiar reasons, the same part of the funnel leaks, and issues you were sure were fixed quietly resurface.
Activity stays high but progress feels thin. Meetings fill the calendar, decks circulate, Slack threads expand, yet when you ask what truly changed in the business this month, the answer feels disproportionately small.
Even your numbers create friction. Conversations focus on where a KPI came from rather than what decision it should drive, which signals not a data issue but a structural trust gap.
When several of these patterns appear at once, your operational runway is already shorter than you think.
Tiny Reframe
Runway isn’t just a cash countdown. It’s also a capacity threshold.
Financial runway: cash ÷ normalized monthly burn.
Operational runway: ambition ÷ backbone.
You will never find operational runway in a spreadsheet because the math is only a metaphor.
You feel it when you ask the question most founders avoid: with this organisation, these meetings, and these decision habits, how many ninety-day cycles can we realistically execute before something critical starts to fracture?
The goal is not to calculate the number precisely. The goal is to stop pretending there is only one countdown running in your company.
Margin Moves To Make Cash Actually Useful
3 Margin Moves to See If Your Backbone Can Carry the Plan
1. Audit your operating cadence against reality
A company (of between 15 and 50 people) needs more than good intentions. It needs rhythm.
What a viable operating cadence (15-50 employees) looks like - (Download template here)
Annually, you define direction and resource bets.
Quarterly, each team commits to two or three real priorities.
Monthly, you review financial and operating performance and decide what changes.
Weekly, teams clarify ownership, blockers, and next steps.
Open your calendar and your leadership team’s calendar, and look honestly.
Do you see a clear cadence that maps to these cycles, or just a wall of recurring meetings?
Can you point to one protected moment where you confront the whole plan and ask whether you are still working on the right things?
If your cadence only exists in a strategy deck, your operational runway is shorter than you think.
More inspiration:
2) Cut your metrics until they are usable
If the operating model is the backbone, metrics are the nervous system. Too many founders overload it.
Limit yourself to no more than five headline numbers that truly matter, such as ARR, net revenue retention, gross or EBITDA margin, burn multiple, and cash runway.
Pair them with two or three simple charts that make performance visible in under two minutes.
For each metric, ask three questions:
Is there one clear owner who can directly influence it?
Does it tell us something unique?
How strongly does it reflect the outcomes we actually care about?
If you cannot answer those quickly, the metric is noise.
3) Remove yourself as the hidden bottleneck
Operational runway collapses fastest where you remain the unspoken owner of everything important.
Take your five headline KPIs and list one to three input drivers beneath each.
Then add two columns: who is the true owner today, vs ideal owner (who should own it) in a functioning company?
Example (E-commerce):
Anywhere your name appears as the true owner but not the ideal one, you have found a runway leak.
Your job is not to work harder on that metric, but to transfer ownership properly with clear definitions, context, and a focused ninety-day experiment plan.
Every time you do this cleanly, you extend operational runway without adding a single dollar to the bank.
Tough Love Corner
A founder asked me this week,
“I need to fire someone for performance, and I’ve never done it before. How do I keep it clear and respectful without inviting debate?”
The truth is that clarity is kindness.
If you have led well, the decision should not be a surprise. Expectations were documented, feedback was given, and the gap was discussed.
When the moment comes, keep it direct and dignified:
“Today is your last day with the company. We’ve had multiple conversations about performance, and we haven’t seen the change we needed. Thank you for your contributions. Our People team will walk you through the next steps.”
Kindness and finality have to coexist. That is what leadership looks like in hard moments.
Got a burning founder question?
Send it my way, just hit reply.
Founder’s Toolbox
You’ll enjoy these:
Before You Go…
40 issues in, one pattern keeps repeating.
In the early days, your company works because of your intensity. Later, it works because of its design. That shift, from force to structure, is what separates companies that scale from those that stall.
Everyone tracks cash runway. Very few track operational runway.|
The second one is usually the real moat.
See you next Thursday,
— Mariya
What did you think of today’s issue?
Hit reply and let me know. I read every single one (for real).
About me
Hey, I’m Mariya, a startup CFO and founder of FounderFirst. After 10 years working alongside founders at early and growth-stage startups, I know how tough it is to make the right calls when resources are tight and the stakes are high. I started this newsletter to share the practical playbook I wish every founder had from day one, packed with lessons I’ve learned (and mistakes I’ve made) helping teams scale.
