What bespoke business software is
Bespoke business software is a system built for one company's way of working: its customers, its jobs, its rules. Evolve designs and builds these for UK businesses when a package would force the process to change. Below is one section for each kind we build most often, with what each replaces, what it connects to, and when a package is fine.
Bespoke CRM
A CRM is only bespoke if it matches how your sales and account work actually flows. Most packaged CRMs assume a pipeline that looks like a software company's. If yours does not, you end up with modules nobody opens and a spreadsheet on the side that is the real CRM.
What it replaces and what it does
- A packaged CRM with unused modules and a workaround spreadsheet
- Pipeline stages you define, with the fields your business actually tracks
- Quotes, follow-ups and renewals in one place, with who did what and when
- Connected to the accounts package and to email, so nothing is typed twice
Buy HubSpot or Pipedrive instead
If your sales process is standard, your team is small, and the only integration you need is email, a package will do the job for less. We will say so on the first call and help you set it up.
Customer and client portals
A portal is the part of your business your customers see without phoning. Order status, documents, invoices, approvals and bookings, behind a login that works on a phone. Behind it sits the system you already run; the portal is a window onto it.
What it replaces and what it does
- The phone calls and email threads that ask "where is my order"
- Documents sent as attachments, now downloaded from one place
- Approvals and signatures with a record of who approved what
- Magic-link or single sign-on login, so nobody has to remember a password
- Connected to the job system, the accounts package or the CRM behind it
Use the portal your system already has
Many accounts packages and practice-management tools include a basic client area. If it shows what your customers ask for and you can live with its look, use it. A bespoke portal earns its place when it has to pull from several systems or do something the built-in one cannot.
Booking and scheduling
Bookings fail in the rules, not the calendar. Which bay, which technician, which room, how long, what deposit, what happens when someone cancels at four in the afternoon. A packaged booking tool has one answer to each of those. Your business has its own.
What it replaces and what it does
- The paper diary, or the shared calendar that double-books
- Availability rules by resource: people, rooms, bays, vehicles, equipment
- Deposits and payments through Stripe, with the cancellation terms you set
- Reminders by email and text, and the no-show rate to show they work
- The desk view the office needs, which is never the customer view
Use a booking platform
If you book one kind of thing, at one location, with simple rules, a hosted booking platform will do it and the monthly fee is worth it. Build when the rules are the business, or when the booking has to flow into a job system behind it.
Internal tools and dashboards
Most internal tools replace a spreadsheet that four people edit at once. The stock list, the rota, the approvals log, the monthly report someone spends two days assembling. Each becomes a screen with one version of the truth, permissions, and a history of who changed what.
What it replaces and what it does
- Shared workbooks that became the system of record
- Approval chains that run through email
- Stock, orders and jobs with live counts instead of a weekly recount
- Owner dashboards read straight from the database: turnover, margin, work in progress, debtors
Stay in the spreadsheet
If one person maintains it, it changes rarely, and nothing else depends on it, a spreadsheet is the right tool. Build when several people edit it, when it feeds other systems, or when an error in it costs money.
Workshop and job management
From the job card on the whiteboard to a screen the whole team shares. We built a cloud workshop-management system for a garage that had been running on a desktop program tied to one PC: bookings, a job board, parts and time against each job, invoicing handed to the accounts package, and reminders sent without anyone remembering to send them.
What it replaces and what it does
- The desktop package licensed to one machine, or the whiteboard and the diary
- Job status visible to the office, the workshop floor and the customer
- Parts, labour and time recorded against the job as it happens
- Invoicing from the job, payments matched, accounts export automatic
- Reminders and follow-ups driven by the records, not by memory
Use an industry package
Every trade has two or three packaged systems, and if one of them matches how you work and does not charge per bay or per user beyond reason, use it. Build when the package is the bottleneck, when it holds your data hostage, or when it is about to stop being supported. See legacy system modernisation.
Bespoke or off the shelf
Every section above has a "when a package is fine" answer because it is often the right one. The decision is about fit and control, not technology. We wrote up how to decide, with a ten-question checklist, and the short version is: buy when the process is standard, build when the process is the advantage.
How a build runs, and what it costs
Discovery first, then a written scope and a fixed price for the first phase, then a demo every week from the second week of the build, then handover with the repository, the cloud account and the database in your name. The full method is on the bespoke software development page.
What moves the price is the number of user types and screens, the systems it has to connect to, how much data has to move across, and how much compliance evidence you need. Every phase is a fixed price, and we do not quote day rates.
Built with AI, decided by people
AI does the mechanical parts of the build: scaffolding, database migrations, tests, seed data and documentation. That is where an agency's weeks go, and where our price is lower. It does not decide what to build, and a person reads every line that ships.
Questions people ask about bespoke systems
What is bespoke business software?
A system built for one company's way of working: its customers, its jobs, its rules. It replaces a package that would have forced the process to change, or a spreadsheet that became the system by accident.
Do we need a bespoke CRM or a package?
If your sales process is standard and you have no unusual integrations, a package like HubSpot or Pipedrive is probably right, and we will say so. A bespoke CRM earns its place when the pipeline stages, the data you track or the systems it has to talk to do not fit any package without workarounds.
Can a customer portal connect to our existing systems?
Yes. A portal is usually a window onto a job system, an accounts package or a CRM you already run. We connect to what has an API and build a bridge for what does not.
Can you build a booking system that takes deposits?
Yes, usually through Stripe, in your own Stripe account. The deposit rules, the cancellation terms and the reminders are yours to set, not fixed by a platform.
Can you replace our spreadsheets?
That is most of what internal tools are. A shared workbook that four people edit at once becomes a screen with one version of the truth, permissions, and a history of who changed what.
How long does a first system take?
A first fixed-price phase usually goes live within eight weeks of sign-off. Larger systems ship in phases, starting with the part that hurts most.
What does a bespoke system cost?
A fixed price per phase, quoted after discovery, with no day rates. What moves it is the number of user types and screens, the integrations, how much data has to move across, and the compliance evidence you need.
Who hosts it and who owns it?
You do, both. The repository, the cloud account and the database are opened in your name in the first week. Hosting is billed to you directly, and nothing sits behind an Evolve login.
Tell us what the spreadsheet is doing
On a free call we will ask what the system has to do, who uses it, and what it has to talk to. If a package would do it, we will tell you which one.