How to Run a Startup All-Hands Meeting

An all-hands meeting is the one time the whole company hears the same story at the same moment. Done well, it builds trust, cuts rumors and helps everyone pull in the same direction. Done badly, it becomes a slide marathon people quietly mute. This guide shows you how to run a startup all-hands that your team actually looks forward to.

Mid-June is a natural time to tune your all-hands. The second quarter is wrapping up, summer schedules are starting to scatter people across time zones and holidays, and many teams are about to set goals for the next quarter. If your current meeting feels stale, this is a good moment to reset the format before the busy planning season arrives.

The ideas below work for a five-person seed-stage team and for a company of a hundred or more. The bigger you get, the more structure you need, but the principles stay the same.

Decide what your all-hands is for

Most weak all-hands meetings try to do too much. They mix company strategy, team status reports, celebrations, policy updates and a product demo, then run long and leave people unsure what mattered.

Start by writing one sentence that describes the purpose. For example: "Our all-hands helps every person understand where the company is going, how we are doing and how their work connects to it." That sentence becomes your filter. If an agenda item does not serve it, move it to a different channel.

What belongs in an all-hands

• Company direction. Mission, strategy and the few priorities for this quarter.
• Progress on goals. A short, honest look at your key metrics or quarterly objectives.
• Big decisions and changes. New hires in leadership, a fundraise, a pivot, a new policy that affects everyone.
• Recognition. Specific thanks for work that moved the company forward.
• Open questions. Time for anyone to ask leadership anything.

What usually does not

• Long team-by-team status reports that only matter to a few people.
• Detailed process changes that need a written guide anyway.
• Debates that need a smaller group to decide.

Choose a cadence and format that fits your stage

There is no single right rhythm. What matters is that the meeting happens reliably, so people trust it as the place where important news lands.

• Weekly. Common for very early teams that change direction often. Keep it short, around 20 to 30 minutes.
• Every two weeks. A good middle ground for growing teams, with room for a short deep dive.
• Monthly. Works well for larger or distributed companies, especially when paired with a weekly written update.
• Quarterly extended session. Many startups add a longer all-hands at the start of each quarter to review results and share the new objectives. If you use OKRs (Objectives and Key Results), which are typically set quarterly, this is a natural place to present them.

For format, decide whether your meeting is in person, fully remote or hybrid. Hybrid is the hardest to run well, because people in the room tend to dominate. If you go hybrid, ask everyone to join the video call from their own laptop, even in the office, so remote teammates see faces rather than a distant conference table.

Build a repeatable agenda

A consistent agenda saves you preparation time and helps people know what to expect. Here is a simple 45-minute structure you can adapt.

A sample all-hands agenda template

Copy this table into your planning doc and fill in owners each time. The timings and topics below are example values.

Notice that Q&A gets the biggest single slot. That is deliberate. Questions are often the most useful part of the meeting, and they tend to get squeezed if you schedule them last with no protected time.

How to prepare in the week before

Good all-hands meetings are built in the days before, not in the hour before. A light, repeatable preparation routine keeps it manageable.

1. Pick a host. The host keeps time, introduces speakers and runs the Q&A. It does not have to be the CEO, and rotating the role can help.
2. Collect agenda items. Ask leaders and teams for items three or four days ahead. Use your purpose sentence to decide what makes the cut.
3. Open the question box. Share a simple form so people can submit questions in advance, with an anonymous option. Google Forms, Typeform, Microsoft Forms or Tally all work.
4. Gather shout-outs. Ask everyone to nominate a colleague for specific thanks. A thread in Slack or a form keeps it easy.
5. Prepare a short deck. Aim for a handful of slides with big numbers and few words. Share it with speakers a day early.
6. Rehearse the hard parts. If you have difficult news, practice saying it out loud with a co-founder. Clear, calm wording matters.
7. Check the tech. Test the video link, screen sharing, microphones and recording before the meeting starts.

Running the meeting itself

On the day, your job is to keep energy up, stick to time and make the room feel safe enough for real questions.

Start on time, every time

Starting late teaches people that arriving late is fine. Begin at the scheduled minute, even if a few people are still joining. A short, upbeat welcome sets the tone.

Share the numbers, good and bad

Your team can usually sense when things are not going well. If you only share good news, people fill the silence with their own, often worse, stories. Show a small set of the same key metrics each time, explain what moved and why, and name one challenge honestly. Then say what you are doing about it and how people can help.

Be careful with sensitive details. Some information, such as fundraising terms that are still being negotiated, individual pay or personal matters, should not be shared in a large group. When you cannot share something, say so plainly rather than dodging the question.

Make Q&A the real thing

The quality of your Q&A tells people whether leadership really wants to hear from them. A few habits help:

• Answer the hardest pre-submitted questions first. Skipping the uncomfortable ones is noticed immediately.
• Read anonymous questions word for word. Do not soften them before answering.
• Say "I don't know yet" when you don't. Then promise a follow-up and deliver it.
• Keep answers short. Aim for a minute or two each, so more questions get answered.

Keep recognition specific

"Thanks to the whole team for a great month" is pleasant but forgettable. "Thanks to Ana for rewriting our onboarding emails, which cut support tickets from new users" tells everyone what good work looks like. Gather shout-outs in advance so quieter teammates are recognized too, not just the loudest voices in the room.

After the meeting: close the loop

The follow-up is where an all-hands earns its trust. Without it, promises made in the room are forgotten and people who missed the meeting fall behind.

1. Post a written summary within a day. Share the key points, decisions and slides in your team chat or internal wiki, such as Notion, Confluence or Slab.
2. Share the recording. Make it easy to find for anyone on leave, in a different time zone or out with customers.
3. Answer leftover questions. List any questions you did not reach, and post written answers within a set number of days.
4. Track your promises. Keep a simple list of every "we'll get back to you" and check it off publicly.
5. Ask for feedback. Every quarter, run a two-question survey: what was most useful, and what should change?

A short feedback loop helps the meeting keep improving. If people keep saying the spotlight slot is the best part, give it more time. If the metrics section feels confusing, simplify the chart.

Special situations

Some all-hands meetings carry more weight than others. A little extra care goes a long way.

• Funding announcements. Explain what the money is for and what it changes for the team, and avoid sharing deal terms you are not ready to share.
• Difficult news. For layoffs, leadership changes or a pivot, tell affected people privately first, then hold the all-hands. Give people time and space to react, and make follow-up conversations available.
• Holiday weeks. Around public holidays, such as Juneteenth in the US, consider skipping or shortening the session and sending a written update instead so people are not left out.
• Very small teams. With five people, an all-hands can be a 20-minute weekly check-in. You still benefit from a fixed agenda and a written follow-up.

Frequently asked questions

The bottom line

A great startup all-hands is simple: a clear purpose, a steady rhythm, a repeatable agenda, honest numbers, specific recognition and a Q&A that tackles the hard questions first. Follow up in writing so nobody is left out, and ask for feedback so the meeting keeps getting better.

Before your next session, write your purpose sentence, set up the agenda template and open a question form. Small changes like these can turn a meeting people tolerate into one they genuinely value.