Bespoke CRM development UK teams can grow into without paying for every new seat

What is bespoke CRM development, and which UK businesses need it?

Bespoke CRM development means building customer relationship software around your own records, stages and rules instead of adapting your business to a generic product. The CRM is yours: its database, its screens and its logic reflect how your team already works.

Most UK businesses do not need one. A florist, a two-person consultancy or a company with a textbook B2B sales funnel will usually be happier on an off-the-shelf tool. The businesses that benefit are those whose core object is not a “deal”: a heating engineer’s job with gas safety paperwork, a recruitment consultant’s candidate moving through interviews and compliance checks, a letting agent’s tenancy with renewals and certificate expiry dates.

Signs you are a candidate for bespoke CRM development in the UK:

• Your team keeps a spreadsheet alongside the CRM because the CRM cannot hold what matters
• You pay for a higher CRM tier just to get one or two features
• Headcount is growing and every new starter adds another monthly licence
• Information about one customer lives in four places: CRM, inbox, WhatsApp and Xero
• A subject access request takes someone an afternoon of searching
• You have rebuilt your workflow twice to fit software updates you did not ask for

If three or more ring true, the rest of this guide will help you judge whether a bespoke build pays back. If only one does, a better-configured SaaS CRM or a single automation may be enough.

Bespoke CRM vs Salesforce or HubSpot: when does building win?

Building wins when your workflow is specific, your team is growing, and you would otherwise pay for premium tiers and add-ons to approximate what you need. Buying wins when your process is standard, you need to start next week, and you value a vendor’s roadmap over control.

Salesforce and HubSpot are excellent products with huge ecosystems. The friction for small UK firms is usually not quality but fit and cost structure: per-user pricing, features gated behind higher tiers, and customisation that requires specialist admins. None of that is a flaw; it is how those products are designed to serve large markets.

A bespoke CRM reverses the trade. You pay more up front, wait weeks rather than days, and own the maintenance. In return, there is no seat fee, nothing is gated, and the software changes only when you decide it should.

How do you compare three years of CRM licences with a bespoke build?

Add up what the SaaS route costs over 36 months, including growth, and set it against the bespoke build plus 36 months of hosting and support. Whichever total is lower, with the fit and risk factored in, is your answer.

For the SaaS side, take the tier you would genuinely need (not the entry tier on the pricing page), multiply by the number of users you expect in each year, and add paid add-ons: extra contacts, marketing tools, integrations, telephony, e-signature, and any admin or consultant time to configure it. Use the vendor’s current published pricing; we do not quote other companies’ prices because they change.

For the bespoke side, take the build quote (ours start at US$900), add your cloud hosting (typically modest for a CRM serving a small team, and billed by your provider), and add ongoing care. We include two months of free fixes, then care starts at US$120/mo if you want it. Budget for a round of improvements in year two, because teams always think of new features once they use the thing daily.

The break-even point tends to arrive sooner for teams that are growing, that need higher tiers for one feature, or that pay for several add-ons. It may never arrive for a stable team of three on an entry plan. Run the numbers with honest assumptions before anyone writes code.

How much does bespoke CRM development cost in the UK?

With BtechWaleTech, bespoke CRM development starts at US$900 for a first release covering contacts, companies, your pipeline, tasks, notes, roles and one integration. UK developers and software houses quote across a very wide range, and the difference mostly reflects scope, team size and where the work is done.

What pushes a CRM quote up is easy to list. Each extra record type (jobs, properties, candidates, contracts, assets) adds screens, rules and tests. Complex permissions, such as branch managers seeing only their branch or consultants hiding candidates from each other, add design time. Integrations each carry their own effort. Messy legacy data can take longer to clean than the features take to build.

What keeps it down: starting with the smallest version your team can use daily, reusing proven components for login, roles and audit logs, and phasing extras such as mobile apps or AI features into later releases. We often recommend a first release that replaces the spreadsheet everyone hates, then a second that adds automation once real usage shows where time goes.

Bespoke CRM for trades and field service businesses

For trades, a bespoke CRM is really a job management system: enquiry, survey, quote, job, certificate, invoice, follow-up. Generic CRMs stop at the quote; a trades CRM carries on until the paperwork is filed and the next service reminder is scheduled.

Typical records for an electrical, heating or roofing firm include customers, properties (one customer may own several), jobs, quotes with line items, engineer schedules, photos, and certificates or test results attached to the property. Engineers update jobs on a phone, customers get automated reminders, and the office sees what is booked, done and invoiced.

The payoff comes from the links. When a job is marked complete, the CRM can raise the Xero invoice, send the customer a WhatsApp message with the certificate, and schedule the next annual service reminder, without anyone retyping the address.

• Property-first records so repeat work at an address shows full history
• Quote builder with your price book and VAT handling approved by your accountant
• Engineer diary with drag-and-drop scheduling and a phone view
• Photo and document upload against each job
• Service and inspection reminders by date

If you are a tradesperson who also needs a better website, see our pages for electricians and builders; enquiries from those sites can land straight in the CRM.

