Commissioning automation is not like buying software; it is wiring something into your business’s nervous system. So the selection criterion should not be “how smart” but “who owns it, how does it break, who fixes it”. This article lists ten questions to ask when choosing an agency, freelancer or “expert”, and the setups to refuse. For what automation is, see what is AI automation; for the tool, what is n8n.
Ten questions to ask
- 01Whose account will the workflow live in? The answer must be “yours”: the n8n/automation account, WhatsApp, email, sheets — all in your name. A workflow built in the agency’s account leaves with the agency when the contract ends.
- 02Where will credentials (API keys, tokens) be kept? In your account, where you can see them. “Safe with us” is dependency.
- 03Where does my customer data go? Which provider receives messages and forms sent to an AI model, is it stored, is it in my privacy notice? The KVKK responsibility is yours, not the agency’s.
- 04What happens when a workflow breaks? Who receives the error alert, how many hours until it is looked at, is that maintenance included?
- 05How is it documented? Is there a document per workflow: what it does, which trigger, what happens at each step, where to look when it fails?
- 06Is handover possible? If one day you want to work with someone else, can you export and move the workflow? Standard tools (like n8n) yes; closed “platforms” usually no.
- 07What is the measure? Which number shows the workflow works: missed forms down to zero, response time down to how many minutes? Unmeasured automation is a feeling of “it works”.
- 08Where is the human handover? What does the bot answer, what does it leave to a human, what does it never promise? If that boundary is not written, false promises reach customers.
- 09What is the fee structure? Setup plus optional maintenance, or a monthly subscription? If the workflow stops when payment stops, it is a rental (the same trap as in social media packages).
- 10Can you show a reference workflow? Not a screenshot, but the documentation and measurement of a running one.
Five setups to avoid
- Being sold “access” to an automation tool hosted by the agency. The tool is the agency’s, you are the tenant; some tools’ licences also forbid this model.
- A WhatsApp workflow tied to one person’s phone. When that person leaves, the workflow ends. A business number and an API-based setup (WhatsApp Business).
- An unbounded chatbot. “Answers everything” = makes false promises. A bot with written scope and defined handover.
- Undocumented workflows. A workflow described as “it works, don’t touch it” stops one day and nobody knows why.
- Delivery without measurement. Without a before/after number you never know whether the automation helped.
How to pick the first project
Small and boring: missed-form notification, order record, stock alert. Built in a week, measured, trust built; the big workflow comes later. Example workflows are on the automation page: order notification, form follow-up, stock alert, market scan.
Our answers
Sufitware’s AI automations service builds workflows in your account, documents and hands them over; credentials stay with you; we do not host and rent the tool; every workflow has a measure and a human-handover boundary. Ask us the ten questions above too — the answers come written in the quote. Write your first small project in the brief form.
Frequently asked questions
- Whose account should an automation workflow live in?
- The business’s own account, including the automation tool, WhatsApp, email and sheets. A workflow built in the agency’s account leaves with the agency when the contract ends.
- Should an AI automation agency charge monthly?
- Setup plus optional maintenance is healthier. If the workflow stops when payment stops, it is a rental; the contract should state the workflow remains yours.
- What should the first automation project be?
- A small, measurable task: missed-form notification, order record or stock alert. Built in a week, with a number that shows the result.

