Skip to main content
usedby

4+ hours

“4+ hours saved on post-mortems”

As published on incident.io, March 2026. Captured by usedby on Oct 7, 2026.

What happened

Built replaced PagerDuty with incident.io for paging, on-call and the rest of the incident lifecycle. Timelines and follow-ups that were previously written by hand are now generated automatically from Slack history and call transcripts, and incidents are run through Slack.

Summary written by usedby from the source page, in English. The figures are those of incident.io and Built, not ours.

  • 50+“50+ engineers using across the cloud platform team”

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.

From the page. incident.io, captured Oct 7, 2026

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.

Jacob Weyer, Manager, Cloud Platform Team, Built. Source, captured Oct 7, 2026

What the story claims, and what we checked

We compared the story with its live page on Oct 7, 2026.

  • The figure: 4+ hoursCheckedPrinted word for word on the page, near the name of Built.
  • The passage quoted aboveCheckedCopied word for word from the page, near the name of Built.
  • The publication dateCheckedRead from the page’s own metadata, never guessed.
  • Built uses incident.ioCheckedConfirmed line. Latest check across sources: Oct 7, 2026.
  • The result itselfNot checkedWe quote it; we did not measure it.

Same company, same tool or same industry.

80%“Approximately 80% of our initial incident-response workflow is now automated.”Kaizen Gaming uses incident.io. Another customer of incident.ioUp to 10x“Up to 10x faster response time”Turbopuffer uses incident.io. Another customer of incident.io114%“Responder deployment reached 114% of contracted seats”Flagstone uses incident.io. Another customer of incident.io