In this guide · 8 sections
Short answer
Choose a consultant who maps your process before building, builds on accounts your business owns, sets up error alerts, hands over written documentation, and estimates monthly task or execution volume so you know the platform bill. Agree up front who fixes things when an app changes.
What an automation consultant actually does
Most small business automation runs on no-code or low-code platforms such as Zapier, Make or n8n, which connect apps through triggers ("a form is submitted") and actions ("create a contact, send a WhatsApp, add a row"). A consultant's job is to choose the right platform, design the workflow, build and test it, and hand it over in a state your team can live with.
Typical small business projects include enquiry follow-up, invoice reminders, booking confirmations, onboarding checklists and moving data between a store, an accounting system and a spreadsheet. For examples with typical scopes, see our guides on automating enquiry follow-up and invoice reminders in Xero and QuickBooks.
Process mapping comes first
Automating a messy process just makes the mess faster. A good consultant asks to see how the work happens today before suggesting any tool.
Write down the current steps
Who does what, in which app, how often, and how long it takes. A simple numbered list or a whiteboard photo is enough.
Mark the decisions and exceptions
Where does someone use judgement? What happens with a duplicate, a missing field or an angry customer? These cases decide what can be automated safely.
Decide what stays manual
Approvals, refunds and anything with legal or money risk usually keep a human step.
Agree how success is measured
Hours saved per week, response time, or fewer missed follow-ups. Without a measure, nobody can say whether it worked.
Estimate volume
How many runs a month? That drives which platform and plan makes sense.
Whose accounts the automations run on
This is the question owners most often forget to ask. If the consultant builds on their own Zapier or n8n account, using their own logins to your apps, you do not control your own business processes. When the relationship ends, everything stops.
A good set-up
- Automation platform account in the business's name, paid by the business
- Consultant added as a team member, removable at any time
- App connections made with a business or service account, not a personal mailbox
- Passwords and API keys stored in your password manager
Red flags
- "We'll run it on our account, you just pay us monthly"
- Connections made with the consultant's personal Gmail
- No list of which apps are connected or with what permissions
- Self-hosted n8n on a server only the consultant can access
Platform costs: tasks, executions and plans
The consultant's fee is only part of the cost. The platform charges every month, and the pricing models differ:
| Platform | How it charges | Entry paid plan (as of Oct 2026) |
|---|---|---|
| Zapier | Per task: each step and connector call uses tasks; free plan includes 100 tasks a month | Professional from US$19.99/month |
| n8n (cloud) | Per monthly workflow execution, regardless of how many steps | Starter from €20/month, billed annually |
| n8n (self-hosted) | Community Edition free to use; you pay for the server and upkeep | Server costs plus maintenance time |
| Make | Per credit for each module action | See our Zapier vs Make comparison |
Zapier's pricing page says that if you reach your task limit you are switched to pay-as-you-go unless you turn it off, so a runaway loop can raise your bill. Ask the consultant to set limits and alerts. For a full picture of build and running costs, see our workflow automation cost guide.
Error alerts, documentation and handover
Automations fail quietly. A token expires, an app renames a field, a form adds a question, and leads stop arriving in the CRM. Before you accept the work, check you have:
Handover checklist
Questions to ask before you hire
Use these in your first call. A good consultant answers them easily.
- Will you map our process before recommending a platform?
- Will everything run on accounts in our company's name?
- How will we know when a workflow fails, and who gets the alert?
- What monthly volume do you expect, and what will the platform cost us?
- What documentation do we get at the end?
- What happens when one of our apps changes its connection or API? Is that covered, and for how long?
- Is the price fixed for the agreed scope, and how are changes quoted?
Be cautious of anyone who recommends a platform before asking about your process, or who prices only by the hour with no defined scope for a simple workflow.
Do it yourself or get help?
A single, simple automation, such as copying form entries into a spreadsheet, is a good first DIY project on any of these platforms. Get help when a workflow touches money, customer data or several apps, or when staff rely on it daily and a silent failure would cost you.
Our Workflow Automation package (S$390 per workflow) covers one workflow end to end: process mapping, build on your own accounts, error alerts, testing and written handover notes.
Frequently asked questions
It depends on scope. Simple single workflows are often priced as fixed packages, while multi-app projects are quoted per project or hourly. Remember the platform costs on top: as of October 2026, Zapier's paid plans start from US$19.99 a month and n8n cloud from €20 a month billed annually, depending on volume.
Zapier is the easiest to learn and has the most app connections. Make is usually cheaper for multi-step workflows. n8n suits technical teams and can be self-hosted. A good consultant picks based on your process, volume and who will maintain it, not on their personal preference.
No. Automations should run on a platform account owned and paid for by your business, with the consultant added as a user. App connections should use business accounts. Otherwise you lose control of your own processes, and everything stops if the relationship ends.
Apps regularly change fields, permissions and connection methods, which can break workflows. Error alerts tell you quickly. Agree before handover whether fixes are included for a period, covered by a maintenance plan, or charged per hour, so you are not left without support.
Yes, but you remain responsible for it. Map which personal data each workflow moves, send only the fields needed, use apps you have assessed, and remove connections you no longer use. If a workflow moves data overseas or to new vendors, reflect that in your privacy notice.