Why weekly competitor research dies
Every team starts strong. Someone volunteers to send a Friday digest. The first three weeks are great. By week six, the digest is one person's part-time job and it lands at 6pm on a Friday when nobody reads it.
The problem isn't the cadence, it's the cost of producing it. Pulling launches, pricing changes, news, and ads every week, by hand, across a dozen rivals, is a job you cannot keep volunteers in.
The fix isn't more discipline. It's making the digest cost zero to produce so it actually shows up.
How a signal gets to your inbox
Every Monday morning, the same pipeline runs across your watchlist. By the time you open the email, the noise has already been filtered out.
- 01
Watch every move
Across each company on your list, we capture launches, pricing changes, news, ad shifts, blog posts, and traffic deltas from the week.
- 02
Score by impact
Each signal gets a score: how big the change is, how close it sits to your business, how fresh it is, and how unusual it is for that company.
- 03
Cut the long tail
Anything below the threshold gets dropped. A blog post about office snacks doesn't make the cut. A $20 pricing increase does.
- 04
Group by company
Multiple signals from the same rival get bundled so you don't read four headlines about the same launch in different sections.
- 05
Send Monday morning
Lands in your inbox before standups. Ten-minute read, click anything to jump to the relevant profile section.
What's actually in the email
The digest is short on purpose. Four sections, ranked, with the headline and a one-line 'why this matters' for each item.
If you only have two minutes, you read the first section and you're done.
Top moves
The two or three signals with the highest impact score this week. Launches, pricing changes, leadership moves. Read this if nothing else.
Pricing & packaging
Anyone who changed a plan, a price, a free-tier limit, or a discount this week. With the diff inline.
Marketing shifts
New paid keywords, fresh ad creatives, big content swings, social pushes. The places they're spending attention.
Quiet but worth it
The slow-burn signals: review trends, traffic deltas, hiring patterns. Not urgent, but worth a glance once a week.
What you do with the digest
The point of the email isn't the email. It's that everyone on the team starts the week with the same picture, without anyone having to write the picture.
The main payoff
Keep your team aligned
Forward to your channel, paste into a standup doc, or pin it in Slack. Sales, product, and marketing read the same five bullets and stop arguing about whose summary is right.
Open the profile in one click
Every signal in the digest links straight to the right section of the right profile. No hunting, no copy-paste back into your tools.
Tune what you see
Mark a signal as 'more like this' or 'less like this' and the score weights adjust for next week. The digest gets sharper the more you use it.
Build the archive
Every digest is saved. Look back at any week to see what the market was doing then, useful for retros, board prep, and 'when did they launch X' questions.
Common questions
Still weighing it up?
Why Monday morning?
Most teams plan their week on Monday. Landing the digest before the first standup gives you something to point at instead of opening the meeting with 'did anyone see what they shipped?'.
Can I change the cadence?
Yes. Daily, weekly, or monthly, per watchlist. Most teams settle on weekly because daily turns into noise and monthly is too late to act on.
How do you decide what's important?
Impact score is a weighted blend of size of change, proximity to your business, recency, and how unusual it is for that company. You can also tune it by marking signals up or down.
What happens during a quiet week?
The digest stays short. If nothing material happened, you get a one-line note saying so, no padding. Some weeks the email is two sentences, that's a feature, not a bug.
Can I get this somewhere other than email?
Yes. Slack, Teams, and a webhook for piping into your own tools. The web version is always there too.
