Should I Hire When My Agency Is Overloaded?

A few months ago, I was on a coaching call with an agency owner who was convinced he needed to hire. He had two big projects in flight, the team was underwater, and he'd been carrying 12-hour days for six weeks. He told me he was going to hire a project manager and a junior designer.

I asked him a different question. I asked what would happen to the work if he changed nothing operationally and just kept going for another month.

He said it would be brutal but they'd get through it.

I asked what would happen if, instead of hiring, he stopped accepting any new work that wasn’t perfectly aligned with their ICP for sixty days and used the breathing room to standardize how the team was running the projects they already had.

He went quiet for a second and said the team would probably be fine. Maybe better than fine.

The instinct under pressure is to add a person. The actual fix, almost every time, is to look at the system that's making the work feel impossible, and the system rarely needs more people inside it. It needs less variation moving through it.

This post is the long answer to the question agency owners type into Google when they're standing inside that exact moment: “should I hire when my agency is overloaded?”

The short answer is no, with one specific exception. The rest of this is why.

Quick Take

• Hiring during overload usually adds drag rather than removing it, because every hire adds vectors that have to align before they add capacity. More people means more friction unless the system is ready to absorb them.
• A new hire's true capacity ceiling is roughly 60% of what it could be when systems and repeatability haven't been built first. You're paying full salary for a fraction of the output and writing off the rest as "ramp time."
• The right order is positioning, then standardization, then hire. Skip either of the first two and the hire becomes overhead, not leverage.
• The honest exception is arbitrage. If a hire can produce 2-3x what you pay them inside an existing repeatable offer, hire. Anything short of that is hope dressed up as headcount.
• Most agency owners don't have an accurate read on their own capacity. The overload is usually a measurement problem, not a workload one.
• The first move this week isn't hiring. It's auditing what your current team would be doing differently if the offer was sharper and the engagement template was real.

The One-Sentence Answer

No, you should not hire when your agency is overloaded, because adding headcount without first sharpening positioning and standardizing delivery imports the existing chaos into a larger team, which makes the chaos more expensive, slower to fix, and harder to see.

The longer answer has a structure: a mechanism that explains why hiring usually backfires, a coaching pattern that shows what actually breaks when owners hire too early, an order of operations that prevents the mistake, and a real arbitrage exception worth taking when it shows up.

Why Hiring Usually Adds Drag

The instinct to hire when overloaded comes from a basic math assumption. More hands equals more output. Two people can do twice the work of one. Three people can do three times the work of one. If the agency is running at capacity, hiring fixes the capacity problem.

That math holds in factories. It does not hold in service businesses, and it especially does not hold in service businesses where every project requires custom thinking from scratch.

Here's the mechanism. Every person you add to a company is a new vector. They have their own way of approaching the work, their own sense of what "good" looks like, their own pace, their own assumptions about scope, their own opinions about what to do when things go sideways. For the team to produce coherent output, all those vectors need to be moving in roughly the same direction. The more vectors, the more alignment work the system has to do to keep them pointing the same way.

In a small agency without sharp positioning or standardized delivery, that alignment work has nowhere to live except inside the founder's head. The founder is the alignment system. They make the call when two team members disagree on approach. They hold the picture of what the engagement is supposed to look like. They translate the work from how the client described it to how the team will execute it.

Adding a person doesn't reduce that load. It adds to it. The new person doesn't just need to do the work. They need the founder to align them, train them, correct them, ramp them, and then keep aligning them every time the work shifts. The founder's day didn't get easier when the headcount went up. It got more crowded with management decisions on top of the strategic and delivery decisions that were already there.

This is why so many agencies hire and immediately feel worse. The math said capacity should go up. The actual experience is that capacity went down because the founder is now spending hours managing people instead of doing the work that only they could do in the first place.

The deeper failure isn't the new hire. The new hire is doing exactly what new hires do. The failure is that the system wasn't ready to absorb them, and the cost of that gap is paid by the founder.

The 60% Rule

Here's the rule I keep coming back to with coaching clients. When you hire before you've standardized, the new person operates at roughly 60% of the capacity they'd hit in a system that was actually ready for them. Sometimes higher, sometimes lower. The 60% number is rough but the direction is consistent.

