Custom CRM: when it beats a standard one

A custom CRM pays off when the way you win, follow up with and look after your customers is part of what sets you apart and does not fit a tool made for a generic sector, or when you already pay for a licence and still keep the real follow-up in spreadsheets, in email or in one person’s head. In every other case, a well-configured standard CRM is usually cheaper.

And when it does pay off, it is almost never worth building whole: you start with the part of the process that hurts most and connect it to what you already use, instead of replacing everything at once.

A CRM is the system where a company keeps and follows its relationship with customers: contacts, opportunities, quotes sent, pending follow-ups, incidents. It can be an off-the-shelf product that is configured, or a system built for that company’s specific process.

“Custom” is used for three different things, and it helps to know which one a quote is talking about: an off-the-shelf CRM configured your way, an off-the-shelf CRM with modules or automations of your own added, or a customer management system built from scratch. Each has a different cost, risk and owner.

It is not the same as an ERP. The ERP runs the operation (orders, stock, invoicing); the CRM, the relationship with the customer before, during and after the sale. Many small businesses need the two connected, and very few need both custom-built.

This comparison describes kinds of solution, not specific products or suppliers. No row carries figures because they depend on each case.

When it fits

A standard CRM, when your sales cycle looks like your sector’s: contact, opportunity, quote, close. A custom one, when the follow-up has steps, rules or data that no catalogue product allows for.

What you pay for

The standard one usually means a licence per user and its configuration. The custom one, building it and maintaining it. Neither has a price that can be given without scoping the case.

How the process fits

With the standard one, your team adapts to the tool and whatever does not fit stays outside. With the custom one, the tool adapts to the process, but the process has to be defined well before building.

Who maintains it

The standard one is updated by its vendor. The custom one needs someone to maintain it, which is why it is delivered with its code and its documentation.

What happens to your customer data

With the standard one it depends on the licence and on whether you can export it in full. With the custom one, the data and the code are yours.

This is the half that gives the other its value. It does not pay off when what you need is standard: there, the cheap option is to buy it, and a studio that says building always pays off is not informing you, it is selling.

• Your sales cycle is the usual one in your sector and an off-the-shelf CRM covers it with configuration.
• The problem is in a small part: an automation between the CRM you already have and your invoicing or your email solves more with less.
• Nobody in the company is going to fill it in. A custom CRM without the discipline to use it is an empty database with a development cost.
• It is not yet known which part of the follow-up fails. Before building comes the preliminary analysis.

These are the signs that, when they recur, justify looking at a build of your own. None of them justifies it on its own.

• Quotes are produced outside the CRM, in a spreadsheet or a document, and then copied in by hand.
• The real follow-up lives in email or WhatsApp and the CRM is updated afterwards, if someone remembers.
• There is customer data that matters to your business and has no place in the catalogue record.
• The CRM does not talk to invoicing, the warehouse or the booking system, and someone reconciles by hand.
• The rules for assignment, priority or alerts are yours and not the ones the product ships with.

If, after comparing, building pays off, it is done in parts. You start with the one that takes the most time or loses the most opportunities, validate it with real data and move on to the next.

The method is that of any custom software project: understand the real process, define in writing what is in and what is out, design before building, deliver in phases and leave what has been done measured.

• First it is compared with an off-the-shelf CRM and with automating the one you already have.
• The first part is the follow-up that gets lost most: quotes without a reply, contacts without an owner, incidents never closed.
• It is connected to what already works (email, invoicing, bookings) instead of replacing it.
• Each part is validated with real data before it is opened to the whole team.

These decisions belong to the business, not to the system. Having them thought through shortens the preliminary analysis.

• What steps your sales and service cycle really has, as opposed to the org chart.
• Which customer data is essential and which is asked for out of habit.
• Which system is the source of truth for each piece of data when the customer also lives in invoicing.
• Which programs it has to coexist with (email, calendar, invoicing) and whether they allow connections.
• Who is responsible for keeping the information up to date, and what happens if it is not.
• Who will maintain it once it is running.

Almost all of them are avoided if they are named at the start.

• Building a record for everything: a CRM that allows for everything gets filled in by nobody.
• A scope with no written limits: without a list of what is in and what is out, the system never gets finished.
• Migrating contacts without cleaning them: duplicates and stale data move to the new system with the same weight as the good ones.
• Personal data without deciding who accesses what: a CRM holds information about people, and that has rules.
• A system only one person understands: avoided with documentation and with the code handed over.

A working system, with its repository and its documentation. The code we develop specifically for your project is yours once the corresponding amounts have been paid, and if we use third-party libraries or services, their licences are identified before they are incorporated.

To decide whether it pays off in your case, the first step is a preliminary analysis, with its scope, its deliverable and its fee agreed in writing before starting.

Custom software

When it pays off and what we deliver

Custom ERP: when it beats a standard one

The same comparison for the system that runs the operation

Consulting and discovery

The preliminary analysis, before building

What is a custom CRM?

It is a customer management system built for a company’s specific process (contacts, opportunities, quotes, follow-ups, incidents), instead of adapting the process to an off-the-shelf CRM. The name is also used for a standard CRM extended with modules or automations of your own.

When does a custom CRM pay off against a standard one?

When the way you win and follow up with customers is part of what sets you apart and does not fit a generic CRM, or when you already pay for a licence and still keep the real follow-up in spreadsheets or email. If your sales cycle is the usual one in your sector, an off-the-shelf one is cheaper.

How much does a custom CRM cost?

It depends on the scope, on the data that already exists, on the integrations (email, invoicing, bookings) and on the number of users. A serious figure cannot be given without scoping the problem first, which is why the fee is agreed in writing before starting. A well-configured standard CRM usually comes out cheaper than one of your own.

Are a custom CRM and a custom ERP the same thing?

No. The ERP runs the operation (orders, stock, invoicing) and the CRM the relationship with the customer before, during and after the sale. Many small businesses need the two connected and very few need both custom-built; the usual thing is to build only the part that does not fit the catalogue.

Can it connect to email, invoicing or bookings?

It is the usual case and it shapes the whole project, which is why the integration is studied before designing. We review what each tool allows, which system is the source of truth for each piece of data and what happens if one does not respond. If something cannot be connected, we say so at the start, not halfway through.

Who owns the data and the code of a custom CRM?

Your customers’ data is yours from day one. The code developed specifically for your project is yours, with its repository and its documentation, once the corresponding amounts have been paid; if third-party libraries or services are used, their licences are identified before they are incorporated.

Custom ERP: when it beats a standard one

When a custom ERP pays off against a standard one, how it is planned module by module, what to decide before starting and the risks it carries.

How much custom software costs and what drives it

What the price of custom software depends on, how to estimate it rigorously and how to compare two proposals without being sold an invented number.