THE CHALLENGE
Betting platforms live under unpredictable load. A big fixture can multiply traffic in minutes, and customers
expect every bet, bonus and balance to be right every time. Legacy coupling made it hard to change anything
quickly. Our team was embedded with the client to ship new features and modernise the platform at the same
time.
Three questions framed the work:
What we built
Bonus Engine
A rules-driven orchestration layer for promotional logic, configurable without rewriting code. It was first developed for specific sporting events, where domain requirements were tight and the turnaround was short.
My Account
Critical account logic re-architected for reliability, security and scale.
Games redesign
A new front end built for smooth, low-latency play.
Foundations underneath
How the team worked
The developers worked as contractors inside the client’s main team. They were new to this niche domain and
to the business, and still completed features and user stories within sprint timeframes and demoed changes to key stakeholders.
They shared knowledge across teams, including business insights for the games team so it could better
understand what the business needed. Several of the practices they introduced have since been adopted by the client. One developer also stepped up to lead and shape a new team.
Service quality is tracked across incident response time, resolution time, customer satisfaction, cost efficiency, service quality and the ability to handle change.
Why It Matters
The platform now has a modular, observable base. New promotions can be configured rather than
hand-coded. Account services are built to withstand upstream failures. The games front end is set up to roll
out features faster. Load testing and telemetry give the client evidence of how the system behaves before a
major event, not after.
TECHNOLOGY USED
.NET 10
Blazor
