Ably × Fin (formerly Intercom)
80% reduction in HTTP GET requests
Designing around gaps to trusting the system
Members read free
Enter your email to open every case study in the library: the full screenshot, why it works, and the one thing worth stealing. One email unlocks all of them.
Free. No spam. Unsubscribe anytime.
You're in — enjoy the library.
The case study earns its efficiency tag through three concrete metrics and a named engineer explaining the before-state in specific terms. The 'run less software' philosophy gives the decision a quotable rationale that generalises beyond this customer. There is a mild coin-flip between Efficiency and New Capability, but the framing leads with reduction in engineering burden rather than a net-new ability, so Efficiency wins.
Frame the build-versus-buy decision as an opportunity cost argument: show what engineering time was being consumed by maintenance and what it could be spent on instead. This reframes infrastructure replacement as a product investment, not a cost-cutting exercise.
Click to enlarge ↗ This is editorial commentary and curation. The case study, screenshot, and all metrics are Ably's published work; we link to the source and lead with our analysis.