Hiring an automation consultant in Switzerland: what to ask before you sign

A Swiss fiduciary, clinic or law firm looking for automation help faces the same questions as anyone else (what will it cost, will it work) plus a few that are specific to Switzerland: professional secrecy, where data is stored, which language the team works in, and how VAT applies if the consultant sits across the border.

The short answer: before you sign, get four things in writing. A scope that defines what "done" means, a pricing model that matches the size of the job, a data processing agreement that reflects the revised Federal Act on Data Protection (FADP), and a clear plan for documentation and support in your team's language. This guide covers the questions that get you there. It is general information; check legal and tax points with your lawyer or fiduciary.

1. What exactly will you deliver, and how will we know it is done?

Ask for a written scope before any build starts. It should list every system involved, the trigger and outcome of each workflow, the exceptions to handle (duplicate clients, missing fields, a client with two billing contacts) and what is explicitly out of scope. Exclusions matter as much as inclusions.

A good consultant will want to understand your current process before quoting. If someone prices a "CRM to accounting sync" in the first call without asking which records are the source of truth, expect change requests later. Our guide to what a workflow automation audit includes shows what a proper discovery phase covers.

2. Day rate or fixed price?

Swiss consultants commonly quote either a day or hourly rate, or a fixed price against a defined scope. Neither is wrong; they put risk in different places.

If you accept a day rate for a build, ask for a capped estimate, weekly time reports and a rule that work stops for your approval at the cap. Our article on what automation consultants cost compares the models in more detail.

Also ask about the platform bill. Zapier, Make, n8n and Power Automate subscriptions are separate from the consulting fee and keep running after the project. Ask the consultant to estimate monthly task or credit usage, because a workflow triggered by every inbound email can push you into a higher plan.

3. Whose accounts will the automations run in?

The answer should be yours. Workflows should be built in your firm's own Zapier, Make, n8n or Microsoft account, under a firm-owned login, with the consultant added as a user you can remove. If they build in their own account, you do not fully own the work, your client data sits in an account you do not control, and ending the relationship becomes a migration project.

4. Will you sign an NDA and a data processing agreement?

Anyone who sees client data while building workflows is acting as your processor. Under Article 9 FADP, you may entrust processing to a processor only if they process data as you yourself would be allowed to and no legal or contractual secrecy duty forbids it; you must satisfy yourself that they can guarantee data security, and they may not hand the work to a third party without your prior approval. If they serve EU clients or you have EU operations, GDPR Article 28 applies too.

The FADP does not impose a formal template, but a written DPA is best practice. Our guide on what to put in a data processing agreement with an automation consultant lists the clauses to check. Two Swiss-specific follow-ups:

• Professional secrecy. Lawyers, doctors and other professions covered by Article 321 of the Swiss Criminal Code (unofficial English translation) carry secrecy duties that extend to their auxiliaries. Ask the consultant to acknowledge this in writing, and ask your lawyer whether your professional rules require anything more.
• Breach reporting. Under Article 24(3) FADP, a processor must report any data security breach to you as quickly as possible. Make sure the contract names who calls whom.

5. Where will our data be stored and processed?

List every tool the consultant plans to use and where each stores data. Many automation platforms are US-hosted. The Federal Council recognized the United States as adequate from 15 September 2024 only for companies certified under the Swiss-US Data Privacy Framework, so ask whether each vendor is certified. Make runs separate EU and US zones, and self-hosted n8n can run on a server in Switzerland, though self-hosting makes security your responsibility. Also ask how long each platform keeps run logs, since those logs hold copies of the data that passed through.

Ask too about the consultant's own tools: if they paste a sample record into an AI assistant to debug a workflow, that assistant has processed your data.

6. Which language will you work in?

Switzerland has no single business language, and your team should not have to work in a second one to use its own systems. Ask:

• Which language the workshops and training sessions will be in: French in Romandie, German in Zurich or Basel, Italian in Ticino, or English.
• Which language the documentation will be in. A runbook nobody on the team can read comfortably will not be used.
• Whether client-facing outputs (emails, reminders, forms, invoices) can be produced in several languages, and who checks the wording before they go live.

7. How will VAT work on the invoice?

If the consultant is Swiss and VAT-registered, expect VAT at the standard rate, 8.1% as listed by the Federal Tax Administration in October 2026. If the consultant is abroad, Swiss VAT on services generally works through acquisition tax: according to the Federal Tax Administration, a VAT-registered recipient declares it, and a recipient not on the VAT register becomes liable once such services exceed CHF 10,000 in a calendar year. Ask your fiduciary how this applies to you, and agree up front whether invoices are in CHF or EUR.

8. What happens after go-live?

Automations need upkeep: connected apps change their fields, login tokens expire and staff leave. Ask:

• How failures are reported, and to whom. Silent failures are the expensive kind.
• What documentation you will receive: what each workflow does, what triggers it, where errors appear, who to call.
• Whether there is a support window after launch, and what ongoing help costs.
• Whether the consultant's time zone and availability match your working hours.

Also ask for a reference from a comparable firm, ideally in your sector and canton or language region.

How Flow Mesh helps

In one of our engagements, a Swiss healthcare facility got about 60 hours a month back. Every engagement starts with a first call and an NDA, then a stack audit scoped in writing before it starts, with a verdict on every tool (keep, configure, consolidate or replace). Builds are quoted in writing after the audit and done inside your own accounts; a DPA is available on request.

Key takeaways

• Get a written scope with explicit exclusions before any build is priced.
• Day rates suit small or exploratory work; a fixed price against a written scope suits defined builds.
• Insist that workflows run in your own accounts, and sign an NDA and a DPA that reflect Article 9 FADP and any professional secrecy duty.
• Ask where every tool stores data and in which language the documentation and training will be.
• Check VAT with your fiduciary, especially acquisition tax if the consultant is outside Switzerland.