Comparison
Automation agency, in-house hire or VA: choosing who builds and runs your automations
Each route is right in some cases. This page sets out when an agency project fits, when a hire fits, when a VA with automation skills fits, and how the routes combine.
Decision table
| Compared on | Automation agency | In-house hire | VA with automation skills |
|---|---|---|---|
| Who scopes the work | The agency, with you, in a written scope | The hire, with direction from a manager | You, usually, with the VA's input |
| Who builds | The agency team | The hire | The VA, within the tools they know |
| Who maintains | You, or the agency under a quoted support arrangement | The hire, continuously | The VA, alongside other work |
| Continuity | Set by the handover notes and the support terms | Depends on the person staying | Depends on the person staying |
| Cost structure | A project fee, tool subscriptions billed separately, optional support | Salary and benefits, plus tools and management time | Hourly or monthly rate, plus tools and management time |
No amounts are shown. Rates differ by role and arrangement, and the figures that matter are your own.
When an agency fits
Defined project
A finite piece of work
One assistant, one set of workflows, one integration. A scope can describe it, and it ends with a handover.
Several tools
Many systems to connect
Messaging channels, a CRM, a sheet and an accounting tool in one flow benefit from a team that has connected them before.
No manager
Nobody to direct a builder
If no one in the business can brief and review technical work, a scoped project asks less of you than a hire does.
When an in-house hire fits
Continuous backlog
Automation is a daily job
If there is always another process to automate or adjust, a full-time person is closer to the work than a project team.
Proprietary systems
Systems only insiders know
Internal software and unusual data models are easier for someone embedded, who builds knowledge you keep.
Technical manager
Someone who can direct the work
A hire needs a manager who can set priorities and review output. If you have one, a hire can thrive.
When a VA with automation skills fits
Light automation
Tool-level automations
Connecting forms to sheets, setting up simple scenarios in a no-code tool or tidying a CRM pipeline.
Mixed with admin
Automation as part of a wider role
When the person also handles inbox, scheduling and bookkeeping, a little automation in the same hands makes sense.
Compare the routes with your own figures
The routes are paid for differently, so compare formulas, not headline prices. We quote no amounts as typical and cite no wage figures.
- Agency: project fee plus vendor subscriptions plus any support you choose, as listed in a quote.
- In-house hire: salary and benefits multiplied by the time the person spends on automation, plus tools and the manager's time.
- VA: rate multiplied by hours, plus tools and the time you spend directing.
- Inputs you supply: the workload, the salary or rate, tool costs and management time.
The ROI calculator takes your inputs and shows its formula.
Agency builds, staff operates
- Scope written together (Both), Agency
- Agency builds and tests (Agency), Agency
- Staff review real replies (You check), Your staff
- Handover and notes (Documentation), Agency
- Staff operate the workflow (Daily use), Your staff
- Changes requested as needed (Support or in-house), Your staff
Handover and documentation are what make this work: a person who did not build the automation can read the notes, see where it runs and change it. The steps are on the how we work page.
Ask these whichever route you choose
Ownership
Whose accounts is it built in?
Workflows and assistants should sit in accounts that belong to you wherever the tool allows.
Documentation
What written notes will exist?
Where it runs, what it connects to, who has access and how to change it.
Continuity
What happens if the person leaves?
For a hire or a VA this is the main risk. For an agency, it is covered by notes and support terms.
Data access
Who can see customer data?
Ask for the access list and how access is removed at the end.
What this page does not advise on
Not covered here
- Employment terms, pay or hiring decisions
- Whether to reduce or replace staff
Covered here
- Which route suits which kind of automation work
- How the cost structures differ
- How to combine routes
Questions we get asked
Is it better to hire an automation specialist or engage an agency?
It depends on the workload. A defined project suits an agency. A continuous backlog suits a hire. Many businesses use an agency for the first build and a staff member to operate it.
What does an in-house hire need from the business to succeed?
A manager who can set priorities, access to the systems involved and documented processes to automate. Without these, a hire spends time waiting.
Can our VA maintain what an agency builds?
Often yes, if the handover includes written notes, an access list and a walkthrough. Changes to the logic of a workflow may still need technical help, and support can be quoted for that.
What should be documented at handover?
What was built, where it runs, which accounts it uses, who has access, how to change the common settings and what to do when something fails.
Next step
Talk through your case.
Describe the work and who you have today. We will say which route looks right and whether an agency is the one.