Software

Building your own CRM with AI

Marc Cornelius15 October 2026 · 4 min read

How many times a week do you retype the same number from one tool into another? A CRM for your clients, a separate tool for projects, a third for hours, a fourth for invoices, and your proposals sitting in a folder somewhere. Each piece works fine on its own. Nothing connects. And that is exactly where the pain lives.

Why an off-the-shelf package eventually gets in your way

A standard CRM like HubSpot or Pipedrive is a fine start. You fill it in, you click around, you are up and running by the afternoon. Easy to start. But easy to start is not built to last. The moment your way of working diverges from the default, you start adapting yourself to the tool instead of the other way round. And then the retyping begins. We ran into this ourselves. A separate CRM, a project tool, time tracking, invoicing and a separate home for our proposals. Everything stood alone. Numbers had to be retyped. And nobody had a view from client to invoice.

What a standard CRM will not do for you

A package built for everyone fits nobody completely. It does not know your steps. It does not know that in your business a deal only counts after a certain moment, that a project consists of sprints, or that your hours hang off a revenue line that hangs off a proposal. You can try to force it with custom fields and Zapier links, and for the quick stuff that works. But once your business process is genuinely your own, you keep tinkering with something that never quite fits.

Start with the process, not the tool

Before you have anything built, you first map your entire process. From first contact to paid invoice. Which step follows which, who does what, where the most time and the most hassle sit. You do that in a plain sheet, without thinking about a tool. Only once that is on paper do you know what your CRM needs to do. Whoever starts with the tool builds an expensive version of a broken process. Whoever starts with the process builds something people use the very next day.

“Whoever starts with the tool builds an expensive version of a broken process.”

Controllable from Claude via MCP

We built our own agency CRM. One source of truth that fits the way we work: clients, projects, sprints, hours, revenue and proposals in the same system. And we put our own MCP server on top of it. MCP is a bit like USB for AI: a universal plug that connects a tool to Claude. Because of that I run the whole CRM in plain language. I no longer type across ten screens, I ask Claude to do it. Create a new client, move an issue, log hours. That saves clicking every single day.

When a custom CRM is a bad idea

I will not sell you this as the holy grail. For plenty of businesses a custom CRM is a poor plan. If you run a common process with no odd quirks, an off-the-shelf package is cheaper and faster. If you have no internal person to keep it running, or no budget for maintenance, custom becomes a millstone. Custom only pays off once your process is genuinely your own and the retyping costs you enough time or errors. Otherwise a licence is simply the smarter call.

A client who started himself and got stuck

Recently someone came to us who had already built a CRM himself. Via Cursor, entirely local on his own laptop, with data from Exact, SharePoint and a few other tools. Every day he manually exported an Excel from those systems and imported it into his own CRM. Impressive for a beginner. It worked for him. Until he wanted to give others access and did not know how to move from local to live. Because he had built it himself, he could give us a perfect brief of what he wanted: a user structure, a secure environment, EU only. We laid that foundation. After that he could carry on building his own product himself.

How you keep building in your own environment

That further building happens in Empathree Studio. It holds only placeholder data, no real client information. So you can keep developing without hitting API restrictions or accidentally touching real data. You set the direction, the base stays safe. Humans in the loop, even when the client is the human in the loop.

Want to spar on whether it fits you?

A custom CRM is not a goal in itself. It is a fix for retyping and scattered tools that do not connect. Want to know whether it makes sense for you, or whether a standard package will do? We will tell you honestly if it does not fit, because that is how we work. Book an intro and we will map your process together. Let's go.