Bespoke database development for trades and service businesses.
Bespoke database development turns the spreadsheet that quietly runs your business into a proper system: shared safely, checked as people type, with a record of every change. Our custom database development keeps the process your spreadsheet already proves works, and removes the risk of one file, one bad paste or one person holding everything together.
Fixed quote before we start. One-off build fee, then ongoing management from go-live.
Keep the process, lose the risk.
Most businesses do not set out to run on a spreadsheet. It starts as a simple list, grows a tab at a time, and one day it holds every client, job, certificate or booking the business has. It works, which is exactly why it has become hard to replace.
A bespoke database is an internal tool built around that same information and those same rules, with the structure a spreadsheet cannot give: linked records, checked entries, permissions, history and reminders. We treat your spreadsheet as the first draft of the specification, not something to throw away, so the team recognises their own process on the first day.
Signs your spreadsheet has become the business.
Excel, Google Sheets, Airtable and Notion serve many teams well. These are the signs yours needs a database built around how the business actually works.
One file runs the business
Jobs, clients, certificates or bookings all live in one spreadsheet. If it broke tomorrow, the business would stop until someone rebuilt it.
Several people edit it at once
Two people change the same row, a filter hides half the data, or someone sorts one column and not the others. You find out weeks later.
Rules held together by colour
Red means overdue, yellow means waiting for parts, bold means do not touch. New staff learn the code by getting it wrong.
Copies everywhere
There is a master, a version for the office, a version on someone’s laptop and an export sent to a client last month. Nobody is sure which is current.
No idea who changed what
A price, a date or a status changed and nobody knows who did it or what it said before, so mistakes are hard to trace and harder to prevent.
Too slow, too big, too fragile
The file takes a minute to open, formulas break when someone inserts a row, and only one person really understands how it works.
What goes into a bespoke database.
Every internal tool we build includes the first four. Discovery decides which of the rest you need now, and management lets you add them later.
One spreadsheet, four very different databases.
These are illustrative examples, not client projects. They show the kind of spreadsheet that most often becomes a bespoke database.
A gas and electrical compliance contractor
A register of every property, appliance and installation, with each certificate, its expiry date and the engineer who issued it. Renewals become jobs months ahead, and landlords can receive an up-to-date schedule on request.
A property maintenance company
Every block, flat, contact and repair in one place, with access notes, keys held and contractor history. Reactive and planned work share a single record per property, instead of a tab per building.
A training provider
Courses, dates, venues, trainers, delegates and certificates, linked together. A course fills from bookings, certificates issue on completion, and refresher reminders go out before they lapse.
An events business
Suppliers, venues, staff and each event’s requirements in one database, with availability and costs per event. Quotes draw on supplier prices that someone updates once, not in twenty copies.
From spreadsheet to system.
Your data is the valuable part. We move it across carefully, show you every decision, and never switch off the old sheet until the new system has proved itself.
Read the spreadsheet as a specification
Your columns, tabs, formulas and colour codes already describe your process. We map every one of them and agree with you what each means before anything moves.
Clean and restructure
We split combined columns, remove duplicates, standardise names, dates and postcodes, and flag rows that need a human decision, then show you the result.
Run side by side, then switch
The team uses the new system alongside the old sheet for an agreed period, compares results, then switches over on a date that suits you. The old file stays archived.
Connected to the tools you already pay for.
A database should sit at the centre of your systems, not on an island. We connect it to the tools you keep, and we never rebuild accounting or payroll. We check what each tool’s API exposes during discovery.
From the file everyone fears to a tool everyone uses.
A database build follows the same five stages as all our bespoke software: discovery, a written scope with a fixed quote, a build in stages, go-live, then ongoing management.
Discovery starts with the spreadsheet itself, shared on a video call. The people who use it every day walk us through a normal week: what they add, what they check, what they colour, and what goes wrong. The unwritten rules come out here, and they go into the written scope.
The first milestone is usually the core records with checked forms and history, because that removes the biggest risk straight away. Views, reminders and integrations follow. If approvals or handovers sit around the data, workflow automation can run them from the same system, and if the sheet is really a customer list, a bespoke CRM may be the better starting point.
A fixed quote, and your data stays yours.
Every bespoke database has a one-off build fee, fixed in a written quote after discovery, plus monthly management from go-live covering hosting, monitoring, updates, fixes and small improvements. Adding users does not add per-seat fees. The full pricing model sits on our bespoke software page.
A licence to use it
Scalepoint keeps the code and you hold a licence to use it, with the option to buy the code out later.
The code becomes yours
Once you pay the build in full, you own the code.
Your data is always yours
Every record in the database belongs to your business under UK GDPR, and you can export it at any time.
Common questions about bespoke databases
How much does bespoke database development cost?
It depends on scope, so we quote after discovery rather than publish a price. Turning one well-organised spreadsheet into a shared system costs less than joining several sheets into a database with roles, reminders and integrations. Your written quote fixes the build fee before you commit and sets out the monthly management fee in the same document.
Why not move to Airtable or Microsoft Access?
If one or two people use the data and the process is simple, Airtable or a tidier spreadsheet may be all you need, and we will say so. A bespoke database earns its place when several people depend on it every day, when permissions and change history matter, when the rules are too specific for a template, or when per-seat pricing starts to add up.
Can we still get our data into Excel?
Yes. You can export any view to Excel or CSV whenever you like, and we can schedule regular exports. The difference is that the database stays the master copy, so exports never drift out of date.
Does it work on a phone?
Yes. We build it to run in a browser on a phone, tablet or desktop, so staff on site can look up a record or update a job without a laptop.
Who owns the database and the data?
Your data is always yours, and you can export it at any time. Code ownership is agreed per project in writing: by default Scalepoint keeps the code and you hold a licence with the option to buy it out, or the code becomes yours once you pay the build in full.
What happens after go-live?
Ongoing management starts from go-live with every build: hosting, monitoring, updates, fixes and small improvements. When you need a new field, a new report or a new view, management covers the small changes and we quote the larger ones first.
Share the spreadsheet you would hate to lose.
Walk us through it on a call, and we will show you what it would look like as a system your whole team can rely on.
More on bespoke software.
Every kind of software we build, and how a project runs
Learn more →Approvals and handovers that run on your rules
Learn more →Your numbers from every system in one view
Learn more →When the spreadsheet you outgrew tracks stock
Learn more →When the spreadsheet is your pricing
Learn more →When the spreadsheet is your rota
Learn more →