Custom database software
When important records no longer have one reliable home.
I build owned database-backed software for businesses whose jobs, assets, inspections, orders, certificates, stock or customer records have outgrown spreadsheets, Access, FileMaker or disconnected tools.
Problem diagnosis
The real problem is usually trust in the record.
- Teams keep separate copies of customer, asset, job or order data.
- Reports require manual exports, cleanup and interpretation by one person.
- People can change important records without the right permissions or change history.
When the record is unclear, decisions slow down and operational confidence moves from the system into people’s memory.
Responsibility
A useful database starts with the questions the business asks.
I design the records, roles, search, reports and change history around the process, then build the smallest system that makes those records reliable.
What I would build
The first useful version would be concrete.
- 01
A clear record model
Customers, assets, jobs, orders, certificates, inspections or suppliers are structured around the real process.
- 02
Role-based access
Users get the screens and permissions they need without everyone editing everything.
- 03
Search and reporting
The system answers the operational questions people actually ask, not just generic database queries.
- 04
Audit trail where it matters
Important changes, approvals and state moves can be recorded so the business can see what happened.
- 05
Migration and integration paths
Existing records can be imported or connected to other tools where the workflow requires it.
Fit filter
Probably right, probably not.
Probably right when…
- The records are important to operations, billing, quality or customer service.
- Several people or teams need different views and permissions.
- Reporting, audit trail or integration now matters.
Probably not me when…
- You mainly need SQL help or a one-off report.
- A simple no-code database will be enough.
- You want ongoing database administration rather than a built and handed-over system.
First step
Start with diagnosis, not a big commitment.
The first conversation is about the records that matter and the decisions people need to make from them.
£150 per hour plus VAT where applicable. Two hours minimum for new clients. No retainer, no minimum term, no lock-in. You own everything I build.
Useful things to send before a call
- Sample records or exports
- Current forms, screens or spreadsheets
- Reports people depend on
- User roles, permissions and change-history needs
Objections
Questions this page should answer before you email.
Can an old database be migrated?
Usually, if the records can be exported or accessed. The important part is checking meaning and relationships, not just moving fields.
Will this become overbuilt?
It should not. The first version should cover the core records and workflows that are causing the most risk or admin.
Is this Access or FileMaker support?
No. Those can be starting points, but the work here is a custom database system the business owns.
Next step
If this looks like your problem, send me the awkward bits.
The useful first email is short: what is breaking, what product or process cannot handle it, and what working would need to mean.