Beemy · beemy.co
Printed from beemy.co/inbox-cost/for/team-managers/
Calculator · Team managers
Between 1:1s, a full inbox and a status update that's always due, there's no time left to triage carefully. Start from a team manager's week below, then move every slider until it matches yours.
Starting point: Team managers
A starting point, not a measurement of any real manager's time: more 1:1s than hours in the day, plus a recurring status update. Every slider below is yours to move. See the numbers for how we picked it.
Your numbers
Per year
Show the maths
Hours/day × working days = hours/week on email. Add recurring reports and newsletter/news reading, then multiply by 52 weeks. No hidden multipliers.
A placeholder for the value of your time, yours to adjust. Move the slider to match your own rate, and the rest of the maths follows it.
Triage (read, classify, decide, draft a first pass) is repetitive and context-dependent rather than judgement-heavy, and it's most of the time in most inboxes we've looked at early in beta. The remaining share is judgement calls that still come back to you. This is our own working assumption rather than a measured industry figure, and we haven't yet published usage data from our own beta to replace it with a real one.
We have not measured this figure. Every draft still waits for a one-tap review until its category earns level 2, and only four categories (meeting_confirmation, scheduling_ack, simple_ack, routing_filing) can ever reach auto-send — see /what-you-still-do for the full case. Twenty percent is our own guess at what that ongoing review still costs you, not a study of it. Move the slider to your own number; this default exists to be replaced. See what you still do for the full case.
Want the deeper argument for why triage (not raw hours) is the real cost? Read the real cost of email overload.
Sources & assumptions: the 117-emails-a-day figure above is Microsoft WorkLab's own 2025 telemetry; the 60% reclaim rate, the 20% review share we subtract back out, and every preset's starting numbers are our own assumptions, not citations. Every number this calculator uses, sourced or assumed, is on /the-numbers.
Where the hours actually go
A scheduling question turns into twenty replies before anyone actually answers it. Reading the whole thread just to find the one decision inside it eats a chunk of the morning. One clear answer, sent early, would have closed the thread before it reached twenty replies.
A meeting ends with five things to chase, and by lunchtime three of them are already forgotten. Somebody still has to notice which owner has gone silent, then follow up without nagging the rest. A nudge sent the same day keeps the list from growing past what anyone can track.
A project update means opening six different docs and pulling the same figures out again. Nothing about the update has changed since last week, only the effort of rebuilding it from scratch. A template that pulls straight from those docs turns the copying into a quick check.
A new invite lands and the honest answer depends on a calendar that takes a minute to check properly. Confirming it right, instead of guessing, adds up across a week full of invites. A calendar check that runs itself would turn each invite into a single tap.
Read next
Beemy is in private beta. Join the waitlist and go from connect to a quiet, triaged inbox before you close your laptop tonight.
You're in the hive. We'll buzz you when it's your turn.
While you waitLast updated
Links do not work on paper. Open the address above to follow them.
To join the waitlist, go to beemy.co/waitlist.