The spine is the system a business runs on. Everything else exists to make that system worth having — the apps in front of it, the data underneath, the cloud it sits on, the documents that explain it and the people who keep it alive.
01
For distributors, wholesalers,
manufacturers and traders
The operational software a company opens every morning: what was ordered, what is in stock, what went out, who owes what. Most businesses this size are running it on a register, a spreadsheet and a WhatsApp group, and it works right up until an order is missed or nobody can say what the month actually earned.
The hard part is never the screens. It is that stock, orders, invoices and the dealer ledger all describe the same events, so they have to move together or not at all — and when they disagree, the system has to be able to say which one is right and why.
02
For anyone whose customers,
staff or dealers are online
Public sites, customer portals, booking flows and internal tools. We build them to be maintained for years rather than launched once — which mostly means resisting the urge to add a framework the client will later have to pay somebody to understand.
Performance is measured on a mid-range Android phone on mobile data, not on a developer’s laptop. That is where your visitors actually are, and it changes what is worth building.
03
For the people who are not
sitting at a desk
Field staff, drivers, dealers, customers. The ones who need the system in their hand, usually standing somewhere with bad signal, usually in a hurry.
Our rule is that an app is a window onto the same system, not a second island of data. One API behind both platforms, one source of truth, and a sync that assumes the connection will drop — because on a delivery route it will.
04
For the counter, the warehouse
and the back office
Sometimes a browser tab is the wrong tool. A sales counter needs to keep working when the internet does not. A warehouse terminal needs a barcode scanner, a weighing scale and a label printer to just work. Back-office staff need keyboard speed, not a page reload.
So these are local-first: the machine holds its own copy, keeps going on its own, and reconciles with the central system when it can reach it.
05
For systems that have grown
slow, or data that has grown messy
This is where most slow systems actually break, and it is almost never the language. A query that is fine at fifty thousand rows is an incident at five million, and the symptom shows up as “the software is slow” long after the cause was a missing index or a schema that made the right question expensive.
We also take on the unglamorous half: pulling decades of data out of spreadsheets and legacy systems, reconciling it, and loading it without quietly deciding which version of a disagreement is correct.
06
For systems people use daily
and cannot afford to lose
Deployment is part of the design, not a step at the end. On a system people use every day, downtime is a design flaw rather than an inconvenience — and the most common cause of it is a release process nobody wrote down.
We also ask the question most projects skip until it is urgent: when this breaks at nine at night, who finds out, and what do they do?
07
For anyone who does not want to be
locked to the firm that built it
Most software firms treat documentation as something to apologise for at handover. We treat it as part of the product, because a system nobody can operate or change is not an asset — it is a liability with a login page.
It also protects you from us. If you decide to move to another developer, you should be able to hand them a folder and have them get to work, without needing a single meeting with the people who left.
08
For businesses whose customers
find them by searching
Technical first. Content on a site that loads slowly, cannot be indexed properly or has no structured data is content nobody will see, and no amount of writing fixes a site search engines struggle to read.
We will also tell you when SEO is the wrong spend. If your real problem is that enquiries arrive and nobody follows them up, more traffic will not help you.
09
For every client who has been
left holding software nobody updates
Software is not finished when it ships. Rules change, staff change, a payment provider changes an API, a certificate expires. The firms that treat support as an afterthought are the reason so many businesses are running something that works but cannot be touched.
A named person answers, in your working hours. And it is monthly and cancellable — we would rather keep it because it is worth keeping.
Most people arrive describing a symptom rather than a service — something is slow, or manual, or a number nobody trusts. Tell us the symptom. Working out which of the nine it is, is our job, and it is free.