That gap shows up everywhere.

Their first month is not full-output. Onboarding a person into a bespoke agency takes longer than onboarding into a productized one, because there's no template to hand them. Every situation is novel, which means every situation requires senior input. They can't act independently for weeks because the patterns don't exist for them to copy.

Their decision-making is constrained by what they don't yet know. Even after onboarding, they're routing decisions back to the founder because they can't tell which calls are theirs to make. In a standardized system, the call is "do X when you see Y." In a bespoke system, the call is "ask Chris." Every call back to the founder is a slowdown for both of them.

Their context-switching tax is invisible but expensive. They're being pulled across multiple client situations that each require fresh learning. Their effective time on any one piece of work is half of what it should be, because every transition requires re-loading the situation from scratch.

Their work needs more review than the system was built to handle. The bespoke pattern means every output is unique enough that review can't be templated. The founder ends up re-reviewing things that, in a productized agency, the team would catch on its own.

If you add up those four costs, you land on something like 60% of nominal capacity for the first six to twelve months. You're paying full salary for a partial-output person, and the gap is being absorbed by the founder either as more hours or as accepted-quality slippage.

The hire isn't the wrong person. The hire is the wrong sequence.

Two Coaching Stories That Run Backward

I've worked with two agencies inside the last year where the lesson played out from the opposite direction. Both lost team members involuntarily. Both got more efficient afterward. Neither expected it.

