Nobody starts a business because they love regulation. Then growth arrives, and with it a discovery every founder makes sooner or later: the rules were written as if every business had a legal department, and yours has you, a phone, and a list of jobs for tomorrow.
Consent rules govern your marketing messages. Privacy expectations govern the customer data sitting in your apps. Review platforms have rules about how reviews may be requested. Your booking, payment, and messaging tools each carry terms that can suspend an account that ignores them. Individually, each rule is reasonable. Together, carried in one person's head, they become the kind of background anxiety that founders describe as "feeling exposed" without being able to name why.
The answer is not to become a part-time lawyer. It is to treat compliance the way this whole series treats revenue: as a system problem. What is remembered fails under pressure. What is built into the routine happens on the busiest day of the year, which is usually the day it matters most.
Start with the rules that touch revenue. A founder does not need a catalogue of every regulation in two countries. Start narrower: which rules touch the way you win and keep customers? For most founder-led service businesses, that list is short enough to write on one page. How consent is captured and recorded before marketing messages go out, and how an opt-out is honoured. What customer information you collect, where it lives, who can see it, and how long you keep it. How reviews and referrals are requested, so the ask never becomes pressure or an incentive that breaks platform rules. And what your messaging and calling tools require before automated messages are sent from your numbers.
Writing that page is itself a compliance act. Most exposure I see in small businesses is not defiance; it is drift. A tool was connected quickly, a list was imported from somewhere older, a message sequence was copied from a template written for another country's rules. Nobody decided to break anything. Nobody decided anything at all — and that is exactly the gap a one-page inventory closes.
Build each rule into a step, and keep the proof. Then convert each rule into a step that runs itself. Consent is captured on the form and stored on the contact record, with its source, automatically. An unsubscribe stops the sequence without anyone being asked to remember a name. Review requests go out at a defined moment, in approved wording, to every customer equally — which is both fairer and safer than a team member improvising requests on good days. Access to customer data is limited to the people whose work needs it, on the principle of minimum access: the fewer hands on the data, the smaller the accident when something goes wrong.
Keep proof as you go, in the ordinary course of business. The record of consent, the copy of the message as sent, the date a request was honoured — if your system stores these by default, a complaint or a question from a regulator becomes a lookup instead of an excavation. Founders fear the day someone asks, "Show me." A system that keeps its own records turns that day into an email attachment.
Two boundaries deserve to be explicit. First, this is general information from an operator's chair, not legal advice; rules differ between Canada and the United States and change over time, and a business running campaigns at scale should have its situation reviewed properly. Second, some questions should never be improvised at all — a legal threat, a regulator's letter, or a dispute over a trademark. Those go, untouched, to the professional whose job they are. Knowing which pile a problem belongs in is itself part of the system.
Compliance as a growth asset, not a tax on it. Here is the reframe I offer founders who experience all of this as friction: the businesses that handle consent, data, and reviews cleanly are the same businesses customers describe as professional. The disciplined follow-up, the message that arrives because it was agreed to, the review that was requested once and gracefully — the customer cannot see your compliance, but they feel its effects as order and respect.
Growth multiplies whatever a business already is. If the routine is improvised, growth improvises at scale, and the clean-up costs more than the discipline would have. Build the rules into the foundation while the business is small enough that doing so is a week of decisions rather than a year of repairs. Small business, big rules is not a complaint. Handled early, it is a head start.