The use case: how Built deploys incident.io
Built replaced PagerDuty with incident.io to run its full incident lifecycle, including paging, on-call, and automated timelines and post-incident documentation, through Slack. It has also adopted incident.io status pages.
More reported results
Figures published in incident.io’s case study. They are not independently measured by usedby.
50+ engineers using across the cloud platform team
In the customer’s words
As an incident manager, I can focus on the incident and not the paperwork. I can focus on the problem. I don't have to worry about documenting the steps that we did; I can have it auto-generated. That has been just night and day.We brought in incident.io for roughly what we were paying for PagerDuty. Except now we had the full incident management lifecycle. That was the big ROI.Other AI tools used by Built
Other public relationships recorded on usedby.
Explore Built’s AI stackOther companies using incident.io
Customers across industries, with public evidence.
AccurxConfirmed
AudioStackConfirmed
Bold CommerceConfirmed
BufferConfirmed
ClariConfirmed
ContentfulConfirmedGo straight to the source
Based on incident.io’s published case study. We check the public evidence; the results are reported by the vendor.
incident.io- Source published
- Mar 26, 2026
- Last checked
- Nov 11, 2026
Open source capture What the story claims, and what we checked
What we compared with the page.
- The figure: 4+ hoursChecked
Printed word for word on the page, near the name of Built.
- The passage quoted aboveChecked
Copied word for word from the page, near the name of Built.
- The publication dateChecked
Read from the page’s own metadata, never guessed.
- Built uses incident.ioChecked
Confirmed line.
- The result itselfNot checked
We quote it; we did not measure it.
Timeline generation now happens automatically from Slack history and call transcripts. What used to be a post-incident obligation became something that looked after itself.

