Agency or In-House: How to Choose

The usual framing asks which is cheaper. The better question is whether the work will still be there, at the same intensity, in eighteen months.

Agency or In-House: How to Choose — Troiana insight cover

In short

Use an agency for bursts of specialised work, new builds and fast starts when you lack the skills or the time to hire. Build in-house when the work is continuous, central to your competitive advantage and needs deep product knowledge. Compare full costs, including recruitment, management and gaps in skills. Many companies do best with a hybrid: an agency to launch, and internal ownership over time.

The question to ask first

Will you have a full-time role's worth of this work every week, for years? If so, hiring starts to make sense. If the work comes in bursts, such as a redesign this year and very little next year, an employee will be underused and an agency will fit better.

Second question: is this work what makes you different? Things that define your product and how you compete usually belong closer to the company. Things that every company needs done well, but which don't set you apart, can more easily be bought.

Core to your advantageNot core
Continuous workIn-houseIn-house lead, or a retainer
A defined projectAgency to launch, in-house to runAgency
A simplification of the two questions above, using the hybrid options the article describes further down.

When an agency makes sense

  • A defined project with a beginning and an end, such as a new website, a rebrand or a first product version.
  • You need several skills at once. One project can need strategy, design, front end, back end, content and SEO, which are hard to find in a single hire.
  • You need to start soon. Agencies can usually begin much faster than you can recruit, even allowing for their own schedule.
  • You're testing something uncertain. You can stop a contract more easily than you can undo a hire.
  • Your team needs outside challenge. People who've seen many companies can spot patterns that insiders miss.

When in-house makes sense

  • The work is continuous. A product with a steady stream of changes generates more than enough work for a full-time person.
  • Deep context matters. Knowing your customers, your systems and the history of past decisions lets people make better calls without long briefings.
  • It's core to your advantage. If your software is the product, you'll generally want its knowledge and decisions inside the company.
  • You need speed on small things. A person down the corridor can fix a problem today, with no ticket, quote or contract change.
  • Sensitive data or strict compliance makes outside access awkward.

Compare the real costs

Salary against invoice isn't a fair comparison. Here's what should be on each side:

In-house costsAgency costs
Salary, tax, benefits and equipmentFees and any contingency
Recruitment time and feesTime spent on briefings and reviews
Management and trainingKnowledge lost when the project ends
Software and tool licencesChange requests
Cover for holidays and leavingAny handover to the next team
Idle time when work is quietWaiting for a slot when you need help

Don't forget the cost of a skills gap. One generalist hire can't be an expert in security, design, performance and SEO. Also, include the risk of a key person leaving, which can be serious if only one person understands your systems.

On the other side, an agency's daily rate looks high until you remember that it only bills when it's working for you, and you aren't paying for management or empty weeks.

The hybrid options

The choice isn't really binary, and many of the best arrangements sit in the middle.

Agency to launch, in-house to run. The agency builds the first version with a planned handover, and you hire someone to take over. This works best when you plan the handover from the beginning, including documentation, access and overlap time.

In-house lead plus specialists. One senior person owns the direction and buys in specialists as needed. This often gives you the best of both, since you keep the context while getting access to expert skills.

Retainer. A set amount of agency time each month for improvements and support. It's suitable when you have a steady trickle of work, but not enough for a full-time role. See what a retainer should include.

Embedded contractors. Specialists work inside your team for a fixed period to fill a gap or to teach a skill.

Freelancers. For a small, well-defined piece of work, a freelancer may be better than either.

AI tools shift this slightly. A small internal team can now produce much more, which helps with routine work. However, it also makes experienced judgement more valuable, not less, so a senior person's oversight matters more than before.

Warning signs

You may have hired too early if your developer has little to do between projects, or if you're inventing work to fill their week.

You may have stayed with an agency too long if small changes need a quote, your costs keep climbing, nobody at your company understands how things work, or you can't get changes made quickly.

You may be set up for trouble if a single supplier or employee holds all your knowledge and credentials. Make sure that you own your code, domain and accounts, whichever route you take.

Keep ownership inside, wherever the work happens

Even if an agency does all the building, somebody in your company should own the outcome. They set priorities, review the work and are accountable for results. A team with no internal owner tends to build what's easy to measure, instead of what the business needs.

Whoever does the work, insist on code in your own repository, written documentation and accounts in your name. That keeps your options open. A good supplier won't object.

A simple way to decide

  1. Estimate your workload for the next 18 months, in hours per month.
  2. Mark what's core to your advantage and what's not.
  3. List the skills needed, and how many of those one person could really cover.
  4. Price both routes, using the full costs above.
  5. Choose a next step that you can change. A short contract or a part-time hire leaves more room to adapt than a big commitment.

If you're weighing this up, read how to choose a web design agency as well, or book a call. We'll tell you if we think you should hire instead.

Common questions

Is it cheaper to hire in-house or use an agency?

It depends on your workload. For steady, full-time work, hiring often wins over the long term. For occasional projects, an agency is usually cheaper, as you aren't paying for idle time, recruitment or management. Compare full costs across 18 months.

When should a startup hire its first developer?

When the product has steady, ongoing work and early signs of demand, and when a founder can manage and assess a technical hire. Before that, a freelancer or agency may help you learn faster with less long-term commitment.

Can an agency work alongside an in-house team?

Yes, and it's often very effective. Common setups include an internal lead with specialist agency support, or a retainer for overflow work. Agree on who owns decisions, how code is reviewed, and how knowledge will be shared between the teams.

How do I move work from an agency to in-house?

Plan early. Get the code into your own repository, secure all accounts, and request documentation. Hire before the agency leaves, and allow for an overlap period, so your new person can ask questions while working on real tasks.

Have something worth building right?