Free Calculator
Should You Delegate This Task? Or Just Do It Yourself?
The instinct to keep doing it is real. The math is usually wrong. This calculator shows the real break-even point, training amortization, and 3-year savings of delegating.
How long the task takes you, with your current expertise
Base salary. We auto-load it by 1.3x for benefits + taxes.
The person you would delegate to. Same loading applied.
Your time to teach them once, including Q&A
Your time to review & correct while they are learning
After this many, review overhead drops to near zero
Expected % of early work you will redo or fix
Verdict
Delegate. The math is not close.
You save $4,160/year, reclaim 98 hours, and break even after ~4 instances.
You do it
$9,360
per year
They do it (Y1)
$5,200
with training + review
They do it (Y2+)
$4,732
fully ramped
3-year savings
$13,416
cumulative
Year 1 Cost Comparison
Year 1 delegation cost includes: $186 training + $155 review overhead + $4,732 employee time + $124 quality catch-up.
Break-Even Point
After how many instances does delegation become cheaper than doing it yourself?
~4
instances to break even
At 52 instances/year, you break even in week 4. Every instance after that is pure savings.
What You Actually Get Back
Hours reclaimed
98 hours/year
~1.9 hours per week
% of your work week
4.7%
assuming a 40-hour week
The question is not whether this time is worth reclaiming. It is what you will do with it. A reclaimed hour on your calendar is only valuable if it flows to higher-leverage work: strategy, people decisions, stakeholder conversations, or actually thinking. If it just flows to more email, delegation did not create value, it just shifted it.
What This Result Actually Means
The "I'll just do it myself" instinct is almost always wrong.
Short-term, delegation looks slower. Training and review eat your week. Long-term, delegation compounds. This task will happen again, and again, and again. Every future instance you delegate is time you do not spend on it. That is the trade most managers miss.
The quality drop is bounded. The cost of keeping it is not.
A 20% quality hit on 5 ramp instances is $124. The cost of keeping the task is $9,360 per year, forever. Bounded pain vs. unbounded cost. This is not a close call on paper. Emotionally, it is always a close call. That is the whole problem.
Delegation is growth capital for the person receiving it.
This calculator only captures the dollar math. The bigger return is not on your P&L. It is in their career. Every task you keep instead of teaching is an hour of their growth you denied. Over a year, that is 50+ hours of learning they did not get. That cost shows up in retention surveys, not spreadsheets.
Why Delegation ROI Is Almost Never Calculated
Most managers make delegation decisions based on feeling, not math. The feeling usually goes: "I could teach this, but it would take longer than just doing it myself. So I will just do it." That reasoning is short-term correct and long-term catastrophic. A task done by you once is an hour lost. A task done by you 52 times per year for 3 years is 156 hours lost, plus all the second-order costs: you become a bottleneck, the person you should have trained never grows, and your whole team plateaus at the ceiling of what you personally can produce.
The Math Behind the Calculator
We use loaded hourly cost (salary ÷ 2,080 × 1.3) to approximate what the company actually pays per hour of someone's time. The 1.3x factor covers benefits (health insurance, 401k match), payroll taxes (FICA, unemployment), and standard overhead. This is the accepted approximation used by most corporate finance teams when building labor cost models.
For the delegation scenario, we add four costs: (1) a one-time training investment equal to your hourly cost × training hours, (2) review overhead during the ramp-up period equal to your hourly cost × review hours per instance × number of ramp instances, (3) the employee's time to do the task at their hourly rate, and (4) a quality correction cost equal to the quality drop percentage × ramp instances × task value.
The break-even calculation compares cumulative cost of both paths instance by instance. The moment the delegation path's cumulative cost drops below the manager-does-it path, that is your break-even point. For most recurring tasks, this happens within 3-7 instances. For weekly tasks, that is the first 4-8 weeks. After that, every instance is net savings. This is why the "I'll just do it myself" instinct is so dangerous: the cost is invisible in week 2 and enormous in month 12.
Three Scenarios Where You Should NOT Delegate
- Tasks that happen fewer than 3 times per year. Training cost is fixed. Frequency amortizes it. If you teach someone a process that runs twice annually, the amortization never catches up. Keep it, or batch-train someone as part of a broader cross-training effort (where the cost spreads across multiple tasks).
- Tasks that require managerial judgment or authority. Performance reviews, salary decisions, firing, representing the team to senior stakeholders, strategic direction. These are not delegation candidates because the authority itself is the value, not the task. Delegating these undermines your role and confuses accountability. See our guide on how to delegate as a new manager for the full decision framework.
- Tasks where a mistake has outsized downside. Legal filings, board deck numbers, customer escalations for tier-one accounts, anything regulated. The bounded quality cost assumption breaks down when the downside of one mistake is a lawsuit or a churned customer worth $500K. For these, the math is not the question, the risk profile is.
For everything else, which is typically 60-80% of what lives on a manager's calendar, the math is usually decisive and usually in favor of delegating. The instinct to keep things is the #1 cause of new-manager burnout. Our article on time management for new managers goes deeper on this trap.
How to Actually Delegate (Once the Math Is Clear)
Knowing you should delegate and actually doing it are different things. Most managers fail at the handoff, not the decision. The three moves that matter:
- Teach once, deliberately. Do not explain as you go over the course of three tasks. Block one dedicated training session, walk through the why, the how, the edge cases, the failure modes. Record it if possible. Training as byproduct of doing is 3-5x slower than training as an event.
- Define the authority level explicitly. "Do it and tell me" is different from "do it and I will check before it ships" which is different from "propose it and I will decide." Most failed delegations failed here. Be specific about where the decision lives and what quality bar triggers escalation.
- Review against outcomes, not style. The fastest way to kill delegation is to re-do the work yourself "because they did it slightly differently." If the outcome meets the bar, leave it. Style is your preference. Outcomes are the deal.
If you want a complete system for the 12 delegation decisions new managers face most often (decision matrix, authority levels framework, task briefing template, review checkpoints, and a growth-tracking tool), the Delegation Matrix Kit gives you all of it in one PDF.
Frequently Asked Questions
When is it actually faster to just do it myself?
How do I account for the training cost upfront?
What about the quality drop while they are learning?
What if their hourly cost is higher than mine (e.g. a senior specialist)?
What counts as "loaded hourly cost"?
How do I handle tasks that only my direct expertise can do?
Stop Doing. Start Teaching.
The math says delegate. The next question is how. These resources walk you through the framework.