Software development
Applications, integrations, and the web platforms in front of them.
Most of what we build replaces something that already works, badly — a spreadsheet holding a process together, a system two people understand, or software bought years ago that no longer matches how the business runs.
We write the replacement to fit the process you actually have, connect it to the systems that already hold your data, and keep maintaining it after launch. A build that nobody owns afterwards is a liability with a nice interface.
What you get
- Line-of-business applications: quoting, scheduling, stock, case handling, internal portals
- Integrations between systems that were never designed to talk — ERP, accounting, CRM, suppliers
- Public websites and customer portals, built for speed and accessibility
- APIs for your own products, and for the partners consuming them
- Taking over an existing codebase someone else left behind
- Maintenance, dependency upgrades and small changes on a standing arrangement
How it usually starts
Fixed-scope build
A defined piece of work with a written scope, a range rather than a false-precision figure, and staged delivery you can see running.
Ongoing development
A recurring block of engineering time against your backlog, with priorities you set at the start of each cycle.
Rescue
A project that stalled, or a system whose original author has gone. We start with an assessment you can act on with or without us.
Is this the thing you need?
Describe the situation and we will tell you — including when the answer is no.