Enterprise SaaS · sub-niche
Runbook from doc generators.
Generate executable runbooks from existing docs + Slack messages + incident history.
Month-long buildTrickle — one deal per quarter
Why now
Runbooks are written once and never updated. AI keeps them living.
What the signal looks like
Repos with documentation-ingest libraries, step-extraction models, and runbook-execution 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 / Incident.io adjacency
- Cortex / OpsLevel runbook shape
- Open-source runbook libraries
What this displaces
A Confluence page from 2020 that the on-call doesn't trust.
Our build-vs-invest call
Niche but durable. The wedge is the doc-ingest accuracy + the runbook-execution integrations.
Common questions about this niche
- Buyer?
- SRE + platform engineering teams.
- Pricing?
- Per service or per organization.
- Moat?
- Doc-ingest accuracy + executability.
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.