---
title: "Post-mortem automation — niche opportunity inside Enterprise SaaS"
url: https://signals.gitdealflow.com/niche-down/enterprise-saas/post-mortem-automation
description: "Generate incident post-mortems from PagerDuty + Slack + GitHub + observability data."
source: VC Deal Flow Signal
---
# Post-mortem automation

> Generate incident post-mortems from PagerDuty + Slack + GitHub + observability data.

**Sector**: [Enterprise SaaS](https://signals.gitdealflow.com/niche-down/enterprise-saas)  
**Build cost**: Month-long build  
**Deal velocity**: Trickle — one deal per quarter

## Why now

Post-mortems are skipped because writing them is painful. AI drafts the first 80%.

## What the signal looks like

Repos with incident-data adapters, timeline-reconstruction libraries, and post-mortem template frameworks.

## Public examples

*Public projects + categories only — we never name founders tracked inside the paid product.*

- Rootly shape
- Incident.io adjacency
- Open-source incident-postmortem tools

## What this displaces

An incident channel that gets forgotten by Monday.

## Our build-vs-invest call

Wedge with engineering ops. The moat is the data-source integration + the workflow.

## Frequently asked

### Buyer?

Engineering ops + SRE leaders.

### Pricing?

Per organization or per incident.

### Defensibility?

Integration breadth + template quality.

## Canonical

https://signals.gitdealflow.com/niche-down/enterprise-saas/post-mortem-automation