Should you build your own CRM? Build the tools, never the record.
The tools around your pipeline are cheap to build and getting cheaper. The record, who your customers are and what was said and agreed, has to hold up for people who did not build it, and a homemade one rarely does. And the record can now build itself, the one thing that was never true before.
I built one in 2006, and it lasted exactly until someone had to trust it
I helped build a homegrown CRM in 2006, because that is what you did then. It worked. It held the accounts, it held the notes, it did the job for the people who built it. It was migrated the day someone outside the team had to trust it, and not a day before.
Twenty years on the tooling costs a fraction of what it did and trust costs no less than it ever did. You measure the build against a licence fee, win easily, and never put a number on the day your own system has to be believed by somebody who did not build it.
Two halves. Build one of them.
Flip it. The tools are yours either way. The switch is where the record comes from, and what it costs you every year after.
Cheap to build, cheaper every year, safe to throw away. The same in both states: these are yours.
Your own tables. Correct while the author is paying attention.
A record that writes itself from the work.
Structure, reconciliation and history are the vendor's problem. What is left to you is one page on how you work, kept current, and the tools above.
The day somebody who did not build it has to believe it.
A new hire, an acquirer, a partner, a board. They ask where a number came from and the answer is a person, not a record. That was the day the 2006 build got migrated.
Every number carries who set it, and when.
The outsider checks it themselves. Nobody has to choose to keep it honest, which is the only kind of honest that survives a change of staff.
The mistake is not building. The mistake is building the wrong half.
Three things that were not true in 2006, and you can check all of them
Each claim is the vendor's own, read September 2026.
- 01The record can build itself from work that already happened.
Connect email and calendar and companies, contacts and deals appear, history included, before anybody types anything. In 2006 the only way to get data into a record was to make a person enter it.
- 02A bought record can say who changed a number, and when.
A history on every field, exportable, so a figure carries the person or automation that set it and the date. Homegrown systems almost never can, because nobody builds a history for a database they already trust.
- 03The licence maths that justified building has weakened.
Per seat is no longer the only shape on offer. Per agent and per work pricing mean colleagues who only need to see the record can see it for nothing.
What the record costs you every year after the build is finished
A model with every input printed, not a survey of anyone's build. Argue with the hours; the total is derived from them.
- 96 hKeeping the structure current as the business changes.
One engineer day a month, because a record that stops matching how you sell stops getting used.
- 104 hReconciling the record against the systems that hold the money.
Two hours a week. Billing, the bank and the pipeline disagree by default.
- 32 hAnswering where a number came from when somebody outside asks.
One day a quarter, assumed low on purpose. That row, opened up.
- 24 hWalking each new person through a system whose documentation is the people who built it.
Four hours a hire, six hires. That row at its worst.
Four signs you built the record, not the tools
Answer these about your own setup. Nothing is sent anywhere and nothing is stored. The verdict appears underneath, and it can tell you to leave your build alone.
Your reps route around it. Somebody wants to move a deal, so they tell an assistant to move it, and the required fields never get filled.
The numbers are fiction. Someone asks who the economic buyer is and the answer gets invented, because nobody will ever listen back to the call and check.
It only works while one person feeds it. Every hygiene push works for about a week, then the data quietly rots.
You could not hand it to an outsider. A new hire, an acquirer or a partner could not trust what it says without a tour.
Answer all four and the verdict appears here.
Keep the tools you built. Move the record onto something that maintains itself.
When the record is a byproduct of the work instead of a tax on it, the reps stop routing around it, the numbers stop being invented, and it survives the week discipline runs out. An outsider will believe a record like that, because nobody had to choose to keep it honest.
If you have not built it yet, the plan is usually right about the problem and wrong about the target. Your nouns do not fit, the tools are terrible, or the cost per head is brutal. None of those needs you to own the record. Build anything you could throw away without an argument.
Kesey is a revenue operations practice, a Day.ai Solutions Partner and an Attio Expert Partner. We draw the line with you between the tools worth keeping and the record worth moving, and more often than not the record stays where it is with the layer that remembers on top. When it does move, we move it and stay on after go-live. No case study here and no percentage. The argument does not need one. Kesey is not Day AI, Inc. or Attio Ltd., and it is not affiliated with Clarify or HubSpot.
Who this is for, and who it is not
This is you
- You built something and it is now load bearing and fragile. It runs the business and it worries you, in that order.
- Or the build is still a plan. The cheapest possible moment to have this argument is before anybody writes the first table.
- You have a real process worth capturing. Stages that mean something and the way you sell, not a pipeline nobody agrees on.
- Your team sells by conversation. The record can build itself from calls and email, because that is where the truth already is.
Not you, today
- Your build works and you like it. Then leave it alone. This is for the people it stopped working for, not the people it still serves.
- You run on Microsoft Outlook. Some of the self building records lean on Google Workspace and do not support Outlook yet. We will tell you in the first ten minutes, not the first week.
- You have no process and no conversations to capture. Then a record is not your problem, and no platform will invent one for you.
- You are one person and the only reader. Then the cheapest record is the one you already have. Four steps over your own mail and calendar, and the three places it stops.
- You need the odd object more than you need the record. Sometimes the right answer really is your own system alongside a bought record, and we will say so.
Four questions, and the answer is underneath
The live page carries eight. The other four are answered in the sections above.
Should you build your own CRM?
Build the tools, never the record. Outreach, reporting and enrichment are worth building and safe to throw away. The record, the trusted account of who your customers are and what was agreed, has to hold up for people who did not build it, and a homemade one usually does not. The working rule is to build anything you could throw away without an argument.
Is it cheaper to build or buy a CRM?
The build looks cheaper because you compare it to a licence fee and win that easily. The cost you did not price is the day somebody outside the team has to trust it: a new hire, an acquirer, a partner. A homemade record gets migrated at that point, and you pay for the whole thing at once. The per seat maths that used to justify building has also weakened, because per agent and per work pricing now exist.
What does it cost to maintain a homegrown CRM?
On the assumptions set out on this page, about 256 hours a year, roughly six and a half working weeks. It goes on keeping the schema current as the business changes, reconciling the record against the systems that hold the money, answering where a number came from, and walking each new hire through a system with no documentation but the people who built it. At a loaded $125 an hour that is $32,000 a year, every year, and none of it is the build. It is a model with its inputs printed rather than a survey, so substitute your own; if yours come out lower, keeping what you have is the right answer.
When should you stop building your own CRM?
When your reps route around it to do their job, when fields carry numbers nobody checks, when it only works for the one week a quarter someone has the discipline to feed it, and when you could not hand it to an outsider without a tour. Those are not tuning problems. They are the sign you built the half that should have been bought.
What is the difference between a CRM tool and the CRM record?
A tool does a job and can be replaced: a sequence sender, a dashboard, a script. The record is the durable, trusted account of your customers and conversations. Tools are worth building because they are cheap and disposable. The record is worth buying because it has to be trusted, and trust comes from it being maintained without anyone choosing to.
What if our data model does not fit a normal CRM?
It is the best reason to build and it still does not mean owning the record. Either choose a record whose object model actually fits, or keep the unusual object in your own system and have it reference the record rather than replace it. Owning one odd table is very different from owning the customer history.
Which CRMs build their own record?
Day.ai, Clarify and Attio each build the record from connected email, calendar and calls to different degrees, so the data is a byproduct of the work rather than a data entry tax. Day.ai populates companies, contacts and opportunities from connected email and calendar history, including history from before signup. They differ in ways that matter for your situation.
Does Kesey do the migration?
Yes. We are a revenue operations practice, a Day.ai Solutions Partner and an Attio Expert Partner. We help you separate the tools worth keeping from the record worth moving, migrate the record onto a platform that maintains itself, and operate it after go-live. You keep the tools you built.
Stop maintaining the part you cannot prove.
Keep the tools you got right. Move the record onto something that stays honest without a person feeding it. A call is the fastest way to find out which half you built.