Team

Hiring engineers vs outsourcing: how to decide

In-house team, agency, contractors or a mix, a decision framework based on what you are actually optimising for, and the hidden costs on both sides that founders discover late.

3 min readBy Mayur Kale

Key takeaways

  • Hire in-house for anything that is your competitive advantage and will change continuously. Outsource what is well-defined, bounded, or needed faster than you can hire.
  • The real cost of hiring is not salary, it is three to six months of lead time before anyone is productive, and the risk of hiring wrong before you can evaluate engineers.
  • The real cost of outsourcing is knowledge that leaves when the engagement ends, unless you deliberately structure against it.
  • If you cannot technically evaluate work, you are buying judgement. Buy it explicitly rather than hoping it comes free.
  • The hybrid that usually works: a strong in-house lead who owns architecture, with external capacity around them.

The question is usually framed as a cost comparison, which is why it usually gets answered badly. Day rates are the least interesting variable.

The useful frame: what are you optimising for right now, speed, cost, or the accumulation of capability? You can have two.

What each option is actually good at

In-house builds institutional knowledge. Someone who has worked on your product for two years makes better decisions in five minutes than an outsider makes in a week, because they know which things break and why the odd bits are odd. That compounds, and it is the entire case for hiring.

An agency buys speed and a team that already works together. You skip recruitment, onboarding and the risk that your first hire is wrong. You pay a premium and you accept that the knowledge is on loan.

Contractors are the cheapest way to get specific, well-defined work done, provided you can specify it and evaluate it. That proviso is doing a great deal of work in that sentence.

The decision that actually matters

For any given piece of work, two questions:

  1. Is this our competitive advantage?
  2. Will it change continuously, or is it a bounded project?
Bounded projectContinuous change
Core advantageOutsource, transfer knowledge deliberatelyHire
Not coreOutsource, or buy itOutsource with a long-term partner

The top-right cell is the one people get wrong. Outsourcing the thing that makes you different, and that changes every week, means paying a coordination tax forever on the work where speed matters most.

The costs on each side

Hiring, honestly:

  • Three to six months from opening a role to productive output
  • A bad senior hire early is severe, one person is a large share of a small team
  • Your first engineer sets the technical culture for everyone who follows
  • You need someone who can evaluate engineers; if that is not you, this is harder than it looks
  • Salary is the smaller part; equity, tooling, management time and the cost of being wrong are the rest

Outsourcing, honestly:

  • Knowledge leaves at the end unless you deliberately structure against it
  • Specifying and reviewing is real work on your side, and it is not free
  • Communication is slower than a colleague at the next desk, always
  • Some firms build to deliver rather than to be lived in, the difference shows up in month eight
  • Rates are visible, so the cost feels larger than it is relative to loaded salary

Timing

Pre-product-market-fit: external, almost always. You need speed, you cannot yet describe the team you will need, and hiring wrong is expensive to undo. Get to a real answer first.

Early revenue, roadmap forming: hire your first engineer. Ideally someone senior who can own architecture and review external work. This is the highest-leverage hire the company will make.

Scaling: in-house core, external for surge capacity and specialist work. The core team owns the system; external teams take bounded pieces around it.

Any stage, specialist need: outsource. Nobody's first five hires should be a security specialist or a data engineer.

Making the hybrid work

The arrangement that works: one strong internal engineer who owns the architecture and reads every pull request, with external capacity for delivery.

The arrangement that fails: external architecture, internal implementation. Nobody owns the shape of the system, and the shape is what determines the cost of everything afterwards.

If you go hybrid, be specific about who decides. Ambiguous ownership between an internal lead and an agency lead produces two coherent plans and one incoherent system.

The honest version

If you can technically evaluate engineering work yourself, you have more good options and all of them are cheaper.

If you cannot, you are buying judgement, and the question is only where you buy it, an agency with accountability, a senior first hire, or a fractional CTO. All three are legitimate. What does not work is assuming judgement comes free with implementation capacity.

Frequently asked questions

Should a startup hire developers or use an agency?

Before product-market fit, an agency or contractors usually make more sense: you need to move faster than hiring allows, and the shape of the team you eventually need is not yet knowable. After you have a product people pay for and a roadmap that keeps changing, in-house becomes better value, continuous change is where the cost of coordinating an external team compounds.

What are the hidden costs of outsourcing development?

Knowledge leaving at the end of the engagement is the main one, and it is avoidable if you plan for it. Others: time spent on your side specifying and reviewing, which is real work; slower communication than a colleague at the next desk; and the risk of a codebase built to be delivered rather than to be lived in. All are manageable, none are zero.

What are the hidden costs of hiring in-house?

Lead time is the big one, three to six months from opening a role to productive output is normal, and can be longer for senior engineers. Then there is the cost of hiring wrong, which is severe early on when one bad hire is a large fraction of the team, and the reality that a first engineer sets the technical culture for everyone after them.

Can you mix both?

It is the most common arrangement that works. One strong in-house engineer who owns architecture and reviews everything, with external capacity for delivery. The failure mode is the reverse, outsourcing the architecture and keeping only implementation in-house, which leaves nobody accountable for the shape of the system.

How do I manage an outsourced team well?

Give them outcomes rather than tasks, insist on weekly deployed increments rather than status reports, keep the code in your repository from the first commit, and have someone on your side who reads the pull requests. If nobody internally is looking at the work as it lands, you will find out about problems at the end.

References & further reading

  1. [1]
  2. [2]

Turn the trend into shipped software

I contract as a senior fullstack and data engineer, building the production systems your customers and your reporting depend on.

Explore services↗