The decision is usually framed as a cost comparison, which is the wrong frame. It is a utilisation question: an engineer is only cheaper than an agency if you can keep them busy.
Here is the arithmetic, honestly, including the point where hiring genuinely wins. If you want the agency side of it, our automation engineer page sets out how the engagement works.
What each actually costs
In-house: a US automation or integration engineer runs $95,000–$160,000 a year in salary. Loaded — payroll taxes, benefits, equipment, software — assume roughly 1.25–1.4× that. Call it $120,000–$220,000 all in. Add three to five months to hire, and the real risk that the first hire is not right.
Agency, fixed scope: a defined project quoted as a number. Ours start at $499 for one process and $1,499 for a department. No recruitment lag, no ongoing commitment.
Agency, embedded: an engineer working through your backlog on monthly terms. Cheaper than a US salary, no notice period, and you can stop when the backlog is done.
The test: how much work is actually queued?
Write down every manual process you would automate if resource were free. Now estimate each one honestly — most single processes are one to three weeks of engineering.
- Under about 6 months of queued work: buy the builds. You will pay a full salary for someone who runs out of work in the second quarter, and automation engineers who run out of work leave.
- 6 to 12 months of queued work: genuinely borderline. An embedded engineer on monthly terms usually fits best — you get continuity without a permanent commitment.
- More than 12 months, and growing: hire. At that volume in-house is cheaper per unit of work, and the institutional knowledge compounds in a way agency work does not.
What in-house genuinely does better
- Context. Someone who has sat in your operations meetings for a year spots automation opportunities you would never think to brief.
- Response time. When something breaks at 9am, they are already there.
- Iteration. Small tweaks happen the same day rather than through a change request.
- Institutional memory. They know why the weird exception exists, and they know not to automate it away.
What an agency genuinely does better
- Breadth. A team that has integrated forty different systems has seen your awkward legacy software before.
- Starting now. Weeks, not a hiring cycle.
- Not carrying the cost between projects. Automation demand is lumpy for most businesses.
- Bus factor. One in-house engineer is a single point of failure, and this role tends to accumulate undocumented knowledge fast.
The hidden cost nobody budgets for
Whoever builds it, someone has to maintain it. Third-party APIs change, dependencies age, business rules shift. An automation nobody owns quietly stops working, usually without anyone noticing for weeks.
If you hire, that is part of the job and you should say so in the job description. If you use an agency, ask explicitly what happens after handover and what a fix costs. We include 30–90 days of tuning depending on tier and quote fixes individually after that — deliberately, so there is no retainer you are obliged to be on.
The hybrid most mid-size companies land on
One internal person who owns the automation estate — knows what exists, watches the alerts, makes small changes — plus an agency for the builds that need specialist work. That person does not have to be a full-time engineer; often it is an operations lead who is technical enough.
This is usually the cheapest arrangement that does not leave you fragile.
Frequently asked questions
What should an automation engineer actually know?
API integration, at least one scripting language, error handling and monitoring patterns, and enough SQL to work with your data. For AI-adjacent work, add retrieval, prompt design and — most importantly — how to build an evaluation set. Anyone who cannot describe how they would measure accuracy has not shipped this in production.
Can we start with an agency and hire later?
Yes, and it is a sensible sequence — provided you own everything from day one. Insist that every workflow, key and account is in your name, and that documentation is a deliverable. Then a future hire inherits a working estate rather than a black box.
How do we keep an agency from locking us in?
Get ownership in the contract, name the specific assets, and require plain-English documentation. If an automation only the vendor understands, you have bought a dependency. Our builds hand over the workflows, servers, keys and accounts as standard.
Is an offshore agency a false economy?
It depends on what makes it cheap. Cheap because of a lower cost base can be excellent work. Cheap because corners were cut on error handling and documentation is expensive later. The test is not the rate — it is whether they can answer the "what happens when it goes wrong" question in detail.
Not sure which side of the line you are on? Send us your list of manual processes and we will tell you honestly whether it justifies a hire. See how the engagement works or message us on WhatsApp.
