Enterprise SaaS · sub-niche
Post-mortem automation.
Generate incident post-mortems from PagerDuty + Slack + GitHub + observability data.
Month-long buildTrickle — 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
We name publicprojects + categories only — never founders we track inside the paid product. The buyer’s edge stays inside the 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.
Common questions about this niche
- Buyer?
- Engineering ops + SRE leaders.
- Pricing?
- Per organization or per incident.
- Defensibility?
- Integration breadth + template quality.
More inside Enterprise SaaS
- Workflow automation for revops — Lead routing, account scoring, opportunity hygiene — AI-native revops automation.
- B2B pricing experimentation — Test price + packaging changes at the customer or segment level, with attribution.
- Internal LLM copilots by role — Role-specific copilots (sales, support, ops) that know company data and respect access controls.
- Agent permissioning for SaaS — OAuth + scope management when the user is an agent, not a human.