Approach
Build. Connect. Remain.
Engagements are scoped after a short discovery call. We do not publish a price list — the work depends on the operation.
01
Custom operations software
Discovery through launch. One system tailored to how the business runs.
- Product-led discovery and a written scope before build starts
- UI designed for operators, not a demo deck
- Full-stack build with QA and a planned release
- Migration from spreadsheets and existing tools
- Pricing is scoped after a short discovery call
02
Integrations
Connect the system to tools you already rely on — only where it earns its keep.
- Payments, email, calendars, and accounting
- CRMs and WhatsApp Business APIs where staff already live
- APIs in and out so you are not trapped in a silo
- We pick the connection to fit the problem, not a partner list
03
Ongoing care (retainer)
Fixes, small features, and reliability after launch — with someone who already knows the product.
- Dedicated care contact on the retainer
- Monitoring, hosting coordination, and routine upkeep
- Small features without reopening a full project
- Clearer than hiring a freelancer who has to relearn the system each time
What discovery produces
01
A map of how work, stock, and money move today — including the exceptions a template never modelled.
02
A written scope: what is in, what is out, what depends on an integration.
03
Roles: owner, floor, and anyone who needs a thinner portal.
04
A sequence of slices you can review before anything is ‘done’.
Method
01 Discover
How work, stock, and money move today — including the exceptions.
02 Design
Roles and screens for the floor, not a demo deck.
03 Build
Shipped in reviewable slices. History migrated, not discarded.
04 Launch
Training, monitoring, an operating change — not a URL.
05 Care
A named contact. Fixes and small features on retainer.
On the engagement
Product lead
Discovery and scoping — the person who makes sure we are building the right system.
UI/UX designer
Screens and flows your team can use under time pressure, on the floor and at a desk.
Full-stack engineers
The application, data model, and integrations. Senior attention, not a revolving bench.
QA / release
The unglamorous work that keeps launch from becoming a second job for your staff.
Dedicated care contact
On retainer: a named person for fixes and small changes after you are live.
- TypeScript
- React / Next.js
- Node.js
- Python
- PostgreSQL
- REST / GraphQL APIs
- Cloud deploy (Vercel / AWS)
- Stripe and common business APIs
Problems we solve
Where the floor usually breaks.
Event hire
event hire booking softwareDiary, warehouse, and invoice as one job — not three files rebuilt on Monday.
Equipment hire
kit availabilityA hold that can block a pick before Saturday finds the clash.
Deposits & damage
deposit and damage trackingRelease rules and workshop gates on the kit, not in a notebook.
Field service
field service operations softwareDispatch, complete, and invoice from the same visit.
Wholesale
wholesale operations softwareOrders, credit, and stock by site without a morning reconstruction.
Clinics
clinic day-list softwareChairs, consumables, and balances on the same day — not three tools at close.
Workshop
workshop job card softwareMOT slot, courtesy car, and keys on the job — not a diary and a drawer.
Job shop
job shop operations softwareQuote, materials, and delivery on one card — not a whiteboard.
Property
property operations softwareUnits, turnovers, maintenance, and owner reports on one calendar.
3PL
3PL warehouse operations softwareWaves, inbound, and client stock that is not a pool.
Contracting
snags, variations, and retentionPractical completion cannot sign while a snag is open.
Membership
membership club operations softwareDoor, class capacity, and direct debit on the same member.
Compare
Packaged hire software vs the floor.
Fair pages for operators already searching a named product. Templates fit some shops. Custom wins when the exception is the week.
From the floor
Notes on the week, not a magazine.
Equipment hire
Kit clashes happen before the van leavesThe van is not where the clash starts. It starts when sales confirmed a date the warehouse could not honour, and availability was a colour instead of a lock.
Deposits & damage
The till book is not a deposit systemA deposit was taken. Nobody can say against which kit, or whether it should still be held because a head came back warm. That is not a bookkeeping quirk. It is a missing object.
Field service
The visit should write the invoiceWork is booked in a diary. Parts are guessed from memory. Technicians update status in a chat. Invoices are written days later from whatever survived. That is three objects. It should be one.
United Kingdom · SMEs
WhatsApp is not the operations systemUK SMEs do not fail because they lack software. They fail because the tools do not share a record. Accounts may already live in Xero or QuickBooks. Jobs still live in a spreadsheet. WhatsApp carries the exceptions.
Event hire
When Excel breaks on show weekShow week is not when the spreadsheet gets a bit messy. It is when the diary, the warehouse, and the invoice stop being the same job.
Custom ops
Template ERP is not the floorA template is a bet that your exceptions are someone else’s average. Most growing operations lose that bet on the floor, not in the demo.
Tell us what’s broken in ops.