Custom CRM vs off-the-shelf for franchises and multi-site businesses

For most franchises and multi-site businesses, an off-the-shelf CRM such as HubSpot, Salesforce, Zoho or Pipedrive is the right place to start. A custom CRM starts to make sense when you have dozens of users across many sites, a way of working the standard tools fight against, or per-user licence bills that have grown larger than the cost of building your own. In our experience the tipping point is usually somewhere around 40–80 users, or earlier if you are paying a consultant every month to bend a generic CRM into shape. Below we set out the real trade-offs, with worked three-year numbers.

We build custom CRMs and integrations for UK businesses, and we also tell a fair number of people not to. Both answers are in here.

Why multi-site businesses outgrow standard CRMs

A single-site business uses a CRM for a fairly standard job: track leads, log calls, send quotes, follow up. Off-the-shelf tools are very good at that. Franchises and multi-site operators add a layer the standard tools were not really designed around:

• Two levels of ownership. Head office needs to see everything; a franchisee in Leeds should see only Leeds, and should not be able to export the whole customer list on the way out of the network.
• Lead routing by territory. An enquiry from a postcode in Salford needs to land with the Manchester franchisee within minutes, not sit in a shared inbox.
• Royalties and reporting. Franchisors often calculate fees on revenue recorded per site, so the CRM is close to the finance process.
• Operational data, not just sales. Jobs, bookings, technician visits, stock, compliance checks. Many multi-site businesses really need a CRM and a light operations system in one.
• Very different users. A sales director, a part-time receptionist and a van-based engineer all need different screens. Training cost multiplies with every site.

You can solve most of these in a top-tier off-the-shelf CRM. The question is what it costs you in licences, configuration and consultant time, and whether your team will actually use the result.

Off-the-shelf CRM: what you get and where it pinches

Strengths

• Live in weeks, not months. You can trial most of them free before committing.
• Mature features: email sync, pipelines, mobile apps, reporting, marketing automation.
• Large ecosystems of integrations with accounting, telephony and email marketing tools.
• Someone else handles hosting, security patches and uptime.
• Easy to hire people who already know the tool.

Where it pinches

• Per-user pricing. At the time of writing, mainstream CRM plans in the UK typically run from roughly £15 to £100+ per user per month, with enterprise tiers well above that. Features franchises need, like advanced permissions, custom objects and territory management, often sit in the higher tiers. Check current pricing with each vendor, as plans and names change often.
• Configuration creep. Bending a generic CRM to a franchise model often needs a certified partner, and many businesses end up on an ongoing consultancy retainer.
• Workarounds. When the tool does not match how sites work, people keep spreadsheets on the side, and your data quietly splits in two.
• Price rises and plan changes are outside your control, and moving away later means a data migration project.
• Data location and processors. Usually fine under UK GDPR, but you need to check where data is held and what the vendor’s terms say.

Custom CRM: what you get and what it costs you

Strengths

• Built around your process: territories, franchisee permissions, job flows and royalty reports exactly as you run them.
• No per-user fees. Adding the 30th site costs hosting, not another licence bill.
• Only the screens each role needs. A field engineer gets three buttons on a phone, not a sales dashboard.
• You own the code and the data, and can host in the UK if that matters to you or your clients.
• Integrates directly with the systems you already rely on, through APIs rather than third-party connectors.

The honest downsides

• Upfront cost and time. A focused first version usually takes a few months, not weeks.
• You are responsible for it. Hosting, security updates, backups and bug fixes need a budget and a supplier.
• Key-person risk. If one developer understands the system, you have a problem. Insist on documentation, readable code and repository access.
• Feature envy. You will not get every bell and whistle of a giant SaaS product. You should not need them, but expect someone to ask.

Three-year cost: a worked example

Here is an illustrative franchise: 12 sites, 6 CRM users per site plus a head office team of 8, so 80 users. The numbers for the off-the-shelf side are assumptions for illustration, not a quote from any vendor. The custom side uses our real hourly rate.

Our hourly maths: Custom Web Development is £60/h, so 100 hours is £6,000 less the 25 % volume discount, £4,500 + VAT. Four blocks build the first version; one block a year covers improvements and support. Hosting at £150–£300 a month adds £5,400–£10,800 over three years.

Now run the same exercise for a smaller business: 3 sites, 10 users on a £25 plan. That is £3,000 a year in licences, or £9,000 over three years plus modest set-up. A custom build cannot compete with that, and we would tell you so. Custom wins on scale and fit, not on principle.

