The annual cost of daily standups (with math)

Daily standups are the poster child for "meetings that don't feel like meetings." Fifteen minutes, whole team, everyone already online. Surely the cost is negligible? Annualize it. A nine-person engineering team at typical mid-level TC can burn five figures a year on standup alone—before lengthening, topic drift, or the PM who joins "just for context."

Standup cost formula

Let n = attendees, d = workdays per year (often 260), s = standup seconds per day, tc_i = annual TC per attendee.

annual_standup_cost = Σ_i (tc_i ÷ 7,488,000 × s × d)

Meeterboard computes the same per-second logic; this article annualizes mentally.

Scenario A: nine mid-level engineers

Illustrative TC $250,000 each, 15 minutes (900 seconds), 260 days:

Per person per day: 250,000 / 7,488,000 × 900 ≈ $30.01

Nine people: ~$270/day

Annual: ~$70,200

That is a junior engineer salary equivalent in many markets—spent on status sync.

Scenario B: mixed levels

Same standup with seven mids ($250k) + one senior ($380k) + one EM ($320k):

Daily ≈ 7×25.01 + 38.04 + 32.01 ≈ $255 → annual ~$66,300 (senior/EM bump modest if most heads are mid).

Add a director who attends "when available" twice a week (30 min each):

Extra ~$4.40/min × 30 × 2 × 52 ≈ ~$13,728/year on top.

Scenario C: lengthening to thirty minutes

Doubling duration doubles cost. Standups that become problem-solving forums are thirty-minute meetings with standup branding—$140k+ in Scenario A.

When standups earn their burn

Standups can ROI positively when:

• blockers get resolved in under twenty-four hours because everyone heard them live
• distributed teams lack shared async rhythm
• new teams need rapid trust formation

They fail ROI when updates are round-robin Jira reads with no dependencies resolved.

Optimization playbook

Async standup in chat/tool with bot reminder; live only on blocker days.

Three-day live / two-day async hybrid cuts ~40% burn.

Smaller circle: only engineers who share dependencies; PM consumes async summary.

Hard fifteen with timer visible—run standup in Meeterboard once so the team feels second-by-second creep.

Measuring your real standup

Create a meeting in Meeterboard, add your team's bands, run one standup live (or simulate fifteen minutes). Multiply daily total by 260. Compare to async experiment for a month.

Standup vs retro vs planning — other agile ceremonies deserve the same math.

Caveats

PTO reduces effective days. Not everyone attends daily. Illustrative TC is not your employer's live Levels.fyi pull. Part-time members scale down.

Bottom line

Standups are not free coffee. They are recurring micro-purchases of team attention. Worth it sometimes—always priced.

Retro and planning: compare ceremony costs

Teams often debate standup length but ignore sprint planning and retros. A two-hour biweekly planning with ten mids ($250k) costs roughly $1,000 per occurrence in illustrative math—×26 per year ≈ $26,000. A one-hour retro with the same team adds half that annually. Together, agile ceremonies can exceed a standup's yearly burn if they are long and crowded.

Use Meeterboard once per ceremony type, annualize each, and prioritize the largest line item first. Cutting standup five minutes helps; cutting planning thirty minutes helps more when headcount is double.

Distributed standups across time zones

When standups split into EU and US sessions because nobody will join at 7am, you may duplicate labor: two standups × smaller groups can cost more than one larger sync unless attendance is strictly partitioned. Model both patterns in the calculator with representative bands before mandating a single global slot.

Reporting standup cost to leadership

Frame dollars as optional sync labor rather than wasted time. Example: "Daily 15m standup = ~$70k/year at current level mix; async experiment saved ~$28k equivalent focus weeks." Leadership responds to annualized numbers tied to headcount planning.

When standups should stay expensive

Early-stage startups with five founders, regulated teams with daily compliance check-ins, and incident-heavy weeks may rationally pay high standup burn. ROI review—not blanket cancellation—should drive the decision. See meeting ROI.

Tooling integrations teams ask for

Engineers often want Jira ticket auto-close from standup or bot summaries. Those features reduce talk time but have build cost. Compare engineering hours to build bots vs annual standup labor saved—sometimes automation ROI beats calendar cuts. Meeterboard gives the standup labor line item for that build vs buy debate.

Physical standup circles

In-office standups that run long because people linger with coffee behave like 25-minute meetings with standup labels. Time the circle honestly in Meeterboard once; lingering is visible in per-second climb even if calendar invite says fifteen minutes.

Async standup bots

Bots that nag for text updates still cost labor to write updates—usually cheaper than live sync but not zero. Compare async writing time (rough self-estimate) vs priced live standup for a fair A/B.

Closing note

Standups are habits. Price the habit annually once; then decide if the habit still earns its slot in the sprint rhythm.