Engineering · Charlee
One codebase for every insurer client, with features behind flags and deployments automated
Charlee’s features had been built in isolation for different insurers. We turned them into modules behind feature flags, automated deployments and took over the infrastructure.


The problem
Charlee turns unstructured insurance claim notes into numbers a machine can use. Insurers use it to predict which claims will go to litigation, how severe they will get, and which look like fraud. The company holds three patents on how it does this.
Over the years, features had been built separately for different insurer clients. Sharing one client’s feature with another meant copying code. The infrastructure was run by another firm whose replies could take three or four hours when something broke.
What we did
- Split the codebase into self-contained modules, each behind a feature flag.
- Added one control panel to turn any feature on or off for any client.
- Set a standard way for features to plug in, so code built for one insurer can be reused for the next.
- Automated deployments, so releasing a feature is a flag change, with no downtime.
- Took over DevOps: monitoring, recovery when search or storage fails, and a named backup whenever someone is away.
“We found that he’s a lot more customer focused than the other company that we had.”
Rama, Charlee
What changed
The codebase went from siloed to modular. Features move between clients without duplicate code, deployments are automated, and the team ships more often. When the system has a problem, someone answers quickly.
“You guys have been pretty responsive … anytime we contact you.”
Rama, Charlee
“We are pretty happy, very happy with how you guys are supporting us.”
Rama, Charlee
What you get · Engineering
What this means for you
Got features built one client at a time? We can turn them into modules you switch on per client, and run the infrastructure behind them.




