Custom Software Development
Custom software, built for how your organisation really works
We build web and mobile software that replaces spreadsheets, paper and tools you've outgrown: one system around your processes and your data. Our engineering team has delivered systems for hospitals, banks and cooperatives, each live within 4–6 months.
Organisations we've built for
Best for
When custom software is the right move
If your key work depends on one of these, an off-the-shelf tool won't fix it.
Spreadsheets and paper
Key work runs on spreadsheets, paper forms and email, and only a few people know how it fits together.
One system with your workflows, roles and approvals built in, and the data in one place.
Outgrown tools
The tool you bought no longer fits, and every workaround adds another manual step.
Software built around how your teams actually work, with the parts of the old tool that still work kept or connected.
Disconnected systems
Your ERP, accounting and other tools don't talk to each other, so people copy data between them.
Integrations through APIs and data imports, tested on every release, so data is entered once.
Staff and customer apps
Staff in the field, or your customers, need an app, and your systems can't offer one.
Web and mobile apps on top of your systems, built for the people who use them every day.
What you get
What your system includes
Built to be run for years, not just to launch.
Web and mobile apps
Browser apps for your teams and mobile apps for iOS and Android, from one codebase where it fits.
Workflows and roles
Your processes, approvals and permissions in the software, with an audit trail of who did what.
Integrations
Connections to your ERP, accounting, identity provider and other tools through their APIs.
Reporting
Dashboards and exports built on the data the system holds, so the numbers come from one place.
Every build includes
Code in your repository from day one
Automated tests and a deployment pipeline
Accessible by default, built to WCAG 2.1 AA
Documentation, training and a handover your team can run
How we deliver
From the first workflow to a system your teams run on
The same three steps as every project we run, starting with how the work happens today.
01
Plan
We map the workflows, roles and data with the people who do the work, then agree the scope, the risks and a list of what we won't build.
02
Thin slice
One workflow working end to end early, in a staging environment, with a demo every week. Then the system grows slice by slice.
03
Launch and handover
Data moved over from the old tools, users trained, monitoring in place and documentation, so your team can run the system.
Security and data
Built for the data your organisation holds
Systems like these hold staff, customer and financial data. They're built so you can show how it's protected.
Roles and permissions.
Each person sees and changes only what their role allows, and every change is logged.
Secure by design.
Encryption in transit and at rest, secrets kept out of the code, and dependencies checked on every build.
Data moved with care.
Data from the old tools migrated with checks, and test data that's synthetic or anonymised, never copied from production.
Sectors and technologies
Where we've built, and what we build with
Sectors
Our engineering team has built hospital systems, fleet management for a cooperative, shareholder management for banks and a national digital addressing system.
Healthcare
Financial services
Logistics & mobility
Public sector & geospatial
Technologies
Widely used technologies your future hires will know. We agree the stack with you, and work in yours if you already have one.
TypeScript
React
Java
Python
.NET
Flutter
PostgreSQL
AWS
FAQ
Questions about custom software development
Off the shelf, if a tool fits your process with small changes: it's faster and cheaper. Custom software pays off when the process is what sets you apart, when the workarounds cost more than a build, or when your systems have to work together. In the first call we tell you which applies.
The systems our engineering team has delivered went live 4 to 6 months after kickoff. One workflow works much earlier, in staging, with a demo every week. The written proposal after our first call sets out the timeline for your scope.
As a fixed scope when the requirements are clear, or as time and materials when they will change as you learn. You see the cost model, the team and the timeline in the written proposal before anything is signed, and the proposal is free.
Yes. We move one workflow at a time, run the old and the new side by side where needed, and migrate the data with checks, so people switch over when the new part works.
Usually, through their APIs or data imports. We check what each system offers during the plan, and every integration is tested on each release.
It depends on who uses it and where. Mobile apps for iOS and Android are built from one codebase where that fits, and every web app is built to WCAG 2.1 AA, so it works for all its users.
Your team, us, or both. You get the code, the documentation and a handover either way, and our DevOps and managed support service can run and patch the system for you.
The code we write for you is yours to use, change and license once it is paid for: exclusive, unlimited rights, with the source in your repository from day one. Open-source parts keep their own licences, and a platform core, if you start from one of ours, is licensed to you.
Related services
Often combined with
Build
SaaS Platform Development
Multi-tenant platforms with sign-in, billing and admin, if you'll offer the system to other organisations.
Data
Data Foundations & Analytics
One source of truth for your reports, built on the data your new system holds.
Rescue & run
DevOps & Managed Support
Pipelines, monitoring and patching once the system is live, so it keeps running.