The exact way to tell your team your runway is shrinking

Runway got tight in month fourteen. I sat on the news for six days before I told anyone besides my co-founder, running the same sentence in my head every night: how do I say this without triggering a wave of resignations. If you're staring at a spreadsheet that says nine months instead of the eighteen you told people at the last offsite, here's the structure that keeps a team steady instead of scared: tell them the number first, the plan second, and the ask third. Skip any one of those three and you get either panic or false calm, and both cost more than the truth would have.

The reassurance instinct is the mistake

Most founders default to reassurance. "We're fine, don't worry about it" is the sentence that comes out first, and it's the one that does the most damage. Your best people already sense something is off: slower deal cycles, a canceled offsite, a founder suddenly running more one-on-ones than usual. Vague reassurance without a number attached reads as either a lie or a founder who doesn't actually know the number. Neither builds trust.

The instinct to protect the team from the real number usually comes from a good place. It backfires because people fill an information vacuum with worse guesses than the truth. A team that hears "we're fine" and later learns runway was nine months, not eighteen, doesn't just lose trust in that number. They lose trust in every number you give them after.

The 3-part structure that keeps trust intact

A runway conversation that works has three parts, in this order: the number, the plan, the ask.

1. The number. State it plainly: "we have 9 months of runway at our current burn." Not "we're being careful with spend." A specific number is verifiable, and verifiable is the only thing that stops speculation.
2. The plan. What changes because of the number: which costs get cut, which hires pause, what the next 90 days look like operationally. This is the part that turns a scary number into a manageable situation.
3. The ask. What you need from the team specifically: ship a feature faster, hold off on a conference, stay heads-down through a raise. People perform better against a specific ask than a generic sense of urgency.

The exact script

Here's language that has worked in this exact conversation:

"I want to be straight about where we are. We have [N] months of runway at our current burn, tighter than the [X] months I shared at [prior update]. Here's what changed: [specific reason, e.g. the enterprise deal slipped a quarter]. Here's what we're doing about it: [1-2 concrete moves]. What I need from the team over the next [timeframe] is [specific ask]. I'll give you a real update every [cadence] so this isn't a surprise again."

Notice what's missing: no apology tour, no forced optimism, no comparison to other startups that had it worse. Just the number, the plan, and the ask, delivered once and then repeated on a schedule.

What not to say

Cut three phrases entirely: "we're fine," "don't worry about it," and "just focus on your work." Each one asks the team to trust you without giving them anything to verify that trust against.

Also avoid over-sharing the fundraising process itself. Walking the team through every term sheet detail or every investor pass creates a different kind of anxiety, tied to a process they can't influence. The runway number and the operational plan are theirs to know. The blow-by-blow of investor conversations isn't.

The 30 days after the conversation

The first conversation buys you trust. What you do in the following month decides whether that trust holds. Put a recurring update on the calendar even if the news hasn't changed, because silence after a hard conversation reads as something new going wrong. Hit at least one commitment from the plan within that window, even a small one, so the team sees the plan is real and not just a speech.

Frequently asked questions

How often should you update the team on runway?

At minimum monthly once runway drops under 12 months, and every two weeks once it drops under 6. Silence gets read as bad news even when there isn't any.

Should you tell the whole company or just leads?

Tell the whole company the number and the plan. Reserve investor-process details, specific term sheet terms, and name-specific hiring decisions for leads only.

What if the plan involves layoffs?

Separate that conversation entirely. Runway updates are ongoing and routine. A layoff is a single, distinct event that needs its own dedicated conversation, not a line item inside a runway update.

Does being this direct scare people into leaving?

Vague updates cause more attrition than direct ones. People leave when they sense a founder is hiding something, not when they're given a hard number and a plan.

The number always comes out eventually, either from you on your terms or from a slower deal cycle, a canceled perk, or someone else's Glassdoor review. Say it first, attach a plan to it, and ask for something specific. The founders who get this right aren't the ones with the best runway. They're the ones who talk about it before they have to.