An Irish utility company ran its customer loyalty platform on WordPress. The program was live and members were using it, but even a small campaign update needed a developer, and the site was never built to be a platform. The client is not named on the RaftLabs record, so it is not named here either.
This is the short version. The full record is published by RaftLabs, our parent studio: the headless loyalty platform case study.
What we built
The platform was rebuilt on a headless setup: the marketing team publishes rewards, campaigns, member tiers, and banners in a content tool built for editors, and the member-facing site is generated from that content. Members kept their accounts, rewards catalogue, and dashboard. The move from the live WordPress site took 12 weeks, without disrupting the active program.
The point of the build was operational, not cosmetic. A loyalty team that can publish a campaign the day it is approved runs more campaigns, and a platform that generates its pages ahead of time stays fast under promotional load.
The honest label on the numbers
The record carries three figures: page loads 3 times faster, engagement up 40%, and content update time down 60%. All three were pre-launch projections. No post-launch measurements were published for this project, so this page reports the build and labels the figures as what they are: estimates made before launch, not results measured after it.
What this means for a program like yours
If your loyalty program runs on a website that was never meant to be a platform, the rebuild question is not which technology to pick. It is whether your team can run the program without filing a ticket for each change, and whether your members keep their balances through the move. Get those two right and the technology choice gets much easier.
Talk to the studio
If your program has outgrown the website it runs on, the next step is a scoping call. Bring your member count and the list of changes your team cannot make today.
Book a scoping call. Projects start at $9,500.


