The sixty-second answer
Every business needs one place where customer records live. It only needs to be a dedicated CRM once more than one person touches the same customer, the sales cycle runs long enough that context is lost between contacts, or you must answer questions about what you hold. Before that, a disciplined spreadsheet is legitimate.
The question behind the question
"Do I need a CRM" is usually asked by someone who has already noticed a symptom. A customer got called twice about the same quote. A follow-up that was definitely going to happen did not. Someone left and took the state of six deals with them. Nobody asks this question in the abstract.
So the useful answer is not a yes or a no. It is a description of the point at which the informal system stops working, so you can tell whether you have reached it. Most Canadian businesses asking are very small: as of December 2024 there were 1.10 million employer businesses in Canada, and 1.08 million of them were small [4]. At that size, buying a system that assumes a sales team of twelve is its own kind of mistake.
What a CRM actually is
Strip the category name away and a CRM does three things a contact list does not.
It records history, not just state. A contact list tells you a phone number. A CRM tells you that the number was called on the fourteenth, that a quote went out on the fifteenth, and that nothing has happened since.
It records intent. What is supposed to happen next, by when, and whose job it is. This is the part that fails hardest when it lives in someone's memory.
It survives people. When the person who owned the relationship is on holiday or gone, the relationship is still legible to everyone else.
If you do not need those three things, you do not need a CRM. You may still badly need one contact list instead of four, which is a different and usually cheaper problem.
The three thresholds
More than one person touches a customer. One person can hold context. Two people cannot hold it jointly without writing it down, and the moment they try, the writing-down becomes the system. This is the most reliable single trigger.
The cycle is longer than your memory. If a customer enquires in March and buys in July, you will not remember March in July. A trade doing same-day work can run on a calendar for years. A business quoting on projects that close months later cannot.
You need to answer questions about the record itself. Not "what is their number" but "when did we collect this, why, who has seen it, and can we delete it". This threshold arrives quietly, and it is a legal one as much as an operational one.
The privacy obligations arrive either way
A spreadsheet of customers is a database of personal information, with all the obligations that implies. PIPEDA's Schedule 1 requires that the purposes for collection be identified before or at the time of collection (Principle 2), that collection and use rest on knowledge and consent (Principle 3), and that information not be used or disclosed for new purposes without consent (Principle 5) [1]. It also requires, at clause 4.5.3, that information no longer required be destroyed, erased or made anonymous, and that the organisation develop guidelines and implement procedures to govern that destruction [1]. A folder of spreadsheets going back nine years is the exact opposite of a retention procedure.
Principle 9 is the one that decides whether your system is adequate. On request, an individual must be informed of the existence, use and disclosure of their personal information, given access to it, and allowed to challenge its accuracy and have it amended [1]. Try answering that from four systems and a shared drive. Then try it from one record with a history attached. That difference is most of the argument for a real system, and it has nothing to do with sales pipelines.
If you also market to those customers, Canada's Anti-Spam Legislation requires consent — express or implied — before a commercial electronic message, and requires the message to carry prescribed identifying and contact information [2]. Consent is a fact about a person, which means it belongs on the customer record, not in a separate mailing platform that drifts out of sync. Where your messages travel matters too: the Electronic Commerce Protection Regulations exempt messages sent and received on an electronic messaging service where the required identifying information and unsubscribe mechanism are conspicuously published and readily available on the interface, and the recipient has consented [3]. In-product notifications and outbound email are not the same object.
When a spreadsheet is still the right answer
Plenty of vendors will tell you that a spreadsheet is amateurish. It is not. It is free, universally understood, exports perfectly, and does not disappear when a subscription lapses. A sole operator with a short cycle and a hundred customers can run one for years without a single bad consequence.
What a spreadsheet cannot do is concurrent editing without conflict, history without discipline, or access control at the row level. Notice that all three are about other people. The spreadsheet is not failing at data; it is failing at coordination. If you are the only person who touches a customer, the failure mode has not arrived.
What you should not do is run several spreadsheets, or a spreadsheet plus a mailing list plus a booking tool that each hold their own copy of a customer. That is worse than either extreme, because there is no version anybody trusts. Our guide to how many subscriptions a business actually needs works through counting data locations rather than tools.
Buying one without regretting it
Three questions decide most of this.
How does the data get out? Ask before you sign, and ask for a sample export. A system you can leave is a system you can negotiate with. The domain-name world provides the contrast: under ICANN's Transfer Policy registrants must be able to move registrations between registrars, transfer processes must be clear and concise, and a transfer lock has to be removed or an accessible removal method provided within five calendar days [6]. No such rule governs your customer database, so the export test is the only leverage you have.
What is the evidence for the claims? Vendors quote conversion lifts and hours saved. Under paragraph 74.01(1)(b) of the Competition Act, a performance or efficacy representation is reviewable where it is not based on an adequate and proper test, and the proof of that test lies on the person making the representation [5]. Asking what test produced the number is not rudeness; it is the statutory allocation of proof.
Will people actually use it? A CRM that the team routes around is worse than a spreadsheet, because now the real record is somewhere you are not looking. If entering a call takes longer than the call, nobody will enter the call.
Migrating without losing the past
Move contacts first, then history, then anything automated. Open the export before you trust it — a file that downloads is not a file that contains what you think. Run the old system read-only alongside the new one for a full cycle, and only cancel once you have successfully found something in the new system that you last saw in the old. Our walkthrough on switching business software without downtime sets out the sequence in full.
Where we sit
MapleWorkSuite treats the contact record as shared infrastructure rather than as a product. Whichever apps you switch on — booking, invoicing, email, phone — they read and write the same Canadian-hosted customer record, so history accumulates in one place without anyone syncing anything. That is the specific problem we set out to solve: not a better pipeline view, but the absence of five competing copies of the same person.
We will say plainly where this is the wrong buy. If you sell into long, complex, multi-stakeholder deals and live inside forecasting, a dedicated sales platform will go deeper than we do. If your problem is that a customer's booking, invoice and email history are three different systems that disagree, that is ours. Our comparison of a suite against best-of-breed tools lays out both sides without pretending the answer is always us.
The test is not whether you feel like a CRM company. It is whether you can currently answer, in under a minute, what has happened with any given customer and what happens next. If you can, keep your spreadsheet. If you cannot, you already need the thing.