# How Built uses incident.io

**4+ hours**: “4+ hours saved on post-mortems”

As published on [incident.io](https://incident.io/customers/built), March 2026. Captured by usedby on 2026-10-07.

- Company: [Built](https://www.usedby.ai/companies/built.md)
- Tool: [incident.io](https://www.usedby.ai/tools/incident-io.md)
- Teams: Cloud Platform Team, Engineering

## What the story says

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.

> 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.

- **50+**: “50+ engineers using across the cloud platform team”

> 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

## What usedby checked

We compared the story with its live page on 2026-10-07.

- Checked: the figure 4+ hours is printed word for word on the page, near the name of Built.
- Checked: the passage quoted above is copied word for word from the page, near the name of Built.
- Checked: the publication date is read from the page’s own metadata, never guessed.
- Checked: Built uses incident.io. Confirmed line. Latest check across sources: 2026-10-07.
- Not checked: the result itself. We quote it; we did not measure it.

---
Source: https://www.usedby.ai/case-studies/built-incident-io · How we check: https://www.usedby.ai/methodology