---
# === IDENTITY ===
id: business/startup-operations/meeting-cadence-design/2026
canonical_question: "What recurring meetings does a startup need — by company size, don't copy enterprise meeting structures?"
aliases:
  - "Startup meeting cadence design 2026"
  - "Recurring meeting structure by company size"
  - "Lightweight meeting framework for startups"
entity_type: execution_recipe
domain: business > startup-operations > meeting-cadence-design
region: global
jurisdiction: global
temporal_scope: 2025-2026

# === VERIFICATION ===
last_verified: 2026-03-12
confidence: 0.87
version: 1.0
first_published: 2026-03-12

# === TEMPORAL VALIDITY ===
temporal_validity:
  status: evolving
  last_breaking_change: "Async-first tooling (Loom, Geekbot, Notion) matured enough to replace most status-update meetings by 2025"
  next_review: 2026-09-08
  change_sensitivity: high

# === CONSTRAINTS ===
constraints:
  - "Meeting load must stay below 15% of total team hours — exceeding this signals cadence bloat"
  - "No meeting without a written agenda shared 24 hours in advance — enforced by calendar tool"
  - "Status updates are never meetings — use async channels (Slack bot, Loom, written posts)"
  - "Every recurring meeting gets a 90-day expiration date — renew only if participants confirm value"
  - "All-hands frequency must decrease as headcount grows — weekly at 5, biweekly at 25, monthly at 50+"

# === SKIP CONDITIONS ===
skip_this_unit_if:
  - condition: "User needs a strategic operating cadence plan, not tactical meeting setup"
    use_instead: "Search knowledgelib.io for strategic operating cadence — no dedicated unit yet"
  - condition: "User is building a board meeting cadence specifically"
    use_instead: "business/startup/first-board-meeting-playbook/2026"
  - condition: "Team is fully remote and needs async-only communication design"
    use_instead: "business/startup-hiring/remote-team-setup-guide/2026"

# === AGENT HINTS ===
inputs_needed:
  - key: company_size
    question: "How many people are on the team right now?"
    type: choice
    options: ["1-5 (co-founders)", "6-10 (first hires)", "11-25 (teams forming)", "26-50 (departments emerging)", "50+ (scaling org)"]
  - key: work_mode
    question: "What is the team's work arrangement?"
    type: choice
    options: ["fully co-located", "hybrid (some remote)", "fully remote", "multiple time zones"]
  - key: existing_meetings
    question: "Does the team already have recurring meetings?"
    type: choice
    options: ["none — starting fresh", "a few informal ones", "too many — need to cut", "inherited enterprise structure"]
  - key: tool_stack
    question: "What collaboration tools does the team use?"
    type: choice
    options: ["Slack + Google Calendar", "Teams + Outlook", "Notion + Slack", "no preference — recommend tools"]

# === EXECUTION METADATA ===
execution:
  required_inputs:
    - name: "Current team roster and org chart"
      source: "founder/CEO"
      format: "document or list"
    - name: "Existing meeting inventory (if any)"
      source: "calendar audit"
      format: "spreadsheet or list"

  outputs:
    - name: "Meeting cadence calendar"
      format: "shared calendar with recurring events"
      description: "All recurring meetings configured with agendas, attendees, and 90-day review dates"
    - name: "Async alternatives map"
      format: "document"
      description: "Which updates moved to async channels, with tool configuration"
    - name: "Meeting hygiene rules"
      format: "document"
      description: "Written team agreement on meeting norms, shared in team handbook"

  tools_required:
    - name: "Google Calendar or Outlook"
      purpose: "Schedule and manage recurring meetings"
      tier: free
      cost: "$0"
      alternatives: ["Cal.com", "Calendly (for external)"]
    - name: "Slack or Teams"
      purpose: "Async standups, updates, and decision threads"
      tier: free
      cost: "$0 (free tier sufficient)"
      alternatives: ["Discord", "Twist"]
    - name: "Geekbot or Standuply"
      purpose: "Automated async standup collection"
      tier: free
      cost: "$0 for up to 10 users"
      alternatives: ["Slack workflows", "manual daily posts"]
    - name: "Loom"
      purpose: "Async video updates replacing show-and-tell meetings"
      tier: free
      cost: "$0 for up to 25 videos/person"
      alternatives: ["Notion clips", "screen recording"]

  credentials_needed:
    - service: "Calendar platform"
      type: "OAuth"
      where_to_get: "calendar.google.com or outlook.office.com"
      free_tier_limits: "Unlimited for Google Workspace / Microsoft 365"
    - service: "Geekbot (optional)"
      type: "Slack OAuth"
      where_to_get: "https://geekbot.com"
      free_tier_limits: "Free for up to 10 participants"

  estimated_duration: "2-4 hours for full audit, design, and implementation"
  estimated_cost: "$0 (all tools have free tiers sufficient for startups under 50 people)"

