Alerts
A question that fires
A monitor is a saved analysis that becomes a signal. When persistence, republication, a price change or a volume spike crosses the rule, the team is told - with the proof attached.
The monitor
A rule on the series, not a model guess.
Anomaly score
Mentions versus rolling baseline. Flag when z-score exceeds 2.
7d · vs previous 7 days · as of 27 Aug, 07:42
Threshold
z > 2
Named facts, then a page
Alerts fire on facts you can name: a story that persists, a page that disappears, a republication, a volume spike. Not a guess. If you cannot say what would fire, do not save it.
A monitor is a saved analysis. Keyword soup is not a monitor. Production alerts sit on items already in the feed.
Delivery where work happens
Slack, email, Teams, webhook. Terrain skins can go to WhatsApp or SMS when the pack is notification-first. Quasi real time means minutes on priority sources, not a promise of the second it published.
The payload is the item: source, date, link. Incident channels should not receive a paragraph with the dates stripped. COMMAND fans out per client without mixing brands.
Alerts is not a second corpus. If the item is not in the feed, the view is empty. That emptiness is the product being honest.
Questions we get
- Is it real time?
- Quasi real time: minutes on priority sources, with cadence, timezone and quiet hours. Not a one-second stream of the whole web.
- Do you cover everything?
- No. Public pages in the workspace or pack. Official sources, company sites, documented providers. Exhaustiveness is not the offer.
- What if the audit finds nothing?
- We do not sell. The dated sample is yours to keep. That is the wedge, not a trial of empty dashboards.
- Who is the client?
- A B2B workspace. Particulars, candidates, buyers and creators are never the client. At most a channel the customer already uses.
See it on your market
The first meeting is a dated audit. If the backtest is empty, we do not sell.
Then sources, cadences, the first monitors. Minutes on priority sources.