Most founders ask the wrong question when considering a hire. The question is rarely whether to hire. It is almost always when, and to do what specifically.
Asked too early, a hire adds cost without solving the actual constraint. The new person needs to be taught what is in the founder's head, which means the founder is now doing the original work plus the work of teaching. Productivity drops in the short term, and if the role was unclear to begin with, it never recovers.
Asked at the right time, a hire transforms the business. Output multiplies. The founder graduates to higher-leverage work. The structural ceiling that was capped at one person's hours lifts.
The difference between the two scenarios is whether three conditions hold before the hire is made. This post is the protocol for that test, plus the realistic math of what to expect once the hire is in place.
The Three Conditions
A hire pays back when:
Condition 1: The work consistently exceeds your capacity for at least 90 days.
Not a busy week. Not a busy month. Ninety days minimum of consistent overflow. The reason for the duration is that short-term overflow is usually a project, it ends, and the work compresses back into available capacity. Long-term overflow indicates a structural pattern that will not resolve without additional hands.
The 90-day measurement is also the point where the founder has lived with the overflow long enough to know what kind of work is actually piling up. Hiring for "I am too busy" is hiring blind. Hiring for "I am consistently behind on customer onboarding emails by 2-3 days, the volume is averaging 40-50 per week, and this has held for the last 90 days" is hiring with definition.
Condition 2: The role would generate revenue greater than its cost.
The math has to work, both ways:
- Direct math: the role's output produces revenue (a salesperson, a delivery person, a marketer producing leads). The role earns more than it costs.
- Indirect math: the role frees the founder to produce revenue (an admin person freeing the founder to deliver work, an operations person freeing the founder to sell). The freed-founder time produces more than the role costs.
If neither math works, the role is not yet worth filling, even if the founder is busy. Hiring to relieve busyness without producing revenue is borrowing against the future without an income source to pay it back.
The conservative test: a $60K role should generate at least $90-120K in revenue (directly or via founder leverage). If it does not, the hire is operationally a luxury.
Condition 3: The standard operating procedure for the role is written and tested.
Not "we have a vague sense of how this should work." Written. With specifics. Tested by you running it for at least 5-10 reps yourself, so the SOP reflects the actual job and not your imagination of the job.
The reason: a new hire's first task is learning the role. If the role is undefined, the new hire spends their first 30-60 days trying to figure it out, often incorrectly. By the time the role is clear, the hire has either failed (unclear job) or developed habits that do not match the actual operation.
A written, tested SOP changes the onboarding from "figure out what this job is" to "execute this job." The first version produces results in week one or two, not month three.
If all three conditions hold, the hire pays back. If any one is missing, the hire is premature.
The 50% Rule
Once the hire is made, expect about 50% of your output in the same role.
Not because the hire is weak. Because that is the math of delegation early on. The first version of any role, executed by someone other than the founder, produces roughly half the output the founder produces. The reasons are structural:
- The founder has accumulated context the hire does not yet have
- The founder has implicit shortcuts that do not appear in the SOP
- The founder integrates the role with adjacent work in ways the hire cannot yet see
- The founder makes judgment calls that the hire has to escalate
Over time (usually 6-12 months), a strong hire closes that gap. Some hires get to 80-90% of founder output in the role. A few exceed the founder, particularly in roles where the founder was operating outside their strength.
The 50% rule has implications for the hiring math. A founder who produces 100 units of output in a role and hires someone for that role does not double output to 200. They produce 150, their original 100 minus the time they now spend managing the hire (call it 30 units), plus the hire's 50% (which is 50 units after subtracting their ramp inefficiency early on). Net: 150.
The math becomes:
Output without hire: 100 (founder full-time on this role) Output with hire: 150 (founder freed for 70 units of higher-leverage work + hire's 50)
The 50 units of hire output and the 70 units of founder leverage time are what justify the hire. If the higher-leverage work the founder shifts into is worth less than 70 units, the hire was structurally a wash. If it is worth significantly more, the hire is a win.
The Hiring Ramp Math
The 50% rule applies steady-state. The early ramp is worse.
A typical hire's productivity curve:
- Month 1: 10-20% of founder output. Mostly learning, ramp, supervision overhead.
- Month 2: 25-35%. Operating semi-independently on routine work.
- Month 3: 40-50%. Steady-state for most hires by end of quarter one.
- Months 4-12: 50-80%. Continued improvement as the hire integrates context and judgment.
Two implications.
First, the founder cannot expect leverage in month one. The first month is typically a productivity drop relative to before the hire, the founder is doing their own work plus training. Founders who do not budget for this dip often pull the plug on the hire before the math turns positive.
Second, the hire that is going to work usually shows progress visible by month three. A hire that is still at 20% productivity at the end of month three is unlikely to reach 50%. The 90-day mark is the right point to evaluate whether the hire is on track or whether the role-fit is wrong.
The Common Failures
Failure 1: Hiring to relieve busyness. The founder is overwhelmed. Hires to relieve the overwhelm. The new hire arrives, the founder is now also training someone, the overwhelm gets worse before it gets better. The hire either departs or settles into producing 30% of founder output, where they cost more than they generate. The founder is no better off than before.
The fix: hire when conditions 1-3 above hold, not when overwhelmed.
Failure 2: Hiring for the work the founder doesn't want to do, regardless of leverage. Founders often hire to offload the work they personally find unpleasant, admin tasks, customer service, financial bookkeeping. This can work, but only if the math holds. Hiring a $50K admin person to free a founder for $40K worth of higher-leverage work is a structural loss disguised as productivity.
The fix: the question is not "what do I want to stop doing." It is "what would I be doing instead, and is that worth more than this hire's cost."
Failure 3: Hiring without a written role. The founder has a sense of what the role should be, but no written description, no tested SOP, no defined success metrics. The hire arrives, both parties spend three months figuring out the job, and the role either solidifies into something useful or fails.
The fix: write the role first. Test the SOP yourself. Document what success looks like in 30, 60, 90 days. Then post the job.
Failure 4: Treating the first hire as a generalist. Founders sometimes hire a single person to do "everything I'm doing", a kind of clone that takes on whatever the founder needs offloaded. This produces no specialization, which means no measurable productivity gain in any specific area. The hire ends up being a junior version of the founder, which is rarely what the business actually needs.
The fix: hire for a specific role with specific output expectations. Generalist hires are usually executive assistants, which is a defined role with genuine specialization, not a vague offload.
When NOT to Hire
Three signals that hiring is not the right move yet.
Signal 1: The work is still being figured out. If the founder is still iterating on the offer, the customer profile, the marketing approach, hiring locks in choices prematurely. The hire is structured around the current version, which may not be the version that survives. Better to let the work stabilize first, then hire to scale what is working.
Signal 2: The cash flow does not support the hire. A hire is a multi-year commitment. The cash flow today has to support the role's salary plus benefits plus operating overhead, with cushion for downturns. Founders who hire on optimistic projections often have to lay off six months later, which is more expensive than the original hire decision.
The conservative test: 6-12 months of full salary plus operating costs in cash reserves before making the first hire. The number can be lower for revenue-confident businesses; it should not be lower for early-stage ones.
Signal 3: The role would replace something the founder loves doing. Hiring to offload work the founder genuinely enjoys produces a strange dynamic, the founder becomes the supervisor of work they would prefer to be doing. This frequently causes the founder to micromanage, second-guess the hire, or take the work back. The role fails not because the hire was weak but because the founder did not actually want the role filled.
The fix: hire to offload work the founder does not love or does not produce well. Keep the work the founder loves and excels at as core founder work, even at the cost of some scaling.
The First Hire vs. Subsequent Hires
The first hire is structurally different from later hires.
The first hire establishes how the founder thinks about delegation, how SOPs get written, how performance gets evaluated. The patterns set with the first hire repeat across every subsequent hire. If the patterns are bad, the second and third hires inherit the dysfunction.
Subsequent hires benefit from the structures the first hire forced into existence. SOPs already exist. Hiring criteria are already known. The founder has practiced the meta-skill of identifying the role, defining it, hiring for it, and managing it.
The first hire takes longer and costs more relative to its output than later hires. This is normal. The investment is partly in the hire and partly in the systems that the first hire makes the founder build.
What This Produces
A hire made under the right conditions, against a written role, with realistic ramp expectations, produces a different operation.
Within 30 days. The founder's calendar shifts. Work the hire is taking on starts to come off the founder's plate. The first month often feels less productive (training overhead), but the structural change has begun.
Within 90 days. The hire is at or near steady-state output. The founder is experiencing the first meaningful leverage from the role. The higher-leverage work the founder has shifted into starts producing visible results.
Within a year. The hire is fully integrated, often producing closer to founder-level output in the role. The business has adjusted to operating with two people on the work that was previously one. Capacity has lifted in a way that opens new options, taking on more customers, launching adjacent products, freeing the founder for partnerships or strategic work that did not exist before.
Across years. The pattern set by the first hire compounds. The second and third hires take less time to ramp, because the systems exist. The founder graduates further from execution, into the work that only they can do, the strategic decisions, the customer relationships that require founder presence, the vision that defines what the business becomes.
The team is downstream of how the founder operates. The right hire, made at the right time, against a defined role, is the founder's way of operating made portable. Done well, it is the most leveraged decision a small business makes.
That is the protocol. Three conditions before hiring. Written, tested role. 50% expected output, ramping over 90 days. Hire for leverage, not for relief.
The hire that pays back is the hire that was earned in advance.
The Seven Figure Framework. An email series on positioning, metrics, and execution for founders ready to scale. Free.