A remote team of three to ten people does not need a big operating system. It needs a small number of predictable rhythms, most of them written, so that everyone knows what matters this week, what changed, and where to look for answers without pinging a founder. This guide is a concrete weekly cadence you can adopt on Monday, plus the monthly and quarterly layers that sit on top of it.
For the broader principles — async-first communication, documentation, hiring for remote — see managing a remote startup team.
The weekly cadence
| When | What | Format | Time cost |
|---|---|---|---|
| Monday morning | Weekly plan: top 3 company priorities, each person’s main commitments | Written, one shared doc or channel post | 15 min each |
| Daily | Check-in: done, next, blocked | Async message in a dedicated channel | 5 min each |
| Tuesday or Wednesday | Team sync: blockers, decisions that need discussion, one metric review | Video call, 30–45 min, agenda in advance | 45 min |
| Every 1–2 weeks | 1:1s between each person and their manager (or founder) | Video call, 30 min, the report owns the agenda | 30 min |
| Friday | Weekly update: shipped, learned, numbers, next week’s risks | Written, founders write theirs first | 20 min each |
That is roughly one and a half hours of meetings per person per week. Everything else is written and can be read when it suits each person’s time zone.
Monday: the weekly plan
One person (usually the CEO) posts the company’s top three priorities for the week by Monday morning in the earliest time zone. Each team member replies with their two or three main commitments and how they connect to those priorities. This replaces most “what should I work on?” messages and makes overload visible early.
Daily: async check-ins
A short post in a single channel: what I finished, what I’m doing next, anything blocking me. Keep it to three lines. The rule that makes it work: blockers get a response the same working day, from whoever can unblock them. Tools like Geekbot or a simple scheduled Slack reminder are enough.
Midweek: the one meeting
Hold one team-wide synchronous meeting a week, scheduled inside your overlap hours. Collect agenda items in writing beforehand; if nothing needs live discussion, cancel it. Use it for decisions that are genuinely easier to talk through, not for status updates that were already written. Record decisions in a decisions log immediately after.
Friday: the written update
Everyone writes a short update: what shipped, what they learned (from customers, experiments, or mistakes), the number they own and how it moved, and the biggest risk for next week. Founders write theirs first and include the company metrics. Over a few months these updates become the most useful record of how the company actually evolved — and the raw material for investor updates.
The monthly and quarterly layers
- Monthly metrics review (60 min): revenue, burn, runway, and the two or three product metrics that matter at your stage (see the startup metrics guide). Write the commentary before the call.
- Monthly retro (45 min): what to keep, stop, and start in how you work together. Rotate who runs it.
- Quarterly planning: agree three to five goals for the quarter, each with an owner and a measurable outcome. Publish them where the Monday plan can link to them.
- In-person time: if budget allows, meet in person once or twice a year. Plan it around relationship-building and the hardest strategic conversations, not around work you could do remotely.
Write a one-page communication charter
Most remote friction comes from mismatched expectations. Agree these on one page and pin it:
- Channels: chat for quick questions, the tracker for work, docs for anything that needs to be found later, video for nuance and conflict.
- Response times: for example, chat within a few working hours, docs and reviews within one working day, true emergencies by phone.
- Overlap hours: a two-to-four-hour window when everyone is reachable. Schedule the weekly meeting inside it, and rotate the inconvenience if time zones make that impossible.
- Decisions: where they are recorded, and the rule that decisions made in DMs or calls are summarised in the shared log.
- Off-hours: no expectation of replies outside working hours; use scheduled send.
The minimum tool stack
For a team this size, four tools are enough: a chat tool (Slack, Microsoft Teams, or Discord), a documents/wiki tool (Notion, Google Docs, or Confluence), a task tracker (Linear, Jira, Asana, or Trello), and a video tool (Google Meet, Zoom, or Teams). Add a password manager and a device-management or admin console early, so company accounts and laptops can be handed over cleanly when someone leaves. Resist adding a tool for every ritual; most of the cadence above runs fine in chat and a shared doc.
Start the handbook now
A company wiki or handbook does not need to be impressive. Start with five pages: how we communicate (the charter), how we plan (this cadence), how to ship (dev and release process), how to handle a customer issue, and onboarding for a new hire. Add a page every time someone asks the same question twice. GitLab’s public handbook is the extreme example of the habit; a five-person team needs a fraction of it.
Common problems in a five-person remote team
- Founders become the bottleneck. If every question routes through a founder, the decision-rights section of your co-founder agreement and the handbook are not doing their jobs yet.
- Silent overload. Monday commitments that never get finished are the earliest signal. Talk about it in 1:1s, not in the team meeting.
- Isolation. Small remote teams have less casual contact. A short optional social call every week or two and occasional in-person time help more than elaborate virtual events.
- Meeting creep. Audit the calendar every quarter and delete anything that could have been a written update.
Frequently asked questions
How many meetings should a small remote startup team have?
For a team of three to ten people, one weekly team meeting of 30 to 45 minutes plus regular 1:1s is usually enough. Daily stand-ups, weekly plans and weekly updates can all be written and asynchronous.
What tools does a small remote team need?
Four are enough at the start: a chat tool, a documents or wiki tool, a task tracker and a video tool. Add a password manager and device or admin controls early so accounts can be handed over when someone leaves.
How do you run async stand-ups?
Each person posts a short message in one channel every working day with what they finished, what they will do next and anything blocking them. The rule that makes it work is that blockers get a response the same working day.