Competitive Intelligence

News about competitors was always already inside the company. The problem was that it arrived one person at a time. A sales rep hears from a customer that a rival dropped its price. An engineer reads the rival's technical blog and learns about a new feature. The CEO hears about an acquisition from an investor. None of the three knows what the others know, and across the company nobody holds the whole picture.

The cost of that shows up most sharply in customer meetings. When a buyer says a competitor started giving that feature away last month and the rep visibly hears it for the first time, what's lost in that room isn't a feature comparison — it's the buyer's sense that this company is paying attention to its own market. The same thing happens in reverse when internal material still lists a rival's strength that the rival quietly discontinued three months ago.

Competitive intelligence exists to move that information out of one person's head and into something the team owns. This is where it parts ways with a one-off research project. Research finishes; the market doesn't, so anything not revisited every quarter sits inside the company as a statement that used to be true. A deck written for one board meeting ages into the file everyone quotes. Wrong material is worse than none. With none, people check before they walk in. With some, they don't.

It runs as a loop: narrow down what you watch, collect on a fixed rhythm, then attach judgment and hand it to the people who need it. Five steps.

1. Narrow the field. Not every competitor — the three or four a customer actually evaluates alongside you. Commit to ten and you'll be watching none of them within a quarter. Whether the shortlist is right is answered by counting where recently lost deals went.
2. Decide what to track. Pricing pages, feature announcements, job postings, customer stories, review-site ratings. Job postings earn their place because who a company hires is the earliest signal of what it plans to build.
3. Collect on a schedule. One person walks the same list on the same day each week, and there is one open channel where anyone can drop what they heard.
4. Separate fact from reading. "The starter plan disappeared from the pricing page" is a fact. "They seem to be backing out of the low end" is a reading. Blend the two into one line and a wrong reading later takes the fact down with it.
5. Push it into the places people use. Circulate the summary, and update whatever changed in the battlecard or the messaging document — the sheet that holds a product's core descriptive language. Getting the revised material into a rep's own mouth is picked up by sales enablement.

Skip step five and the other four spin freely. The most common failure is a folder of well-built monthly summaries next to a sales deck from last year. So whether the loop is working is measured by how many sentences changed because of last month's summary, not by how many summaries got sent.

One product marketer owns it, and everyone else contributes by passing along what they can see.

1. The product marketer. Owns collection, write-up, and circulation. With no named owner it becomes everyone's job, which means nobody's.
2. Sales. Passes on comparison remarks made in meetings and the actual quotes competitors put in front of buyers. The fastest and most concrete input comes from here.
3. Customer success. Passes on where churned customers went and why. Accounts running a competitor alongside you surface here too, and those teams later become the comparison evidence in a customer story.
4. Product. Judges how good a rival's shipped feature actually is. Announcement copy makes everything sound impressive. One engineer who made an account and wrote "the sync works but there's no undo" changes the weight of that launch.

The timing splits three ways. Tips come in continuously, the write-up and circulation run monthly, and anything big — a price change, a major launch — gets summarized that week regardless of the cycle. Monthly is the default because a weekly cadence leaves most weeks with nothing to report and the format survives without the content, while a quarterly one means every sales meeting in between is run on stale material.

"Is that confirmed, or are we guessing from their blog post?"

Checking whether fact and interpretation got mixed together in the summary.

"Did the competitor's new pricing make it into the battlecard?"

Asking whether what we collected reached the material people actually use.

"They hired five security engineers last quarter."

Reading job postings as a sign the rival is moving toward enterprise buyers.

At Pagedeck, Ravi sends the summary in the first week of every month. Four competitors' pricing, last month's announcements, and complaints posted on review sites go onto one page, with three lines at the top headed "what we should respond to this month." The three lines sit on top because not many people read to the bottom of the table. Two of the three usually conclude that nothing should change, and he writes those down too, because deciding not to react is still a decision.

Sofia contributes from the other direction. She writes down comparison remarks buyers make in meetings, word for word, and hands them to Ravi. Last month three different accounts brought up the same competitor's free storage tier, and Ravi rewrote that section of the battlecard. One account saying it is that customer's situation; three saying it is the competitor's strategy.

Some people assume this means digging things up covertly, because the word intelligence suggests espionage. The actual raw material is pricing pages, job postings, launch decks, and customer reviews — things anyone can look at. Booking a sales call under a false identity, or pressing a rival's customer for their contract terms, crosses into legal exposure, and the moment it becomes known it erodes the trust a company spent years building.

The other worry is that knowing competitors too well turns a company into a copycat. Companies that chase every rival announcement do exist, so the fear isn't baseless. But that's not a problem caused by having information — it's caused by having no internal standard for what to work on. With a standard, the same information produces a faster "we're not doing this." Cutting off the information doesn't improve the judgment; it just slows it down. Teams that avoid looking at competitors tend to discover the same facts anyway, six months later, from a customer who is explaining why they are leaving.