Guide · Custom CRM

How much does a custom CRM cost? Start with the hours.

Every software price is hours multiplied by a rate, and the hours are the part you can check. Here is what goes into a custom CRM, module by module, with three worked examples in hours and weeks.

Get a quote Read the guideUpdated 27 October 2026 · Luke Fenech
In short
  • A focused CRM with customer records only is about 70–130 build hours, roughly 3–5 weeks.
  • Every system starts with 30–50 hours of shared groundwork: logins, roles, admin, hosting and backups.
  • A CRM with reports, Gmail, WhatsApp and a spreadsheet import comes to about 140–285 hours, or 5–10 weeks.
  • Integrations, user numbers, a phone app and moving data from another system are what move the number most.
  • Phasing means you use the must-haves first, while the rest is still being built.

Why I talk about hours and weeks

Every software quote is hours multiplied by a rate. The rate is the easy number to compare and the least useful one. Two studios can quote the same screens with very different hours, and the gap is usually in what was left out or guessed. So on this page I stay with hours and weeks, because those are the part you can hold up against your own list of needs.

The ranges below are the ones my quote builder uses. They come from work I have delivered, and I plan on about 30 build hours a week. How I turn hours into a fixed quote is explained on the pricing page.

The groundwork every system needs

Before your CRM has a single customer screen, every system needs the same plumbing: logins, roles and permissions, an admin area, hosting and backups. I count that as 30 to 50 hours, once per system, however many modules sit on top of it.

That is also why building on one system is usually cheaper in hours than building two separate tools. Add invoicing to the CRM later and the groundwork is already there.

What the CRM itself adds

Customer records are the core module: 40 to 80 hours. That is one record per client with their history, notes, files and search. The choices you make then move the number:

  • Where enquiries come from: a website form adds 4–8 hours, WhatsApp 6–12, email 6–12 and social media 4–8. Phone calls and walk-ins are logged by hand and add nothing.
  • What the CRM does with them: a sales pipeline adds 10–20 hours, follow-up reminders 6–12, email templates 5–10 and duplicate clean-up 4–10.
  • How many records you have: under 500 is the base. 500 to 5,000 multiplies the module by 1.1, and over 5,000 by 1.25.
  • Reports and dashboards for the numbers you want live: 25–60 hours.
  • Quotes and invoicing: a separate module at 50–100 hours, because VAT-ready documents and numbering take real care.

Three worked examples

These come straight from the quote builder’s arithmetic, for a small group of users and no extras unless stated. They are build weeks at about 30 hours a week, not calendar weeks.

  • A focused CRM: customer records only. The module plus the groundwork is about 70–130 hours, roughly 3–5 weeks. One job done properly, easy to grow later.
  • A CRM that talks to your inbox: customer records and reports, Gmail and WhatsApp connected, and your spreadsheet imported. About 140–285 hours, roughly 5–10 weeks. The integrations (20–40 hours for Gmail or Outlook, 17–30 for WhatsApp) and the spreadsheet import (10–25) are what lift it.
  • CRM, invoicing, a client portal and reports, in two phases: the whole system is about 200–420 hours, or 7–14 weeks. Put the CRM and invoicing first and phase one is about 120–230 hours, 4–8 weeks, so you are using it while the portal and reports are still being built.

What pushes the number up or down

Waiting for your feedback, your data or a decision adds calendar time on your side of the table. The ranges are wide on purpose: until I have seen how your business really runs, I would rather give an honest range than a precise figure I would have to defend later. These are the things that move it:

  • More people using it: 4–10 users multiplies the whole estimate by 1.05, 11–30 by 1.1 and over 30 by 1.2. Separate roles and permissions add 12% on top.
  • A native phone app: an iPhone and Android app on the same backend adds 130–270 hours. A browser version that works well on a phone is already included.
  • Another language: each extra language adds about 8%.
  • Moving data: from spreadsheets is 10–25 hours, from another system 25–60.
  • Starting with the must-haves brings the first release down. Storex started as a client and invoice tracker synced with Wix and grew, phase by phase, into the platform the office and crew now run on.

When a custom CRM is not worth the hours

If you have a couple of people, a simple pipeline and no integrations, an off-the-shelf CRM will cost you fewer hours of anyone’s time, and I will tell you so. Even a modest custom build is dozens of hours.

Custom starts to pay off when the CRM also has to run invoicing, WhatsApp or bookings, or when per-user subscriptions keep growing with the team. The custom versus off-the-shelf comparison sets out both sides.

Get the number for your own business

The fastest route is the quote builder. It takes about five minutes and shows hours and weeks for your own mix of modules as you pick them. I then reply with a fixed quote in phases.

If you are in Malta and thinking about the Digitalise Your SME grant, read the Malta page first, because the order of events matters.

FAQ

Questions, answered.

Is this a quote?

No. These are the ranges the quote builder uses, so you can see what drives the effort. A fixed quote comes after I have seen your actual needs.

Why no euro figure on this page?

Because the hours are the honest, checkable part. I give a fixed price once the scope is clear, and the pricing page explains how I get there.

Is hosting included?

Setting up hosting, backups and logins is part of the groundwork hours. Running and improving the system after launch is separate, on a monthly support plan or pay as you go.

Can I start smaller and add modules later?

Yes, and I usually recommend it. The groundwork is built once, so adding invoicing or a portal later does not repeat it.

How long until I can use it?

In the phased example above, the first phase is about 4–8 build weeks. Your own feedback time comes on top.

Logo