Web platforms and portals
Customer portals, operational dashboards and the APIs behind them — responsive from the first line, because most of your users arrive on a phone in a yard or a corridor.
Not a website
This is not brochure work. A web platform is the thing people log into and do their job in: the portal where your customers check their own orders instead of ringing you, the dashboard where a manager sees the depot at a glance, the screen where a hundred records get approved on a Friday afternoon.
That changes what matters. Nobody cares about a hero animation on a page they open forty times a day. They care that the list loads instantly with eight thousand rows in it, that the filter remembers what they picked, that the keyboard works, and that the thing they do most often takes one click rather than four.
Mobile-first, and we mean it
Responsive design gets claimed far more often than it gets done. In practice a great many business systems are built at desk width and squeezed down afterwards, which is how you end up with a twelve-column table that needs horizontal scrolling on the device the user actually holds.
We design the narrow case first, because for most of our clients it is the common case — the supervisor in a corridor, the driver at a gate, the inspector on a roof. If it works properly at phone width it will be fine on a monitor. The reverse is almost never true.
Portals that cut your phone traffic
A customer portal pays for itself in calls you stop taking. Order status, documents, invoices, service history, raising and tracking a job — every one of those is a phone call someone in your office is currently fielding and retyping into another system afterwards.
The same applies internally. A supplier portal, a subcontractor portal, a tenant or resident portal: the pattern is identical, which is letting the person who wants the information fetch it themselves, safely, without needing an account on your core system.
APIs and dashboards
Where a mobile app, a portal and an internal system all need the same data, a REST API in the middle stops you maintaining three versions of the truth. We build those properly — versioned, authenticated, documented and rate-limited — whether they are for your own apps or for a customer integrating with you.
Dashboards we approach with some scepticism. A dashboard that nobody opens twice is a cost, and most are built to impress rather than to be used. The ones that earn their place answer a specific question somebody asks every morning, and show the exception rather than the total. Mapping and location work, where it is useful, we build with Leaflet rather than a licence you have to keep paying for.
Built on Laravel
Laravel with MySQL or SQL Server, with JavaScript on the front where it adds something. It is a boring, widely-known stack, deliberately — you should be able to hand the code to any competent developer and have them get on with it. You own the code and the data, with full exports, and can host it with us or yourself.
The commercial arrangement is the same as everything else we do: a working prototype first, then a monthly commitment with unlimited developer time under fair use, maintenance and support included.
Related: custom software development, mobile app development, systems integration.
Start with a conversation
The first meeting is free and its job is working out whether this is worth building at all. If it is, you will see a working prototype before any long-term money is discussed.
Book a slot or call 020 4652 7504