An AI automation agency should map one business process, build and test the agreed workflow, and hand over a system your team can control; at WebDrift, Automation Start costs €790, an AI Agent with agent dashboard costs €1,490 and an Automation System starts at €2,900. Choose based on the results of a focused pilot, clear running costs and usable documentation, rather than a demonstration alone.
This guide focuses on choosing and commissioning an agency. Our automation cost guide covers the underlying cost components in more detail.
What should an AI automation agency actually deliver?
An AI automation agency should deliver a working process with agreed boundaries and operating instructions. The visible assistant or dashboard is only one part of that result.
Automation moves a task between steps according to rules. AI can add a judgement step, such as classifying an enquiry or drafting a response from approved material. It does not remove the need to define what should happen when information is incomplete, contradictory or outside the permitted scope.
Consider a trades business receiving enquiries by email. A useful workflow could identify the requested service, extract contact information and create a draft record in a customer relationship management system, or CRM. A team member checks the record and decides whether to send a quotation. Every step needs a defined destination and an owner.
Ask the agency for a process map in ordinary language. It should identify inputs, connected systems, permissions, outputs and human decisions. You should be able to follow it without knowing how the automation platform is configured. If you cannot tell what the system will do, you cannot properly approve it.
The proposal also needs an operating handover. That includes how to pause the workflow, find failed tasks, change approved reference material and contact support. A polished demo without these details may show a useful concept, but it does not describe a service ready for everyday use.
Which first process is suitable for a small business?
A good first process is repeated, sufficiently stable and easy to check. Start where your team can recognise a correct result and recover from a mistake.
Drafting internal summaries, sorting enquiries or transferring approved information can be sensible pilot tasks. They have a visible input and an output someone can compare. Automatically sending binding quotes or making sensitive eligibility decisions introduces more consequences and requires a much more careful assessment.
Choose a process owner before selecting software. This person explains the current steps, approves examples and decides whether the pilot is useful. Without an owner, the agency may build around assumptions that nobody has time to validate.
Document the current work with a small set of representative cases. Include straightforward cases, missing details, duplicate messages and unusual requests. Use these cases to test the workflow. Use synthetic or appropriately anonymised material until the data handling is established.
First check whether your existing tools already solve the problem. A simple routing rule or a better form may remove the manual work without an AI model. We would rather recommend that smaller solution when it fits than add a model whose output you have to supervise unnecessarily.
What are the published prices and ongoing charges?
Our implementation prices are €790 for Automation Start, €1,490 for an AI Agent with agent dashboard and from €2,900 for an Automation System. One provider example does not establish a market price. Compare equivalent scope and current contractual terms before purchasing. Care starts at €99 per month; third-party subscriptions are charged by their providers.
| WebDrift package | Published price | Scope to check against your need |
|---|---|---|
| Automation Start | €790 one-off | One workflow, up to three connected tools, an AI step |
| AI Agent | €1,490 one-off | Agent for internal processes with a knowledge base and agent dashboard |
| Website assistant (chat / voice) | €990 setup plus €149 to €499/month | Subscription only, 3 months minimum term, AI and hosting costs included up to fair use |
| Automation System | From €2,900 one-off | Multiple connected workflows and agents across departments, dashboard, automated reports |
| Care | From €99/month | Monitoring, updates and agreed adjustments |
| Provider charges | Confirm separately | Model use, platform and channel subscriptions |
These are our published AI automation packages, checked on 6 October 2026. Your written proposal should identify the integrations your process needs and explain any additional work. Compare that scope with other offers.
Telephone reception is separate from the AI Agent package. Its published scope describes agents for internal processes; a website assistant with chat or voice is a separate subscription. A voice project needs a separate assessment covering telephony, usage, booking access and handover to a person; do not infer its price from the word agent.
For a simple planning calculation, Automation Start plus 12 months of care at the starting rate is €790 plus 12 times €99, giving €1,978 before provider charges and extra work. That example assumes care starts immediately and the starting rate fits the agreed service. Replace both assumptions with your quote before budgeting.
Ask each supplier to identify recurring charges by provider and unit of use. A fixed implementation price says little about usage growth. You need to know what happens when more messages arrive, when documents become larger or when the team adds another channel.
How do you compare agencies without relying on sales demos?
Compare agencies against the same process brief and the same test cases. Ask them to explain both the straightforward outcome and their response to exceptions.
A demo usually shows a path that has been prepared. Your evaluation should also show a missing customer detail, a disconnected calendar or an enquiry that contains an instruction the assistant should ignore. The agency does not have to have solved your whole project before selection, but it should describe a credible way to test these cases.
Ask who will build the workflow and who maintains it after launch. Request a sample handover document with identifying information removed. A useful sample explains account ownership, configuration, errors and recovery; it does not need to disclose another client's business details.
Ask about the chosen tools in terms of your needs. Why this platform, which operations does the CRM permit and how can you export the configuration? Recognisable software names are not proof that the integration fits your process.
If a provider promises an immediate return, request the calculation and its assumptions. A realistic comparison includes staff time spent reviewing outputs, fixing exceptions and maintaining the knowledge base. Treat a proposed saving as something the pilot must test, not as an established result.
What safeguards and data questions belong in the brief?
The brief should define access, approvals, retained information and failure handling before production use. Your agency's location or a hosting label does not answer all those questions.
For GDPR purposes, identify who determines the processing and who carries it out on their behalf. The European Commission's guidance on controllers and processors explains the roles and contractual duties. Record the providers involved, the permitted data and how access will end when the contract ends.
Operational safeguards are separate decisions. Give the workflow only the access it needs. A tool that drafts a reply may need to read selected information without permission to change every customer record or send messages automatically.
Keep consequential actions behind explicit approval during the pilot. Our explanation of human oversight in automation describes this approach. Define the action being approved, the person responsible and what happens when nobody responds.
Also define recovery. Failed tasks need a visible queue or alert, rather than silently disappearing. A retry must avoid creating a second record or sending the same response twice. Your agency should test recovery with the systems your business actually uses.
What should the pilot prove before you approve launch?
The pilot should show that the workflow handles your agreed cases and that your team can operate it. A successful answer on one prepared example is insufficient evidence.
Set acceptance criteria before the build. For an enquiry workflow, these might include correct routing, required fields, readable drafts, controlled approvals and visible failures. Avoid an arbitrary accuracy percentage unless you have defined the test material and what counts as a correct result.
Use this commissioning checklist:
- One process and a process owner are identified.
- Inputs, outputs and connected tools are documented.
- Representative and exceptional cases are tested.
- Human approval points and escalation paths work.
- Provider charges and care responsibilities are clear.
- Your business controls operational accounts.
- Staff can pause the workflow and recover a failed task.
- Documentation and a handover session are included.
During the trial, record review time and corrections alongside completed tasks. Compare that workload with the old process using the same kinds of cases. The result may justify expansion, a smaller scope or stopping the pilot; all three can be sensible decisions.
What belongs in a concrete brief and acceptance pack?
| Supplier question | Evidence | Red flag |
|---|---|---|
| Which CRM actions? | Test using required permission | Only a logo shown |
| How can we stop it? | Usable pause and recovery | Only supplier can intervene |
| What does operation cost? | Units, limits, alerts | Only low token price |
| Who controls accounts? | Own accounts and export | No configuration access |
| How are faults handled? | Queue, deputy, retry check | Success only in demo |
Ten cases: valid, missing location, duplicate, same person with a different request, CRM outage, calendar outage, expired token, malicious instruction, wrong price and cost alert. Critical access or commitment failures block acceptance despite a high average score. Handover: process owner approves business rules; supplier documents configuration and restore; customer controls accounts and billing; deputy handles the queue; exit checks export, revoked access and recovery. The €1,978 example covers only €790 setup and optional twelve times €99 care, excluding provider fees. Compare further offers covering the same scope.
Documentation and sources: European Commission: applying GDPR.
Conclusion: buy a controlled process with a clear handover
Choosing an AI automation agency means checking how it handles your actual work, including exceptions and ongoing operation. Published prices help you plan, while your process brief determines whether a package fits. Start with a bounded pilot and make the evidence, costs and handover explicit. You can book a conversation with us to assess one process before deciding whether automation is useful.
Sources and verification
Package scope and prices: WebDrift AI automation service data, checked on 6 October 2026. Market comparison: cStack Solutions, automation packages (German), accessed 6 October 2026. Legal roles and contracts: the European Commission's guidance linked in the safeguards section. The scenarios and budget calculation are illustrative planning examples, not reported client results.
Looking for an agency to automate a specific workflow? Book a free first call. We will discuss your needs and explain the relevant options in our AI and automation service.