# === DISTRIBUTION ===
canonical_source: "https://knowledgelib.io/business/startup-operations/meeting-cadence-design/2026"
suggested_citation: "Source: knowledgelib.io — AI Knowledge Library (verified 2026-03-12)"

# === RELATED UNITS ===
related_kos:
  alternative_to:
    - id: "business/startup-hiring/remote-team-setup-guide/2026"
      label: "Remote team setup — communication tooling, async-first norms and response windows, time zone overlap policy, virtual culture rituals"

# === SOURCES ===
sources:
  - id: src1
    title: "Setting The Right Meeting Cadence"
    author: Zack Urlocker
    url: https://buildtoscale.substack.com/p/setting-the-right-meeting-cadence
    type: expert_guide
    published: 2024-11-15
    reliability: authoritative
  - id: src2
    title: "6 Must Reads to Run Fast, Efficient Meetings"
    author: First Round Review
    url: https://review.firstround.com/first-round-reviews-6-must-reads-to-run-fast-efficient-meetings/
    type: curated_guide
    published: 2024-06-10
    reliability: authoritative
  - id: src3
    title: "How We Communicate — The 37signals Guide to Internal Communication"
    author: 37signals / Basecamp
    url: https://basecamp.com/guides/how-we-communicate
    type: company_handbook
    published: 2024-01-01
    reliability: authoritative
  - id: src4
    title: "How To Find The Perfect Meeting Cadence"
    author: Fellow.app
    url: https://fellow.app/blog/meetings/meeting-cadence/
    type: product_guide
    published: 2025-01-20
    reliability: reliable
  - id: src5
    title: "Simplify Everything with The Meeting Pulse"
    author: EOS Worldwide
    url: https://www.eosworldwide.com/strong-in-six/simplify-everything
    type: methodology_guide
    published: 2024-08-01
    reliability: authoritative
  - id: src6
    title: "12 Meeting Effectiveness Metrics to Improve Productivity"
    author: Worklytics
    url: https://www.worklytics.co/blog/top-12-metrics-for-effective-meetings
    type: research
    published: 2025-03-01
    reliability: reliable
---

# Meeting Cadence Design for Startups

## Purpose

This recipe produces a right-sized recurring meeting calendar for a startup at its current headcount, paired with async alternatives that eliminate status-update meetings entirely. The output is a configured calendar with agendas, a documented async workflow, and written meeting hygiene rules — designed to keep meeting load below 15% of total team hours while maintaining alignment as the company grows. [src1]

## Prerequisites
<!-- Agents: verify ALL prerequisites before executing. Missing prerequisites = failed execution. -->

- [ ] **Team roster with roles** available from founder/CEO — list of names, titles, reporting lines
- [ ] **Calendar access** — admin access to shared Google Calendar or Outlook
- [ ] **Slack/Teams workspace** — for configuring async standup bots and update channels
- [ ] **Current meeting inventory** — export of all existing recurring meetings (skip if starting fresh)
- [ ] **Founder alignment** — CEO/co-founders agree on async-first philosophy before implementation

## Constraints
<!-- Hard rules. Agents: enforce throughout execution. Violating these = cadence bloat. -->

- Meeting hours must stay below 15% of total work hours per person. At 40 hrs/week, that is 6 hours max. [src6]
- No meeting exists to share information that could be written. Status updates, progress reports, and announcements are always async. [src3]
- Every recurring meeting carries a 90-day expiration date. If nobody advocates renewal, it dies. [src2]
- Meeting size caps: standups max 8 people, strategy meetings max 6, all-hands unlimited but time-capped. [src4]
- Default meeting length is 25 minutes (not 30) or 50 minutes (not 60) to build in transition time. [src1]

## Tool Selection Decision

<!-- Agent selects the right tool path based on user inputs.
     Each path leads to a different execution flow below. -->

```
Which path?
├── Co-located team, any size
│   └── PATH A: Physical + Calendar — Google/Outlook Calendar + whiteboard
├── Hybrid team, under 25 people
│   └── PATH B: Hybrid Light — Slack + Geekbot + Calendar
├── Fully remote, under 25 people
│   └── PATH C: Remote Async-Heavy — Slack + Geekbot + Loom + Notion
└── Any arrangement, 25+ people
    └── PATH D: Scaled Cadence — Slack + Geekbot + Loom + Calendar + Notion
```

