The short answer
Check four things before you sign. Ask to see a similar workflow that already runs for a real client. Ask who owns the accounts and the code. Get a written scope with a fixed price for the first build. Ask what happens when something breaks. An agency that answers all four plainly is usually a sound choice.
The rest of this guide explains each check and adds a few more. It works for any agency, large or small, in Switzerland or elsewhere.
Start with your own problem, not their pitch
Before you speak to anyone, write down one task that costs your team time every week. Good candidates are copying web form enquiries into a CRM or chasing unpaid invoices. Note how often it happens, who does it today and what a good result looks like.
This one page does more for your search than any comparison site. It lets you judge whether an agency understands the problem or just repeats the word AI. It also gives every agency the same brief, which makes the quotes comparable.
Questions that separate builders from resellers
Some agencies build and run automations themselves. Others resell a subscription tool and add a margin. Both can be fine, but you should know which one you are paying. These questions usually show the difference within a few minutes.
- Can you show a workflow like mine that runs today, and may I speak to the client or see the live result?
- Which tools do you build with, and why those rather than others?
- Where does the AI model sit in the process, and which steps need no AI at all?
- What does a person check before anything is sent to a customer or written to a system?
- Who on your side will actually build this, and will that person join the calls?
Ownership, hosting and data protection
Ask who owns the workflows, the accounts and the code once the project is done. A fair arrangement is that you own what was built for you, with documentation and a handover, while third-party tools keep their own licences. If the agency keeps everything in its own accounts, leaving later becomes expensive.
Ask where your data goes. A good agency can tell you which tools see which data and which AI providers receive text. Switzerland's revised data protection act, the nDSG, has applied since 1 September 2023. It sets duties for how personal data is handled, including when an outside provider processes it for you, so a clear map of data flows is a fair thing to request. If you also serve customers in the UK or the EU, their rules may apply too. This is general information and not legal advice, so have your own data protection adviser review the setup.
If your sector has stricter rules, say so in the first call. Some work needs specific certifications or a Swiss-only host, and an honest agency will tell you early if it cannot provide them.
How to read a quote
A useful quote names what is built, what is not built, how long it takes and what you pay in total. It should separate the one-off build from the running costs, such as tool subscriptions and AI usage. Running costs are the line that most often goes missing.
Published prices vary widely. One German-language comparison guide claims setup costs of EUR 3,000 to 8,000 and monthly retainers of EUR 800 to 2,500 for n8n projects. These are that guide's own claims and not verified figures, and your scope will decide where you land. Use them only to spot a quote that is far outside the range and ask why.
Fixed prices for a defined first build are easier to compare than hourly rates. Ask what happens if the scope changes and who pays for the extra work.
Red flags worth walking away from
Some warning signs show up repeatedly. None proves bad intent, but each is a reason to ask more questions.
- Promises of a specific saving or return before anyone has looked at your process.
- No example you can verify, or case studies with no named client and no live result.
- A demo built on made-up data that never touches your real tools.
- Vague answers about where data is stored or which AI provider sees it.
- Pressure to sign quickly, or a contract that locks you into the agency's accounts.
- No plan for monitoring, so you only learn about failures from your customers.
Compare agencies on one sheet
After the calls, put the agencies side by side on one sheet. Score each from one to five on proof of similar work, clarity of the quote, ownership terms, data handling and how well they listened to your problem. Add a line for how comfortable you felt asking basic questions. If an agency made you feel foolish for asking, that is useful information.
Do not pick on price alone. The cheapest quote can leave out running costs or support, and the most expensive may include work you do not need. Pick the agency whose answers you could repeat to a colleague without getting any of them wrong, because that usually means they were clear.
A note on the studio behind this page
RAWR Productions is one option among many. It is a small studio working from Switzerland and the UK. It builds automations mostly on n8n, self-hosted in the EU, with AI models where a step needs judgement, and it runs its own studio on the same tools. The first step is a free 20-minute call, and a fixed quote follows in writing.
It is not the right fit for everyone. A large enterprise that needs an on-site team or round-the-clock staffed support should look at a bigger firm. The same goes for regulated work that needs certifications the studio does not hold. Apply the checks above to it as you would to anyone else.
Questions
How many agencies should I talk to?
Two or three is enough for most small and mid-sized businesses. Give each the same one-page brief and ask the same questions. More than that tends to add confusion, and you will learn more from comparing three detailed answers than from skimming ten websites.
Should I pick a Swiss agency or can it be abroad?
Location matters less than how they work. A nearby team is easier for workshops, and knowledge of Swiss languages and payment habits helps. What counts most is that they can show real work, explain where your data goes and are available when something breaks.
Is a fixed price better than hourly billing?
For a defined first build, a fixed price is easier to compare and protects you from overruns. Hourly billing suits open-ended exploration where nobody knows the scope yet. Whichever you choose, get the scope in writing and ask how changes to it are handled and priced.
What should be in the contract?
At minimum the scope, the price, the timeline, who owns the workflows and accounts, and how support works afterwards. If personal data is involved, add how it is handled and by whom. This is general information and not legal advice, so have a lawyer review the contract.
How soon should I see a result?
A small first workflow can often go live within a few weeks, though it depends on how many tools are involved. Be wary of anyone who promises results before they have seen your process, and equally of projects with no early milestone that you can check.