Five days to onboard a PM on your competitors

A new product manager joined us on a Monday. By Thursday she could recite our three main competitors' pricing tiers from memory. By the following month she still could not answer the only question that mattered — which of those competitors was actually moving toward our customers, and which was drifting away.

That gap is the whole problem. Competitive onboarding usually means handing someone a deck and a Slack channel, then hoping context accumulates by osmosis. It doesn't. What accumulates is trivia: tier names, feature checkmarks, a vague sense that one of them is "the enterprise one."

Here's a five-day version that produces something better. Not encyclopedic knowledge — judgment. The ability to look at a competitor's change and say whether it matters.

Day 1: Buy from them

Before anyone shows the new PM a battlecard, send them through a competitor's funnel as a customer would experience it. No internal framing, no annotations.

• Sign up for a free trial or request a demo using a personal email
• Take screenshots of every step: the signup form, the empty state, the first-run tutorial, the upgrade prompt
• Note the exact moment the product asks for a credit card or a sales call
• Write down where they got confused, and where the product felt obviously better than ours

The point isn't a feature inventory. It's a felt sense of who this competitor is built for. A PM who has sat through a competitor's onboarding has an intuition that no comparison table transfers. Our 30-minute competitor onboarding audit is a good structure for the write-up.

End the day with one paragraph: who is this product obviously for, and who does it quietly reject?

Day 2: Read the surfaces the marketing team doesn't own

Day two moves to the artifacts that leak more than they intend. Marketing pages get polished. These generally don't.

• Changelog and release notes — what shipped in the last six months, and how the cadence changed
• Job postings — which teams are hiring, what tools appear in the requirements
• Docs and API reference — objects and endpoints that exist before the feature is announced
• Integration directory — which ecosystems they're courting
• Status page history — where the system strains under load

Ask the new PM to read these without a summary layer. Reading a competitor's changelog for six months takes about ninety minutes and it is the single highest-return ninety minutes in the whole week. Patterns show up that no summary preserves: the three-month gap, the sudden burst of infrastructure work, the feature that shipped and then quietly disappeared from the docs.

Hiring is the loudest of these. As we've written before, job postings lead product announcements by a quarter or more.

Day 3: Talk to the three people who already know

Every company has internal competitive knowledge that never made it into a document. It lives in three places, and a new PM should spend day three collecting it.

• A support rep — what do customers say when they mention the competitor? Which complaints repeat?
• A salesperson who loses deals — not the top performer, the one who loses. Losses carry more information than wins.
• A long-tenured engineer — they've watched the competitor's technical choices for years and usually have an opinion about what those choices cost.

Structure each as thirty minutes with one question: "When was the last time a competitor came up, and what happened?" Specific incidents, not general impressions. General impressions are how competitive intel stops being trusted — they can't be checked, so they harden into folklore.

Day three usually contradicts day one. That's the point.

Day 4: Build a timeline, not a deck

Now assemble. The output of the week is not a battlecard — battlecards are a sales artifact and they go stale on a predictable schedule. The output is a dated timeline of what each competitor actually did over the last twelve months.

• One row per observed change, with a date and a source link
• Pricing changes, positioning changes, launches, executive hires, funding, deprecations
• A short "so what" column — left blank when the answer is genuinely nothing

The dates are the hard part. Most public surfaces don't stamp their own changes, and reconstructing when something happened from the Wayback Machine is slow, manual work. This is the part of the week where tooling earns its place: Seeto watches public competitor surfaces continuously and records each change as a discrete, dated event, so the timeline exists before the new PM starts building it. It doesn't interpret the changes or tell you which ones matter — days one through three are what makes a person able to do that. It just means nobody is reconstructing six months of history by hand.

By the end of day four the new PM should be able to point at a row and say "this one mattered, this one didn't, and here's why."

Day 5: Write down what would change your mind

The last day is the one most onboarding skips, and it's the one that converts a week of reading into a working model.

Ask the new PM to write two short lists:

• Three things I now believe about each competitor. Stated plainly, no hedging. "Competitor A is moving upmarket and will stop caring about our core segment within a year."
• What would prove me wrong. For each belief, the specific observable that would falsify it. A pricing page that adds a cheaper tier. A hiring post for an SMB sales team. A changelog that goes quiet.

That second list becomes their monitoring brief. It turns passive watching into a set of standing questions, which is the difference between a person who reads competitor news and a person who notices something in it. It also fits naturally into a weekly competitive habit once the week is over.

Beliefs with falsifiers attached age well. Beliefs without them become the folklore the next new PM will have to unlearn.

What you get at the end

Five days, one document, one person who can now argue about competitors using evidence with dates on it. The deck can wait. It was going to be stale in a quarter anyway.

The test of whether this worked isn't a quiz. It's what happens the first time a competitor ships something and everyone looks at each other. Does the new PM have an opinion — and can they say what it would take to change it?