Custom software
Internal tools, dashboards, portals and integrations — usually replacing the spreadsheet that quietly runs your entire operation.
What this actually is
Almost every business we meet has one spreadsheet that everything depends on, that two people understand, and that nobody wants to touch. Custom software is what you build when off-the-shelf has stopped fitting: when the workaround costs more hours per month than the licence saves, or when an auditor, an insurer or a regulator starts asking how the data is controlled.
What you get.
Not a menu of upsells. Everything below is in the base price, because the work is not finished without it.
- Discovery workshop and a written spec you sign off before we build
- Releases every two weeks, never a big-bang delivery
- Role-based access, audit logging, exportable data
- Integrations with the systems you already pay for
- Automated tests on the paths that would hurt if they broke
- Documentation and a recorded handover session
Built with
Who it's for
The part that
makes the difference.
We start by trying to talk you out of it
The first hour of discovery is spent checking whether an existing product already does this. If your problem is solved by a $60-a-month tool plus two hours of configuration, we will tell you and lose the project. Custom software is worth building when the process is genuinely yours, when integration between systems is the actual product, or when the data cannot leave your control.
Two-week releases, one workflow at a time
You never wait six months for a reveal. Each cycle delivers a working slice your team can use in production, so migration happens gradually rather than on a switchover weekend that everyone dreads. It also means you can change your mind about anything not yet built without a change-request negotiation.
Built to be handed over
Your team, or the next developer you hire, should be able to pick this up without us. That means conventional patterns rather than clever ones, a README that explains the why as well as the how, tests on the paths that matter, and a recorded walkthrough of the architecture. We would rather be re-hired than depended on.
Custom software,
answered honestly.
How much does custom software cost?
Most engagements land between $14,000 and $60,000. The number is driven by how many user roles exist, how many external systems have to be integrated, and how much historical data has to be migrated — not by the number of screens, which is what people usually expect.
What if we want to change direction halfway through?
That is what the two-week cycle is for. Anything not yet built can be re-prioritised at no cost. Anything already built and being replaced gets estimated in writing before we start, and you can decline.
Can you integrate with the systems we already use?
Usually. Anything with a documented API is straightforward. Legacy systems without one can often be handled through scheduled exports or a database read replica. We check this in discovery, because it is the single most common thing that makes an estimate wrong.
Who owns the software?
You do, on final payment for each stage. Code lives in your repository from day one, not ours, and the infrastructure runs in your cloud account.