Don't hire a competitive intelligence analyst yet

Who will read what this person writes?

If you can't name the reader and the decision they make with it, don't open the requisition. A first competitive intelligence hire at a 30-to-150 person SaaS company is usually a response to a feeling: we lost two deals, a rival launched something, the board asked a question nobody could answer. The feeling is real. The hire is the wrong fix.

The analyst inherits a job with no shape

Picture week one. The new analyst asks what you want to know. Sales wants battlecards. Product wants a feature matrix. Marketing wants positioning. The CEO wants "a view on the market."

None of those is a question. They are output formats.

So the analyst does the reasonable thing and produces all of them. By month three there is a Notion space, a monthly digest and a 40-row matrix. By month six the digest open rate is in single digits, and the analyst spends Fridays updating a matrix that one person checks before a renewal call. We wrote about this pattern in count decisions, not competitor reports: volume of output is the metric a shapeless job falls back on.

The analyst didn't fail. The company hired a person to discover what it wanted, and gave them no authority to decide it.

Most of the job is watching, and watching doesn't need a salary

Look at what a junior CI analyst actually does hour by hour. They open pricing pages. They check changelogs. They scan job boards, docs, release notes and review sites. They notice that a plan got renamed or a limit moved from 5 seats to 3.

That is collection. It is repetitive, it has to happen on a schedule, and humans are bad at it. People skip a week. They compare against memory instead of against the last version. They miss the change on the page they checked on Tuesday because it shipped on Wednesday.

This is the part a tool should own. Seeto, for example, checks a competitor's public pages continuously and reports each change as a separate event: this price moved, this plan lost a feature, this docs page appeared. It doesn't write the analysis for you, and it doesn't replace someone reading carefully. It removes the part of the job that nobody should be paid to do by hand, as we argued in tracking a competitor by hand.

Hire before you automate collection, and you pay a skilled person to be a cron job.

Three conditions that make the hire worth it

A CI hire earns their seat when all three of these are true:

• A standing question with an owner. "Why do we lose to Competitor X in mid-market?" asked by the VP of Sales, reviewed every month. Not "keep an eye on the market."
• Collection already runs without them. Changes arrive as events. The analyst starts the day with a list of what moved, not a list of tabs to open.
• More signal than one person can interpret. You track enough competitors and surfaces that the founder or PM can't read the change feed in 20 minutes a week. Our guide on how many competitors to track puts that line higher than most teams expect.

If only the first is true, give the question to an existing PM for a quarter. If the first two are true, you probably still don't need the hire. If all three are true, hire, and hire for judgment rather than diligence.

What to do instead, this quarter

Write down the two or three questions that would change a decision this year. Assign each one to a person who already makes that decision. Point a monitoring tool at the competitors those questions touch. Review what changed once a week, in a meeting that already exists.

After a quarter you will know which questions produced decisions and which produced only notes. That list is the job description. It is also the best interview prompt you will ever have: "Here is what we learned. What would you have seen that we didn't?"

The best competitive intelligence analyst you'll hire is the one who walks into a job that already has questions, already has a feed, and only lacks a mind sharp enough to connect them.