Software development
Internal systems, customer portals and integrations that your operations depend on daily.
Typical duration: 3 to 9 months to first production release.
When to call us
For operations and IT leaders whose business runs on a system that has to keep working: order flows, portals, the integrations around an ERP.
- A system your operation depends on is maintained by one person, or by nobody.
- A supplier built something, left, and took the knowledge with them.
- Releases are rare, because every one of them is frightening.
- A rebuild is on the table, and you need to be sure this one lasts.
What we deliver
We build the systems a company runs on: order flows, portals, the glue between an ERP and everything around it. It gets used hard, so we build it to be maintained by whoever comes after us.
- Architecture written down before the build, with the trade-offs named.
- Web applications, APIs and integrations with your ERP, CRM and finance systems.
- Automated tests, staged releases and a rollback plan for every deploy.
- Monitoring and alerts wired in before launch.
- Documentation a new engineer can follow on their first day.
- Yours at handover
- Source code, infrastructure scripts, runbooks and every account, all in your name.
- Typical duration
- 3 to 9 months to first production release
How it moves through the shop
The same four stages as every project, applied to software development.
1
Assay
We read the existing code and data, map every system it touches, and write down what has to keep running during the change.
2
Forge
Working releases every two weeks in a production-like environment, with tests written alongside the code.
3
Temper
Load tests against your real volumes, a security review, and a rehearsed rollback.
4
Service
Monitoring, patching and small improvements under a service agreement, or a full handover to your team.
Questions about software development
Will you work with our existing code, or do you insist on a rebuild?
We start with what you have. The assay tells you which parts are sound, which need work and which should go, with the reasoning. We recommend a rebuild only when keeping the old system costs more than replacing it.
Which technologies do you use?
Mainstream, well-supported ones that your own team or another supplier could take over. [Preferred stack is confirmed before launch]. If you have standards, we follow them.
Can you take over a system another supplier built?
Yes. It starts with an assay of the code and infrastructure, so both sides know what we're taking on.
Other services
AI implementation
AI that runs inside production systems, with logging, fallbacks and a person in the loop where it matters.
AI consulting
A board-ready view of where AI pays back in your operation, with the engineering cost attached.
Digital marketing
Demand generation built like the rest of our work: measured end to end, from first click to signed contract.
Bring us the system you can't afford to get wrong.
30 minutes. Bring the problem, and we'll tell you whether we're the right shop for it.