What Counterweight needed
Counterweight runs evidence-based weight loss and type 2 diabetes remission programmes. As demand grew, its digital platform was getting harder to run: a microservices setup and a badly configured AWS account pushed up costs, and too many bespoke tools slowed every release.
The team didn’t only need more hands. Development priorities weren’t tied closely enough to what the business needed, so someone had to work out what to change as well as change it.
Who joined
Counterweight hired 3 full-stack engineers through epicX, with experience in AWS, backend scaling and system architecture. They worked directly with Counterweight’s product and leadership team, who set the priorities.
“We were working with a fragile and expensive platform. The dedicated developers from epicX came in, understood the root issues quickly, and rebuilt the system in a way that just worked. Costs dropped, performance improved, and the product became something we could finally scale.”
What the engineers did
- Replaced the microservices architecture with a simpler monolith, which took engineering overhead out of every change.
- Swapped custom-built features for proven tools, including Stream for chat and Sanity for content.
- Reworked how the platform used AWS and removed services it didn’t need.
The result
Counterweight’s AWS costs fell by 70%, and the platform now serves 35,000 users.
Have a similar problem?
See how a forward deployed engineer placement works, or talk to a founder about what’s stuck.