Your first 30 days owning competitive intel

Someone forwarded you a Slack thread that ended with "can you own this?" and now the competitor question is yours. No handoff doc, no dashboard, maybe a stale spreadsheet from two reorgs ago. The instinct is to open a blank page and start reading everything at once. Don't.

The first month is not about being comprehensive. It's about building something small that survives contact with your calendar. Here's a week-by-week version that gets you from zero to a shipped briefing without a hero sprint you can't repeat.

Week 1: Inventory what already exists

Before you track anything new, find out what the company already believes about its competitors — and where those beliefs live.

• Ask sales for their last three lost-deal notes. Loss reasons are the most honest competitive intel you'll ever get, and nobody has to guess.
• Search Slack for competitor names. You'll find scattered screenshots, one-off "did you see this?" threads, and at least one abandoned channel.
• Pull the old spreadsheet, if there is one. Note what's stale, not just what's there. A pricing column last touched in Q1 is a lie by omission.

The output of week one is not analysis. It's a single list: who we think we compete with, and what we currently (mis)believe about each.

Week 2: Cut the list, then map the surfaces

Your inherited list is too long. It always is. Tracking too many competitors is the fastest way to track none of them well.

• Rank by how often each name shows up in lost deals, not by who's biggest or loudest.
• Keep three to five. Everyone else goes on a "glance quarterly" bench.
• For each survivor, write down the public surfaces worth watching: pricing page, changelog, careers page, docs, status page. You don't need all of them — pick the two or three that actually move for that specific competitor.

By Friday you should have a short, named list of pages, not a vague sense of "watching the market."

Week 3: Set a cadence you can actually keep

The failure mode of new CI owners is treating month one's energy as the baseline. It isn't. Design for the tired version of yourself.

• Decide a rhythm: a 20-minute weekly pass, a monthly written summary. Put both on the calendar as real events.
• Write down what counts as a signal worth flagging versus noise. A new pricing tier is a signal. A hero-image swap is not. If you skip this, you'll drown in changes that don't matter.
• This is where the manual approach quietly breaks. Checking five pricing pages by memory every week means you notice the change you were already looking for and miss the one you weren't. Seeto monitors those public surfaces continuously and surfaces the diffs as discrete change events, so week three becomes reviewing what actually moved instead of re-reading pages that didn't. It won't transcribe a competitor's podcast or hand you a strategy — that reading is still your job — but it removes the "did anything change?" tax.

Week 4: Ship one briefing, then stop

Your first deliverable should be almost embarrassingly small. A one-pager beats a deck nobody reads.

• Lead with what changed this month and why anyone should care. Three bullets is plenty.
• Attribute every claim to a surface: "their docs now list a SOC 2 report" beats "they seem to be going upmarket."
• Send it to the two people who asked, not the whole company. Distribution is earned by being useful twice, not by being loud once.

Then close the laptop. You've proven the loop runs. Month two is about repeating it, not expanding it.

What good looks like at day 30

You will not be an expert on your market in a month, and anyone who claims to be after four weeks is guessing. What you can have by day 30 is a short competitor list, a mapped set of surfaces, a cadence on the calendar, and one shipped briefing that named real changes. That's a working program. A one-person program that survives beats an ambitious one that collapses in week six.

The competitor question isn't answered in thirty days. It's made repeatable in thirty days. Build the loop small enough to keep, and let it compound.