The sixty-second answer
Automate the repeated, rule-based task that a customer is currently waiting on. For most small businesses that is booking, invoice follow-up, or the first reply to an enquiry. Do not start with the job you personally dislike most — start where the delay is visible outside your business.
The wrong way to choose
Most automation projects begin with a grievance. Someone hates doing expenses, or hates the weekly report, so that is what gets automated. The result is usually a working system that saves a small amount of internal time and changes nothing a customer would ever notice.
The better starting point is the queue. Somewhere in your business there is a task where the work is trivial but the wait is not — an enquiry that sits until Tuesday, a booking that needs a call back, an invoice nobody has chased in three weeks. Those waits are costing you revenue right now, and they are the cheapest thing to fix, because the rule that governs them is simple enough to write on a sticky note.
This matters at scale. As of December 2024 there were 1.10 million employer businesses in Canada, and 1.08 million of them — 98.2 per cent — were small [1]. Most of these businesses have no operations manager and no slack in the day. The first automation has to pay for itself quickly and visibly, or the second one never happens.
The ranking test
Score every candidate task on four dimensions before you buy anything.
Frequency. Does it happen many times a week? Automating a monthly task is a hobby. The return lives in repetition.
Rule clarity. Can you write the rule in one sentence, with no "it depends"? "If an invoice is unpaid seven days after the due date, send this reminder" is a rule. "Decide whether this customer should get a discount" is a judgment.
Customer visibility. Is someone outside your business waiting on the outcome? Visible waits convert to lost work. Internal waits mostly convert to irritation.
Blast radius. If the automation does the wrong thing a hundred times before anyone notices, how bad is that? A hundred wrong booking confirmations is a bad afternoon. A hundred wrong prices is a legal problem.
High frequency, clear rule, customer waiting, small blast radius — automate it this month. Anything scoring badly on rule clarity or blast radius is a candidate for assisted work, not automated work: the system drafts, a person approves.
The three that almost always come first
Booking. If your business runs on appointments, the highest-value automation is letting people book real availability themselves, without a phone call. It removes a wait, removes a double-entry, and works at eleven at night when your customer is actually thinking about it. The rule is simple and the failure mode is recoverable.
Invoice follow-up. Nothing improves cash flow faster than a reminder that goes out reliably instead of when someone remembers. The rule is a date comparison. The message is polite and identical every time. This is the purest automation candidate most small businesses have, and the one most consistently left undone.
First reply to an enquiry. Not the whole conversation — the acknowledgement. Confirming that a message arrived, saying when a human will respond, and capturing the details you always end up asking for anyway. This turns a silent wait into a known wait, which is the difference between a customer waiting and a customer calling your competitor.
All three share the same profile: constant, rule-bound, externally visible, and cheap to get wrong.
The Canadian rules that shape automated messages
Anything that sends messages on your behalf inherits your obligations. Canada's Anti-Spam Legislation prohibits sending a commercial electronic message unless the recipient has consented, expressly or by implication, and unless the message complies with the requirement to carry prescribed identifying and contact information [2]. The statute does not care whether a person or a scheduler pressed send.
Where the message travels matters too. The Electronic Commerce Protection Regulations exempt messages sent and received on an electronic messaging service where the identifying information and the unsubscribe mechanism required by subsection 6(2) are conspicuously published and readily available on the user interface through which the message is accessed, and the recipient has consented expressly or by implication [3]. In plain terms: an in-app notification with your details permanently visible in the interface sits differently from an unsolicited email. Build with that distinction in mind rather than discovering it later.
The same care applies to the customer data feeding the automation. PIPEDA requires that the purposes for collection be identified at or before collection, that information not be used or disclosed for new purposes without consent, and that an individual be able to access their information on request and challenge its accuracy [5]. A booking form collects a phone number to confirm a booking. Using that number for a promotional campaign eighteen months later is a new purpose, and it needs its own consent.
Judge the claims before you buy
Automation is sold with numbers — hours saved, percentage lifts, headcount avoided. Canadian law puts the burden of proof for those numbers where it belongs. Under paragraph 74.01(1)(b) of the Competition Act, a representation about the performance or efficacy of a product is reviewable conduct where it is not based on an adequate and proper test, and the proof of that test lies on the person making the representation [4]. When a vendor tells you a tool cuts admin by a specific proportion, it is entirely fair to ask what test produced that figure.
Watch the pricing shape too. Subsection 74.01(1.3) treats a price that cannot actually be obtained because of fixed obligatory charges or fees as a false or misleading representation, unless those charges are imposed under an Act of Parliament or a provincial legislature [4]. Mandatory onboarding or setup charges that surface only at signature are precisely the pattern that provision addresses.
What to leave alone
Automate the routing of hard things, never the deciding. Complaints, refunds above a threshold you set, pricing exceptions, anything involving an employee's standing, and anything that would end up in front of a lawyer: these should reach a person fast, with full context attached. That routing is itself a worthwhile automation, and it is a completely different exercise from letting a system answer.
Be similarly careful with anything that computes an obligation. The Canada Revenue Agency's guidance is explicit that the GST/HST rate to charge depends on the place of supply — a Vancouver store delivering to Toronto charges the Ontario rate because that is where the supply takes place [6]. A system that captures the delivery address consistently makes that determination far easier to get right. A system that assumes your home province is where every sale happens will be wrong quietly and repeatedly.
Measure before, not after
Write the number down before you switch anything on: average hours to first reply, average days to payment, number of double bookings per month, number of enquiries with no response at all. Automation almost always feels like an improvement, because the tedious part stops. Feeling and measuring are different things, and only one of them tells you whether to do the next project.
Give it a month, then look. If nothing moved, the task was not the bottleneck, and the honest response is to turn it off rather than defend the purchase.
Where we sit
MapleWorkSuite is modular, so automation arrives one job at a time rather than as a platform migration. If booking is your bottleneck, switch on booking. If invoice chasing is, start there. Apps share one contact list, so an automated reminder and a human phone call are looking at the same record rather than two versions of it — which is what stops a customer being chased for an invoice they settled last week.
We keep a person in the loop wherever the answer matters, and we are direct about the limits: our tools take a booking, acknowledge an enquiry, and chase an invoice reliably. They do not decide whether to give a refund, and we would not sell you one that claimed to. Our article on what AI can actually do for a small business is more specific about that boundary, and the subscription audit walkthrough is a good companion if you suspect you are already paying for automation you never turned on.
Start with the queue that a customer can see. Everything else is easier once that one is moving.