Most all-hands meetings are expensive. Forty minutes of everyone’s time to read a slide deck they could have gotten in an email. The first all-hands you run as a founder sets a template. People will form opinions about whether these meetings are worth attending, whether you’re actually transparent, whether leadership communicates or just broadcasts. Get it right the first time and you’re building a culture of trust. Get it wrong and you’re fighting that impression for years. Here’s how to run it right. They fail for one of three reasons: The fix is architecture. Structure the meeting so engagement is the default, not the exception. For a team of 5–30 people. Adjust timing as you scale. The single most important thing you can do in an all-hands is share real numbers. Not “we’re tracking well” or “growth is solid.” Actual numbers. MRR. Churn rate. Pipeline coverage. Burn rate. Runway. Number of customers. NPS score. Whatever your north star metrics are — show them. When you share real numbers, three things happen: If you’re worried about sharing sensitive numbers with the whole team, that’s a signal you need to either trust your team more or think carefully about who you’re hiring. Most Q&A sessions are a graveyard. One or two people ask questions. Everyone else stares at the floor. Fix this with pre-submitted questions. Open a simple form or Slack channel before the meeting where people can submit questions anonymously. Read the three or four most-asked ones live. Then open the floor. The anonymous pre-submission does two things: it gives introverts a voice, and it tells you what people are actually worried about — which is usually more useful than what they’re willing to ask on camera. 💡 Rule: If someone asks an uncomfortable question, answer it. If you can’t answer it yet, say why and give a date when you will. Deflecting in an all-hands destroys trust faster than any bad news would. Every all-hands should end within 5 minutes of the scheduled end. Running long signals that you don’t value people’s time. Use a visible timer during the meeting if you have to. All-hands is not the place to announce a layoff, a major pivot, or a key departure for the first time. Those conversations need to happen in smaller groups first. Use all-hands to reinforce context, not drop bombs. If your slides are so dense that you have to read them, they’re too dense. If you’re going to have slides at all, they should be charts, photos, and a few words per slide — not paragraphs. Send a written summary within 24 hours: what was shared, what decisions were made, what questions were asked and how they were answered. It creates accountability and gives remote or timezone-challenged team members a chance to catch up. “Write a 5-minute all-hands company update script for a [X]-person B2B SaaS startup. Include: MRR of [amount], [X]% vs last month. Pipeline of [amount]. Key win this period: [describe it]. Key challenge: [describe it]. Be direct and honest — don’t sugarcoat or use corporate language. Founder tone, not PR speak.” “Here are the anonymous questions submitted by my team before our all-hands: [paste list]. Rank them by how much the team probably cares about the answer. Draft a short, direct answer to each of the top 5. If any questions have a ‘right’ answer that founders often avoid giving, flag those and suggest the honest response.” “Summarize our all-hands meeting into a brief that can be sent to the team via Slack/email. Include: key metrics shared, decisions made or announced, top questions asked and answers given, who was spotlighted and why, and the main focus topic summary. Tone: clear and direct, no fluff.” For teams under 15: monthly all-hands, 60 minutes, synchronous. For teams of 15–50: monthly all-hands, 60–75 minutes, with async video option for remote. For teams over 50: quarterly town halls for the big picture, monthly department all-hands for relevance. The worst outcome is that your all-hands becomes optional — the meeting where the calendar invite gets declined. Keep it tight, keep it honest, keep it worth showing up for.How to Run Your First All-Hands Meeting That People Actually Engage With
Why Most All-Hands Fail
The 60-Minute All-Hands Template
The Numbers Section Is Everything
How to Make Q&A Actually Work
Common Mistakes to Avoid
Running over time
Surprise announcements
Slide-reading
No follow-up
AI Prompts for Your All-Hands Prep
Cadence and Format as You Scale
Related Playbooks
How to Run Your First All-Hands Meeting That People Actually Engage With
0–5 min
Pulse check — one anonymous question in your meeting tool (“How’s energy level this week?” on a 1–5 scale). Share the result live. It signals you care about the answer.
5–15 min
State of the company — revenue vs. target, key metric vs. last period, one honest comment about where you’re ahead and where you’re behind. Be specific with numbers.
15–25 min
Department updates — one person per team, 2 minutes each. What shipped. What’s next. What they need from other teams.
25–35 min
Focus topic — one thing that needs the whole team’s attention. Could be a strategy change, a big customer win to dissect, a post-mortem, a product direction question.
35–50 min
Open Q&A — real questions, real answers. Handle the uncomfortable ones in the room, not in DMs afterward.
50–60 min
Close + spotlight — shout out one person who did something notable. End on time, every time.
Prompt — State of the Company Script
Prompt — Anonymous Q&A Prep
Prompt — Post All-Hands Summary