How to Choose an AI Automation Agency: 6 Questions to Ask
Choose an AI automation agency on what you can verify before you sign: who is behind it, a data processing agreement that meets Article 28 of the GDPR, what happens to your workflows and data when you leave, who carries which EU AI Act obligation, and a price with a defined scope. A demo shows what an agency can build; the contract shows what you will get.
You have had three calls and received three proposals. Every agency gave an impressive demo, the prices are far apart, and all three promise to give you hours back. How do you decide?
We are an AI automation agency ourselves, so read this with that in mind. The questions work with any agency, including us.
What should you look for in an AI automation agency?
When choosing an AI automation agency, check six things you can verify before signing, regardless of how good the demo was:
- Who is behind it? A registered company and a contact person who may sign.
- How does it handle your clients' data? A data processing agreement that meets the GDPR.
- What happens when you leave? You know where your workflows run and how to take them with you.
- Who carries which EU AI Act obligation? This matters most when a chatbot talks to your clients.
- What does the price include? A defined scope, support after launch, and a fixed rate for extra work.
- Who builds it and when does it go live? A named builder and a schedule.
How do you check whether an AI agency is legitimate?
You can check in a few minutes whether an agency exists and who may sign for it, in the public company register. In the Netherlands that is the KVK Business Register, which lets you "check who you are doing business with", including "who is authorised to sign on behalf of an organisation" and "whether a business has gone bankrupt."
Then ask for a reference in your sector that you can phone yourself, and for a working example of a similar automation.
What should a data processing agreement cover?
As soon as an agency processes your clients' personal data on your behalf, it is a processor, and the GDPR requires a written agreement. Article 28 of the GDPR states that processing by a processor "shall be governed by a contract or other legal act", which the European Commission describes as "binding on the processor". As controller, you remain responsible for your own GDPR obligations; the agency also has direct obligations of its own as a processor.
Check three points from that article:
- Sub-processors. Under paragraph 2, the processor "shall not engage another processor without prior specific or general written authorisation of the controller". Ask which tools and hosting providers the agency uses, and in which country their servers are located.
- Your instructions only. The agreement must state that the agency "processes the personal data only on documented instructions from the controller" (paragraph 3, point a).
- The end. Afterwards the agency, "at the choice of the controller, deletes or returns all the personal data" (paragraph 3, point g). Agree in advance which of the two you want.
This is how we handle it: every client signs the data processing agreement before we build anything. Our automations run in n8n on a Hostinger server in Frankfurt. Our privacy statement lists the processors we share personal data with and their locations, including GoHighLevel, a US service. More practical measures are in automation without compromising privacy.
Who owns the workflows if you leave the agency?
Whether you can take your workflows with you depends on the contract, because Article 28 of the GDPR only covers what happens to personal data. Settle three things before you sign:
- Whose account it runs in. Are the automations, the CRM and the integrations in accounts in your name or in the agency's? If they are in the agency's, agree a written handover.
- An export you can open yourself. Ask whether the tool can export workflows. n8n saves workflows in JSON format and can export and import them as files. According to the same documentation, those files include credential names and IDs, so also agree how passwords and keys are handed over.
- Documentation and notice period. Ask for a short description per workflow: what triggers it and which systems it touches. Also agree the notice period and any minimum term.
To pick a workflow tool, see our comparison of n8n, Make and Zapier.
How AI-ready is your business?
Take the free AI Readiness Quiz: 7 questions, 2 minutes.
Take the quiz →What does the EU AI Act require from an AI agency?
An AI agency should be able to tell you which EU AI Act obligations apply to what it delivers and who carries them: you, the agency, or both. For a service business, two rules are the most direct:
- AI literacy (Article 4). Since 2 February 2025, providers and deployers of AI systems have had to take measures on the AI literacy of their staff (AI Act, Articles 4 and 113). The Digital Omnibus on AI, in force since 27 July 2026, softened that duty: you take measures "to support the development of AI literacy", and the obligation "does not require providers or deployers to guarantee any specific level of AI literacy of any individual." Ask for staff instructions at handover.
- Transparency for chatbots (Article 50(1)). An AI system that interacts directly with people must be designed so that they "are informed that they are interacting with an AI system", unless that is already obvious. This duty sits with the provider and applies from 2 August 2026 under Article 113. If an agency builds a chatbot or phone assistant that talks to your clients, put in writing who the provider is and how the client can tell they are talking to AI.
For the rest of the AI Act, see EU AI Act 2026: a practical guide for small businesses.
How much does an AI automation agency cost, and how do you compare proposals?
You can only compare AI agency proposals fairly once you know what the price includes and what extra work costs. Agencies charge by the hour, per project, or a one-off fee for the build plus a fixed monthly fee for management. For every proposal, ask:
- which work is included, and up to how many hours or workflows
- what extra work costs per hour and whether it is agreed in advance
- who monitors for failures, what response time applies, which repair work the monthly fee covers, and whom you can reach outside office hours
- which third-party costs are billed separately, such as licences, hosting and messaging fees
Our own packages on the services page are Foundation (EUR 4,500 setup plus EUR 650 per month), System (EUR 7,500 plus EUR 950 per month) and Bespoke (from EUR 12,000 plus from EUR 1,500 per month). Every proposal carries the same scope clause: work that exceeds the included scope is discussed in advance and invoiced at the current hourly rate of EUR 175 excluding VAT. A broader cost overview is in how much does AI automation cost?
Who builds it, and when does it go live?
Ask who builds the automation and when it goes live, and have both written into the proposal. You want to meet the person who builds your workflows, and to know who takes over during illness or holidays. Also ask for a step-by-step schedule.
One of our own projects, for comparison. Before we started working with an accounting firm, its intakes arrived through scattered emails, documents came in late or incomplete, and chasing them was manual work. The project took 6 to 10 weeks to go live, and the working day now ends at 18:30 instead of 23:00 (own measurement, one client, 2026). The full case is on our cases page. At Mindsora, the founder builds the systems in person.
When don't you need an agency?
You do not need an agency for a single simple connection between two tools that you can set up yourself, such as a form that adds a row to a spreadsheet. Examples are in 5 business tasks you can automate today. An agency earns its fee when a process runs through several systems, touches your clients' personal data, or has to keep running while nobody is watching.
Which questions should you ask in the first meeting?
Take these six questions to every first meeting and ask for written answers:
| Question | A good answer includes |
|---|---|
| Under which company registration number do you sign, and who is authorised to sign? | A number you can find in the business register, with an authorised name |
| Can I see your data processing agreement, and which sub-processors do you use? | An agreement that covers the points of GDPR Article 28, plus a list of parties and countries |
| Whose account do the workflows run in, and how do I take them with me if I leave? | Your account or a written handover, with an export and documentation |
| Who is the provider of the AI that talks to my clients? | A name, and how the client can tell they are dealing with AI |
| What does the price include, who handles failures, and what does extra work cost? | A defined scope, a response time and a fixed hourly rate for extra work |
| Who builds it, and when does it go live? | A name, a stand-in and a step-by-step schedule |
To find out which of your processes would gain most from automation before those meetings, take the free AI Readiness Scan.
Ready to automate?
Book a free consultation and discover what AI automation can do for your business. Or take the 2-minute AI Readiness Quiz first.
Book a call