Most businesses don’t set out to buy software. They set out to stop doing something by hand.
The quoting lives in three spreadsheets. Job sheets get typed up twice. Nobody can answer “where’s that order” without ringing two people. There’s an off-the-shelf package that does 70% of it and fights you on the rest.
We’ve built custom systems for business, local government and central government since 1999 — designed around how the work actually happens rather than how a product assumed it would.
The kinds of system we build
[IMG-1] — A real system screen, anonymised. Something recognisably operational — a job list, a stock screen — not a dashboard.
Alt: Bespoke job management system built for a UK business
Job and works management — scheduling, allocation, completion, costing. The system the business runs its day on.
Product and stock databases — parts, specifications, pricing, variants, suppliers, stock levels across locations.
Supplier and contractor management — approved supplier lists, contracts, purchase orders, performance, insurance and certification expiry.
Quoting, ordering and invoicing — from enquiry through to invoice without rekeying it at each stage.
Compliance and checks systems — inspections, audits, safety checks, and things like display screen equipment (DSE) assessments, where the record of having done it matters as much as the doing.
Asset and equipment tracking — what you own, where it is, who has it, when it was last serviced, when it’s next due.
Scheduling and resource planning — people, vehicles, plant and rooms.
Reporting and management information built in from the start, rather than exported into Excel afterwards → reporting and business intelligence
Most real systems are two or three of these joined together, because that’s how businesses actually work.
Design comes before development
The systems that fail are the ones built straight from a list of screens somebody asked for.
We start with how the job actually moves through the business — including the parts people have stopped mentioning because they’ve always done it that way, and the workarounds that exist because the last system couldn’t cope.
That usually turns up two or three things worth changing before a line of code is written, and it’s where most of the value in a project comes from. It’s also where you find out what it’ll cost, before you’ve committed.
What a system built for you should do
- Fit the way you work, rather than making you fit it
- Stop the double entry. One number, entered once, everywhere it’s needed → integration and APIs
- Catch mistakes at the point of entry, not at month end
- Be usable at speed by the people in it all day — keyboard-first where there’s volume, and laid out the way the job is done rather than the way the tables are structured
- Produce finished output — reports, documents and figures that don’t need five minutes in Excel afterwards
- Reach beyond the office where it needs to → web applications – mobile apps
- Change as the business does, without a rewrite each time
Built on solid foundations
All successful software projects start with a solid database design. Get the data model wrong and you spend the next ten years working around it.
- SQL Server or Azure SQL for most builds →SQL Server design and development
- Microsoft Access where it’s genuinely the right fit — single site, manageable numbers, Office already licensed, working in weeks rather than next year → Access design and development
- MySQL where an existing system or hosting arrangement calls for it → MySQL
- Web and API layer in .NET and C#, or Node.js and NestJS
- Browser interfaces in React and Next.js
- Mobile in React Native — one codebase for iOS and Android, so there’s one app to maintain rather than two
- Hosted in Azure or on your own servers, whichever suits → Azure and cloud
Should it be bespoke at all?
We’ll tell you if it shouldn’t.
If there’s a package that genuinely does what you need, buy the package. It’ll be cheaper, it’ll be supported by more people than us, and you’ll be up and running sooner. Plenty of businesses are better served by Sage, a decent CRM or an industry system than by anything we’d build.
Bespoke earns its place when the way you work is the business — when the thing that makes you money is a process no product understands, when you’d have to change how you operate to fit the software, or when you’ve already bought three packages and you’re still typing between them.
We’d rather have that conversation honestly at the start than build something you’ll regret.
What you get, and what you own
- Fixed scope and a fixed price for the build, agreed before we start
- Something working early. Most first versions are in front of users in weeks rather than months. You see it working, tell us what’s wrong with it while it’s still cheap to change, and we build out from there.
- Your data, in a format you own, on your hardware or in the cloud
- Documentation of how it’s put together, so you’re not dependent on us to understand your own system
- Testing with the people who’ll use it, before go-live rather than after. They’ll find things, and it’s far cheaper to fix them then.
- Somebody to ring afterwards who remembers building it → support
That last one is the point. Most of the systems we get called out to were built by someone who’s no longer reachable.
Case studies
Aire Valley Catering: four mobile apps, an Access business system, and engineers with no signal
Engineers working on customer sites across the UK can't count on having a signal, and the job still has to be recorded. Four production apps across both app stores, an Access and SQL Server business system behind them, and a roadmap that keeps offline working rather than trading it away.
View case study →Recovering audit and customer data across multiple corrupt SQL databases
Several customer databases became damaged and wouldn't open, putting audit records, operational data and customer information at risk of permanent loss. A structured recovery programme rebuilt usable datasets from the corrupt files and returned multiple customer systems to service.
View case study →ACC Worldwide: a faster SQL Server platform, noticed on day one
A business-critical system was working but slow, and staff felt it every day. Work on the SQL Server environment behind it delivered an immediate speed increase, and left ACC's own IT team with the logging and monitoring tools to keep developing it.
View case study →
Tell us what the business needs to do
Not what screens you want. We'll work out how the job actually moves through your business, what would need building, and what it costs — including when the answer is to buy something off the shelf instead.
Send us the details →
How we work →
Tell us what the business needs to do
Not what screens you want. We'll work out how the job actually moves through your business, what would need building, and what it costs — including when the answer is to buy something off the shelf instead.
Send us the details → How we work →