Articles·Go-to-market
My CRM is a data dumping ground. What a custom CRM does that the big one can’t.
A custom CRM is a screen you build for the way you actually sell, connected to the commercial CRM you already pay for, which keeps being the place the data lives. The fix for a CRM that makes you click twelve times to do one thing is to leave the data where it is and build the view on top. I never gave up on the big-name CRM. I turned it into a data dumping ground, ran my activity reports out of it, and did the work somewhere else.
Why does a commercial CRM get in the way of selling?
A commercial CRM gets in the way because it’s built for every business and every process, so it fits none of them exactly. The screen for a phone call is the same screen for an account review. A cold email campaign runs in a separate tool and never tells the CRM what happened. Moving a lead to the next step in your cadence is a series of clicks, and if the next step lands on a Saturday, that’s your problem.
The reports are good. Mine were built on my own activity, and they kept me honest. The doing is where it drags.
What do most agencies try first?
Most agencies try to make the CRM do everything. They buy the add-ons. They pay for the AI credits. They spend a quarter trying to find a human at the vendor to help them set up a workflow, and the workflow still doesn’t do the one thing they wanted. If you’re stuck in a deal with a commercial CRM, trying to find a human to help you, here’s my one rule: just don’t pay for the AI credits.
The other version is switching CRMs. New tool, same problem, and now the history is in two places.
Wanna fix it?
A CRM that gets in the way gets fixed by leaving it as the data home, connecting to it through its API, and building the screens and buttons your sales process actually needs on top.
- Keep the commercial CRM as the dumping ground. Every lead, every activity, every report still lives there. You’re adding, not replacing.
- Connect through the API. When I discovered APIs, I finally got everything I ever wanted out of a CRM: a view to crush volume on the phone, and a massive cold email campaign that still updated the CRM it wasn’t running in.
- Build the buttons you actually push. In mine, a lead has a button that brings in the last two agents on my AI SDR team, the copywriter and the QA agent, and the drafts get written. Another button moves the lead to the next step in the cadence, and it skips weekends if the step lands on one.
- Put the cadence in the custom layer. My multi-channel cadence lives in the custom CRM, because the commercial one never held it the way I run it.
- Make it the hub. Enrichment tools, scrapers, agents, email replies, email dispositions, lead cadence. The custom CRM is where all the tethers meet. It can be your sales home.
What does it look like once it’s running?
Once it’s running, you open one screen in the morning and it looks like your process. If you don’t like the list view, change it to Kanban. If a step is wrong, change it. A bunch of things I thought I’d want turned out wrong after I used them, so I tweaked them or changed them. That’s the beauty and the power of anything custom. You stitch the glove based on the size of your own hand.
It took a long time. It started as one thing and kept growing and kept growing. It was a weekend hobby. The connection to the cold email platform broke more than a few times before I rebuilt it as a direct one. That’s the honest version of “custom.”
Can you do this yourself?
Partly. Every major CRM has an API, and a custom layer isn’t mutually exclusive with Salesforce or HubSpot. You can build something that connects to either one. The first version can be a single screen that does the one thing your CRM makes hard: a dialing view, or a button that writes the follow-up.
Where DIY stops is the plumbing. Connecting a sending platform, an enrichment service, and a team of agents to a CRM, and keeping those connections alive when one of them changes, is a job. If one screen would fix your week, build that screen. If your whole sales process is spread across five tools, build the hub.
Quick answers
- Should a small agency replace its CRM with a custom one?
- No. Keep the commercial CRM as the data home and build the custom layer on top.
- What does a custom CRM connect to?
- The commercial CRM, the email sending platform, enrichment tools, scrapers, and AI agents, all through their APIs.
- What’s the first custom screen worth building?
- The one your CRM makes hardest. For me it was a dialing view with four outcome buttons.
- Can a custom CRM connect to Salesforce or HubSpot?
- Yes. It sits on top of either one through the API.
- Should I buy the CRM’s AI credits?
- My rule: don’t. Build the button that does the thing instead.
- How long does a custom CRM take?
- Mine was a weekend hobby that kept growing. The first useful screen is the fast part.
Image brief for Astra (header, same treatment as the other headers)
Next step
If you’d rather talk it through, the intro call is free and 30 minutes: dobetter.plus/talk.
---
One header image, same series. Match smug-guy-dobetter-colors-FINAL.png exactly for style: same man (dark wavy hair, aviator sunglasses, navy button-down, dark pants, brown boots), same semi-realistic painted texture, same deep blue palette with one streak of warm light, same deadpan mood. Wide 16:9. No text in the image.
Scene: He sits at a workbench like a cobbler, sewing a leather work glove by hand with a big needle. The glove is clearly shaped to his own hand, which is resting flat on the bench as the pattern. Around the bench, cables run from the glove to a laptop, a desk phone, and a small filing cabinet.
Alt text: “A salesman at a workbench sews a leather glove shaped to his own hand, with cables running from it to a laptop, a phone, and a filing cabinet.”
+Talk to Chris