// Guides · Startups

When should a startup get a CRM?

By Kevin Bluett, co-founder of Ahoy · Updated September 4, 2026

Get a CRM the first time a second person needs to know what happened with a customer, or the first time you forget a follow-up you promised. Those two moments are the trigger, whatever your headcount or funding stage. Before them, a spreadsheet holds a founder's pipeline fine, up to a few dozen live conversations. After them, each week without one loses context your first hire will need.

What actually triggers the need for a CRM?

Two events, and both of them are about memory rather than size. The first is that somebody other than you needs the history of a customer conversation: a co-founder about to join a call, or a first hire inheriting an account and its open questions. The second is that you promised a follow-up and it slipped, because you were fundraising or shipping that week and the promise lived in your head.

Most of my career was spent inside HubSpot's CRM, on the engineering side, and the company I co-founded afterwards runs founder-led sales, so I know this question from the vendor's side and from the buyer's. The vendor's answer is usually a headcount or a round, because that is when the deal gets bigger. I think that is the wrong clock. A three-person company with sixty open conversations needs a CRM more than a twelve-person company with eight.

Until one of those two events happens, a spreadsheet works. In my experience it holds up to somewhere around 20 to 40 active conversations, an illustrative range rather than a rule, and your number will depend on how long your deals run and how good your memory is under pressure. Past that range the sheet stops being opened, the promises start slipping, and you find out which conversations you dropped when the prospect emails to ask why you went quiet.

Founders sometimes tell me they will get a CRM after the seed round, and I have stopped nodding along. A round changes how many conversations you have and does nothing for how many you can hold in your head.

How do you know you are already past due?

Most founders who are past due already know it in the abstract and have not connected the feeling to the tool. These are the signs I see most often on calls with early teams, what each one looks like on a normal Tuesday, and what to do in the same week you notice it.

Signal	What it looks like	What to do that week
A second person needs the history	Your co-founder asks "where are we with them?" and the answer is in your inbox, not anywhere they can read	Start the CRM. Import the sheet and connect email, steps 1 and 2 below
A promised follow-up slipped	You said "I'll send that Friday" and remembered on Tuesday, or when the prospect chased you	Write every open promise into one list with a date today, then move that list into the tool
The spreadsheet stopped being opened	Last edit was over a week ago while conversations kept happening	Do not repair the sheet. Replace it
Inbox archaeology before every call	Ten minutes of scrolling threads to remember what was said last time	Connect the calendar so each meeting carries its own history
Someone asks for the pipeline	An investor or advisor wants the list, and building it from memory takes an afternoon	Define three stages and put every live conversation into one of them
Two people wrote to the same prospect	A buyer got two different messages from your company in one week	One shared record per conversation, with an owner, before the next email goes out

If two or more rows describe your week, you are past the trigger and the question has changed from whether to which. That second question is a different guide: CRM for startups covers the tools. This one stays on timing.

What are the signs it is too early?

Vendors rarely say this part. There is a real cost to getting a CRM before the trigger, and the cost is admin that nobody does. You set up stages and a few fields, you create a handful of records, and then a busy two weeks arrives and the tool goes stale. Now you have a spreadsheet and a half-empty CRM, and the second attempt is harder because the first one taught you the tool is a chore.

Four signs that you should wait:

You can hold every live conversation in your head and you have tested that by listing them from memory and checking against your inbox. If the list matches, you are fine for now.
Nobody else needs the history. You are the only person who talks to customers and will be for the next few months. A CRM at this stage is a report for an audience of one.
You are still working out who you sell to. A pipeline formalizes a sales motion. If the motion is going to change twice before the summer, you would be formalizing something you are about to throw away.
The reason you want one is that a peer has one. That is not a trigger. Wait for the follow-up that slips.

We have watched several startups start a CRM trial and never activate it, because the founder had no time to set anything up. In each case the founder was already past the trigger by the time they signed up. The tool was right and the timing was right; the setup was the wall. That changes what to buy, and the tool section below comes back to it.

What do the first two weeks with a CRM look like?

Short, if you keep them short. The founders I have seen succeed with a CRM did four things in the first two weeks and nothing else, and the ones who stalled tried to configure the whole thing before entering a single deal. This is the version I would run.

Import the spreadsheet as it is. Day one. Do not clean it first; you will clean it faster once it is in a tool that can show you duplicates. Every row becomes a contact or a deal. If the sheet has a column you cannot map, drop the column, not the row.
Connect email and calendar. Day one or two. This is the step that decides whether the CRM survives contact with a busy month. If the tool cannot read your inbox and calendar on its own, it is the spreadsheet with more fields, and it will go stale the same way. After connecting, open five deals and check that their threads and meetings are attached.
Define three stages, and only three. Something like Talking, Evaluating, Closing. Write one sentence per stage describing the condition a deal meets before it moves in. Seven stages at this size means six boundaries nobody agrees on. You can add stages when a first hire needs them, and not before.
Run one weekly review. Week two, thirty minutes, same slot every week. Sort every open deal by days since the buyer last replied, give each one a next step with a date, and park the ones you are no longer working. The weekly pipeline review guide has the full agenda; at this size you can run it alone.

