Should we share the runway number with the whole company?

Yes, above ~30 employees, with context. Employees are computing it anyway (headcount growth, funding announcements, industry benchmarks). Getting the actual number with context ('we have 24 months and here's the plan') builds trust; leaving them to guess erodes it.

How do we handle information leaks?

Investigate but don't obsess. Most leaks come from expanding the trust circle too fast, not from bad actors. Solution: be more deliberate about who's in the loop for sensitive information (M&A, layoffs, senior departures), and default to more transparency for everything else so the delta between 'closed' and 'open' is small.

What tools should we use?

Doesn't matter much. Slack + Notion/Google Docs + Zoom + email covers 95% of companies. The discipline is what matters, not the tool. Switching tools rarely fixes a communication problem.

Startup Internal Communications: All-Hands, Updates, Async

Internal communications at 20 people is a shared Slack channel. At 200, it's a discipline that determines whether the company runs on shared context or rumor.

Internal Communications: The Discipline That Prevents Rumor and Rework at Scale

Internal communications is the practice of making sure the right people inside the company have the right context at the right time. It sounds mundane until you experience the failure mode: rumors filling information vacuums, decisions being remade because half the room wasn't in the loop, top performers leaving because they feel disconnected from strategy. Good internal comms is a leadership responsibility, not an HR function.

The channels and what belongs where

All-hands (monthly, sync): strategy, financials at appropriate transparency, wins, one deep-dive. CEO weekly note (async, written): what's on my mind this week, top priorities, asks. Function updates (weekly, async): what shipped, what's next, blockers. Slack: real-time coordination, not durable decisions. Docs: durable decisions and context that will be referenced later. Email: external and formal internal notices. Confusing these — running strategy debates in Slack, or making product decisions in all-hands — is the most common failure.

Transparency: default to open, be deliberate about closed

Default posture at a growing startup: financial position and burn shared with the whole company monthly, strategic priorities visible to everyone, org changes announced with rationale. Deliberately closed: individual comp, individual performance issues, active M&A conversations, litigation. The pattern that fails is inversion — leadership treats routine information as secret, which trains employees that information must be extracted rather than shared.

Written weekly updates

Every function lead writes a weekly update (Friday, 200-500 words): goals for the week, hits, misses, next week, help needed. CEO synthesizes into a company-wide note by Monday morning. This ~2 hour weekly investment eliminates entire categories of 'I didn't know we were working on that' failures. Companies that skip this rebuild the same context in every meeting.

All-hands that people actually want to attend

Signals of a good all-hands: attendance stays above 90% voluntarily, Q&A produces real questions (not planted softballs), meeting ends on time, people reference specific content the following week. Signals of a broken all-hands: attendance drops, Q&A dries up, meeting runs long, content is undifferentiated from the CEO's weekly note. Fix a broken all-hands by cutting length, adding real questions from the team, and giving airtime to voices other than the CEO.

Handling sensitive news

Reorgs, departures, cuts, missed quarters, funding challenges: communicate them faster and more honestly than you're comfortable with. The pattern that works: leadership hears the news → 24-48 hours to plan the communication → announce in an all-hands (video, live) → written summary within an hour → manager 1:1s within 48 hours → follow-up Q&A within a week. The failure mode is waiting weeks 'until we have all the answers,' during which the rumor mill produces worse answers than the truth would have.

Frequently asked questions

Should we share the runway number with the whole company?: Yes, above ~30 employees, with context. Employees are computing it anyway (headcount growth, funding announcements, industry benchmarks). Getting the actual number with context ('we have 24 months and here's the plan') builds trust; leaving them to guess erodes it.
How do we handle information leaks?: Investigate but don't obsess. Most leaks come from expanding the trust circle too fast, not from bad actors. Solution: be more deliberate about who's in the loop for sensitive information (M&A, layoffs, senior departures), and default to more transparency for everything else so the delta between 'closed' and 'open' is small.
What tools should we use?: Doesn't matter much. Slack + Notion/Google Docs + Zoom + email covers 95% of companies. The discipline is what matters, not the tool. Switching tools rarely fixes a communication problem.

Related fundraising guides (40)

Investor directory · Fundraising library · Articles A–Z · Company funding database