Here's the trap. Somebody asks whether you have a CRM, you say no, and it lands like an admission. So you buy one, spend a fortnight setting it up, and six months later it holds a partial copy of what is still really in the spreadsheet.
The trigger is not headcount, revenue or funding stage. It is the first time you cannot answer a question about a customer without asking a colleague. Everything below is a way of noticing that moment earlier.
A spreadsheet is a genuine system of record, as we set out in what a CRM actually is. It fails in four specific ways, and until one of them bites you are not behind.
Threshold one: two people editing the same row
This is the earliest and the most under-rated, because it fails quietly. Two people update the same account on the same afternoon and one edit wins. Nothing warns you. You find out weeks later when somebody calls a customer about a thing that was already resolved.
The symptom: anyone has said "I think I updated that" more than once. The threshold: the second person who touches customer records. Not the second employee, the second person doing sales.
Threshold two: one company, many people, many deals
A flat sheet has one row per thing. Real business-to-business selling has a company with four contacts, two open opportunities and a closed one from last year. Represent that in rows and you start duplicating the company name, which means it is now spelled three ways and your count of open deals is wrong.
The symptom: you have started colour-coding, or you maintain a second tab to reconcile the first. The threshold: the first account with more than two contacts involved in a live deal.
Threshold three: nothing arrives on its own
Everything in a spreadsheet is there because somebody typed it, so the record is exactly as complete as your least diligent week. That is survivable when the person selling is the person who cares most. It stops being survivable the moment somebody is doing it because they were asked to.
The symptom: your pipeline review starts with twenty minutes of updating the sheet. The threshold: the first hire who did not choose this job.
Threshold four: memory stops covering the gap
Under about twenty open deals with a short cycle, a good salesperson simply remembers. The spreadsheet is a backup for a brain that is doing the actual work. Two things break that: volume, and time.
The symptom: a customer refers to a conversation you cannot recall, or a deal you thought was dead comes back and nobody knows why it stalled. The threshold: roughly twenty concurrent open deals, or any sales cycle running past a month.
What if you pick the wrong one?
This is the fear that keeps people on spreadsheets past the point of usefulness, and it is worth separating into two very different migrations.
Spreadsheet to CRM is easy. It is a CSV import, it takes an afternoon, and every CRM in the category has built that path deliberately because it is how they acquire customers. The risk of moving too early is close to zero.
CRM to CRM is not. Custom fields, activity history, integrations, automations and whatever your team has quietly come to rely on all have to be rebuilt, and the activity history is the part that exports badly. That is the migration worth fearing, and it arrives later.
The practical consequence runs against the instinct: starting on a free tier early is cheap insurance, and agonising over which product to pick while still on a spreadsheet is optimising the wrong decision. You are choosing between an easy migration now and a hard one later either way.
So what should you actually do at each stage?
- One person, short cycles, under twenty deals: a spreadsheet, and no guilt about it. We run a complete outbound motion on a free Notion database in our $17 a month stack, which handles the relational problem better than a sheet does at no cost.
- Second salesperson, or the first long cycle: move to a free CRM tier. HubSpot and Attio both have genuinely free plans, so this step costs nothing but the migration afternoon.
- People doing outbound calling all day: Close at $19 a seat has calling built in, which removes a separate tool rather than adding one.
- Before you pay anything: check how the price behaves as you grow, not what it is today. Contact-tier escalation and seat caps are what actually bite in this category, and one popular option reprices your whole team when you cross ten users.
The honest summary is that most teams buy a CRM about a year later than the moment they should and set it up about a year before they need what they are setting up. The four thresholds above are observable, which is more than can be said for the stage-based advice written by people selling the software. When one of the four does bite, the choice is mostly about how each option gets expensive later: a headcount cliff, a contact-count drift, or a narrower integration list.