Capability 03
Systems
Software shaped to one organisation's actual operations.
Every organisation past a certain size runs on a spreadsheet that one person understands, plus three tools that do not talk to each other. We replace that with software modelled on the actual operation: the roles, the records, and the state transitions the work moves through. We build these tailored today, and we are packaging the proven ones into configurable systems that can be deployed and adapted rather than rebuilt.
How it works
What a project looks like.
The same order every time, so you always know which stage you are in and what comes out of it.
- 01
Observe
We sit with the people doing the work. The spreadsheet they actually maintain is the real specification, and it is always more accurate than the org chart.
- 02
Model
The data model comes first: entities, roles, permissions, and the state transitions each record moves through. Get this wrong and no amount of interface saves it.
- 03
Pilot
One department, real data, a matter of weeks. Something people can use before the rest is built, because a demo tells you far less than a Tuesday.
- 04
Extend
Modules are added against observed usage, not a launch wishlist. Features requested twice by different people get built; features requested once get discussed.
- 05
Hand over
Documentation, administrator training, and access to the source. No lock-in through obscurity.
- 06
Operate
Backups, updates, monitoring, and a support line — for as long as you want us on it, and a clean exit when you don't.
Systems
Where to start.
Each one is scoped, priced, and run the same way.
What's included
Everything you get.
Each one lists how it is actually done, so you can check the claim rather than take it on trust.
The data model is the product
Interfaces are cheap to change and models are expensive. We spend the first weeks on entities, roles, and state machines.
- Explicit state transitions per record
- Role-based access down to the field
- Audit trail on every mutation
Built for the room it runs in
A clinic front desk, a factory floor, and a venue on event night have nothing in common except that a laptop is the wrong device.
- Responsive down to a phone in one hand
- Tolerant of unreliable connections
- Barcode, QR, and label printing where relevant
Reports somebody actually asked for
Every system accumulates dashboards nobody opens. We build the reports that already exist as manual work, and remove that work.
- Scheduled exports and statements
- Role-scoped operational views
- Direct export to sheets and PDF
Deploys where you need it
Cloud by default. On-premise when regulation, connectivity, or institutional policy requires it.
- Containerised deployment
- On-premise and private cloud
- Documented backup and restore
Integrates rather than isolates
The new system has to live alongside accounting, messaging, and whatever hardware is already on site.
- Accounting and payment integrations
- SMS, WhatsApp, and email notifications
- Import from the spreadsheets already in use
From bespoke to configurable
Patterns repeat across organisations in the same sector. Where they do, we turn a proven build into a configurable system rather than starting again.
- Configuration over customisation
- Per-tenant branding and rules
- Upgrade path that survives configuration
Honest limits
What we will not do.
Worth reading before you get in touch — it saves both of us a call.
- We do not do big-bang replacements of systems that currently work. Pilot first, migrate department by department.
- We do not build a feature because it was mentioned once in a workshop.
- We do not hold your data or your source hostage. Export and handover are written into the engagement.
- We will tell you when an off-the-shelf product is the better answer. Custom software is a serious commitment and it is not always the right one.
- TypeScript
- Next.js
- Postgres
- Prisma
- Redis
- Docker
- Linux
- S3-compatible storage
- Grafana
Questions
Asked before.
Is this bespoke software or a product?
Today, bespoke: built for one organisation, around its actual operation. Where a build proves itself across several clients in the same sector, we package it as a configurable system. Both are on the table.
How long does a system take?
A usable pilot in a single department is typically measured in weeks. A full operational system across departments is measured in months. Anyone quoting you a fixed number before seeing the operation is guessing.
What happens if we want to take it in-house later?
You get the source, the documentation, and a handover. That is the intended end state for many clients, not a failure case.
Can it run without reliable internet?
Where the operation demands it, yes — on-premise deployment and connection-tolerant interfaces are both things we build.
Do you maintain it afterwards?
If you want us to. Support, updates, and monitoring are a separate ongoing agreement, and it can be ended without stranding you.
Next step
Describe the problem in your own words.
No brief required. Tell us what is slow, wrong, or manual today and we will tell you what it would take to fix — including when the answer is that you do not need us.