Build · Software, systems & data
When the product
does not fit,
build the fit.
Buying software is usually the right answer. But when every option on the market forces you to change how the operation works — or costs more per year than building it once — the maths turns over. We tell you which side you are on.
What we build
Systems for operations
that do not fit a box.
-
Operational platforms
The system the business runs on: the thing that replaces the spreadsheets, the clipboard and the WhatsApp group.
- Role-based access for different teams
- Multi-site and multi-company support
- Audit trails on every change
- Automated alerts on exceptions
-
Warehouse management
Stock you can trust, because it is captured where the work happens instead of typed up later.
- Receiving, putaway and bin locations
- Pick lists and dispatch confirmation
- Cycle counts and stock adjustments
- Barcode scanning on handhelds
-
Manufacturing execution
What the line is actually doing, against what it was supposed to do, while the shift is still running.
- Job and batch tracking
- Downtime capture with reasons
- Yield, scrap and rework
- Shift and operator reporting
-
Mobile apps for field teams
For staff who work away from a desk, on a phone, sometimes with no signal.
- Android and iOS from one codebase
- Photo capture as evidence
- QR and barcode scanning
- Designed for gloves and cracked screens
-
Websites & web applications
Public-facing sites and internal tools, built to be fast and handed over cleanly.
- Works on any device
- Accessible and keyboard-navigable
- Content you can edit yourself
- Documented for whoever comes next
-
Integration & reporting
Making the systems you already own talk to each other, and turning the result into numbers you trust.
- API and file-based integrations
- Accounting and payroll connections
- Scheduled automation with failure alerts
- Dashboards refreshed automatically
How we build
Small pieces, working,
as we go.
Big-bang software projects fail in a predictable way: everyone agrees a specification, disappears for eight months and delivers something that describes the business as it was at the start. We deliver in usable stages instead.
- Watch the work happen Before writing anything we spend time where the job is done — the warehouse floor, the weighbridge, the admin office. What people actually do is rarely what the process document says.
- Scope and price the first slice The smallest piece that delivers real value on its own, with a fixed price and a date. Not a prototype to throw away, but production software you keep using.
- Build in the open You see it every couple of weeks and use it on real data as early as it is safe to. Feedback lands while it is still cheap to act on.
- Roll out with the people who will use it Training, a parallel-run period where the old way still exists, and someone reachable during the first weeks. Adoption fails more often than software does.
- Support, then extend A support arrangement for fixes and small changes, and the next slice quoted when you want it. You are never obliged to keep buying.
What you own
The code is yours.
Custom software is worthless to you if it can only ever be maintained by the company that wrote it. That is a commercial trap, and plenty of development shops rely on it.
So we write down the arrangement at the start. You own the source code and the data. It sits in a repository in your organisation's name. It is documented well enough for another competent developer to pick up, and we use mainstream technology precisely so that developer is findable.
We would rather keep your business because the work is good than because leaving is expensive.
- Source code
- Yours, in your repository
- Data
- Yours, exportable in open formats
- Hosting
- Your accounts, or ours if you prefer
- Documentation
- Handover pack on delivery
- Technology
- Mainstream and widely supported
- TypeScript
- NestJS
- Next.js
- PostgreSQL
- Flutter
- Docker
Common questions
Software, answered.
Should we build or buy?
Buy, if something on the market covers most of what you need without forcing you to change how you work. Build when the process is genuinely your competitive advantage, when licence costs for enough users exceed the cost of building, or when the only products that fit are enterprise systems priced for companies ten times your size. We will say so when buying is the right answer.
What does custom software cost?
The honest answer is that it depends entirely on scope, which is why we price the first slice rather than the whole vision. A focused first release addressing one real problem is typically a matter of weeks, not months, and gives you a real number to plan the rest against.
What happens if we stop working with you?
You keep the source code, the data and the documentation, and it runs on infrastructure in your name. We will do a handover to your new developer if you ask. Nothing about the arrangement depends on us still being there.
Can you work with the systems we already have?
Usually. Most business systems expose an API, a database or at minimum a scheduled file export, and any of those is enough to work with. Where a supplier genuinely locks their system down, we will tell you what the workaround costs before you commit to it.
Who supports the software once it is live?
We do, under a support arrangement agreed alongside the build: fixes, small changes and keeping the underlying platform current. If you have internal developers who would rather take it on, we hand over and stay available for the difficult questions.
Related
Next step
Tell us what you need.
A paragraph is enough to start. We come back with what we would do, what it would cost and how long it would take.