Two caveats keep this example honest. Large CRM vendors negotiate, so a real 80-seat deal may come in below list price. And custom projects can overrun if the scope is vague, which is why we build in stages and you can stop after any of them.

The hybrid option most businesses should consider first

There is a middle path that often gives you 80 % of the benefit for a fraction of the cost: keep an off-the-shelf CRM for head office and sales, and build custom pieces around it.

• A franchisee portal showing each site only its own leads, jobs and reports, pulling data from the main CRM through its API.
• Lead routing from your website by postcode to the right site, with an SLA timer and escalation.
• Integrations with your booking system, accounting package or ERP so nobody re-keys data.
• Royalty and performance reports built from CRM data plus your finance system.

This keeps the licence count down (franchisee staff may not need full CRM seats) while giving each role a tool that fits. A typical hybrid project might be 80–200 hours, so roughly £3,840–£9,000 + VAT depending on volume discount: 80 hours at £60 with the 20 % discount for 50+ hours is £3,840, and two 100-hour blocks are £9,000. Our API development and integration service covers exactly this kind of work, and on the charity side our ERP integration work for LAV followed the same principle of connecting systems rather than replacing them.

How to decide: a checklist

Tick the ones that apply. Four or more ticks and a custom or hybrid build is worth a proper conversation; two or fewer and you should stay off the shelf.

• You have more than 40 users, or expect to within two years.
• You run franchise or territory structures where sites must not see each other’s data.
• Your team keeps spreadsheets alongside the CRM because it does not fit how they work.
• You pay a consultant every month to configure or fix the current CRM.
• You need the CRM tightly connected to bookings, jobs, stock or finance.
• Field staff need a simple mobile screen, not the full CRM.
• You want customer data hosted in the UK under your control.
• You have a clear owner internally who can make decisions about the system.

UK GDPR in a franchise CRM

Data protection gets more complicated with franchises, because there are at least two businesses involved. Depending on how your network works, the franchisor and franchisees may be separate controllers, joint controllers, or controller and processor, and your agreements should say which. The ICO’s guidance on controllers and processors is the place to start, and your solicitor should confirm the set-up.

Practically, any CRM in a franchise network should support:

• Role-based access so each site sees only its own customers, with head office access logged.
• Audit trails recording who viewed, changed or exported records.
• Retention rules that delete or anonymise old records on a schedule rather than keeping everything forever.
• Subject access and erasure requests answered within the one-month deadline, which is far easier when data lives in one system.
• A clean exit for departing franchisees, with clear rules about what data stays with the network.
• Data processing agreements with every vendor that touches personal data, including your CRM provider or hosting company.

Off-the-shelf tools offer most of these on higher plans. In a custom build we design them in from day one, which is easier than retrofitting them.

How we build a custom CRM

1. Discovery (typically 10–20 hours). We sit with head office and two or three sites, map how leads and jobs actually move, and write down what the first version must do. Often this alone shows that a hybrid will do.
2. Clickable prototype. Our UX team prototypes the key screens for each role so people can try them before we write code.
3. First working version. Usually Laravel or Node on the back end, React or Vue on the front end, a relational database, single sign-on if you use Microsoft 365 or Google Workspace, and an API from the start.
4. Pilot with two sites before rolling out to the network. Real users find the problems demos never do.
5. Migration and rollout, including importing and cleaning data from the old system and spreadsheets.
6. Support and improvements from a block of hours that never expires.

You own the code and the data, with access to the repository and documentation throughout. If you ever want another developer to take it over, they can. Our experience building custom platforms, such as UNICEF’s custom CMS and donation platform, has taught us that the boring parts (permissions, audit logs, backups) are what make a system trustworthy.

Most of our CRM clients work with us remotely from across the UK. Our office is in St Albans, so if you are in London or the Home Counties we are happy to run discovery sessions in person.

Our recommendation

• Under about 20 users, simple process: pick a mainstream CRM, configure it well, and spend your budget on training.
• 20–60 users, or a franchise structure: start with an off-the-shelf CRM and add custom portals and integrations where it pinches.
• 60+ users, unusual processes, or heavy consultant spend: price a custom CRM properly with a paid discovery phase, then compare three-year totals side by side.

If you want a second opinion on which route fits your network, get in touch. You can read more about our custom CRM development service, or book hours for a discovery phase. If a mobile app for field staff is part of the plan, see how much an app costs in the UK.

Photo: Christina @ wocintechchat.com via Unsplash