Agency, freelancer or software house? Who should automate your process
Search for “process automation” and you get everything at once: freelancer profiles, agencies, software houses with portfolios of mobile apps. Each of them will do “automation”, but the result you have a month later will be completely different.
The short answer
A freelancer works well for one simple connection between two tools, if you can describe what you want yourself. An automation agency is the best choice when you want a whole process to run on its own: from analysis, through the build in your tools and testing, to documentation and support after launch. A software house is the choice when you need a completely new application.
For most service businesses that want to give their team time back, an agency is the right choice.
Freelancer
One person, usually found through a recommendation or on a platform such as Upwork. They charge by the hour or by the job. For a well-described, small task it is a quick route.
Good uses include sending form submissions to a spreadsheet, a Slack notification after a new order, or copying contacts between two systems. One scenario, few exceptions.
The limitations come from it being one person. If they fall ill or take on a bigger job, nobody steps in. Process analysis, documentation and testing across different cases usually have to be ordered separately or done yourself. It also happens that scenarios are built on the supplier’s private account. The company then pays for an automation it does not formally own.
Automation agency
An agency builds automations on platforms such as Make, n8n or Zapier and connects them with the tools you already have: your CRM, inbox, calendar, spreadsheet. It starts by understanding the process and ends with a solution that runs without supervision.
It is the right choice when you automate a whole process. An example is the path from enquiry to booked call: a reply to the client within a minute, assigning a salesperson, a reminder after three days and recognising that the client has already replied. There are usually a dozen or so such conditions and exceptions. Someone has to think them through before the first scenario is built, and that is where an agency has the advantage.
How it works at AIROX
- Joint process analysis. At the free consultation we go through how the process runs today together, including the exceptions nobody ever wrote down.
- An individual approach. The same person leads the project from the first conversation to the end. We build for your company, not from a template.
- Your tools and your accounts. You do not have to replace anything, and everything we build belongs to you.
- A fixed price before we start. One amount for an agreed scope, with no extra charges along the way. The packages are on our pricing page.
- Thorough testing. We check every scenario against all the cases in the process map before it reaches your team.
- Documentation and a process map. You know what runs automatically and what is still done by a person, and you have it in writing.
- Support after launch. For 14 days after go-live, or 30 for a system, we fine-tune everything that comes up in day-to-day work. After that you can choose ongoing care.
We also match the technology to the step: a plain rule where it is enough, and an AI model where it genuinely shortens the work. More on this in A rule or an AI agent.
An agency is not the cheapest option on the market. An implementation that gives your team several hours a week back usually pays for itself within a few months, though, and keeps working after that. You can run the numbers for your process in our payback calculator.
Software house
A software house writes software from scratch: a web or mobile application, a custom system for the company. It works as a team (developers, a tester, a project manager) and usually plans a project in weeks or months.
You choose one when you are building your own product for clients or need an application that simply does not exist on the market. After launch, every change to the code is made by a developer, so maintenance is an ongoing cost. Hiring a software house to connect a form to a CRM is like hiring an architect to move a wardrobe.
How to choose in practice
Start with two questions. First: do you need something that does not exist on the market, or a connection between things you already have? Second: is it one step, or a whole process with exceptions?
| Situation | Who |
|---|---|
| A form should send submissions to a spreadsheet | freelancer |
| Enquiry handling from form to booked call | agency |
| Follow-up after a sent quote | agency |
| Client onboarding across several tools | agency |
| A chatbot answering from the company’s knowledge base | agency |
| A weekly report from several sources | agency |
| Your own application that you sell to other companies | software house |
More important than the label is whether the supplier asks about your process first. That is how we start every project: with a conversation about how you work, and the price comes after it.
Questions before signing
Ask them of every supplier you talk to. The answers quickly show who knows their stuff.
- Whose account will the automation be built on? The right answer is: yours.
- What exactly is included in the price? Analysis, number of processes and integrations, testing, documentation, a guide for the team.
- What happens after launch? How many days of fixes are included and what care looks like afterwards.
- Will I get a process map and a description of what was built?
- Who exactly will work on it? Is it the same person you talk to at the start?
- What does sign-off look like? Do you approve the implementation only once everything works as agreed?
At AIROX you will find the answer to each of these questions in the proposal, before you sign anything.
Warning signs
- A price given before the first conversation about the process, or only as “from”.
- No questions about exceptions: what should happen when the client replies, when data is incomplete, when someone is on holiday.
- An AI model proposed for every step of the process, with no explanation why.
- Work on the supplier’s account with no plan to move it to yours.
- Not a single documented implementation you can look at. You will find ours in our case studies.
If you want to see what this looks like in your company, book a free consultation. In 30 minutes we will go through one process together and you will find out how much time your team can get back.
Frequently asked questions
A freelancer’s rate can be lower, but compare the full cost of the implementation. With an agency, the price usually includes process analysis, testing before launch, documentation and fixes after go-live. With a freelancer these often have to be bought separately or done yourself. What also counts is how many months the implementation takes to pay for itself, and that depends on how well the process was thought through.
An automation agency connects the tools you already use into one working process on platforms such as Make or n8n. A software house writes software from scratch. For typical processes in a service business, such as enquiry handling, follow-up, onboarding or reports, an agency delivers results faster and at a lower cost.
Yours. Scenarios, spreadsheets and tool accounts should belong to the company, and the supplier gets access for the duration of the work. That is how we work at AIROX: everything we build remains your property.
Process analysis at the consultation, a process map, the build in your tools, testing before launch, documentation, a guide for your team and a fixes period after go-live: 14 days, or 30 for a system. The price is fixed and agreed before we start. Package details are on our pricing page.
Yes. If the automation runs on your account and is described, an agency can take it over and extend it without starting from scratch. At the consultation we can also review what already works and point out what is worth building on.
At AIROX, automating a single step takes 5 working days and a full process 10 working days from receiving access. For a system connecting several processes, we agree the timeline in the quote.
He spent five years building operations at WebWave: from creating a support department from scratch to the role of Head of Operations and leading the integration after the company was acquired. While putting those processes in order he noticed how much time is taken up by work that develops nobody — and that the tools capable of taking it over already exist. A graduate in corporate finance from the SGH Warsaw School of Economics.
LinkedIn profile →