What You're Actually Buying When You Hire Someone
This week I sat with four different clients who are all at the same inflection point: they've made a hire, or they're about to. And in every single conversation, the same tension showed up.
Not "can I afford this person?"
The real question: Can I actually give up what I'm hiring them to do?
That distinction matters more than the job description, the salary, or the onboarding plan. Because here's what I keep seeing: leaders make the hire, then quietly hold onto the work anyway. They hover. They check and re-check. They step back in "just this once." The role fills up, but their calendar doesn't change, their focus doesn't shift, and six months later they wonder why the hire didn't move the needle.
The hire was sound. The release was not.
One client this week hired an assistant and within weeks had 20-30 hours back on his calendar. He didn't know what to do with it at first. But he figured it out fast, and now he's planning his next three hires because he finally understands what leverage actually feels like. That's the upside.
Another client hired someone and is anxious because cash flow hasn't improved. But when we dug in, the problem wasn't the hire: it was that the leader hadn't changed his own behavior. He was still avoiding the revenue-generating work. He bought himself help and then kept doing what he'd always done. The hire didn't fail. The release did.
A hire is not a relief valve. It's a trade. You give something away so you can go do something more valuable with that time. If you don't actually do the more valuable thing, you've added overhead without adding leverage.
3 Levels, One Lesson
Solo Operator: The first hire is the hardest because it forces you to answer a question you've been avoiding: what is your time actually worth? If you're spending hours on tasks a capable person could handle at a fraction of your rate, you're not being diligent. You're being cheap with the wrong currency. Figure out what only you can do, and start protecting that time before you hire, not after.
Mid-Level Team: You probably have people, but you may not have leverage. Ask yourself: if your best team member doubled their output, would that free you to do more, or would it just surface the next bottleneck? Leverage isn't headcount. It's clarity about what you're supposed to be doing with your time once the work is covered.
Large Organization: At scale, you're hiring for judgment, not tasks. The leaders around you need to make decisions you'd be comfortable with, without asking you. And culture becomes an operational risk: every business is an expression of its values. If the people around you haven't internalized yours, they're not extending your culture. They're quietly building their own version of it. The business doesn't get hijacked all at once. It drifts, one decision at a time.
One Question for the Week
What are the three activities in your business that generate the highest return per hour of your time, and what percentage of your week are you actually spending on them?
Quick Hits
A hire only works if you're willing to give up the thing the hire is supposed to take from you.
The bottleneck is rarely the workload. It's usually the identity attached to the work.
Hiring for relief and hiring for leverage feel identical at first. They produce very different results at month six.
AI Tip
Paste a week's worth of calendar blocks into your AI of choice and ask: "Which of these could be fully owned by someone else with clear training and a defined standard?" The list will be longer than you expect. That's your hiring brief.
Worth Your Time
Two books that fit this week's theme perfectly:
Impact Players by Liz Wiseman. Why some people contribute far more than their role requires while others stay stuck in their lane. Required reading if you're trying to hire people who grow with the business instead of just filling a seat.
The Ideal Team Player by Patrick Lencioni. The three virtues that make someone coachable, hireable, and worth building around. If you're about to make a hire, read this first.




Comments