Public outage or incident
A company posts a major incident on its status page, or an outage spreads on social media.
An outage puts reliability, monitoring, and incident response on the leadership agenda overnight. Budgets that were hard to get last week get approved in the review that follows.
- Strength
- Good
- Act within
- The 30 days after the incident
- Best for
- Companies selling observability, security, infrastructure, and support tools
How we detect it
Runs on Apify, Clay, and Statuspage.
- Monitor public status pages for your accounts and keep the incidents that lasted hours or touched core services.
- Wait for the postmortem when there is one, since it names what will change.
What it triggers
An opening line, to show the angle. It never goes out as written.
After a long incident, the postmortem usually names 2 or 3 fixes and funds 1. If alerting is on that list, we can show you what other teams changed.
- Content: Share a postmortem guide or a playbook for the failure type, with no pitch.
- Email: Write to the engineering leader after the postmortem, about the fix it calls for.
Where it goes wrong
- Reaching out during the outage. Wait a week.
Stack it with
A second signal on the same account moves it up.
Competitor has a bad week
A competitor raises prices, has an outage, is acquired, or sunsets a product.
New compliance or security mandate
An account takes on a new compliance, security, or regulatory requirement, such as a SOC 2 audit, a new regulation, or an enterprise customer’s security review.
More company moments signals
Every company moments signalFunding round
A target account announces a new round of funding.
New office or market expansion
An account opens a new office, enters a new country, or announces a new region.
Product launch
An account launches a new product, a new tier, or a major feature.
FAQs about this signal
A company posts a major incident on its status page, or an outage spreads on social media. An outage puts reliability, monitoring, and incident response on the leadership agenda overnight. Budgets that were hard to get last week get approved in the review that follows.
Monitor public status pages for your accounts and keep the incidents that lasted hours or touched core services. Wait for the postmortem when there is one, since it names what will change. Understory Agency runs it on Apify, Clay, and Statuspage.
The window to act is the 30 days after the incident. Understory Agency routes it to content and email. Share a postmortem guide or a playbook for the failure type, with no pitch. Write to the engineering leader after the postmortem, about the fix it calls for.
It works best for companies selling observability, security, infrastructure, and support tools. It is strongest alongside “Competitor has a bad week” and “New compliance or security mandate”.
Or let us run it for you
Understory Agency's GTM engineers build the detection in Clay, wire it to the play that fits, and sync every touch to your CRM. Tell us who you sell to, and we'll show you where we would start.