Internal business systems
The unglamorous tools your team runs on, built properly instead of living in spreadsheets.
- Engagement
- Fixed-scope build with a two-week parallel run
- Typical timeline
- 8–9 weeks
- Starts with
- A copy of the spreadsheet and a morning with the person who keeps it alive.
Every operations team eventually builds a spreadsheet that becomes load-bearing. Yours has forty columns, colour rules nobody documented, and an hour of manual repair each month after someone sorts a single column.
Operations that survive both growth and staff turnover.
What we build
Concrete artefacts, handed over and documented.
One system for the process, holding the records, statuses and approvals your operation genuinely uses
Permissions by role, so warehouse, finance and management each see the version that concerns them
Bulk actions and imports, because operations work arrives in batches of two hundred rather than one at a time
Full history on every record: who changed what, when, and what the value was before
Reporting views that replace the weekly export, drawn from the same records the team edits all day
What changes
The spreadsheet stops being the system of record and becomes an export
Month-end reconciliation runs off an audit trail instead of somebody’s memory
A new operations hire is productive in days rather than after weeks of shadowing
How it runs
01Shadow the process
We sit with the team for a morning and record what really happens, which is never quite what the process document says.
02Build the core
Records, statuses, permissions and the daily screens, reviewed each week by the people who will live in them.
03Migrate and run in parallel
Two weeks of both systems side by side, so the team trusts the new one before the old one is switched off.
Chosen per project. Named here so you can see the shape of it.
- Next.js
- Postgres
- Prisma
- Vercel
Questions we get asked
Tell us the outcome, not the tooling.
Send us the situation you are in. We will tell you which discipline it belongs to, what we would do first and what it costs, including when the answer is to wait.