One version of those two weeks, with illustrative counts. Two founders, one of whom does most of the selling, have 34 rows in a sheet and roughly a dozen follow-ups they have promised and not yet sent, some of them overdue. On day one they import all 34 rows. Six turn out to be duplicates or conversations that ended months ago, so 28 deals remain. They connect the selling founder's Gmail and calendar, and by the next morning 28 deals have their email threads and past meetings attached without anyone typing a note.

On day two they define three stages and sort: 15 deals in Talking, 9 in Evaluating, 4 in Closing. In the first weekly review, seven deals show more than two weeks since the buyer last wrote back. Three of those get parked and leave the forecast, and four get a dated re-engagement. The dozen floating promises become a dozen tasks with dates, five of them already late, and all five go out that afternoon. The second founder can now answer "where are we with them?" for any of the 28 without asking. Total founder time across the two weeks: around three hours, most of it in the two reviews. Your numbers will differ.

What does getting the timing wrong cost?

Too early costs you admin, covered above. The tool becomes a chore, the chore gets skipped, and you end up maintaining two records, neither of them complete.

Too late costs you context, and that cost is larger and harder to see. When the first sales hire starts, they inherit relationships they were not part of. If those relationships live in your inbox, the hire either asks you about each one, which takes your time, or guesses, which takes the deal. The threads you could have captured for free in month three have to be reconstructed by hand in month nine, and some of them never are.

If I had to choose an error, I would choose slightly early, on one condition: the tool has to fill itself in. Early with a tool that needs feeding is the admin trap described above. Early with a tool that captures on its own costs an afternoon of setup, and the record keeps itself current from there.

What to look for in a tool

On sales calls this year, founders ask us about pricing and seats before they ask about a single feature, and the phrase I hear most is that they want "everything under one roof." Both instincts are sound for a company that has no admin time and no RevOps hire coming. With those two instincts in mind, the criteria for a first CRM are short:

Does it build the record from email and calendar on its own, so that a founder with no setup time still ends up with a pipeline? The unactivated trials I mentioned are the argument for this being the first question.
Can you import a spreadsheet in an afternoon and be working out of the tool the next day, or is there a setup project between you and the first deal?
What does it cost at two seats, and what will it cost at six? Ask whether AI is included in the seat or metered on top, because the second budget line is the one that surprises people in year two.
When it sees a meeting end, does it prepare the follow-up and put it in front of you to approve, so the promise gets kept without you remembering it? I would want that approval step to stay; a tool that emails your customers without asking is a decision to make separately, and most early teams do not want it.

Ahoy was built for teams at this point: it captures email, calendar, and meetings by itself, prepares the follow-ups and record updates for one-tap approval, and Starter is $79 per seat per month billed annually, with AI included and never metered. If you are not sure whether you are past the trigger, the free CRM audit is 45 minutes with us going over your current sheet or tool, and we will tell you if you should wait. For the which-tool question, see CRM for startups.

Frequently asked questions

At what stage should a startup get a CRM?

At the stage where a second person needs the history of a customer conversation, or where a promised follow-up slips because it lived only in the founder's memory. That can happen at three people or at fifteen. Headcount and funding stage are poor predictors; the count of live conversations and the number of people touching them are better ones.

Can a startup run sales from a spreadsheet?

Yes, for a while, and many should. A spreadsheet holds a single founder's pipeline well up to a few dozen active conversations, an illustrative range that depends on deal length. It fails when it stops being opened during a busy two weeks, because it captures nothing on its own and reminds nobody of anything. When the last edit is over a week old and conversations kept happening, the sheet has already failed.

Do you need a CRM before you hire a salesperson?

Ideally the CRM is running before the hire starts, so the history they inherit is already captured. A new salesperson who joins a company with no CRM has to reconstruct every relationship by asking the founder or guessing, and both are slow. Setting up a capture-first CRM a month or two before the hire costs an afternoon and saves the hire's first month.

How many customers or deals before a startup needs a CRM?

There is no fixed number, but somewhere around 20 to 40 active conversations is where a spreadsheet and a founder's memory usually stop keeping up, as an illustrative range. The count of people who need the history matters more than the count of deals. One founder with 30 conversations may be fine; two founders sharing 15 usually are not.

What happens if a startup waits too long to get a CRM?

Context is lost, and it is lost quietly. Follow-ups slip, and when the first sales hire arrives the relationships live in the founder's inbox rather than anywhere the hire can read. Threads that could have been captured automatically in month three get reconstructed by hand in month nine, and some never are.

Book a Demo Get a Free CRM Audit