| Path | Tools | Cost | Setup Time | Best For |
|------|-------|------|-----------|----------|
| A: Physical + Calendar | Google Calendar, whiteboard | $0 | 1 hour | Co-located teams wanting minimal tooling |
| B: Hybrid Light | Slack, Geekbot, Calendar | $0 | 2 hours | Mixed in-office/remote under 25 people |
| C: Remote Async-Heavy | Slack, Geekbot, Loom, Notion | $0 | 3 hours | Fully distributed small teams |
| D: Scaled Cadence | Slack, Geekbot, Loom, Notion, Calendar | $0-$50/mo | 4 hours | Growing teams crossing 25+ headcount |

## Execution Flow

### Step 1: Audit Current Meeting Load

**Duration**: 30 minutes
**Tool**: Google Calendar / Outlook export

Export the last 4 weeks of calendar data for all team members. Count total recurring meeting hours per person per week. Categorize each meeting as one of: decision-making, brainstorming, status update, relationship-building, or ceremony.

```
Audit checklist:
1. Export all recurring events from shared calendars
2. For each meeting, record:
   - Name, frequency, duration, attendee count
   - Category: decision | brainstorm | status | relationship | ceremony
   - Does it have a written agenda? (yes/no)
   - When was it last explicitly renewed? (date or "never")
3. Calculate: total meeting hours per person per week
4. Flag: any meeting categorized as "status" (candidate for async)
5. Flag: any meeting with no agenda (candidate for elimination)
```

**Verify**: Total meeting hours per person calculated. Status-update meetings identified.
**If failed**: If calendar export is unavailable, manually list meetings from memory with the team in a 15-minute session.

### Step 2: Design Cadence by Company Size

**Duration**: 45 minutes
**Tool**: Document editor (Notion, Google Docs)

Select the cadence tier matching current headcount. Do not copy the next tier up — add meetings only when the pain of not having them becomes real.

**Tier 1: 1-5 people (co-founders + first hires)**

| Meeting | Frequency | Duration | Attendees | Purpose |
|---------|-----------|----------|-----------|---------|
| Co-founder sync | Daily | 15 min | Co-founders only | Decisions, blockers, priorities |
| Weekly planning | Weekly | 50 min | Everyone | Set weekly goals, review last week |
| Retrospective | Biweekly | 50 min | Everyone | What's working, what's not, experiments |

Total sync time: ~2.5 hrs/week per person. Everything else is async. [src1]

**Tier 2: 6-10 people (first hires, pre-product-market fit)**

| Meeting | Frequency | Duration | Attendees | Purpose |
|---------|-----------|----------|-----------|---------|
| Leadership sync | Daily | 15 min | Founders + leads | Blockers, decisions needed today |
| Team standup | Async daily | — | Everyone | Geekbot: done/doing/blocked |
| Weekly all-hands | Weekly | 25 min | Everyone | Wins, key metrics, upcoming priorities |
| 1:1s | Weekly | 25 min | Manager + report | Growth, blockers, feedback |
| Sprint planning | Weekly or biweekly | 50 min | Product + eng | Scope, priorities, capacity |
| Retro | Biweekly | 50 min | Everyone | Process improvement |

Total sync time: ~3.5 hrs/week per IC, ~5 hrs for leads. Standup is async. [src2] [src5]

**Tier 3: 11-25 people (teams forming)**

| Meeting | Frequency | Duration | Attendees | Purpose |
|---------|-----------|----------|-----------|---------|
| Leadership L10 | Weekly | 50 min | Dept leads + CEO | EOS-style: scorecard, rocks, issues |
| Team standups | Async daily | — | Per team (4-8) | Geekbot per channel |
| All-hands | Biweekly | 25 min | Everyone | CEO update, wins, metrics, Q&A |
| 1:1s | Weekly | 25 min | Manager + report | Growth, blockers, feedback |
| Team sprint planning | Weekly | 50 min | Per team | Scope and capacity per team |
| Cross-team sync | Weekly | 25 min | Team leads only | Dependencies, handoffs |
| Retro | Biweekly | 50 min | Per team | Process experiments |

Total sync time: ~4 hrs/week per IC, ~6 hrs for leads. [src1] [src5]

**Tier 4: 26-50 people (departments emerging)**

