What is a custom CRM, and when is it worth building one?

When people ask me to build "a backend", they usually mean one of a few things. This guide gives each one a plain name, then helps you decide whether to buy one or build one.

What these systems are called

• CRM (customer relationship management): leads, customers, conversations, deals and follow-ups in one place.
• Client portal: a private area where your customers see their project, documents, invoices or results.
• Admin dashboard: the screen your team uses to run the day: orders, bookings, enquiries, numbers.
• Booking engine: availability, rules and payments for rooms, tables, appointments or tours.
• ERP (enterprise resource planning): stock, purchasing, production and accounting together. Usually a bigger, longer project.

The umbrella term is a custom web app, or a business system: software that runs in the browser, built around how your business works.

Signs you have outgrown spreadsheets

• Leads arrive by email, WhatsApp, Instagram and phone, and nobody can see them all in one place.
• You find out a quote was never followed up when the customer has already gone elsewhere.
• The same details are typed into three different tools.
• Only one person knows the real status of each job, and they are on holiday.

Buy or build?

Start with an off-the-shelf CRM such as HubSpot, Pipedrive or Zoho if your sales process is close to everyone else's: a lead comes in, you call, you quote, you win or lose. These tools are mature, well supported and quick to set up.

Building your own starts to pay when:

• Your process is your advantage. A tour operator who builds custom itineraries, or a clinic whose patients download lab reports, does not fit a generic pipeline.
• Fees grow with your team. Per-user pricing is cheap for three people and expensive for thirty.
• It has to work with everything else. When the CRM, the booking calendar, quotes, payments and a customer portal must share one source of truth, joining five tools with automations becomes fragile and costly.
• You need to own the data. Some businesses need full control over where customer data lives and who can see it.

An example: the system iVishwa runs on

I built our own system because no off-the-shelf tool joined the parts the way I wanted. This is how it works:

1. A visitor designs a website in our Design Studio and asks for a quote. The design, the details and the website visit it came from land in the admin, and I get an email and a WhatsApp alert.
2. I reply and send a quote. The client accepts it with a typed signature in their private portal and pays by card or bank transfer.
3. During the project, the client approves designs, shares files and chats with me in the portal. Their messages reach my WhatsApp, and my replies go back to their portal.
4. Every approval, payment and sign-in is recorded in an activity log.

None of that is unusual on its own. The value is that it is one system, so nothing falls between tools.

How a custom CRM project runs

1. Map the process. We write down how work really flows today, including the messy parts.
2. Build the core first. The few screens your team will use every day, done properly, rather than every idea at once.
3. Move the data. Import existing customers and history, cleaned.
4. Launch, train, adjust. Real use always reveals things a plan misses. The second month is where a system becomes yours.

Before you decide

• Who will use it, and what is the one screen each person opens first?
• Which tools must it connect to, and which can it replace?
• Who owns the code and the data? With a custom system, it should be you.
• How is it secured? Look for passkeys or two-step sign-in, roles with the least access each person needs, and backups.
• What will hosting and maintenance cost each year?

Written by Vish Jay

I design and build websites, online stores and business systems for clients in the US, UK, Europe, Australia and Canada, from Colombo, Sri Lanka. When you work with iVishwa, you talk to me directly, from the first call to launch and after.