Turn a competitor outage into three enterprise trials.

Radar surfaces a competitor outage discussed on Reddit and X in the morning briefing, with sentiment analysis and an estimated affected-user count. Marketing publishes a targeted "reliability-first" ad within hours, three enterprise trials start that week.

Run Radar
AuthorMariete
AgentRadar
RuntimeDaily briefing at 08:00
IndustryMarketing
  1. 1

    Describe the task

    Radar reads the public conversation about your competitors overnight, Reddit, X, status pages, support forums, and lands a briefing on your desk each morning. When a competitor stumbles, you hear about it with sentiment and scale attached, not three days later when it’s already old news.

    Tell Radar which competitors to watch, which signals mean opportunity, and how you want the briefing framed, and it will surface the moments worth acting on instead of a raw feed you have to read yourself.

    Every morning at 08:00, brief me on public sentiment about Northwind CRM and Ferro Suite. Surface: - Outages or reliability complaints on Reddit, X, and their status page - Spikes in negative sentiment and roughly how many users are affected - Any competitor incident we could respond to with a campaign For each opportunity, give me an estimated affected-user count, a sentiment read, and a suggested angle we could run within hours.

  2. 2

    Give Radar context

    Give Radar the handles, subreddits, and status pages worth watching for each competitor. It samples the conversation continuously and rolls the signal up into one briefing, so a reliability storm shows up as a ranked opportunity rather than a scroll.

    Be explicit about what counts as an opportunity. "Outage or sustained reliability complaints" is actionable, "anything negative" buries the real openings under routine grumbling that isn’t worth a campaign.

    Required context
    A competitor watch list with the handles, subreddits, or status pages to monitor
    A definition of an actionable signal, e.g. outage, sustained complaints, sentiment spike
    Optional context
    Slack connector, posts the morning briefing to your channel at 08:00
    Your ad-account or landing-page templates, so Radar can pre-draft the response angle
    A sentiment baseline per competitor, so Radar flags spikes rather than steady-state noise
    watch-list.csvsignal-rules.mdSlack (optional)
  3. 3

    What Radar creates

    Radar delivers a ranked morning briefing: what happened, how loud it is, how many users it touches, and the angle you could run. Below is a captured briefing from the morning a competitor’s auth service went down.

    From Radar: Morning briefing, 08:00: one high-priority opportunity: a Northwind CRM login outage trending on Reddit and X.

    ~2,400Affected users (estimated)
    -71%Sentiment vs baseline
    3 hrFrom briefing to live ad
    High-priority opportunities1 signal
    CompetitorSignalReachSentimentSuggested angle
    Northwind CRMLogin outage, 2+ hours~2,400 usersSharply negativeRun a "reliability-first" ad to their frustrated users
    Monitoring: no action yet2 signals
    CompetitorSignalReachNote
    Ferro SuiteScattered billing complaintsLowRoutine grumbling, below opportunity threshold
    Northwind CRMFeature-request threadModerateWorth watching, not campaign-worthy

    "Northwind’s login has been down about two hours and roughly 2,400 users are venting on Reddit and X. This is a clean reliability-first opening: want me to draft the ad copy and a landing page so you can be live within the hour?"

  4. 4

    Follow-up prompts

    Draft the reliability-first campaign

    While the outage is still trending, ask Radar to turn the signal into ready copy, ad variants and a landing headline aimed at the exact frustration users are posting about.

    Draft three "reliability-first" ad variants and a landing-page headline targeting Northwind users hit by today’s login outage. Reference uptime and migration ease without naming the outage directly.

    Push the briefing to Slack at 08:00

    With the Slack connector, the morning briefing lands in your channel before stand-up, ranked opportunities first, so the team walks in already knowing where to move.

    Post the 08:00 briefing to #competitive-intel each morning: high-priority opportunities first with reach and sentiment, then a short monitoring section.

    Track how the response performed

    After the campaign runs, ask Radar to tie the competitor incident back to your trial signups so you can see which opportunistic responses actually converted.

    Correlate this week’s reliability-first campaign with new enterprise trial starts, and tell me which competitor incidents drove the most signups.

  5. 5

    Tips and troubleshooting

    Define opportunity, not just negativity

    Every competitor has steady low-level complaints. Tell Radar the bar, sustained outage, sentiment spike, mass complaint, so the briefing surfaces openings you can act on rather than background noise.

    Move while the signal is hot

    The affected-user estimate decays fast. A reliability-first ad shipped within hours reaches frustrated users still mid-migration-decision; the same ad two days later lands on an empty audience.

    Give Radar a sentiment baseline

    A spike only means something against a normal. When Radar knows each competitor’s typical sentiment, it flags real deterioration instead of treating an ordinarily grumpy forum as breaking news.

  6. Ready to try it yourself?

    Let Radar read the overnight conversation so a competitor’s bad morning becomes your reliability-first ad, live within hours, not a missed window.

    Run Radar