What You Still Do
Beemy counts what it takes off you. This page counts what it hands back to you to do.
The inbox cost calculator now nets a review-time term off its reclaimed figure. This is the honest case for that term: the three jobs that stay yours, and why the effort never reaches zero.
The short version
You still place what Beemy would not guess, approve what it drafted, and answer what it escalated. Only four categories can ever reach auto-send, and ten never can. We have not measured how much time that leaves you, so the calculator's review-share slider is our own guess, not a study.
On this page
Where your time goes
Three jobs that stay yours.
Every one of these sits in the code today, not in a future release.
You place what Beemy would not guess.
Beemy scores a new item against your own learned routing history. When nothing points clearly enough, it asks you to place the item yourself, rather than guessing.
PriorEngine.score · backend/src/pipeline/priors.ts, PriorEngine.score
You approve what it drafted.
A category at draft_only always routes its output to your approval before it sends. Beemy never sends from that category unattended.
PolicyEngine.evaluate · backend/src/policy/policyEngine.ts, PolicyEngine.evaluate (draft-only-level rule)
You answer what it escalated.
A high-stakes or novel action always escalates to you. Beemy never executes it on your behalf.
classifyStakes · backend/src/policy/categories.ts, classifyStakes; backend/src/policy/policyEngine.ts, PolicyEngine.evaluate
Why it does not reach zero
Six rules the policy engine enforces on every category.
None of these are bugs. Each one is a deliberate default-deny choice, and each one puts an item back in front of you.
A new user starts at read_only, for every category.
Beemy executes nothing until you promote a category by hand. No grant row means read_only, on day one.
PolicyEngine.getLevel · backend/src/policy/policyEngine.ts, PolicyEngine.getLevel (falls back to read_only when no grant row exists)
The ladder moves one rung at a time, per category.
The ladder runs read_only, then draft_only, then auto_with_categories. A forward move cannot skip a rung, and a skip attempt fails outright.
canTransition · backend/src/policy/levels.ts, LEVELS and canTransition; backend/src/policy/grantService.ts, GrantService.grant
Only four categories can ever reach auto-send.
Meeting confirmations, scheduling acknowledgements, simple acknowledgements, and routing or filing: that is the whole list.
SAFE_CATEGORIES · backend/src/policy/categories.ts, SAFE_CATEGORIES
Ten categories never auto-send, at any confidence.
Payment, invoice, financial commitment, legal commitment, contract, hiring or firing, apology, bad news, promise, and first contact with a VIP: none of these can ever reach auto-send.
EXCLUDED_CATEGORIES · backend/src/policy/categories.ts, EXCLUDED_CATEGORIES; classifyStakes forces high stakes for each one
An ambiguous item waits for you, by default.
A classification commits only above a 0.75 confidence score, with at least a 0.15 lead over the next best guess. Anything short of that waits in your queue.
CLASSIFY_CONFIDENCE_THRESHOLD · backend/src/pipeline/config.ts, CLASSIFY_CONFIDENCE_THRESHOLD and CLASSIFY_MARGIN; backend/src/pipeline/pipeline.ts, decide()
A busy hour sends more to you, not less.
A category caps at 20 auto-sent actions an hour, and your account caps at 50. Past either cap, Beemy asks you instead of sending.
DEFAULT_POLICY_CONFIG · backend/src/policy/types.ts, DEFAULT_POLICY_CONFIG (perCategoryCap, globalCap); PolicyEngine.rateCapReason
What we cannot tell you yet
The ceiling, stated plainly.
This is the part that makes this page worth reading. We would rather name the ceiling than let a slider imply we've measured past it.
We have not measured how long this review work takes you.
The 20% review-share slider on the inbox cost calculator is our own guess, not a study. Move it to your own number.
n/a · src/data/research.ts, assumptions["review-share-pct"]
We track two of your workload numbers, and publish neither yet.
The backend counts a quarantine rate and a correction rate for every account. We have not published either figure.
classificationMetrics · backend/src/pipeline/metrics.ts, classificationMetrics (quarantineRate, correctionRate)
There is no undo, in the code, today.
Nothing in the backend reverses a sent message or a filed item once it lands. Catch a mistake before it sends.
n/a · no undo/rollback path exists anywhere in backend/src today
There is no approval queue shipped yet.
require_approval is a decision the policy engine returns. The surface that would hold that queue for you to work through is still being built.
PolicyDecision · backend/src/policy/types.ts, DecisionOutcome ("require_approval"); no approval-queue table or route exists in backend/src today
When this is a bad trade
Four kinds of inbox where the trade is small.
Your mail is mostly payments or invoices.
Beemy can draft a reply, and it will never send one alone. Payment and invoice mail always escalates to you.
Your mail is mostly contracts or legal commitments.
The same limit applies. Beemy drafts a first pass; you still decide, every time.
Your mail is mostly hiring or people decisions.
Beemy stays in draft mode for hiring, firing, and other decisions about people. It never sends those for you.
Your mail carries bad news, an apology, or a promise.
Beemy escalates that message to you. It never sends bad news, an apology, or a promise on your behalf.
Beemy still triages and drafts every message. You still approve almost everything it writes, because the categories that fill an inbox like that are the ones this site names as excluded.
What to do about it
Three moves that actually shrink your share.
Correct early.
A correction is Beemy's training signal, not wasted time. Fix a mis-filed item as soon as you see it.
PriorEngine.learn · backend/src/pipeline/priors.ts, PriorEngine.learn (LEARN_INCREMENT, DECAY_FACTOR)
Walk one low-stakes category up the ladder first.
Pick one low-stakes category. Promote it to draft_only, then to auto_with_categories, before you try the rest.
canTransition · backend/src/policy/levels.ts, canTransition
Put your own review share into the calculator.
Move the review-time slider on the inbox cost calculator to your own number, and see your real net hours back.
n/a · see /inbox-cost
Then put your own number into the inbox cost calculator. The review-share slider is yours to move.
Read next
Get your time back.
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