The cost of manual work is best understood as a hidden payroll: the hours your team spends on status updates, re-typing data, chasing approvals, and assembling reports, multiplied by their loaded hourly cost. For a typical 10-person team, that’s often 40–60 hours a week — more than a full-time salary spent on work nobody was hired to do.
Nobody’s job description says “spend Friday afternoon copying numbers from the CRM into a slide deck.” And yet, on most teams, that’s exactly where Friday afternoon goes. The administrative burden on teams doesn’t show up on any org chart or budget line — which is precisely why it survives budget review after budget review, quietly compounding.
This post is about making that cost visible. We’ll walk through the invisible second job every role carries, a simple audit you can run this week to calculate your own hidden payroll number, and the costs that never show up in a spreadsheet at all. The product we build makes a brief appearance near the end, but the audit stands on its own — run it whether or not you ever talk to us.
The second job nobody was hired for
Look at any role on your team and you’ll find two jobs stacked on top of each other. The first is the one on the job posting: the salesperson sells, the accountant closes the books, the recruiter recruits. The second job is the connective tissue around the first, and it looks remarkably similar across every department:
- Status updates. Writing the weekly summary, prepping for the check-in, answering “where are we on this?” in three different Slack channels.
- Re-typing data between tools. The lead from the form into the CRM. The CRM into the forecast sheet. The forecast sheet into the deck. The same number, keyed four times.
- Chasing approvals. Sending the request, waiting, nudging, escalating, nudging again. The approval takes thirty seconds; the chasing takes thirty minutes.
- Assembling reports. Pulling numbers from five places into one document that gets skimmed for ninety seconds on Monday.
- Follow-up emails. “Just circling back.” “Bumping this to the top of your inbox.” Not the first email — the third, fourth, and fifth.
- Calendar tennis. “Does Tuesday at 2 work?” “How about Wednesday?” Six emails to book a thirty-minute call.
None of these tasks is hard. None takes long individually. That’s exactly the trap: each one is too small to fix, so nobody fixes any of them, and together they eat a quarter of the week.
How much time is wasted on busywork? Run this audit
You don’t need a consultant or a time-tracking rollout to answer this. You need one meeting and some honest arithmetic. Here’s the exercise:
- List the recurring tasks. Ask each person (or each function) to list the administrative tasks they do every week that aren’t the core of their role. Use the six categories above as prompts.
- Estimate hours per week. People underestimate, so ask for a range and take the middle. Don’t argue over precision — you’re sizing an iceberg, not weighing it.
- Multiply by loaded hourly cost. Salary alone understates what an hour costs you. Loaded cost — salary plus taxes, benefits, tools, and overhead — typically runs 1.25–1.4× base. A $75,000 salary is roughly $100,000 loaded, or about $50 per working hour.
- Annualize it. Weekly cost × 50 working weeks. That’s your hidden payroll number.
Here’s an example scenario for a 10-person team where loaded cost averages $50/hour. Suppose the audit surfaces this:
| Recurring busywork | Team hours/week | Weekly cost | Annual cost |
|---|---|---|---|
| Status updates and meeting prep | 12 | $600 | $30,000 |
| Re-typing data between tools | 10 | $500 | $25,000 |
| Chasing approvals and follow-ups | 8 | $400 | $20,000 |
| Assembling recurring reports | 8 | $400 | $20,000 |
| Follow-up and reminder emails | 8 | $400 | $20,000 |
| Scheduling and calendar tennis | 6 | $300 | $15,000 |
| Total | 52 | $2,600 | $130,000 |
Fifty-two hours a week is more than a full-time role. In this scenario, a 10-person team is effectively paying an eleventh, invisible salary — $130,000 a year — for work that produces nothing customers ever see. Your numbers will differ; the point is that once you write them down, the administrative burden on your team stops being a vague complaint and becomes a line item you can act on.
What does busywork cost beyond the money?
The dollar figure is the easy part. The costs that don’t fit in the table are usually worse:
The context-switching tax. Busywork doesn’t arrive in a tidy block; it arrives as interruptions. Every “quick status update” pulls someone out of deep work, and the re-focusing cost is paid on top of the task itself. Ten five-minute interruptions cost far more than fifty minutes.
Morale. You hired sharp people to sell, build, and close — and they know it. Every hour spent re-keying data is an hour of being underused, and being underused is corrosive in a way that being overworked is not. “You didn’t hire them for this” isn’t a slogan; it’s what they’re thinking.
Your best people leave first. The people most frustrated by administrative drag are exactly the ones with the most options. Busywork functions as an invisible retention tax that’s levied most heavily on your top performers.
Dropped balls. When busywork overflows — and it always overflows in the busiest weeks, which are also the highest-stakes weeks — things slip. The follow-up that didn’t go out. The renewal nobody chased. The report that shipped with last month’s numbers. The cost of manual work includes the manual work that didn’t happen.
Why does busywork survive every efficiency push?
If this is so expensive, why hasn’t it been fixed? Two reasons.
Each task is too small to fix individually. Nobody writes a business case for eliminating “chasing approvals.” Any single task is fifteen minutes a week; the fix — evaluating tools, building a workflow, training the team — costs more than the task. So it survives. Busywork is death by a thousand line items, each individually beneath attention.
Tools automate steps, not responsibilities. The last decade of workflow software genuinely helped, but almost all of it automates a step: send one email, update one cell, post one notification when a form is filled. The responsibility — notice the invoice is overdue, decide the right tone for the third reminder, chase the promise-to-pay, escalate when it breaks, report on all of it — still belongs to a human. Automating steps leaves the human as the glue between the steps, and gluing is itself busywork. You’ve replaced typing with orchestrating.
The shift: delegate responsibilities, not clicks
The pattern that actually removes busywork isn’t a faster tool for each step. It’s moving the whole responsibility off a person’s plate — the way you would with a new hire. “Own accounts-receivable follow-up” is a responsibility. “Send this reminder email” is a click.
This is the idea behind AI employees: named, autonomous workers you delegate an ongoing responsibility to, end-to-end. Instead of a human watching the invoice table and triggering reminder emails, an AI employee owns the loop — watches for overdue invoices, drafts the escalating reminders, tracks promises to pay, follows up when they break, and reports back daily. The human’s job shrinks to the part that genuinely needs judgment: reviewing and approving what goes out. Drafts are prepared; a person still sends them.
That’s a different category from automation, and it maps directly onto the audit you just ran: each row in your table is a candidate responsibility to delegate, not a set of steps to script. If the concept is new, what an AI employee actually is covers it properly, and the ROI math picks up exactly where your hidden-payroll number leaves off.
Frequently asked questions
How do I measure how much time my team wastes on busywork?
Run a one-week audit: have each person list their recurring administrative tasks (status updates, data re-entry, chasing approvals, assembling reports, follow-ups, scheduling), estimate hours per week for each, then multiply by loaded hourly cost — roughly 1.25–1.4× salary. Annualize the total. Self-reported estimates are imperfect but directionally reliable, and the exercise takes one meeting.
Which busywork tasks are best to delegate first?
Start with tasks that are recurring, rule-describable, and low-risk when reviewed before anything goes out — invoice reminders, report assembly, status digests, intake triage, follow-up sequences. Avoid starting with anything requiring judgment calls you couldn’t write down, and keep a human approval step on everything customer-facing at first.
Isn’t this what interns and virtual assistants are for?
Sometimes — but a VA is another salary on the visible payroll, needs training and management, works set hours, and turns over. Delegating busywork to a person also just moves the morale problem to someone else’s job description. The stronger comparison is cost and consistency: an AI employee handles the repetitive loop around the clock, while your people (including any VAs) keep the work that needs human judgment.
Is busywork really expensive enough to prioritize fixing?
Run the audit before deciding. Teams that assume the answer is “not really” are usually anchoring on any single task — and each task genuinely is small. The cost lives in the sum: in the example scenario above, a 10-person team’s busywork totaled 52 hours and $130,000 a year, more than an entire additional salary.
The audit is the whole ask this week: one meeting, one table, one number. If the number surprises you — it usually does — pick the biggest row and look at whether a Turtle Solution Pack already covers it; most install in 15–35 minutes and every one of them drafts for human approval rather than acting alone. Either way, you’ll never look at “just circling back” the same way again.