| Meeting | Frequency | Duration | Attendees | Purpose |
|---------|-----------|----------|-----------|---------|
| Exec team L10 | Weekly | 90 min | C-suite / dept heads | EOS Level 10: scorecard, rocks, IDS |
| Dept standups | Async daily | — | Per dept | Geekbot or Slack workflow |
| All-hands | Monthly | 50 min | Everyone | CEO update, strategy, wins, Q&A |
| Skip-level 1:1s | Monthly | 25 min | Manager's manager + IC | Pulse check, unfiltered feedback |
| 1:1s | Weekly | 25 min | Manager + report | Growth, blockers, feedback |
| Team planning | Weekly | 50 min | Per team | Sprint or weekly goal-setting |
| Cross-dept sync | Biweekly | 25 min | Dept leads | Dependencies across departments |
| Product council | Biweekly | 50 min | Product + eng + design leads | Roadmap trade-offs, sequencing |
| Quarterly planning | Quarterly | Half-day | Leadership + team leads | OKRs, resource allocation, strategy |

Total sync time: ~4.5 hrs/week per IC, ~8 hrs for dept heads. [src1] [src2]

**Verify**: Cadence tier selected matches actual headcount. Total hours per person calculated and under 15% threshold.
**If failed**: If hours exceed 15%, cut the lowest-value meeting first (usually retro frequency or cross-team sync).

### Step 3: Set Meeting Templates

**Duration**: 30 minutes
**Tool**: Google Calendar, Notion, or Fellow.app

For each meeting in the cadence, create a recurring calendar event with a standing agenda embedded in the description. Every meeting must answer three questions before it starts: What decisions need to be made? What is the pre-read? Who is the DRI (directly responsible individual)?

```
Template structure for each recurring meeting:
---
Meeting: [Name]
Frequency: [Daily/Weekly/Biweekly/Monthly/Quarterly]
Duration: [25 or 50 min]
Attendees: [Roles, not names — roles survive turnover]
DRI: [Who runs this meeting]
Agenda:
  1. [Standing item 1 — e.g., "Review scorecard (5 min)"]
  2. [Standing item 2 — e.g., "Surface issues (10 min)"]
  3. [Standing item 3 — e.g., "IDS: Identify, Discuss, Solve (30 min)"]
  4. [Standing item 4 — e.g., "Action items + owners (5 min)"]
Pre-read: [Link to doc that must be read before meeting]
Expiration: [Date — 90 days from creation]
Success metric: [How we know this meeting is valuable]
---
```

**Verify**: Every recurring meeting has a calendar event with an embedded agenda template and a 90-day renewal date.
**If failed**: If the calendar tool does not support embedded agendas, create a Notion page per meeting and link it in the calendar description.

### Step 4: Establish Async Alternatives

**Duration**: 30 minutes
**Tool**: Slack + Geekbot/Standuply + Loom

Replace every meeting categorized as "status update" in Step 1 with an async mechanism. Configure the tools.

```
Async replacement map:
┌─────────────────────────┬──────────────────────────────────┐
│ Sync Meeting (kill it)  │ Async Replacement                │
├─────────────────────────┼──────────────────────────────────┤
│ Daily standup            │ Geekbot in Slack (3 questions:   │
│                          │ done/doing/blocked, posted 9am)  │
├─────────────────────────┼──────────────────────────────────┤
│ Weekly status report     │ Friday async post: each person   │
│                          │ writes 3-5 bullet update in      │
│                          │ #team-updates channel             │
├─────────────────────────┼──────────────────────────────────┤
│ Show-and-tell / demo     │ 2-3 min Loom video shared in     │
│                          │ #demos channel, async comments    │
├─────────────────────────┼──────────────────────────────────┤
│ FYI announcements        │ Written post in #announcements    │
│                          │ with emoji react for "read"       │
├─────────────────────────┼──────────────────────────────────┤
│ Decision that needs input│ Notion RFC doc with 48-hr         │
│ from many people         │ comment deadline, then DRI decides│
└─────────────────────────┴──────────────────────────────────┘
```

Geekbot configuration (Slack):

```
Channel: #team-standup
Schedule: Every weekday at 9:00 AM (team local time)
Questions:
  1. What did you accomplish yesterday?
  2. What are you working on today?
  3. Any blockers?
Participants: @team-channel
```

**Verify**: At least one status-update meeting eliminated and replaced with configured async tool. Geekbot (or equivalent) posting daily in the correct channel.
**If failed**: If Geekbot setup fails, use a simple Slack reminder: `/remind #team-standup "Post your standup: done/doing/blocked" every weekday at 9am`.

