PEPPY HEALTH / MARCH 2022 TO OCTOBER 2023
Replace a zero-test clinician panel while the service scaled.
A two-person senior frontend team rebuilt Peppy Admin, the web panel clinicians used to support employees receiving Peppy's health benefit.
- 2
- Senior frontend engineers
- 100s
- Components catalogued
- Full E2E
- Cypress coverage
- £12m
- ARR during scale-up
SITUATION / RESPONSIBILITY
Clinicians depended on a tightly coupled panel with no tests.
Peppy Admin was the working interface between clinicians and employees using Peppy's employer-funded health service. Its frontend had no automated tests and tightly coupled screens made changes risky.
Led a two-person senior frontend team while Peppy grew to £12 million in annual recurring revenue. We had to modernise a live clinical tool without slowing the people using it every day.
RELIABILITY PATH
- 01Inherited admin
- 02Component inventory
- 03Cypress in CI
- 04Safer releases
KEY DECISIONS
Make the inherited interface visible before changing it.
- 01
Catalogue the existing interface in Storybook
The team recorded hundreds of UI components and their states. That turned an opaque frontend into an inventory the engineers could inspect, discuss and improve.
- 02
Replace screen-level coupling with components
Clear component boundaries reduced the reach of routine changes. Work could move through smaller units instead of reopening an entire clinician workflow for every edit.
- 03
Run the complete Cypress suite in GitHub Actions
End-to-end checks became part of the delivery path. The team could test the clinician journeys on every change instead of relying on manual confidence.
- 04
Add AI support where clinician cover stopped
The clinician-side Sendbird integration answered common user questions when clinicians were unavailable, including overnight. It extended support without pretending AI replaced clinical care.
PRODUCTION RESULT
More frequent releases, fewer bugs and a team that could change the panel safely.
Storybook made the interface inspectable, Cypress put the main journeys under automated checks, and GitHub Actions ran those checks on delivery. The rebuilt frontend gave a growing healthcare service a more dependable way to ship changes.