Bespoke CRM for recruitment agencies

A recruitment CRM has two customer bases at once, candidates and clients, joined by vacancies and placements. Many agencies outgrow generic CRMs quickly because those tools assume one kind of contact moving through one pipeline.

The core objects are candidates (with CVs, skills, availability and consent status), client companies and hiring managers, vacancies, applications moving through stages, interviews, offers and placements. Placement records can trigger invoices in Xero, with fee or margin calculated by rules you define.

Recruitment data is personal data in bulk, which raises the UK GDPR stakes. The CRM should record why each candidate is held, flag records due for review under your retention policy, and let you export or erase a candidate’s data quickly when they ask. Document expiry dates (for example on identity or qualification documents your process requires) can generate reminders so nothing lapses unnoticed. What checks your agency must carry out is for your compliance adviser to confirm; the CRM just keeps the evidence organised.

Useful extras include CV parsing into structured fields, boolean skill search, and shortlists shared with clients through a secure link rather than email attachments.

Bespoke CRM for letting agents and property managers

Property businesses run on dates: tenancy start and end, renewal windows, deposit protection deadlines, safety certificate expiry, rent reviews. A bespoke CRM for letting agents puts those dates at the centre, so nothing expires without a reminder several weeks earlier.

The main records are landlords, properties, units, tenants, tenancies, maintenance requests and contractors. Maintenance jobs can be raised by tenants through a simple form or WhatsApp, assigned to a contractor, and tracked to completion with photos. Landlord statements pull from rent received and costs incurred.

Estate agency adds applicants, viewings, offers and sales progression milestones. Many agents already use portal feeds and property software for listings, so the bespoke CRM often focuses on the parts those tools handle badly, such as landlord relationships or maintenance, and connects to the rest.

If your listings website needs work too, our letting agent website page explains how enquiries and valuation requests can feed straight into the CRM.

Connecting a bespoke CRM to Xero, email and WhatsApp

The three integrations UK firms ask for most are accounting, email and messaging, because those are where customer information leaks out of the CRM. Each is built against the provider’s official API and authorised by you, so access can be revoked at any time.

Xero: contacts sync both ways, invoices are raised from won jobs or placements with the right account codes and tracking categories, and payment status flows back so staff see overdue balances on the customer record. Your accountant approves the account and VAT mapping before we connect anything.

Email: with Microsoft 365 or Google Workspace, emails to and from a contact can be logged on their record automatically or with one click, and templates send from the user’s own mailbox. Marketing emails are handled separately with consent checks, because PECR rules on electronic marketing, enforced by the ICO, apply to emails and texts.

WhatsApp: through the WhatsApp Business Platform, messages from customers appear on their CRM record, staff reply from the CRM, and approved templates send reminders or updates. That keeps conversations off personal phones, which also helps when someone leaves.

Other common links include website enquiry forms, calendar booking, telephony call logs and e-signature. For online appointments specifically, see our sibling page on custom booking system development.

UK GDPR features every bespoke CRM should include

A bespoke CRM should let you find, export, correct and erase everything held about a person, and record that you did. Those features turn a stressful request into a ten-minute task.

The ICO’s guidance says you must respond to a subject access request without undue delay and within one month, extendable by up to two further months for complex or numerous requests, and that in most cases you cannot charge a fee. For erasure, the ICO says to respond within one month, notes the right is not absolute, and says erasure must reach backup systems as well as live ones (data can be put “beyond use” until backups are overwritten).

We build these into the admin: a person search across every table, including notes, attachments and message logs; a one-click export in a readable format; an erase or anonymise action that respects records you must keep; and an audit log of each request. Retention rules can flag records untouched for a period you define. The ICO’s subject access guide is worth reading before we design these screens.

To be clear about roles: UK GDPR compliance is your organisation’s responsibility, confirmed by your own adviser. The CRM supports your obligations; it does not make you compliant on its own, and we do not give legal advice.

Moving from spreadsheets into a bespoke CRM

Most bespoke CRM projects start by retiring a spreadsheet, or several. The move goes smoothly when the data is cleaned and mapped before import, and badly when it is dumped in as-is.

We begin by collecting every file the team relies on, including the ones kept privately “just in case”. Then we map columns to fields, agree what counts as a duplicate (same email? same phone? same company and surname?), standardise formats for phone numbers, postcodes and dates, and decide what to do with free-text columns that hold three different kinds of information.

Test imports go into a staging copy of the CRM, where your team checks a sample of records they know well. Only when they sign off do we import into the live system. Old files are then archived read-only, so people stop updating them by habit.

• Gather every spreadsheet, export and personal list in one place
• Agree field mapping and duplicate rules in writing
• Clean phone, postcode, date and email formats
• Import into staging and have staff check familiar records
• Import live, archive old files read-only, and switch everyone the same day

What technology is a bespoke CRM built with?

We build CRMs as web applications that run in any browser and on phones, using mainstream open technologies so any competent developer can maintain them later. A typical stack is a TypeScript or PHP back end, a PostgreSQL database, and a React or Vue front end.

