Healthcare Booking Platform
Overview
Led frontend development of a booking platform for a UK private healthcare provider, delivered at IntexSoft. The core product is a six-step booking flow where every step reshapes itself from prior selections - service type, doctor availability, location, insurance - roughly 30 distinct form states with cascading dependencies, running against a WordPress REST backend. The project started in vanilla JavaScript; I drove the mid-project migration to React, redesigned the component architecture, and built the shared library that later powered a second product: a B2B portal for corporate clients. When the fixed-price project drifted from the client's vision, I took over requirements gathering and client calls directly - the realignment ended with the client extending the contract for six more months of B2B development.
Inside the product
Private healthcare, from booking to corporate services.
Anonymized public website views, captured on 7 September 2026. Client branding is redacted. These show current product context rather than archival screens of the 2023–2024 delivery.
My roleLead Frontend Developer · via IntexSoft
What I builtDynamic B2C booking / React migration / shared components / B2B portal
The current public entry point for booking a home visit or phone and video appointment. Captured 7 September 2026.
Key Features
Dynamic Booking Flow
Every step of the booking had to reshape itself based on previous selections - service type, doctor availability, location, insurance - producing around 30 unique form states with cascading dependencies. Hardcoding transitions would have made the flow impossible to extend.
Architected a state-machine-driven form engine in React. Each field change triggers API requests that recalculate the available options downstream, and steps are modular units that can be reordered or added without touching the rest of the flow.
A seamless six-step booking experience that survived two years of scope growth.
Mid-Project Migration to React
The project started in vanilla JavaScript, and the growing UI complexity - dynamic states, shared logic between flows - was making it unmaintainable.
Made the call to migrate to React mid-project rather than keep patching. Redesigned the component architecture around reusability and extracted a shared component library that both the B2C flow and the later B2B portal are built on.
Feature development on the B2B portal ran ~40% faster by reusing B2C components. The shared library became the foundation of both products.
Rescuing a Fixed-Price Project
Fixed-price contract, no dedicated analyst. A month and a half into development, the client said the product did not match their vision - on a fixed budget, that is an existential problem.
Took ownership of requirements myself: joined every client call, re-clarified expectations, restructured the scope of work, and established a regular demo cadence so misalignment could never build up silently again.
Both the B2C and B2B phases shipped, and the client extended the contract for six additional months of B2B development.