What happens today
The patchwork
- A support-down thread you find three days late
- Someone forwarding a screenshot in Slack
- Guessing whether it is a blip or a real fire
- A campaign that lands after the anger cools
Radar playbook
Catch a competitor outage
Three new trials the same week.
- 5 min read
- Intermediate
- 4 moves
- Always on
The number
You catch a competitor outage and log three new trials the same week.
Same day
The situation
From a feed you scroll to a signal you act on.
Point Radar at a competitor and it watches Reddit and Twitter for the outage the moment it starts: reading how many people are affected, how angry the thread is getting, and pinging your team so marketing can reach out to switchers the same day.
With Radar
The workflow
- One always-on watch across every public feed
- Every alert carries the blast radius and the mood
- A reach-out angle in the format your team ships
- You catch a competitor outage and log three new trials the same week.
How the work moves
Four moves.
Radar runs each move with a preview attached, so you know what lands before you ever hit send. Skip freely once you know which parts carry the weight.
Radar at work
One brief travels through the whole job. Context stays attached until the finished work lands.
Watch
Add the competitor by URL. Radar starts watching Reddit and Twitter.
Radar builds the profile from the homepage and its collectors start running: no keyword list to babysit, no dashboard to refresh.
Detect
It picks up the outage the moment the thread starts filling.
Sources are pulled, cleaned, and cross-checked in real time, so a genuine outage is separated from routine grumbling before it reaches you.
Gauge
Radar reads how many are affected and how angry.
The alert names the blast radius and the sentiment, so you can tell a five-minute blip from a lost-my-data meltdown and decide whether it is worth a move.
Move
It pings your team with the angle. Reach out the same day.
A ready-to-send reach-out lands in the format your team already uses: you edit the last 10%, not the first 90%, while the anger is still fresh.
Prompts worth keeping
Paste these into Radar.
Three prompts, a kickoff, a full run, and a packaging pass. Copy the one that matches the phase you're in. Rewrite any detail to fit your business.
Kick it off
You are Radar. I want to catch a competitor outage: add my competitor by URL and watch Reddit and Twitter for signs they are down. When an outage starts, read how many people are affected and how angry the thread is getting, and ping me so I can move. My goal: catch a competitor outage and win switchers the same day. Walk me through the first move and tell me what you need from me.
Run it in one shot
Run the full playbook end-to-end: add the competitor by URL and start watching. Detect an outage the moment the thread fills. Gauge how many are affected and how angry. Ping my team with a same-day reach-out angle. Ask before skipping any step. Show work as you go.
Package the output
Deliver the output as a single alert I can drop to the team: lead with "Same day", then the receipts: the blast radius, the sentiment, and the reach-out angle. Call out anything that changed the read mid-thread.
What goes in. What comes back.
Inputs in, outputs out.
Radar runs on the inputs on the left and hands back the artifacts on the right. Skip any input, the agent will ask for it the first time it needs it.
Give it
- The competitor's URL
- The feeds worth watching (Reddit, Twitter, and more)
- The switcher angle you want to lead with
Get back
- A real-time alert with blast radius and sentiment
- A same-day reach-out you can forward
- A note the moment the outage escalates or clears
The finished artifact
A finished alert, not a todo list.
Every run ends the same way, a packaged alert in the channel your team already reads. Here's a preview of what shows up.
Radar → your team
Competitor outage live: reach out today
playbooks
Now · 2:14 PM
Their status thread is filling up right now. I picked up the outage as it started, gauged how many are affected and how angry, and packaged a same-day reach-out for Slack and the shared drive.
- Add the competitor by URL. Radar starts watching Reddit and Twitter.
- It picks up the outage the moment the thread starts filling.
- Radar reads how many are affected and how angry.
- It pings your team with the angle. Reach out the same day.
What moved
Same day
You catch a competitor outage and log three new trials the same week.
alert.pdf · threads.csv · outreach.md
Before you run it
Where teams stall.
Three ways we see this go sideways and how to avoid each one.
Keep judgment with the team. The playbook should make the work clearer, not hide the assumptions behind it.
- Chasing every grumble. Let Radar gauge the blast radius first, so you only move on an outage that is actually hurting.
- Reading the alert tomorrow. The window closes fast: reach out while the thread is still angry, not after it cools.
- Sending a generic line. Lead with the specific pain the thread is voicing, so the switcher feels seen instead of sold to.
Questions
Before you start.
It watches Reddit and Twitter continuously, so it picks up the thread as it starts filling rather than on a schedule. The alert reaches you in real time: the whole point is to move the same day, while the anger is still fresh.
Radar gauges the blast radius and the sentiment before it pings you: how many people are affected and how angry the thread is getting. A five-minute blip and a lost-my-data meltdown read very differently, and the alert tells you which one you are looking at.
Marketing or growth owns it. The output is a same-day reach-out angle, so whoever runs switcher campaigns is the natural owner; they decide whether the outage is worth a move and send the outreach while the window is open.
Set the threshold on blast radius and sentiment, and Radar stays quiet until an outage clears it. You get the same-day heads-up for the fires that matter and none of the noise from every minor hiccup.