The first agency lost two large clients in the same quarter. Revenue dropped enough that they had to let go of three team members. They were certain it was going to break delivery. What they found inside the next sixty days was that the remaining team was doing the same volume of work without the dropped capacity. Not the same volume of revenue (they'd lost the clients too) but the same effective output per active engagement. The team that was now smaller was getting the same work done as the team that had been larger.

When they sat down to figure out why, the answer wasn't flattering. The three people they'd lost had been absorbing senior bandwidth in ways nobody had named. The founder had been spending two or three hours a week on alignment conversations with each of them. After they were gone, those hours came back. The remaining team had to pick up some additional execution, but the absence of the alignment overhead more than paid for it. The math worked out backwards from what anyone expected.

The second agency made a deliberate cut. They had a couple of mid-level team members whose performance had been mediocre for a while without anyone naming it. They restructured. Two people left. The owner braced for delivery to suffer.

What happened instead was that the founder was forced to look at his systems for the first time. He had no choice. The headcount wasn't there to absorb the gap. So he wrote down how the engagements actually ran, sharpened the templates, and shifted some of what the team had been doing in real-time onto a documented pattern.

Six months later, the agency was delivering the same work at a substantially better margin than before, with a smaller team, and the owner was less involved in day-to-day delivery than he'd been in years. The cut forced the systematization that the larger team had let him postpone.

I want to be clear about what these stories are not. I'm not telling agency owners to fire people. I'm not saying the answer to overload is to shrink the team. The point is the inverse: a larger team can mask a system problem indefinitely. The fact that the team is keeping up by force of effort hides the fact that the underlying pattern would run cleaner with less effort if the system were better.

When you hire to relieve overload, you're often paying to keep the system unfixed.

The Order of Operations

The right sequence is positioning, then standardization, then hire. Each step assumes the one before it has happened. Skipping order is the most common mistake in sub-$1M agency operations, and it's the mistake that creates the conditions for "I need to hire" to feel true even when it isn't.

Positioning first. The signal that positioning is solid is simple: people are interested in the specific thing you do, and they're buying it. Not buying generic services. Buying the specific shape of work you've claimed. If your inbound calls open with "I saw your post about X and that's exactly what I'm dealing with," positioning is working. If your inbound calls open with "I'm not totally sure what you do but a friend mentioned you," positioning hasn't happened yet.

Positioning has to come first because everything downstream is shaped by it. The standardized engagement is a standardized version of *something specific*. You can't standardize an offer that hasn't been named. The hire is hired to deliver *a specific kind of work*. You can't recruit cleanly for a role that's defined by "whatever the client needs."

Most agencies that try to standardize before positioning end up with a beautiful template for work nobody is asking for. Most agencies that try to hire before positioning end up with a person whose role keeps shifting under their feet because the offer keeps shifting under the founder's feet.

Standardization second. Once positioning is sharp, the work starts to repeat. The same kinds of clients. The same kinds of engagements. The same kinds of decisions inside those engagements. Standardization is the act of writing down what's already repeating, so the team can run it without the founder being the alignment layer for every call.

The signal that standardization is sufficient is also concrete: a competent senior team member could run your most common engagement next month, end to end, without you on the senior decisions. If the answer is yes, the system can absorb a hire. If the answer is no, the hire is going to create more decisions for the founder, not fewer.

Hire third. When positioning and standardization are both real, a hire converts cleanly into capacity. The new person has a clear role, a documented pattern to follow, and decisions that route to the senior team rather than to the founder. The 60% capacity penalty drops dramatically. They can be at 80 to 90% of nominal output inside two months instead of six.

This is the version of hiring that actually feels like growth. The version where the founder hires before the first two steps are done is the version where hiring feels like work. And work that feels like work usually is.

More, Better, New

Once you've earned the right to hire, meaning positioning is sharp and the engagement is standardized, there's a sequence inside hiring itself that matters.

The first hire is More. Their job is to give you more capacity inside the work that already exists. They take execution off your plate so you can do marketing, run the business, and protect strategic time. They are, by design, a capacity hire. You're not hiring them to optimize anything. You're hiring them to absorb hours.

The signal you're ready for the More hire: you can describe their week in concrete tasks that you currently do, and those tasks are the kind of execution work that you would not miss doing. If you can't describe their week, you're not ready. You're hoping a person will figure out what to do, which is the most expensive way to hire.

The second hire, only after More is fully working, is Better. Their job is to optimize the system you've built. Sharpen the engagement template. Tighten the QA loop. Improve the handoffs. They make existing work run cleaner, faster, more reliably. This is usually a senior hire — someone who's run a similar pattern before and can level it up.

The Better hire is wasted on a system that hasn't been stress-tested by More first. You don't yet know what's actually breaking. You don't have the volume of repeated outputs to optimize against. The Better hire arrives with sharp instincts and gets put on a system too small to need them.

The third hire, only after Better is in place, is New. They're hired to expand into something the current offer doesn't cover. A new service. A new vertical. A new delivery model. This is the hire that adds optionality to the business.

Most agencies skip to New too fast. They hire someone to launch the new thing while the current thing is still bespoke and the founder is still the alignment system for everything. The new thing then competes with the existing chaos for the founder's attention, and the founder ends up running two unfinished systems instead of one finished one.

If you want a tripwire for when each hire is right, this is it. More is right when you have execution work you can describe in concrete weekly tasks. Better is right when you have an execution layer that's running and you can name three things in the system that should run faster. New is right when the existing offer is stable enough that adding to it doesn't break it.

Most "I need to hire" instincts are More disguised as Better, or New disguised as More. Naming which one you're actually trying to hire tends to clarify whether the hire is real or premature.

The Honest Exception: Arbitrage

There's a clean version of hiring during overload that works, and I don't want to pretend it doesn't exist. The frame is arbitrage. If you can hire a person who will produce 2 to 3 times what you pay them inside the existing offer, hire. The math works on its own.

The conditions for arbitrage to apply are specific. The offer has to be sharp enough that the role is defined. The engagement has to be repeatable enough that the new person can deliver against a pattern. The work has to be priced high enough that 2-3x cost is achievable inside the rate. And you, as the founder, need to be at least at $20K per month of revenue before you start adding people at all. Below that, the arbitrage math doesn't have enough margin to work; above that, it does.

If those conditions are met, hire. The decision is mechanical. You're trading $X in salary for $2X-3X in delivery capacity, and the gap is your margin. This is the situation that makes hiring straightforwardly correct.

The reason this exception isn't more common is that the conditions for it require that you've already done the positioning and standardization work. The arbitrage hire is the natural output of finishing the order of operations. It isn't an alternative path; it's where the path lands when it's been walked properly.

The mistake to watch for is calling something arbitrage that isn't. If the role is defined as "help me do whatever I'm doing," that isn't arbitrage. It's labor sharing. If the work isn't priced high enough that 2x cost still yields margin, the arbitrage doesn't pencil. The arbitrage frame is a clean test, and most "I should hire" instincts fail it. The ones that pass are usually obviously true once you run the math.

The other situation worth naming: sometimes hiring is the right call even though it's expensive in the short term, because it changes how everyone in the agency interacts. Adding a senior person can shift the culture toward more delegation and less founder-as-alignment-layer. That's a real benefit. It's also a slow benefit, and it doesn't relieve immediate overload. Don't confuse "this hire will be good for the agency in eighteen months" with "this hire will fix the thing breaking next week." Those are different decisions.

What Typical Agency Advice Gets Wrong

The standard agency-coaching answer to overload is some version of "hire when you're at capacity." It sounds reasonable. It's also not actually wrong if you take it literally. The problem is that almost no one has an accurate read on what capacity actually is.

Most agency owners measure capacity in hours. The team is working 50-hour weeks. The founder is working 60. The calendar is full. The math says capacity is exhausted.

That's not capacity. That's a workload measurement that includes a large amount of self-imposed waste. If the team is spending three hours a week in meetings that could be a Loom, that's not capacity. If the founder is on every senior decision because the team can't act independently, that's not capacity. If half the engagement time is going to context-switching across mismatched scopes, that's not capacity. The hours are real. The capacity isn't.

Real capacity is what the team could deliver if the system were running cleanly. In most overloaded sub-$1M agencies, real capacity is somewhere between 30 and 60 percent higher than nominal capacity. The agency feels at the limit, but the limit is mostly drag, not output.

When the standard advice says "hire when you're at capacity," it's accidentally telling you to hire when you've maxed out a poorly-running system. Hiring then locks the poorly-running system in place at a higher cost. The new headcount has to be supported by the same broken pattern, which means the new person becomes part of the broken pattern. The agency now has more revenue commitments, more salary obligations, and the same drag, just with more people inside it.

The accurate version of the advice is: hire when you're at capacity *inside a system that runs cleanly*. The first half is what most people hear. The second half is the part that does the actual work.

This is also why the most useful question to ask before hiring isn't "do I need more hands?" It's "what would my current team be doing differently if the offer was sharper and the engagement template was real?" Most owners can answer that question pretty quickly once they sit with it. The answer almost always reveals capacity that the existing team has but isn't being asked to deploy.

When Hiring Becomes the Bottleneck Instead of the Fix

There's a point in agency growth where the hire becomes its own constraint. The founder wants to hire. The math seems to support it. But the act of hiring well requires senior time the founder doesn't have, and the senior time isn't available because the agency is overloaded, and the agency is overloaded because there aren't enough people, and the loop closes.

This is why "I need to hire" sometimes stays true for six or twelve months without a hire actually happening. The conditions that make hiring necessary are the same conditions that make hiring impossible.

The way out of that loop is rarely to push harder on hiring. It's to take the same time pressure and use it to compress the engagement template instead. Two days of intensive work to write down how the most common engagement actually runs. Three days to template the proposal, the kickoff, the weekly checkpoints, and the handoffs. A week to clean up the references and tooling so that someone new could read it and follow along.

That week of work usually frees up more capacity than the hire would, and it also makes the hire much faster when you do get to it. The new person is walking into a documented system instead of a vibe.

Most agency owners are reluctant to take that week, because the immediate pressure says "I don't have a week to spare." That sentence is exactly true and exactly the trap. The week you don't have is the week that would give you the next year back.

The Move This Week

If you're inside an overload right now and convinced you need to hire, do this before you start the search.

Audit how the current team is actually spending time. A week of timesheets at 30-minute granularity, even rough ones. You'll find at least 20% of the team's time going to alignment, rework, scope ambiguity, or context-switching across mismatched engagements. That's the capacity that's hidden inside drag.

Write down what the most common engagement actually looks like, end to end. Proposal, kickoff, weekly cadence, deliverables, handoff, wrap. If you can't write it in a single document, the engagement is too bespoke to support a hire. The act of writing it down often reveals what to standardize.

Identify which decisions on that engagement currently route to you and which could route to the senior team. Most founders find that 30 to 50 percent of the decisions they're absorbing don't actually need them; they're being routed up because no one has practiced making them without the founder. Push them down. Senior team members get sharper from carrying decisions, not from being protected from them.

Then look again at whether you need to hire. In most cases, after these three moves, the overload has eased meaningfully. The capacity was always there. It was just buried.

If you've done all three and the overload is still real, and the math passes the arbitrage test, then hire. That's the version of hiring that compounds. The version that runs without these steps is the version that turns overload into a more expensive overload.

How to Tell the Hire Was Right

Six months after a hire that was timed correctly, you should see specific things.

The founder is on fewer senior decisions per engagement, not more. The hire didn't just absorb tasks; they absorbed decisions. If the founder is making just as many calls per project as before, the hire was a labor add, not a leverage add.

The engagement template feels more locked in, not less. A good hire forces the team to articulate how things actually run, because they need to. The template gets sharper because someone new needs to read it and follow it.

The agency takes on the next 25% growth in volume without proportional founder hours going up. This is the real capacity test. If revenue grows and founder hours grow with it, capacity didn't get added. If revenue grows and founder hours stay flat or drop, capacity actually got added.

The next hiring decision feels easier. Hires compound when they're built on the right system. Each subsequent hire is faster to onboard, faster to ramp, and faster to give responsibility to. If the second hire feels just as hard as the first, the system underneath isn't doing its job.

If those signals show up, the hire was right. If they don't, the hire was a Band-Aid on a system problem, and the system problem is still there, just with one more salary on the books.

FAQ

Isn't there a point where you're objectively at capacity and have to hire?

Yes, but it's much later than most agency owners think. The objective capacity ceiling is the point at which the team, running a cleanly standardized engagement on a sharp offer, cannot absorb the next client without breaking the engagement template. That's the real ceiling. Most sub-$1M agencies hit a felt ceiling much earlier because the engagement isn't standardized and the offer isn't sharp. The felt ceiling is real to the founder. It's not the actual capacity ceiling. The fix is to push the felt ceiling toward the actual one before adding headcount.

What if the overload is genuinely from too much demand?

That's the cleanest situation to hire into, and it's also the rarest. If the demand is from clients who fit the existing sharp offer, the engagement is standardized, and the math passes the arbitrage test, hire. If any of those three conditions are missing, the demand isn't actually demand for what you do well. It's demand for whatever you're willing to accept, which is a different problem and usually a positioning issue, not a capacity issue.

Can I hire a fractional or contract person to test the waters?

Yes, and this is often the right move. Fractional hires reduce the financial commitment and let you test whether the role actually exists in your business before you commit to a full-time salary. The risk is that fractional people don't get deeply integrated into the system, so they can't fix system problems. They can absorb tasks, but they're rarely the right move if you're hoping the hire will improve the agency itself. Use fractional for capacity, full-time for capability.

What if I can't afford to standardize first because I'm too busy?

This is the version of the trap that catches most agencies. The week you don't have is the week that would give you the next year. There's no clean answer. The honest path is to clear three to five days from the calendar by declining the next two prospects you'd otherwise take, using that time to standardize the most common engagement, and accepting the short-term revenue hit. Most owners can't bring themselves to do this. The ones who can usually compound out of the trap inside two quarters.

Should I tell my team I'm thinking about hiring?

It depends on why. If you're hiring to take work off the existing team's plate, telling them is a morale boost. If you're hiring because you're disappointed in current output, the hire signals that to the team in ways that often backfire. The cleanest version is to be transparent about the role and the reasoning, and to involve senior team members in defining what the hire is for. Their read on what's actually missing is usually sharper than the founder's, because they're closer to the work.

What about hiring during a known seasonal surge?

A short-term, defined-arc surge can be absorbed by contractors, fractional help, or temporary scope reduction on lower-priority work. Hiring a full-time person to absorb a three-month surge is almost always the wrong move, because the surge ends and the salary doesn't. The exception is if the surge is the leading edge of a permanent volume shift, in which case the question isn't really about the surge — it's about the long-term capacity profile, and the standard order of operations applies.

---

If you're sitting with the "should I hire?" question right now and want to run it against the actual diagnostic instead of the gut version, the Dynamic Agency Community is where agency owners work this out together. Join at dynamicagency.community.