Your First Agency Hire: When, Who, and What It Costs

The first hire is the point where an agency stops being a person who does the work and becomes a business that delivers it.

It is also the decision most often made from exhaustion. Someone is working every weekend, a big project lands, and the response is to hire whoever is available quickly. Six months later there is a person on the payroll who is 40% utilised, the founder is still working weekends because delegating turned out to be harder than doing, and the cash position is worse than before.

This guide covers when to hire, what to hire first, the arithmetic that tells you whether you can afford it, how to write a role that attracts the right person, and what to do in the first ninety days.

When to hire

Three signals, all of which should be true.

You have turned work away, repeatedly, for three months. Not once. A single busy period is a scheduling problem; a consistent pattern is a capacity problem. Three months is long enough to distinguish them.

Your capacity plan shows sustained overrun. Committed hours exceeding available hours, week after week, across a rolling eight-week view. This is the objective version of "we feel busy," and it is the one worth acting on.

There is pipeline, not just current load. A hire is a bet on the next twelve months, not the last three. If the current overload is one large project ending in eight weeks, a contractor is the correct answer.

The signal that is not sufficient on its own: feeling overwhelmed. Overwhelm is frequently a process problem - bad estimating, absorbed scope, no QA checklist so everything comes back - and hiring against a process problem simply adds a person to a broken system, at cost.

What to hire first

Almost always delivery, and the reasoning is structural.

Most small agencies can sell more than they can produce. The founder's network, reputation and existing clients generate more demand than one person can serve, which means the binding constraint is production capacity rather than lead flow. Hiring sales into a delivery constraint produces more work you cannot deliver, and the fallout lands on the clients you already have.

The exception is genuine: if you are consistently at 60% utilisation and cannot find work, your constraint is demand and a sales or marketing hire is right. But test that honestly against your actual utilisation figures rather than impressions - our guide to utilization rate covers the measurement.

Within delivery, hire for what you are worst at, or slowest at, or dislike most. Not a copy of yourself. A founder who is an excellent designer and a reluctant project manager should hire the project manager, even though hiring another designer feels more obviously productive. The work you avoid is the work that silently blocks everything else.

Workamajig's overview of agency roles and Saka's breakdown of the core agency roles are both useful for seeing the standard shapes before deciding which one your constraint actually matches.

The arithmetic

Do this before writing a job description.

What the hire costs. Salary × roughly 1.25 for employment costs, plus equipment, software licences and recruitment. A £40,000 salary is realistically £52,000-55,000 in year one.

What they can produce. A full-time delivery person generates about 1,000-1,100 billable hours a year after holiday, internal time, admin, and realistic utilisation. Not 2,080. Our guide to calculating a billable rate walks through why the gap is that large, and it is the single most common miscalculation in agency hiring.

The revenue they need to generate. 1,000 hours × your rate. At £90/hour that is £90,000 against a £55,000 cost - viable. At £45/hour it is £45,000 against £55,000, which loses money every year regardless of how good they are.

The ramp. They will not be at full productivity for three to six months. Budget for it. A hire who reaches full utilisation in month five has generated perhaps 60% of a year's output in year one.

The cash gap. You pay salaries monthly and get paid on terms. A new hire consumes cash from day one and generates invoiceable work from roughly week three, paid in week nine. Check the 13-week cash forecast before committing, because this is precisely how growing agencies hit cash trouble in a good quarter.

Employee, contractor, or neither

Three options, and the decision should be deliberate.

A contractor suits variable or uncertain demand, specialist skills needed occasionally, and testing whether a role is genuinely permanent. Higher hourly cost, near-zero commitment. Covered in our guide to working with freelancers and contractors.

A full-time employee suits work that is permanent, needs deep knowledge of your systems and clients, or requires client trust - account leads and project managers particularly. Lower hourly cost, high commitment.

Neither, yet - the option most often overlooked. If the constraint is process rather than capacity, a hire will not fix it. Look first at whether you are absorbing scope without change orders, estimating badly, or underpricing. Recovering ten hours a week from process is cheaper and faster than recruiting, and it is frequently available.

Writing the role

Two principles.

Describe the outcome, not the CV. "You will own delivery on three to five concurrent client projects, running them from kickoff to handoff, and be the main day-to-day contact for those clients" tells a candidate what their week looks like. A list of required tools does not.

Be honest about the stage. A four-person agency is not a scaled organisation and pretending otherwise attracts people who will be disappointed. Say that processes are still forming, that the person will help shape them, and that variety comes with ambiguity. The right candidate finds that appealing; the wrong one self-selects out, which is exactly what you want at this size.