Hosting goes in your own cloud account, on AWS, Google Cloud, Azure or a UK host you prefer. UK businesses often choose a London or EU region for their data; that choice is yours, informed by your adviser. We set up automated backups, encrypted connections, role-based access, and two-factor sign-in for staff.

For field staff who need offline access or phone features such as the camera, we either make the CRM an installable web app or build a companion app in Flutter or React Native. Our React Native and Flutter pages explain the difference.

We avoid exotic frameworks and proprietary low-code platforms for core systems, because they tie you to one vendor or one developer. Boring, documented technology is the kind that survives staff changes.

How long does bespoke CRM development take?

A first release of a bespoke CRM usually takes 6–12 weeks. A focused system for one team with one integration sits at the lower end; multiple departments, complex permissions and several integrations push towards twelve weeks.

The first two weeks go on discovery: sitting (on video) with the people who will use it, mapping their current process, listing record types and fields, and agreeing what the first release includes. Design and build follow in short cycles, each ending with something your team can click through on a staging site.

Data migration and training run in the last fortnight. We prefer a single switchover date for everyone, preceded by a short parallel period where the old spreadsheet stays read-only. After launch come the requests nobody predicted; those go into a second release rather than delaying the first.

Who owns a bespoke CRM: the code, the data and the accounts?

You own all three. The source code lives in a repository in your account (GitHub, GitLab or Bitbucket), the database runs in your cloud account, and every third-party integration is authorised under your own logins.

This matters more for a CRM than almost any other system, because it holds your customer relationships. If a supplier controls the hosting or the code, they effectively control your business records. We add ourselves as collaborators with only the access needed, and you can remove us whenever you like.

At handover you receive documentation: how the system is structured, how to deploy it, how backups work, what each integration does and which credentials it uses. Another developer should be able to take over from that document alone. Our terms cover general conditions; anything project-specific goes in your written quote.

Bespoke CRM risks and red flags to check before you commission one

The main risks with bespoke CRM development are scope creep, poor adoption, supplier lock-in and neglected security. Each can be managed, and a good proposal tells you how.

Scope creep: a CRM can absorb every idea in the building. Protect the first release by writing down what is out of scope. Adoption: if the team was not consulted, they will keep their spreadsheets. Involve the heaviest users from week one. Lock-in: insist on code in your repository and hosting in your account from the first commit. Security: ask how passwords, backups, access roles and updates are handled.

Red flags in a proposal: no discovery phase, a fixed feature list written before anyone spoke to your staff, hosting on the supplier’s own servers with no exit plan, proprietary platforms you cannot move away from, and no mention of data protection features.

Commissioning a bespoke CRM from a team in India: how it works from the UK

We work from India, which in practice means your afternoon is our evening and your morning has our progress notes waiting. India is four and a half hours ahead of London in summer and five and a half in winter, giving a comfortable overlap from UK late morning to early evening for calls.

Discovery sessions run on Teams or Zoom with screen sharing, recorded if you like so people who missed them can catch up. Between calls, questions go through WhatsApp, answered seven days a week, and decisions are confirmed in writing. Staging sites let your team test features at their own pace and leave comments.

We have no UK office and do not make site visits; if your project truly needs someone in the room, a local developer is the better fit. Quotes are itemised in USD, payable from GBP by Wise, bank wire or PayPal, with milestones set out before work begins. Invoices come from India, and your accountant can advise on recording them.

Worked example: a hypothetical recruitment agency in Leeds

Imagine a Leeds recruitment agency with nine consultants placing engineers and technicians. They use a SaaS CRM on a mid tier, plus spreadsheets for compliance documents and a shared inbox for timesheets. They plan to hire six more consultants within two years. This is a hypothetical scenario to show the thinking, not a client.

The three-year sum: fifteen users by year three on the tier they need, plus paid add-ons for e-signature and texting, against a bespoke build, hosting and care. The owner runs it with current published prices and sees the bespoke route pay back within the period, largely because of growth.

Release one covers candidates, clients, vacancies, applications, placements, document expiry reminders and a Xero invoice on each placement, with a subject access export and erase tool. Release two adds CV parsing and WhatsApp messaging with candidates. Spreadsheets are migrated with consultants checking their own candidates.

The first release lands at around ten weeks and sits above our starting price of US$900, because of two integrations and the data clean-up.

Bespoke CRM development checklist for UK buyers

Before you ask anyone to quote, work through this list. It sharpens the brief, shortens discovery and makes quotes easier to compare.

• Name your core record: deal, job, candidate, tenancy, member or something else
• List every spreadsheet and tool the CRM should replace
• Count users now and your honest estimate in three years
• Price three years of the SaaS tier you would really need, with add-ons
• List must-have integrations: Xero, email, WhatsApp, forms, calendar
• Decide who can see what: roles, branches, teams
• Agree retention periods and who handles subject access requests
• Choose where hosting lives and confirm it is in your name
• Insist on source code in your repository from day one
• Define release one and write down what is out of scope

Send us that list, even half-filled, through the contact page or WhatsApp, and we will come back with questions and an itemised quote.