In-house vs agency vs freelancer
Go in-house if you have continuous automation work and someone who wants to own it — a full-time automation capability costs $80,000 to $130,000 a year loaded and only makes sense with a real pipeline to fill it.
Use a freelancer for well-defined, self-contained builds where you already know what you want. Cheapest per hour, and the risk is continuity: when they move on, undocumented work becomes your problem.
Use a firm when you need the discovery as much as the build, when the work spans several systems, or when something must still be supported in two years. More expensive per hour, and you are buying process and continuity rather than hours.
The comparison
| In-house | Freelancer | Firm | |
|---|---|---|---|
| Cost | $80k–$130k/yr loaded | $40–$120/hr | Fixed project, $8k–$35k |
| Best for | Continuous pipeline | Defined, self-contained builds | Discovery plus build plus support |
| Knows your business | Deeply, over time | Only what you tell them | Learns it during the audit |
| Speed to start | 2–4 months to hire | Days | 1–2 weeks |
| Discovery included | Yes, implicitly | Rarely — you supply the spec | Yes, and usually charged for |
| Support in 2 years | If they are still there | If they are still available | Contractual |
| Main failure mode | Not enough work; they leave bored | Undocumented work, no continuity | Overselling scope you did not need |
In-house: the honest test
The question is not whether an internal person would be useful. It is whether you have twelve months of genuine automation work lined up.
Most businesses under 200 people do not. They have three or four meaningful automations, then a long tail of small changes. That is perhaps four months of work in the first year and considerably less afterwards — which means either an expensive person underused, or someone hired for automation who is quietly reassigned to general IT and leaves within eighteen months.
Where in-house genuinely works: businesses with continuously changing processes, regulated environments where external access is difficult, or where automation is close enough to the product that the knowledge should stay inside. Full arithmetic on hire or automate.
Freelancer: cheapest, with a specific risk
A good automation freelancer is excellent value and we recommend the route regularly. The hourly rate is genuinely lower, there is no agency overhead, and for a defined build you can brief precisely, the outcome is often identical to ours at lower cost.
Two risks to manage rather than avoid.
Continuity. When they take a full-time role or get busy, you have automations nobody understands. This is entirely manageable: make documentation a contractual deliverable, insist credentials live in your vault, and get a recorded walkthrough. If a freelancer resists any of that, walk away.
Discovery. Most freelancers price against a spec you provide. If your spec is the happy path — and first specs almost always are — the build handles the happy path, and the exceptions come back as change requests. See the exception problem.
Pay someone for a proper audit, then hand the resulting specification to a freelancer to build. You get rigorous discovery and a lower build rate. Our audit reports are deliberately written to be actionable by anyone, including your own team or a contractor, and we do not obfuscate them to force the follow-on build.
Firm: what you are actually paying more for
Not better engineers. A good freelancer is frequently as capable as anyone we would put on the work.
You are paying for four things: discovery done systematically rather than from your spec; process — error handling, parallel running, documentation as standard rather than as optional extras; continuity, meaning someone still exists in two years and is contractually obliged to answer; and estimating risk transfer, because fixed price means overruns are the firm's problem.
Whether that is worth the premium depends entirely on the project. For a well-defined single-system build, probably not. For a five-system integration where nobody has documented the process, almost certainly.
When not to hire us
Stated plainly, because it should be.
- Your automation is a two-step Zap. Build it yourself this afternoon.
- You have a precise spec and a tight budget. A freelancer will do it well for less.
- You need continuous availability rather than delivered outcomes. That is a hire, not a firm.
- Your need is under $5,000. We would either do it badly or lose money, and neither serves you.
- An off-the-shelf product does it. See build vs buy.
How to evaluate whoever you pick
Four questions that separate firms and freelancers who have done this from those who have not.
- "How did you arrive at this estimate, and who did you watch?" A quote from a one-hour call with a manager has priced a process that does not exist.
- "What happens when this automation fails?" If the answer is not immediately about retries, alerting and dead-letter handling, error handling is not in the build.
- "What documentation do we get?" It should be a named deliverable, not a promise.
- "Whose accounts will this run in?" Yours. Any other answer creates a dependency you do not want.
Not sure we are the right route?
Ask on the call. We will tell you if a freelancer or an in-house hire fits your situation better.