Include the salary. Roles without a stated range get fewer and worse applicants, and it wastes everyone's time to discover a mismatch at offer stage.

Interviewing for the thing that matters

At a small agency, the differentiator is rarely raw skill. It is judgement under ambiguity, because there is no process to fall back on.

Three questions that reveal it:

"Tell me about a project that went wrong. What did you do?" You are listening for ownership and for a coherent account of what they changed afterwards. Someone who has never had a project go wrong has either not done enough or is not being straight.

"A client asks for something small that is outside the agreed scope. What do you do?" There is no single right answer, and the reasoning is everything. You want someone who recognises the tension rather than reflexively saying yes or reflexively refusing.

"What would you need from us in your first month to be effective?" Reveals self-awareness and how they think about onboarding - which tells you a great deal about whether they will thrive without a structured programme.

Run a paid trial task wherever practical. A few hours of real, representative work, paid at their rate. It is far more informative than any interview and it respects the candidate's time.

The first ninety days

The hire is not the decision; the first ninety days determine whether it works.

Have work ready. The most common failure is hiring for future capacity and having nothing concrete for week one. Line up their first project before they start.

Give them one client relationship early, small and low-risk. Ownership accelerates competence faster than shadowing does.

Set the delegation boundary explicitly. What they decide alone, what they check first, what always comes to you. Ambiguity here produces either paralysis or unpleasant surprises, and both are avoidable with one conversation.

Accept slower and different. They will do things differently and initially worse. If you correct every deviation you will train them to check everything with you, which recreates the bottleneck you hired to remove.

Review at 30, 60 and 90 days. Short, specific, both directions. Problems surface early and cheaply when there is a scheduled place for them.

Our guide to onboarding a new team member covers the structure in detail.

The alternatives to hiring

Before committing to a permanent hire, four options are worth genuinely evaluating rather than dismissing.

A contractor for the peak. If the overload is a specific project or a known busy period, a contractor covers it at higher hourly cost and zero ongoing commitment. Our guide to working with contractors covers the break-even: roughly, if the role would be busy above your utilization target, hire; below it, contract.

Raising prices. If you are turning work away, that is a demand signal, and demand exceeding supply is the textbook condition for raising rates. Raising prices 15% and hiring nobody frequently produces a better outcome than hiring at the current rate - more margin, same volume, no management overhead. See raising your rates.

Fixing the process. A meaningful share of "we need another person" turns out to be scope absorbed without change orders, estimates that are systematically optimistic, or rework caused by no QA checklist. Recovering ten hours a week from process is faster and cheaper than recruiting, and it does not add a fixed cost.

Declining work. Genuinely an option, and an underrated one. If the work you would be hiring to service is low-margin, declining it and keeping capacity for better-fitting work improves the business without any hiring risk.

The honest test: if you fixed the process and raised prices, would you still need the person? If yes, hire. If you are not sure, the other two are cheaper experiments.

Where to find people

Three sources, in order of how well they usually work for small agencies.

Your network and your clients' networks. The highest-quality source by some distance. A person who comes recommended by someone who knows your work arrives with context and a filter already applied. Tell your clients and peers you are hiring and be specific about the role.

Communities in your discipline. Local meetups, discipline-specific forums, alumni of agencies you respect. Better signal than a generic job board because the people there are engaged with the craft.

Job boards last. They work, and the volume is high and the filtering expensive. If you use them, the salary range and a genuinely specific role description do most of the filtering for you.

What consistently underperforms at this size is recruiters. Not because they are bad, but because their fee against a first-hire salary is a large proportion of the risk you are already taking, and they are least effective at exactly the roles small agencies hire first - generalists who need to fit a particular culture.

Junior versus experienced

The second decision after choosing the function, and the trade-off is usually framed as cost when it is really about time.

An experienced hire costs more and produces sooner. They need context rather than training, can be given a client relationship within weeks, and will improve how you work by bringing patterns from elsewhere. The risk is fit - a senior person joining an unstructured business may find the ambiguity intolerable, or may want to change things you decided deliberately.

A junior hire costs less and is a training commitment. They will be net-negative for the first two to three months, because someone experienced has to spend real time developing them. That is fine if you have that time and a disaster if you do not.

The question that decides it: who will train them, and do they have capacity? If the honest answer is "the founder, who is already the bottleneck," a junior hire will underperform and it will not be their fault. Agencies frequently hire junior to save money and then discover the saving was notional because the training never happened.

