Custom software, built around how the business actually works.
Internal platforms, case management, dispatch, portals — the systems a business runs on, usually replacing a spreadsheet, a shared inbox or a legacy tool. Specified before it is priced, built by our engineers, and owned outright by you.
What we do
- Internal platforms
- The system at the centre of how the business operates — the one people open first in the morning. Designed around the work as it is actually done, not around a vendor’s idea of your industry.
- Replacing spreadsheets
- Keeping the logic that works and losing the fragility: validation on the way in, permissions on who changes what, history on every change, and no more emailing version seven.
- Case and file management
- Work that moves through stages — applications, claims, files, jobs — with states that cannot be skipped, the right documents demanded at the right time, and deadlines the system tracks so people do not have to.
- Dispatch and scheduling
- People, crews or vehicles matched to jobs and availability, with shift changes and no-shows handled as normal events rather than phone calls.
- Portals
- A customer, partner or supplier view over your existing systems, so they can see status and submit what you need without another email thread.
- Replacing legacy tools
- The Access database or ageing application that runs something important and that nobody can change any more — rebuilt, with the data migrated and the old one retired cleanly.
Three ways to buy a build
Every build is priced as a fixed price against a written scope. What changes is how that scope gets written.
Where it usually hurts
If one of these sounds familiar, it is the kind of problem we are called in for.
- The business runs on a spreadsheet that three people are afraid to sort.
- A shared inbox is doing the work of a queue, and things fall through it.
- Off-the-shelf software fits most of the process, and the part it does not fit is where the business makes its money.
- The tool that runs operations was built years ago by someone who has left, and nobody can change it.
- Every new hire learns the process from a person, because nothing in the system enforces it.
Where this experience comes from
Our lead analyst's career history, described by sector — not an Elarion client list. More on the About page.
- Requirements and process design for a paratransit transportation management system built for New York City, through to go-live and cutover.
- Power Apps, Power Automate and SQL tools built around the ERP at a forest products company, removing manual steps from supply chain and invoicing.
- A multi-agent tutoring platform for a French-language exam-preparation product: agent specifications, an API contract of around sixteen endpoints with its data model, and a service boundary that keeps personal data out of the AI layer.
Systems we have built.
Three in production: a field dispatch platform built for a client, and two of our own products — a regulated case management system and a governed AI platform.
Questions buyers ask
- Who owns the code?
- You do. The repository, the infrastructure and the credentials are handed over at the end with as-built documentation, so you can run it, extend it or give it to another team without asking us.
- Why not buy off-the-shelf software?
- Often you should, and we will say so. Custom software earns its cost where the process is how you compete, where several products would need gluing together, or where the rules change often enough that configuring around them costs more than owning them.
- Will it work with the systems we already have?
- Yes. Most of what we build sits beside an ERP, a finance system or a CRM, reading and writing through supported interfaces so the existing system stays the record.
- What technology do you build with?
- TypeScript, modern component frameworks, relational databases and managed cloud hosting — chosen so your own team, or whoever comes next, can maintain it. Nothing you could not hire for.
- How is a build priced?
- As a fixed price against a written scope. A small, well-defined tool is quoted directly; a larger system is priced from the specification produced in a first, fixed-fee analysis phase. Changes to scope are written down, priced and agreed rather than absorbed.
- What drives the cost of custom software?
- Mostly the number of workflows and roles, the business rules behind them, the integrations, data migration, and audit or compliance needs — far more than the number of screens. Unknowns drive cost too, which is why the specification comes first.
Further reading
- Off-the-shelf or custom software? How to decideThe default should be to buy.
- Replacing spreadsheets with software, without losing what worksThe spreadsheet running your operation is not the problem.
- What drives the cost of custom softwareAsk five firms to quote the same software and you will often get five very different numbers.
Related services
Need custom software?
30 minutes, free. Bring the problem, or the change you already have in mind.