Choosing an automation company: what to ask before you sign
The short answer: first decide which kind of vendor fits the size of the work, and only then compare vendors. Test the vendor itself with a handful of questions: who owns the code and the accounts, what happens when something breaks, how success gets measured, how they reach your data, and who on your side owns the process. A vendor who answers those clearly and in writing is usually one you can work with.
We are an automation company, so read this knowing that. We tried to write it so it helps you choose even if the choice ends up being someone else, and in some of the cases below someone else really is the right answer.
Last updated: 5 November 2026
What kinds of automation vendors are there?
Roughly five, and each is good at different work. "Automation solutions" is a label used by a freelancer who builds workflows in the evenings and by a software house with hundreds of developers, so it helps to know who you are talking to before you compare quotes.
| Vendor type | Fits when... | Fits less when... | What to check |
|---|---|---|---|
| Independent automation developer (freelancer) | There is one defined process across 2 or 3 systems, and the budget is small | The system becomes critical to the business and nobody can cover for them | Who handles a failure while they are on holiday, and whether the documentation stays with you |
| Studio building in visual no-code tools | You are connecting common cloud systems, volume is moderate, and the team wants to change things itself | Volume is high, the logic is complicated, or the data has to stay on your own infrastructure | Whose name the tool account is in, and how the tool's pricing behaves as volume grows |
| Automation and AI company | There are several related processes, steps that read documents or messages, a connection to an ERP or CRM, and the work needs mapping before building | The task is small and defined, and a freelancer would close it in a week | Whether they can tell you what is not worth automating, and what happens after handover |
| Software house | You need a full application with its own data model, users and permissions, on a project of several months | The need is connecting systems that already exist | Whether they are proposing to rebuild something you already run |
| In-house hire | There are many processes, they change constantly, and there is a full-time job's worth of work for the long run | The need is narrow, or nobody can manage that person professionally | Who reviews their work, and what remains when they leave |
A good freelancer is the right answer for more businesses than larger vendors like to admit. They cost less, and on one defined process they are also fast. The risk is that all the knowledge sits with one person. If they take a full-time job or simply get busy, you need the code and the documentation to be with you already.
A studio building in visual tools starts quickly, and your team can open a workflow and see what it does. Watch the pricing of the tool itself: many of these tools charge per run or per task, which is negligible at low volume and can become the largest monthly line in the project as volume climbs.
An automation company fits when it is not yet clear what exactly to build, and you need someone to map the processes before anyone touches code. It also fits when part of the work is reading free text: invoices, emails, WhatsApp messages. Per hour it costs more than a freelancer, and on a small, defined task that difference is money you will not get back.
A software house builds products. When the need is moving data between a CRM, the accounting system and an inbox, building from scratch adds time and cost nobody needed. When the need is a new system the team works inside all day, it is exactly the right call.
Automation consultant or automation development company?
It depends on whether you already know what to build. Automation consultants map the processes, rank what is worth automating and hand over a plan. An automation development company builds what is in the plan. Some vendors do both, and then it is worth making sure the mapping is delivered to you as a document you could take to any other vendor.
If you have one clear process, with an owner and volume the team feels every week, you can skip the mapping and ask for a build quote. If what you mostly have is a feeling that "we should be doing something with AI", a short mapping will usually save you from the wrong project.
What should you ask an automation company before signing?
Six questions. Ask for the answers in writing, inside the proposal. A good vendor answers them without squirming, and a vendor who squirms has already answered.
1. Who owns the code, the accounts and the data?
The answer you want: the code passes to your ownership, and the system runs in accounts registered to your company. The server or cloud account, the automation tool, the keys for the language models. The passwords are yours, and the vendor is given access.
A weak answer is "it runs on our side, you have nothing to worry about". That works as long as the relationship is good. The day it ends, you find you are holding nothing. There is also a legitimate model where the vendor hosts the system and you pay a subscription, and it can fit, provided you know it up front and the contract says what you get when you leave.
2. What happens when it breaks?
Every automation breaks at some point. A system vendor changes its interface, or a file arrives in a format nobody planned for. Ask who gets alerted when a run fails, how quickly someone deals with it, and whether the fix is included or billed separately.
And the question worth the most: how will I know the system is running and producing nothing? A workflow that reports all clear for a week while it moves no records does more damage than one that stops on day 1 and shouts about it.
3. How will we know it worked?
A serious vendor wants a starting number before building: how many hours a week the process takes today, and how long it takes from request to response. Without a number like that the project ends in opinions, and whoever liked it declares it a success. If the vendor does not ask, bring the number yourself and put it in the proposal.
4. How do you reach our data and systems?
The answer you want: a dedicated user for each connection, with the minimum permissions it needs, and a log of every action the system takes. If the answer is an admin login belonging to someone on your team, treat that as a flag.
When a language model reads your customers' documents, ask which account that goes through, where the data is stored, and whether the model provider may use it for training. A vendor who has worked with sensitive data has an answer ready.
5. Who on our side needs to own the process?
A good vendor asks you this before you ask them. Automation without a business owner goes stale: the process changes, nobody updates the system, and within six months the team is working around it by hand. Ask how much time a week this will take from that person during the build and after, and pick the person before you sign.
6. Can we see something similar you built?
A working example from a nearby industry, or a client willing to take a ten-minute call, will tell you more than a slide deck. Ask that client what happened the first time something broke.
Red flags when choosing an automation vendor
- A fixed price before anyone understood the process. A quote written after a half-hour call prices a guess, and someone pays for the gap later.
- A promise of "full automation" with no point where a person approves. In processes that touch money, customers or records other systems read, a person should sign off, at least for the first months.
- "We connect to everything", without asking which system you run, which version, and whether it has an interface.
- The system runs in the vendor's account, and the contract is silent on what happens when you part ways.
- Documentation that will "come at the end", or does not appear in the proposal at all.
- A vendor who sells one tool and offers it for every problem, even where the right setting in a system you already own would have solved it.
- No questions about volume, or about what happens today when a case does not fit.
What does a first automation project look like?
Small. One process, with rules you could write on a page, volume the team feels every week and an owner who wants it. The first project tests the vendor and it tests you, so it is better if it goes live quickly and proves itself before you expand.
With us, one focused process usually takes 2 to 4 weeks of development after a mapping of 1 to 2 weeks, and it runs for a while alongside the old way before you switch over completely. Other vendors work at a different pace. A two-day timeline for a process that touches money should worry you, exactly as much as a six-month timeline for connecting two systems.
At the end of a first project you should be holding a process running on real data, an alert when it fails, documentation that explains what it does, a team that knows how to work with it, and an "after" number you can put next to the starting one. We set out the stages, what each needs from you and what you get at the end of it, in the guide to how an automation project runs.
How are automation services priced?
A serious price follows how many systems the process touches and how messy the data going into it is, and that only becomes clear after someone has seen the process. So there are no figures here. Across quotes from different vendors you can compare the pricing model, and almost every vendor works in one of these or a mix of them.
| Model | How it works | Fits when... | What to check |
|---|---|---|---|
| Per project | A fixed price for a defined scope, usually after mapping, sometimes broken into modules | The scope is clear | What counts as a scope change, and what is included in the period after go-live |
| Hourly | You pay for the hours actually worked | The scope is not clear yet, or there are many small jobs | An estimate up front, a cap, and a detailed hours report |
| Monthly retainer | A fixed monthly amount for maintenance, monitoring and improvements | Several systems are live and the list of improvements never ends | Exactly what is included, how fast a failure gets handled, and what happens to unused time |
| Subscription to the vendor's system | A monthly fee to use a system the vendor hosts and maintains | The need is standard and the vendor has already solved it for many businesses | What you get when you leave, and what happens to the price as volume grows |
Every one of these models comes with running costs that do not go to the vendor: a server or cloud account, language model usage by volume, and licences for the tools the automation depends on. It is better if they are paid straight from your own accounts. That way you see them, and you can keep paying for them if you change vendor.
Ask for those costs as a separate line in the proposal. A cheaper quote with a high running cost can turn out more expensive within the first year.
When do you not need an automation company at all?
Sometimes the answer is configuration. Plenty of requests "for automation" end with a few settings changed in the CRM you already have, or with an off-the-shelf product that does exactly this.
Sometimes the volume is too small. A task that takes someone 20 minutes a week does not justify a project, however annoying it is.
And sometimes the process has to be understood first. If it changes every month, or nobody can explain it from start to finish, automation will only set the mess in code. When there is enough work for a full-time role, hiring is a serious option, and we laid out the comparison, including the full employer cost, in the hire or automate guide.
Where Automation Flow fits
We are an Israeli automation and AI company founded by Heli Netanel and Shahar Saadon. We fit best with companies that have several related processes, systems such as an ERP and a CRM that need to talk to each other, and steps where someone has to read documents, emails or messages. By default, what we build runs in the client's accounts, and the code passes to the client's ownership.
When it is not yet clear what to build, we start with process mapping and AI consulting, which ends in a plan you can take to any vendor. When the process is already clear, we go straight to automating the process. And if what you need is one small connection between two systems, a good freelancer will probably do it for less, and we will tell you so.
Frequently asked questions
How do you choose an automation company?
Start from the size of the work. One defined process fits a freelancer or a studio, several processes involving documents and core systems fit an automation company, and a whole product fits a software house. Then test the vendor with questions on code ownership, failure handling, measuring success, data access and who owns the process on your side, and ask for the answers in writing.
How much do automation services cost?
The price follows the scope: how many systems the process touches, how much human review it needs and the state of the data. Vendors price per project, by the hour, on a monthly retainer or as a subscription, and on top of that come running costs for infrastructure and language models. A serious quote comes after someone has seen the process.
What is the difference between a freelance automation developer and an automation company?
A freelancer costs less and suits one defined process. A company brings more than one person, mapping before the build and someone who answers when something breaks during a holiday. The difference is worth paying for once the system becomes part of the business's daily work.
What should a contract with an automation vendor say?
Who owns the code and the accounts, what maintenance includes and how fast a failure gets handled, what counts as a scope change, how the vendor reaches your data, and what you get on the day you part ways: code, documentation, passwords and an orderly handover to whoever takes over.
How long does a first automation project take?
It depends on the scope. With us, one focused process usually takes 2 to 4 weeks of development after a mapping of 1 to 2 weeks. A first project planned for six months is probably too big to be a first project.
Next step
If you are in the middle of comparing vendors, take each of them through the six questions above. And if you want us to hear about the process and say which kind of vendor fits it, even when the answer is not us, talk to us.



