Automation agency vs hiring in-house: the maths, honestly

The real numbers

The costs that get omitted are the interesting ones. Recruitment takes real management time before anyone is hired. A new hire is not productive for months. And a single in-house specialist is a concentration risk: when they leave, undocumented systems become nobody's problem until they break.

Hire in-house when

• Automation is continuous rather than a project, with a genuine backlog stretching beyond a year.
• Your processes involve sensitive data or regulatory constraints that make external access genuinely difficult.
• You already have someone internally who wants the role. Promoting an operations person who knows the business often beats hiring a technologist who does not.
• You are large enough that the person will be busy. A full-time automation hire with two weeks of work a month will leave.

Use an agency when

• You need it working in weeks. Recruitment alone takes longer than most agency builds.
• You do not yet know what should be built, so hiring a specialist means guessing at the specialism.
• The work is bursty: a few systems this quarter, nothing next.
• You want to prove the value before committing to a headcount, which is a completely reasonable position.

Hiring before you know what needs building is how businesses end up with an expensive person maintaining a tool they were talked into.

The sequence that actually works best

Agency first to diagnose and build the first two or three systems, with documentation and handover written into the scope from the start. Then hire someone to own and extend them once there is a proven backlog and a clear picture of the skills required.

That order means you hire against a real job rather than a guess, and the new person inherits working systems and documentation instead of a blank page. It is what we did at a four-brand business, replacing an external agency with an in-house capability, and it worked because the handover was designed in rather than negotiated at the end.

The test for whether an agency will support that sequence is simple: ask who owns the code. If the answer is anything other than you, the handover was never going to happen. More questions worth asking are in what is a business automation agency.

A note on the hybrid

The most common arrangement we see working is one internal owner, not necessarily technical, plus external build capacity. The internal person holds the context and the priorities. The external team builds. That keeps the knowledge inside the business without needing a full-time engineer, and it is roughly how we structure engagements.