Software Development
Custom software for organisations whose process is not adequately supported by the products available, and staged modernisation of existing systems that are still worth keeping.
Custom software makes sense when the way an organisation works does not fit the products available, or when an existing system has become too risky to change. Before building, we check whether configuring a product already in use, or connecting two systems, would solve the problem at lower cost and risk.
What we offer
Web Applications
Purpose-built browser applications for customers and staff who need to complete a process online, connected to the systems that hold the records.
Internal Systems
Purpose-built internal software for operational processes that have outgrown spreadsheets, local databases or disconnected tools, with clear data ownership and permissions.
Modernisation
Assessment and staged improvement of ageing software: keep what still works, fix what creates risk, and replace components only where the evidence supports it.
One possible response, not the default
We scope a build around the work people do: who does it, which records it touches, and the awkward cases that usually decide the design. Delivery in working pieces lets the organisation use part of the system early and correct the understanding before changes become expensive.
Custom software creates an ongoing asset that must be maintained. Deployment, access, observability and documentation are part of the work, so the system can be run and changed after handover. Technology is chosen for the requirement and for who will support it, not because a particular stack is fashionable.
How we decide what to build
Configure or integrate before building
If a product already in use can do the job with configuration or an integration, that should be considered first. Custom software has to be maintained for as long as it is used.
Keep what still works
Replacing a working system can lose behaviour nobody wrote down. Existing software is changed in stages unless there is a clear reason to start again.
Built to be handed over
Code, deployment and documentation should be understandable by another capable developer. Tooling is chosen with that supportability in mind.
How a typical engagement works
01Discovery
Understand the work first
We find out who does the work, which records it touches and where the awkward cases are, and check whether a product already in use could do the job.
02Scope and design
Scope and design in writing
Scope, data model and security decisions are agreed before the build starts, with the riskiest parts identified first.
03Build
Build in working pieces
Software is delivered in stages, so people can use part of it early and correct our understanding while changes are still cheap.
04Deploy and handover
Deploy and hand over
Deployment, access control, monitoring and documentation are part of the delivery, with training and support arranged to suit the people who will run it.
05Support
Support after handover
After handover, support can continue as new features, fixes and changes come up.
Evidence
Insights
- Where AI helps software development, and where engineering ownership still matters
AI can make implementation, tests, documentation and security remediation cheaper to produce. Risk starts when generated software is trusted because it runs, while nobody still owns its architecture, security decisions or the ability to change it.
- When GitHub Actions is unavailable, what is actually blocked
GitHub's 5 October Actions incident caused job failures and delays on hosted runners. For organisations that build and deploy through Actions, the useful question is what remains possible when the application is healthy but the release path is not.
- When replacing ageing software is the wrong decision
Replacing an ageing system can consume a year and still reproduce the same operational problems. This article looks at how to tell whether the problem is age, what the current system still holds, and what a replacement actually commits an organisation to.
Frequently Asked Questions
Start with a conversation
Book a free 15 minute call. Describe the problem, the systems involved and what you already know, and we will tell you plainly whether we can help and what a sensible next step looks like. There is no obligation.