Direct answer
Hire or outsource?
Why hire-or-outsource decisions go wrong
Most hire-or-outsource debates are really debates about certainty. A hire feels safe because the person is “ours”. Outsourcing feels safe because you can leave. Both feelings describe a real risk, but neither is evidence. The costs also differ in kind: a hire commits salary, management attention and a slow, sometimes legally regulated exit; an agency or contractor commits less per month but leaves knowledge, quality control and priorities partly outside your control.
The usual mistake is to choose the structure first and then argue for it. Choose instead from three properties of the work: how long the need will last, how much context the work requires, and how easily you can specify and check the output.
- Leans toward hiring: the work shapes your product or customer relationships, demand has been steady for many months, and quality depends on context that takes weeks to learn.
- Leans toward outsourcing: the scope is bounded and can be written down, demand is seasonal or uncertain, the skill is specialised and needed part-time, and the output is easy to inspect.
- Leans toward a hybrid trial: the signals disagree. This is the most common situation, and the reason a small test is worth running.
Pause before the recommendation
Three answers could change this decision.
- 01
Which part of the work creates knowledge or relationships the company must retain?
- 02
What evidence shows the workload will remain high enough for the next twelve months?
- 03
What becomes difficult or expensive to reverse after a permanent hire?
How to answer the three questions honestly
1. Which part of the work must the company own?
List the tasks in the workstream. For each one, ask whether losing the person who does it would cost you customer trust, product understanding or negotiating position. Only those tasks argue for an internal owner. Often only a slice of the work has to stay inside; the rest is execution that can be specified.
2. What evidence shows the workload will last?
Use invoices, tickets, tracked hours and pipeline, not forecasts. Look at the last twelve months month by month and separate steady demand from peaks. If you cannot name the customers or contracts behind the next twelve months, treat demand as unproven, however busy it feels today.
3. What becomes hard to reverse?
For a hire: notice periods and legal obligations (which vary by country), onboarding time, recruiter fees and the effect on the team if the role ends. For outsourcing: knowledge that stays with the supplier, switching costs, minimum contract terms and dependency. Write each item as “cost and time to undo”. A tidy list often changes the decision by itself.
“I do not know yet” is a valid answer. It tells you which measure the trial must produce.
Smallest reversible test
One internal owner. One external specialist. Four weeks.
Choose one real workstream. Give one employee clear ownership of the outcome and engage one external specialist for a tightly bounded contribution. Define the handover artefacts before the trial starts.
- Measure
- Cycle time, output quality, internal knowledge captured and hours spent on coordination.
- Success
- Delivery improves and reusable knowledge accumulates inside the company without excessive management load.
- Stop
- Stop if coordination consumes the capacity gained for two consecutive weeks or sensitive knowledge cannot be protected.
Running the four-week trial, step by step
- Pick one real workstream with a visible outcome, not a side task nobody will miss.
- Name one internal owner who is accountable for the result, and one external specialist with a written scope: deliverables, hours and price.
- Agree the measures before you start: cycle time, quality (rework or reviewer score), hours spent coordinating, and knowledge captured in documents or playbooks.
- Set two checkpoints, at the end of week two and week four, with a written stop rule.
- At the end, compare with the previous four weeks as a baseline and write a one-page decision: hire, keep the hybrid, outsource fully, or stop.
A good trial costs a fraction of the first quarter of a hire and can be finished without embarrassment in either direction.
Common mistakes
- Testing a task nobody cares about, so the result proves nothing.
- Letting the contractor do everything so the internal owner learns nothing.
- Comparing cost per hour instead of cost per outcome, and forgetting coordination time and rework.
- Skipping the baseline, so “better” is a feeling rather than a comparison.
- Deciding on the last day, in the mood of the last day.
- Using a contractor arrangement that a local authority could treat as employment. Check the rules where you operate.
Worked example
What changes after the questions?
A small software company believes it needs a permanent marketing hire because launches are repeatedly late.
The three questions reveal that positioning knowledge must remain internal, but specialist production work is variable and easy to specify.
The company assigns one internal product owner and contracts campaign production for four weeks before deciding whether a full role exists.
Second example: support for a growing product
A founder answers customer questions personally and wants to hire a full-time support lead. The three questions show that product knowledge must stay inside, but ticket volume has doubled only in the two weeks after each release. The founder keeps one internal owner for escalations and books a part-time contractor for the post-release peaks for four weeks, measuring response time, resolved-on-first-reply rate and hours spent briefing the contractor. Only then does the full-time role get a job description.
Frequently asked questions
Is it cheaper to outsource than to hire?
Not automatically. Compare the total cost per outcome, including management time, rework and the cost of knowledge that leaves with a supplier. A salary-versus-invoice comparison hides costs on both sides.
When should a small company hire its first employee instead of using a contractor?
When the work creates context you must own, such as customer relationships or product knowledge, and demand has been steady for months. Before that, a bounded contractor engagement usually carries less risk.
How long should the hire-or-outsource trial be?
Long enough to see a full cycle of the work. Two to six weeks suits most workflows; four weeks is a sensible default.
Can a contractor trial create legal obligations?
In some jurisdictions, long, exclusive and closely directed contractor arrangements can be treated as employment. Keep scope and control appropriate and ask a local adviser if you are unsure.
What if the trial result is unclear?
That is information: the scope or the measure was not sharp enough. Extend by two weeks with a narrower measure, or postpone the commitment.
Where this guide stops
A thinking tool is not an authority.
Sources and method notes
- Amazon 2016 letter to shareholders, “High-Velocity Decision Making” (one-way and two-way doors)
- Harvard Business Review: “Performing a Project Premortem” (Gary Klein, 2007)
This page applies those ideas through the original Decide Smaller three-question and reversible-test workflow.