Skip to main content
Based in Scotland · Building software for businesses throughout the UK

Custom CRM software built around the way your business actually works.

Most CRM products are built to suit everybody, which is why they rarely suit anybody exactly. A custom CRM starts from the opposite end: your enquiries, your quotes, your jobs, your follow-ups, in the order you actually do them. I'm Steve Bodman — I've been building business systems since 1997, and you deal with me directly from the first conversation.

  • Built around your process
  • You work directly with the developer
  • Test it while it's being built
  • Remote projects, UK-wide
Does this sound familiar?

Signs a generic CRM no longer fits.

Businesses rarely abandon a CRM because it stopped working. They abandon it because the workarounds got bigger than the system. If several of these are true, it's usually a fit problem rather than a training one.

The real information lives in a spreadsheet alongside the CRM, because the CRM can't hold it.

Half the fields are ignored, and the ones you need don't exist.

Your process has stages the CRM has never heard of, so everything sits in "In Progress".

The same customer is typed into the CRM, the accounts package and a job sheet.

What was actually agreed is halfway down an email chain, not on the record.

Everyone can see everything, because per-person permissions were never practical.

Reporting means exporting to a spreadsheet and fixing it by hand every month.

You're paying per user per month for features nobody has ever opened.

To be fair to the products: if an off-the-shelf CRM genuinely fits how you work, use it. It will almost always be the cheaper answer, and I'll tell you so. A custom CRM earns its place when the way you handle customers is part of what makes you good, and no product respects it.

What it covers

A custom CRM doesn't mean rebuilding Salesforce.

It means building the specific tools your business needs, and leaving out the rest. Most systems use some of what follows, and almost none use all of it — which is rather the point.

Customer records

One record per customer holding what you actually need to know about them, including the fields a general product has no place for.

Enquiries and leads

New enquiries captured from the website or entered by hand, routed to the right person, and visible as a list rather than an inbox.

Quotations

Quotes built from the customer record, sent out, tracked, and turned into work without anything being re-typed.

Jobs and work

What was agreed, who is doing it, where it has got to and what happened — attached to the customer rather than kept separately.

Reminders and follow-ups

The chase-ups that currently depend on somebody remembering, raised by the system on the day they matter.

Notes and history

A readable history of what was said and done, so anybody picking up the customer can see the story without asking a colleague.

Documents

Drawings, certificates, signed paperwork and photographs held against the record instead of in a shared folder nobody dares reorganise.

Email and communications

Where it genuinely helps, correspondence logged against the customer so the record shows what they were actually told.

Staff access and permissions

Who sees pricing, who can edit a record, who only sees their own work — decided by role rather than by trust.

Reporting

The handful of numbers you actually run the business on, current, on one screen — not assembled by hand at month end.

Recurring processes

Annual services, renewals, inspections and repeat orders raised on schedule rather than found when a customer asks.

Integrations

Connections to accounts software, email or payment providers where those systems allow it — checked early, not assumed.

Getting there from where you are

Moving off spreadsheets without stopping the business.

Nobody can afford to down tools for a month while a new system arrives. So the switch is designed to be gradual and reversible for as long as possible.

Step 01

Start with what hurts most

The first thing built is whatever is costing the most time today — usually customer records and enquiries — rather than the full system.

Step 02

Bring the existing data across

Spreadsheets and exports are imported and checked with you. Messy data gets tidied on the way in; it is the natural moment to do it.

Step 03

Use it alongside the old way

You get a login to a live development version and try it with real work, while the spreadsheet is still there as a safety net.

Step 04

Add the next piece

Quotes, jobs, reminders, documents and reporting are added in the order that makes the most difference to you, not in a fixed sequence.

Step 05

Keep improving it

A bespoke system is supposed to keep changing with the business. That is the whole advantage, and it doesn't stop at launch.

Proof

The CRM I know best is the one I use every day.

Customer systems are private by nature, so I can't show you somebody else's. What I can point at is Millennium Software's own — built here, used here, and still being extended.

Millennium's own system

The CRM running this business

Millennium Software does not run on an off-the-shelf package. It runs on a bespoke system covering customers, the working diary, jobs, invoicing, renewals and reporting as one connected thing.

  • Customer records, notes and job history
  • Working diary and scheduling
  • Support contract time tracking
  • Invoicing, renewals and reporting
Read the case study
Live platform

CoachFinder4U

A two-sided platform where the customer-facing side is the system: onboarding, verification, matching, subscriptions, credits, payments and automated notifications.

  • Onboarding and verification
  • Matching between coaches and clients
  • Subscriptions, credits and payments
  • Automated notifications
Read the case study
Questions

Frequently asked questions

What is custom CRM software?

It's a customer relationship management system built for one business rather than sold to thousands. Instead of adapting your process to fit a product, the system is shaped around the way you already win and look after customers. In practice that usually means fewer screens, fewer unused fields and fewer workarounds than a general-purpose CRM.

Does a custom CRM mean rebuilding something like Salesforce?

No — and it shouldn't. A custom CRM isn't an attempt to recreate every feature of a large product. It's the specific set of tools your business needs, built well, without the hundreds of features you'd never open. That's usually what makes it quicker to learn and cheaper to own.

Can you move our existing customer data across?

Usually yes. Spreadsheets, exports from an existing CRM and accounts data can normally be imported. How straightforward it is depends on how consistent the data is, so it's worth looking at the actual files early rather than assuming either way.

Can different staff see different things?

Yes. Permissions are part of the design rather than an afterthought: who can see financial information, who can edit customer records, who only sees their own work. It's one of the more common reasons businesses outgrow a shared spreadsheet.

Will it work on a phone or tablet?

Yes. Everything is cloud software and works in a browser on a phone, tablet or desktop, so people working away from the office are using the same system rather than sending information back to be re-typed.

Do we have to replace everything at once?

No. Most projects are built in stages, starting with whatever is causing the most friction. You get a login to a live development version and try each part as it's finished, so the system arrives gradually rather than in one disruptive switch.

Can it connect to the other software we use?

Often, depending on what the other system allows. Accounts packages, email and payment providers commonly offer a way in. Whether a specific integration is practical is one of the first things worth checking rather than something to discover late.

How much does a custom CRM cost?

There's no standard figure, because there's no standard system. Cost is driven by how much it has to do, how many people use it, how much existing data comes across and what it has to connect to. After a conversation about what you actually need, I can give you a clear written proposal based on the real scope.

No obligation, no sales pitch

Tell me what you're currently managing with spreadsheets, email or separate systems.

You don't need a specification or a budget to get in touch. Describe how customers move through your business at the moment — where the details get typed in, where they get lost — and I'll tell you honestly whether a custom CRM is worth building.

You'll be talking to Steve Bodman, who will do the work — not a sales team, an account manager or an agency in the middle. If what you need is something off-the-shelf, I'll tell you that too.