Custom database development for trades and service businesses.
Custom database development for tradies, clinics, training providers, property services and hospitality groups across Australia whose business now runs on a spreadsheet. We turn it into a proper system with forms, rules, permissions and a full history, so the data stays right whoever is entering it.
A fixed written quote before we start. Pay upfront or in stages. Ongoing management from go-live.
The spreadsheet that quietly became the system.
Almost every business has one: a spreadsheet that started as a simple list and grew into the thing the business runs on. The maintenance schedule, the compliance register, the client tracker, the price list, the equipment log. It works, mostly, and everyone is a little afraid of breaking it.
Custom database development keeps what works about that spreadsheet, the structure your team already understands, and adds what a spreadsheet cannot enforce: forms for entry, rules that catch mistakes, permissions for each role, reminders for due dates and a history of every change. Some call it bespoke database development or building an internal tool. The result is the same: a system the business can rely on.
Databases are one of the tools we build under custom software development, and often the first step. A well-built database is the foundation a client portal, reporting dashboard or workflow automation can be added to later, without starting again.
Book a free strategy callSigns you have outgrown the spreadsheet
Usually a business where several people rely on the same spreadsheet, Microsoft Access database or Airtable base every day, and where a mistake in it costs money.
Several people edit the same file
Rows get overwritten, columns get sorted out of line, and two versions of the "master" sheet end up on two different laptops.
Only one person really understands it
The formulas, the colour codes and the hidden tabs make sense to the person who built it. When they are away, nobody wants to touch it.
Nothing stops a bad entry
A wrong date, a typo in a client name or a missing field goes in without complaint, and turns up weeks later as a missed renewal or a wrong invoice.
You cannot tell who changed what
A number is different from last week and there is no way to see who changed it, when, or what it said before.
What a custom database does that a sheet cannot
Six things a database built for one business does that a shared spreadsheet has to leave to good intentions.
What goes into a custom database
Most internal tools use some of these parts, shaped to the records you keep. We start with the spreadsheet that matters most, and add more later.
Spreadsheet, Airtable or a custom database?
Not every spreadsheet needs replacing. Here is when a sheet or a no-code tool is enough, and when a database built around your records fits better.
Fits small, simple, shared lists
Google Sheets and Excel are perfect for one or two people and data that rarely changes. Airtable, Notion and Smartsheet add structure, views and basic permissions, and are a sensible step for simple team lists.
The trade-off shows as the data and the team grow: rules that cannot be enforced, permissions that are all or nothing, per-user plans, and logic spread across formulas and automations only one person understands.
Fits data the business depends on
A custom build suits records that several people update every day, that carry dates and rules the business cannot afford to miss, and that need to connect to your job, accounting or client systems.
Every role has the right access, nobody pays per seat, and the database changes as your business does, as part of ongoing management.
There is also a middle path. Keep the spreadsheets that work for one person, and move only the shared, high-stakes ones into a database, with exports back to a sheet whenever someone wants to work that way.
What a custom database looks like in different businesses
Illustrative examples to show how the same idea fits different work. They are not past client projects.
Connected to the tools you already use
A database is more useful when it shares data with the rest of the business. We connect it to the systems that already do their job well, and never rebuild accounting or payroll.
Moving your data out of the spreadsheet
Years of rows come with you. We work through the spreadsheet, Access database or Airtable base with you: which columns mean what, which colour codes hide a status, which tabs are still used and which are history.
- Duplicates merged and inconsistent entries tidied
- A trial import you can check against the original
- The old file kept read-only, so nothing is lost
- A walkthrough for the team on the day you switch
The aim is a clean cutover: one day the team uses the sheet, the next they use the database, and nobody keeps a copy of the spreadsheet going on the side.
How a database project is priced and run
A database project runs the same way as every custom software build: discovery, a written scope with a fixed quote, building in stages you test on your real data, then go-live and ongoing management.
Every database is different, so there is no price list. You see both figures, in writing, for an agreed scope, before we start.
A one-off build fee
Fixed in your quote after discovery. Pay it upfront, or in stages tied to milestones.
Ongoing management
Every build comes with it: hosting, monitoring, updates, fixes and small improvements, billed monthly from the day your database goes live. New fields, forms and reports as the business changes are part of looking after it.
Who owns the database, and who owns the data
We agree code ownership per project, in writing, before the build starts. There are two options.
We keep the code, you hold a licence
Scalepoint owns the code and you get a licence to use the database software in your business. You can buy the code out later if your plans change.
You own the code once it is paid for
Ownership of the code passes to you when the build fee is paid in full.
Your data is always yours, whichever option you choose. Every record in the database belongs to your business, and you can export all of it at any time, in a format a spreadsheet or other software can read.
Other ways we can help
Common questions about custom databases
What is custom database development?+
Building a database and the screens around it for one business: the records it tracks, the forms people use, the rules that keep the data clean, who can see and change what, and the reports it produces. It is how a spreadsheet that runs part of the business becomes a proper system.
When should we keep the spreadsheet?+
If one or two people use it, it rarely changes, and mistakes are easy to spot, keep it. Airtable is also a good next step for simple shared lists. A custom database makes sense once several people edit the same data, errors cost money, or the business depends on dates and rules nobody should have to remember.
Can you move our existing data across?+
Yes. Spreadsheets, Microsoft Access databases, Airtable bases and exports from other systems can all be mapped and imported. We clean the data with you first, and you check a trial import before the switch.
Is it a web app or something installed on our computers?+
A web-based database, so it works in a browser on computers, phones and tablets, in the office or on site, with nothing to install. Access is controlled by user logins and roles.
How much does a custom database cost?+
It depends on what the database has to track and connect to, so there is no price list. After a discovery session you get a fixed build fee and the monthly management fee in writing, for an agreed scope, before any work starts.
Who owns the database and the data in it?+
Your data is always yours, and you can export it at any time. Code ownership is agreed in writing before the build: by default we keep the code and you hold a licence to use it, with the option to buy it out, or the code becomes yours once the build fee is paid in full.
Show us the spreadsheet everyone is afraid to break
Walk us through the file the business depends on and who uses it. We will show you what a database built around it would look like.