### Step 5: Implement Meeting Hygiene Rules

**Duration**: 30 minutes
**Tool**: Notion or Google Docs (team handbook)

Write and publish a short meeting norms document. Share it in the team channel and pin it. These rules apply to every meeting in the cadence.

```
Meeting Hygiene Rules (copy and adapt):

1. NO AGENDA, NO MEETING. Every meeting has a written agenda shared 24 hrs
   in advance. If the organizer skips this, any attendee can decline.

2. DEFAULT TO 25 MIN. Use 50 min only for planning or strategy sessions.
   Never schedule 60-minute meetings.

3. START ON TIME, END 5 MIN EARLY. Meetings begin at :00 or :30 regardless
   of who is present. End at :25 or :55 for transition.

4. 2-PIZZA RULE. If you can't feed the attendees with 2 pizzas, the meeting
   is too big. Split it.

5. STATUS UPDATES ARE NOT MEETINGS. If the primary purpose is sharing
   information, it's a Slack post, Loom, or written update — not a meeting.

6. DECISIONS NEED A DRI. Every meeting ends with: who owns each action item
   and by when. No orphan tasks.

7. 90-DAY EXPIRATION. Every recurring meeting has a renewal date. If nobody
   advocates for renewal, the meeting is deleted.

8. OPTIONAL ATTENDANCE OK. Mark attendees as "optional" generously. If
   someone's role doesn't require their input, they read the notes async.

9. MEETING-FREE BLOCKS. Protect at least one 4-hour block per day company-
   wide where no meetings can be scheduled (e.g., 9am-1pm).

10. QUARTERLY MEETING AUDIT. Every quarter, run Step 1 again. Kill meetings
    that have drifted from their purpose.
```

**Verify**: Document published and pinned in team communication channel. All team members notified.
**If failed**: If there is resistance to formal rules, start with just rules 1, 5, and 7 as a minimum viable set.

### Step 6: Measure Meeting Effectiveness

**Duration**: 15 minutes setup, then ongoing monthly
**Tool**: Calendar analytics + survey

Set up a monthly measurement loop to ensure the cadence stays healthy as the team grows.

```
Monthly meeting health scorecard:

Metric 1: Meeting hours per person per week
  - Pull from calendar data (Google Calendar API or manual count)
  - Target: < 6 hrs/week for ICs, < 10 hrs/week for managers

Metric 2: Meeting-to-async ratio
  - Count sync meetings vs async updates per week
  - Target: at least 60% of regular updates handled async

Metric 3: Agenda compliance
  - Spot-check 5 meetings: did they have a pre-shared agenda?
  - Target: 100%

Metric 4: Participant satisfaction (quarterly pulse)
  - Anonymous 1-question survey: "Are our recurring meetings valuable?"
  - Scale 1-5. Target: average > 3.5

Metric 5: Meeting renewal rate
  - At each 90-day expiration, what % of meetings are renewed?
  - Target: 70-80% (if 100% are renewed, you're not critical enough)
```

**Verify**: Scorecard template created. First baseline measurement completed.
**If failed**: If calendar analytics are unavailable, use a manual 1-week time audit by asking each person to track meeting hours.

## Output Schema

<!-- Exact format of the deliverable. -->

```json
{
  "output_type": "meeting_cadence_system",
  "format": "calendar + documents",
  "components": [
    {"name": "recurring_calendar_events", "type": "calendar", "description": "All meetings configured with agendas, attendees, and 90-day expiration dates", "required": true},
    {"name": "async_alternatives_map", "type": "document", "description": "Table mapping killed status meetings to async replacements with tool configs", "required": true},
    {"name": "meeting_hygiene_rules", "type": "document", "description": "Published team norms document, pinned in team channel", "required": true},
    {"name": "monthly_scorecard_template", "type": "spreadsheet", "description": "5-metric health scorecard for monthly meeting audit", "required": false}
  ],
  "expected_meeting_count": "5-12 recurring meetings depending on company size tier",
  "review_cadence": "quarterly"
}
```

## Quality Benchmarks

<!-- How to evaluate if the output is good enough. -->

| Quality Metric | Minimum Acceptable | Good | Excellent |
|---------------|-------------------|------|-----------|
| Meeting hours per IC per week | < 8 hrs | < 6 hrs | < 4 hrs |
| Async replacement rate for status meetings | > 50% | > 75% | 100% |
| Meetings with written agendas | > 70% | > 90% | 100% |
| 90-day renewal compliance | > 50% of meetings reviewed | > 80% | 100% |
| Team satisfaction score (1-5) | > 3.0 | > 3.5 | > 4.0 |

