Membership platform
A ten-year-old application replaced by two sites, public and administrative, with membership status available without having to ask.
- Year
- 2026
- Client
- Confidential
- Sector
- Retail
- Type
- Web platform
- Role
- Front-end developer
- Team
- 3 people
- Stack
- React · Node · MySQL · Google Cloud
The application managing memberships had been in service for more than ten years. It still worked, which is exactly what makes replacement hard to justify, but every year it cost more to maintain and was more awkward to use.
The problem was not the interface
The interface had aged badly, true. But the real cost was that there was no way to check a membership’s status, current promotions or scheduled maintenance without asking someone. The information existed; it just was not available to the people who needed it.
Two sites on one foundation
We built a public site, where members check their own status, and an administrative one from which the company publishes news, events and notices without touching code or requesting a deploy.
I designed the architecture around the fact that the content catalogue would grow far faster than the member count, so the public side is served in a way where adding content does not make each visit more expensive.
Result
Information stopped being scattered across the old application, email and the front desk. It is centralised, it is accessible, and members no longer have to ask in order to know where they stand.