For a genuine first hire, experienced is usually the right call - you are buying capacity, not building a team yet, and you have no training infrastructure. Juniors make more sense once there is someone whose job includes developing them.

What to pay

Two principles that prevent the common errors.

Pay at or slightly above market for the role. Underpaying a first hire is a false economy at a scale where one person is a large proportion of your delivery capacity. The cost of them leaving after eight months - recruitment, lost ramp, the gap the team absorbs again - exceeds several years of the difference.

Do not offer equity instead of salary at this stage. It is common and it usually goes badly. An agency is a services business with no obvious liquidity event, so equity has ambiguous value to the holder and creates real complexity for you. If you want to share the upside, a profit-share arrangement is cleaner, easier to explain and easier to unwind.

Check the arithmetic against the 1,000 billable hours calculation before settling on a number. A salary that makes the role unprofitable at your current rates is a signal to fix the rates first.

Two questions to answer before you advertise

What does this person own in twelve months? If you cannot answer concretely, the role is not yet defined enough to hire against. "Helping out" is not an outcome and it produces a hire who never quite has a job.

What will you stop doing? A hire only creates capacity if something moves off your desk permanently. Founders frequently hire and then keep everything, delegating fragments while retaining ownership - which produces cost without relief. Name the thing you are handing over before they start.

The trial period and what to do with it

Most jurisdictions allow a probation period. Used properly it is genuinely useful to both sides; used as most agencies use it - as a formality nobody revisits - it is worthless.

Set explicit expectations for it at the start. What should be true at three months. Not vague ("settled in") but specific: owning a small client relationship, running a project end to end, working without checking every decision.

Review at 30 and 60 days, not just at the end. The point of a probation period is that problems are correctable while they are small. A first review at day 89 is not a probation process, it is a verdict.

Be honest at 90 days. If it is working, say so warmly and widen the remit. If it is not, say that too. Continuing past the point where you know is unkind to them - they can feel it - and expensive for you.

Distinguish fit from onboarding failure. The commonest reason a first hire struggles is that nobody had time to bring them in properly. That is your problem rather than theirs, and the honest test is whether the things they are getting wrong were ever explained. Our guide to onboarding a new hire covers the structure that prevents it.

After the first hire

Two things change once there are two of you, and neither is obvious in advance.

You are now managing. That is a distinct job with its own time cost - one-to-ones, feedback, unblocking, development. Budget four to six hours a week for it, because it is real work that will otherwise be done badly in the gaps.

Your process has to leave your head. Everything that worked because one person knew it now needs to exist somewhere shared: how projects run, what "done" means, how requests arrive, what gets checked before delivery. Our guide to quality assurance covers the checklist half of this.

The agencies that struggle after their first hire are usually the ones that treated it as adding capacity rather than as becoming a different kind of business. It is the second, and the transition is worth expecting.

The mistakes that cost most

Hiring a mirror of yourself. Comfortable and it doubles a strength while leaving every weakness exactly where it was.

Hiring for the pipeline you hope for. Bet on signed work and consistent overrun, not on the large proposal that might land.

Hiring junior to save money without capacity to train. A junior hire is a training commitment. If nobody has time to train them, they will underperform and it will not be their fault.

Not delegating after hiring. The most common and most human. The founder keeps the interesting work, hands over fragments, and concludes the hire is not working. Delegating whole outcomes rather than tasks is the skill, and it is uncomfortable at first.

Hiring instead of raising prices. If margin is thin because you are underpriced, adding headcount multiplies the problem. Fix the pricing first - see raising rates - because a hire at the wrong rate makes every future month worse.

The offer and the first week

Two small things that disproportionately affect whether a good candidate accepts and stays.

Make the offer quickly and warmly. Good candidates are usually in more than one process, and a fast, personal offer beats a slightly higher one that arrives a week later after silence. Call before you email.

Be specific about what happens next. Start date, what their first week looks like, who they will work with, what they will be doing on day one. A candidate deciding between two offers frequently chooses the one where they can picture the first week.

Then have the work genuinely ready. The single most common first-hire failure is someone arriving to an empty desk in every sense - no access, no project, no clear first task - and forming an impression in three days that takes months to correct.

The honest summary

The first hire is expensive, slow to pay back, and the point at which an agency owner stops being the best person at everything in the business.

Get three things right and most of the rest follows: hire against a sustained capacity constraint rather than a busy month, hire delivery rather than sales, and check the arithmetic - 1,000 billable hours at your rate against a fully-loaded cost - before you advertise.

And then delegate whole outcomes rather than tasks, which is the part nobody warns you is the hardest.