If you have looked into automating anything, you have run into n8n, Make or Zapier.
The tools themselves are inexpensive. The reason people hire help is not the licence fee. It is that connecting real business systems is harder than the marketing suggests, and the failure modes are quiet.
What you are actually paying for
Not the wiring. Anyone can drag boxes onto a canvas.
You are paying for the part that happens after it works once: what happens when the API is down, when a field comes back empty, when someone types a date in the wrong format, when the same record arrives twice.
A workflow that runs perfectly on the demo and silently drops one record in fifty is worse than no workflow, because you will trust it.
The question that reveals competence fastest
Ask how they handle a failure.
A good answer is specific and slightly boring. Retries with a delay. A dead letter queue or an error branch. A notification when something fails rather than silence. A log you can look at afterwards.
A weak answer talks about how reliable the platform is. Platforms are reliable. Your data is not.
Self-hosted or not
n8n can run on someone else’s servers or on your own. That choice matters more than people expect.
Self-hosting costs a bit of setup and gives you the thing that matters if you handle sensitive information: the data stays where you put it. For a clinic, a law firm or anyone holding client financials in Canada, that is often the deciding factor rather than a preference.
Hosted is fine, and it is faster to start. Just make it a decision rather than a default.
Where these tools stop
This is the part most people find out late.
Workflow tools are excellent at moving information between systems on a trigger. They are not a substitute for a system that has to hold a conversation, make a judgement, or handle something it has not seen before.
If your actual problem is that nobody answers the phone, a workflow will not fix it. If your actual problem is that a form submission needs to reach three places and update a spreadsheet, a workflow is exactly right and you should not buy anything more complicated.
Knowing which problem you have saves more money than any pricing negotiation.
Hiring locally, and why it is not just patriotism
Most of the people advertising this work are offshore, and many of them are genuinely good.
The reasons to hire in Canada are practical rather than sentimental. Time zone overlap when something breaks during your working day. Someone who can be in the room if the build is complicated. And, if you handle regulated information, someone who is subject to the same rules you are.
That last one is not a small thing. If your data is going to be handled by a contractor, where that contractor sits is part of your compliance picture, not a detail.
A cheap way to test someone
Give them one real, small, annoying problem. Not the big one.
Something like: when a quote goes out and nothing happens for five days, I want to know. Ask them to describe how they would build it, including what happens when it fails.
You will learn more from that five-minute answer than from a portfolio. Someone who immediately asks what your quoting system is, and whether it can be read by anything else, is thinking correctly. Someone who says it is easy has not started thinking yet.
If you are not sure which you need
Write down the process. Then ask whether it needs to move information, or make a decision.
Moving information is a workflow. Making a decision is a system. Most businesses need some of both, and the order you build them in matters more than the tools.