**If below minimum**: Re-run Step 1 audit. Identify the top 2 meetings consuming the most hours with the least decision output. Eliminate or convert to async.

## Error Handling

<!-- Common failures and recovery actions. -->

| Error | Likely Cause | Recovery Action |
|-------|-------------|----------------|
| Meeting load creeps above 15% within 60 days | New meetings added without killing old ones | Run quarterly audit (Step 1). Enforce 90-day expiration strictly |
| Async standups get ignored | No accountability or too many questions | Reduce to 1 question ("What's your #1 priority today?"). Add thread replies for blockers only |
| 1:1s become status updates | Manager defaults to asking "what are you working on?" | Retrain: share 1:1 agenda template focused on growth, blockers, feedback — not tasks |
| All-hands feels performative | CEO monologue with no interaction | Cap CEO update to 10 min. Add live Q&A (anonymous submission). Share metrics async beforehand |
| Teams resist meeting hygiene rules | Rules feel imposed, not collaborative | Co-create rules in a retro session. Start with 3 rules, add more after team sees value |
| Cross-team sync becomes a status round-robin | No one raises real issues | Switch to exception-based format: only speak if you have a dependency or blocker |

## Cost Breakdown

<!-- Real cost analysis so agents can warn users before execution. -->

| Component | Free Tier | Paid Tier | At Scale (50+) |
|-----------|-----------|-----------|----------------|
| Calendar (Google/Outlook) | $0 (Workspace free or included) | $6/user/mo (Workspace) | $6/user/mo |
| Async standup (Geekbot) | $0 (up to 10 users) | $2.50/user/mo | $2.50/user/mo |
| Video updates (Loom) | $0 (25 videos/person) | $12.50/user/mo | $12.50/user/mo |
| Meeting notes (Notion) | $0 (free plan) | $8/user/mo | $8/user/mo |
| **Total per person** | **$0** | **$10-$29/user/mo** | **$29/user/mo max** |

## Anti-Patterns

### Wrong: Copying enterprise meeting structures into a 10-person startup
Enterprise companies run weekly business reviews, monthly operating reviews, quarterly board prep, and cascading town halls because they have hundreds of people with fragmented context. A 10-person startup copying this structure spends 30-40% of its time in meetings solving problems that don't exist yet. The overhead kills execution speed. [src3]

### Correct: Start with the minimum viable cadence for your size
Use the tier system in Step 2. Only add a meeting when the team repeatedly encounters the specific problem that meeting solves. If you're not sure whether you need a meeting, you don't.

### Wrong: Using daily standups as the default for every team
Daily synchronous standups were designed for co-located Scrum teams shipping software on tight sprints. Applied universally — to marketing, sales, design — they become a ritual with no value. People recite yesterday's tasks without actionable discussion. [src4]

### Correct: Make standups async by default, sync only when blocked
Configure Geekbot or Standuply to collect daily async updates. Only convene a synchronous huddle when someone flags a blocker that requires real-time discussion. This saves 1.25 hours per week per team.

### Wrong: Running all-hands weekly at 50+ people
Weekly all-hands at scale becomes a broadcast nobody listens to. Attendance drops, engagement vanishes, and the CEO talks to a wall of muted cameras. At 50+ people, weekly is too frequent for org-wide sync. [src2]

### Correct: Shift to monthly all-hands with weekly written CEO updates
At 25+ people, move all-hands to biweekly. At 50+, move to monthly. Replace the missing weeks with a short written update (CEO sends a Friday email or Notion post with key metrics, wins, decisions, and context).

## When This Matters

Use this recipe when a startup needs to design or redesign its recurring meeting structure — especially at growth inflection points (5, 10, 25, 50 people) where the old cadence breaks down. This is an execution recipe, not strategy advice: it produces a configured calendar and documented norms, not a slide deck about meeting culture.

## Related Units

- [Operating Cadence Framework](/business/startup-operations/operating-cadence-framework/2026) — strategic cadence this recipe implements
- [One-on-One Meeting Framework](/business/startup-operations/one-on-one-meeting-framework/2026) — deep dive on 1:1 structure
- [Async Communication Design](/business/startup-operations/async-communication-design/2026) — async-only alternative for remote-first teams
- [Team Communication Handbook](/business/startup-operations/team-communication-handbook/2026) — where meeting norms get documented