Buildkite × Intercom
Buildkite x Intercom: 25-minute tests cut to 3 minutes
85% reduction in test times (25 minutes to 3 minutes)
Constant outages and 50% test failure rate to reliable, fast CI
Members read free
Unlock the full breakdown
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.
Why it works
The story earns its efficiency framing with a specific, concrete before-and-after number that is directly attributable to this customer. The 50% JavaScript test failure rate is a sharp before-state that makes the reliability problem tangible before the speed win lands. The mechanism is explained well enough to follow: move orchestration to Buildkite on Intercom's own EC2 infrastructure, add retry automation, then tune for speed once reliability was solved.
Steal this
Stage the win in two steps: lead with reliability as the minimum viable goal, then layer in speed once the foundation holds. This makes the outcome feel earned rather than oversold.
Click to enlarge ↗ This is editorial commentary and curation. The case study, screenshot, and all metrics are Buildkite's published work; we link to the source and lead with our analysis.