How we work
The four stages, and what each one produces.
About
An automation practice that publishes its reasoning
CanAutomate is an automation consultancy based in London, Ontario, working with established businesses across Canada.
The short answer
CanAutomate designs and builds operational automation for small and mid-sized businesses. We are based in London, Ontario, and we work with clients across Canada. The practice was started in 2025. We are deliberately narrow: we do not sell software, we do not resell a platform, and we do not take on work where the process does not exist yet. What we do is map how work actually happens inside a business, decide honestly what should and should not be automated, and build the parts that should be — into the tools that business already runs.
What experience actually buys you
Whether an automation survives its first year is usually decided before anyone writes a line of code.
Most operational processes come in recognisable shapes. Knowing the shape early is what lets us tell you in the first conversation which steps are load-bearing, which ones only exist because someone left, and where a build will quietly create more work than it removes. That judgement is the expensive part of this work. The building is not.
We publish that reasoning in full: twelve workflows we build most often, the nine ways automation projects fail and what to do instead, where AI belongs and where a plain rule is better, and what a workflow audit produces. You can read all of it and judge the thinking before you commit to any of it.
What we will and will not do
Four positions we hold across every engagement. They are here so you can disagree with them before rather than after.
- We will tell you not to automate something
- Some processes are better fixed by removing a step or changing a rule. Recommending that costs us a project and saves you a build, which is the trade we would rather make.
- We design for the day it breaks
- Every workflow ships with failure handling: what retries, what alerts a person, and what the manual fallback is. An automation nobody can recover is worse than the process it replaced.
- You own what we build
- It runs in your accounts, with credentials you control, documented well enough that another developer could take it over. Nothing is built to only work while we are involved.
- A rule beats a model, usually
- We use AI where the input is genuinely ambiguous. Everywhere else a plain rule is cheaper, faster, identical every time, and explainable to an auditor.
Where we are
We are based in London, Ontario. Most of an engagement — design reviews, build, handover — runs well over video and shared documents, and we work with businesses right across Canada. Being in southwestern Ontario mainly matters at the discovery stage, where watching how work actually moves through a place tells you things a call does not.
For businesses in the following communities, meeting in person during discovery is straightforward:
On-site discovery in
- London
- Kitchener
- Waterloo
- Cambridge
- Guelph
- Woodstock
- St. Thomas
- Sarnia
- Chatham-Kent
- Windsor
Everywhere else in Canada: remote, and it works fine.
Get in touch
Two ways, and email is genuinely read by a person.
Email
hello@canautomate.caLinkedIn
/company/canautomateBased in
London, Ontario, Canada
Related
London, Ontario
What being local actually changes, and what it does not.
Questions and answers
Cost, data handling, ownership and measurement.
Disagree with any of this?
Bring it to the audit. Forty-five minutes, and the map is yours either way.
Book a workflow audit