Work · Case study
Twenty-two services rebuilt under a floor that never closed.
01 / Challenge
ClickSeer runs appointments, stock, clinical records and payments for multi-venue salons and aesthetics clinics across London. Years of growth had left defects across every daily-use screen, retention handled by memory, stock with no batch traceability, and sensitive treatment photography with weak access control — on a platform that could not be taken offline to fix any of it.
02 / Approach
We worked inside the running platform rather than beside it. Zero-downtime delivery was the baseline from the first release, not an optimisation added later, which meant every change had to be shippable on its own and reversible on its own.
A shared-kernel pattern kept authentication, domain models and reduced entities aligned across services without collapsing them back into one deployable. Legacy Spring Boot 1.5 and Spring Boot 3.2 services ran side by side through the whole programme, because rewriting the core first would have stopped everything else for a year.
Four front ends were maintained in parallel — the admin console, a token-gated upload app, a service-provider PWA and a waiver-form app — each answering a distinct journey rather than bending one interface to five audiences. Sensitive imagery moved behind one-time upload links, PIN-gated galleries and organisation-scoped storage. OpenAI was added where a judgement was already being made by hand: recommendations, best time to approach, retention drafts, review replies and sentiment.
03 / Outcome
backend services
deployment pipelines
front-end applications
The platform now runs twenty-two backend services, four purpose-built front ends and twenty-nine deployment pipelines, with retention, service packs, batch-tracked stock, a staff training system and nine AI-assisted workflows that did not exist before. Every one of them shipped into live multi-venue operations without a maintenance window.