Every project starts from something concrete: data entry that takes too long, a spreadsheet that can no longer keep up, a field team without the right tool. Here is how each was solved.
The projects below share one thing: each started from a problem someone was already living with, not from an appetite for new technology. Data entry that took four hours, a spreadsheet several people were fighting over, a field team still filling in paper sheets, clients calling for information they could have looked up themselves.
Every case study follows the same shape: where it started, what was built, and what changed. Technical decisions are explained where they illuminate something, never listed for their own sake. Where a result is quantified, the source of the number is stated — and where it is not, none is invented.
Removing a repetitive task without changing the tools already in place. These are often the shortest projects, and the ones whose return is easiest to measure.
A browser extension that fills the field-service tool’s form automatically from the existing file. Around four hours of typing replaced by a few seconds.
A web and mobile client portal that turns a Google Sheet into a live view of a defibrillator fleet: compliance status, map, expiry alerts and service reports.
A case file marked “complete” becomes a PDF report, reaches the right client and archives itself — with billing tracking the investigators never see.
Business software and client portals reachable from a browser, built when a spreadsheet or an off-the-shelf product stopped being enough.
An online ordering platform for snacks and restaurants in La Réunion: each establishment gets its own storefront, in its own name and colours, with no commission on sales.
A web and mobile client portal that turns a Google Sheet into a live view of a defibrillator fleet: compliance status, map, expiry alerts and service reports.
A multi-tenant SaaS platform that digitalises the hotel stay: guests scan a QR code — no app install — to order, request, chat and read the welcome booklet.
A white-label ordering and delivery platform: a single Flutter codebase shipped as distinctly branded applications, with real-time GPS tracking.
A cross-platform B2B extranet for equipment leasing: financing simulation, application build-up, e-signature and contract tracking — two audiences from one codebase.
Applications used in the field, for teams working standing up, outdoors, sometimes with no signal — not at a desk.
An online ordering platform for snacks and restaurants in La Réunion: each establishment gets its own storefront, in its own name and colours, with no commission on sales.
A web and mobile client portal that turns a Google Sheet into a live view of a defibrillator fleet: compliance status, map, expiry alerts and service reports.
A multi-tenant SaaS platform that digitalises the hotel stay: guests scan a QR code — no app install — to order, request, chat and read the welcome booklet.
A white-label ordering and delivery platform: a single Flutter codebase shipped as distinctly branded applications, with real-time GPS tracking.
Taking over a ride-booking application built for the Congolese market: cash payment, three languages, and automatic server-side ride allocation.
In most of these projects the company did not want to change software — and did not need to. A Google Sheet fed by a field tool, business software the team knows well, a well-kept tracking spreadsheet: these are starting points, not problems. The work is filling the gap between them.
On sensitive tasks — a maintenance visit, a report sent to a client — the tool prepares but does not confirm. That is what makes automation acceptable where a mistake has real consequences: the typing goes, the control never does.
None of these projects shipped complete on the first pass. A first version covers the core of the need and goes live; what follows is decided from real use rather than a list drawn up at the start. That is what avoids paying for features nobody uses.
These projects were designed, built and put into production by the same person. For a small business that means quick decisions, no context lost between a salesperson and a developer, and someone who still knows the project six months later.
Let’s talk about what you want to build. I reply personally, usually within 24 hours.