In-house team or agency: an honest comparison
The argument is usually framed as control versus cost. In practice the deciding factor is whether you can keep a team busy and growing for years, not months.
The utilisation problem
A two-person in-house team needs roughly two people’s worth of continuous work to be efficient. Below that, you are paying for capacity you are not using, or for specialists you cannot justify hiring.
Agencies pool that utilisation across clients, which is why they can offer design, backend, mobile and DevOps without each being a full-time hire.
Where in-house genuinely wins
When the software is the product, when decisions need to happen daily with deep context, or when the domain knowledge is too specialised to hand over without months of onboarding.
In those cases the right structure is often a small permanent core team supported by specialists brought in for defined pieces.
The handover clause
Whatever you choose, insist on documented architecture, repository access in your own organisation, and a working deployment that a new engineer can run. Ownership that exists only in someone’s head is not ownership.
Common questions
- Can we start with an agency and hire later?
- Yes, and it is a common path. The condition is that documentation and repository ownership are part of the engagement from day one, not something requested at the end.
- What is the biggest risk with an agency?
- Key-person dependency. Ask who specifically will work on your project, and what happens if that person leaves. Good agencies answer this without hesitation.
Next step
If this question is live in your business right now, describe the situation and you will get a written view on the options, including whether you should build at all.
Discuss your projectRelated notes
All insightsCustom software or off-the-shelf: how to decide
A practical framework for choosing between configuring an existing product and commissioning custom software, based on where your process actually differs.
ReadStrategyHow to write a technical brief that gets accurate quotes
The brief structure that separates a project that can be estimated from one that cannot, with the eight sections worth writing before you talk to any developer.
ReadStrategyRebuild or repair: an honest test for an ageing website
How to tell whether your existing website needs a migration or a targeted fix, using five checks that take an afternoon rather than a month.
Read