Skip to content

Latest commit

 

History

History
124 lines (81 loc) · 11 KB

File metadata and controls

124 lines (81 loc) · 11 KB

Competitive Intelligence Methodology

This document defines what good competitive intelligence looks like. The agent uses it to produce intelligence, not just research. Every report should follow these principles.

Core principle: intelligence, not information

Information is a collection of facts about a competitor. Intelligence is the subset of those facts that changes a decision. The job is to separate signal from noise.

  • A fact is NOISE if knowing it would not change how a reader sells, builds, prices, or positions in comparison to the research subject.
  • A fact is SIGNAL if it would change one of those decisions.
  • A fact is SIGNAL if it would influence a target customer to change their mind about the research subject.

Example:

  • Noise: “Competitor offers unlimited email templates.”
  • Signal: “Competitor offers unlimited templates, which they use to win price-sensitive SMB buyers. Against enterprise buyers who value governance, this is a weakness we can exploit.”

Every finding must answer: so what? If there is no so-what, cut it or move it to context.

The executive summary comes first

The top of every report is an executive summary of 3 to 5 conclusions that actually matter. Not a description of the company. The conclusions. What is the single most important thing about this competitor right now? What is changing? Where are they strong, where are they exposed? What should the reader do differently because of this brief?

The full report is the evidence. The executive summary is the verdict. Lead with the verdict.

Specificity is non-negotiable

  • Use real product names, real numbers, real quotes, real people, real dates.
  • Cite the source of every meaningful claim.
  • If specific evidence cannot be found, say “No specific evidence found” rather than writing generic filler.
  • Never fabricate a data point that does not exist (e.g. earnings for a private company). State that it does not exist.
  • Flag when a number may be stale or when sources conflict.
  • When sources conflict, use the most reputable source.
  • Every quantitative change carries a measurement window, and the window must match the event the sentence describes. An earnings-day reaction is not a cumulative decline from a peak: “the stock fell as much as 16% the morning after the print” and “the stock is down 20% since its IPO peak” are different facts, and swapping one for the other overstates or understates the event. When sources report different windows, use the number for the window your sentence claims, and name the window in the sentence.

Freshness is a dimension of trust

Competitive intelligence decays. A figure that was true two quarters ago can actively mislead.

  • Treat the date of a source as part of its credibility, not an afterthought.
  • For any current-state claim (latest revenue, market share, who holds a role, current pricing, newest product), prefer the most recent verified figure. A recent reputable news source can override an older filing on current state.
  • When you cite a number, prefer ones you can tie to a specific period (e.g. “Q1 2026”), and reconcile to a single value when multiple periods appear.
  • If the most recent data you can verify is old enough that it may be stale, say so.

Hunt the latest news — including the bad news

Catching the moves that change the competitive picture, the moment they break, is the entire point of this tool. Every run actively searches the latest news, anchored to today's date.

  • News-first, from real outlets. Anchor recent events and current status on reputable news (Reuters, Bloomberg, The Information, CNBC, TechCrunch, major outlets) or primary documents — wherever the news actually lives. NEVER on Wikipedia, wikis, encyclopedias, or promo/SEO listicles; those are stale and gameable and are not acceptable sources here.
  • Recency sweep. Explicitly search for what happened in the last ~2-3 weeks (IPO/funding/filings, launches, partnership changes, pricing/limit changes, exec moves). A brief whose newest item is weeks old has missed the story.
  • Surface ADVERSE signals, not just wins. Deliberately hunt the things that move the picture AGAINST the subject: contract cancellations, customers churning or defecting, budget caps and usage limits being hit, outages, layoffs, lawsuits, lost deals, downgrades. A brief that catches good news and misses bad news is dangerous — it lulls the reader. Bad news about a competitor (and risks to your own side) is often the highest-value intelligence in the report.

Keep fact, claim, estimate, and sentiment separate

These are four different things and blurring them is the fastest way to lose a reader’s trust.

  • VERIFIED FACT: traceable to an audited filing, court document, contract, or reputable reporting. State plainly.
  • THE COMPANY’S OWN CLAIM: anything from their blog, PR, or marketing. Reliable for “what they say about themselves” and positioning, NOT for evaluative or market claims. Attribute it (“the company says…”).
  • ANALYST / MODELED ESTIMATE: market share, TAM, ARR estimates, analyst placements. Attribute to the firm and label as an estimate, never as a filed number.
  • SENTIMENT: what users say in reviews and forums. Always framed as sentiment, never as fact.

Also distinguish audited revenue (public companies) from company-stated ARR or metrics (private, unaudited) — say which it is.

Reading signals (what to interpret, not just report)

  • Hiring: what roles are they posting, and what does that reveal about where they are investing? Heavy engineering hiring signals product expansion. Enterprise/sales hiring signals a go-upmarket motion. Read the open JDs for the strategy behind them.
  • Leadership changes: a new exec from a specific background signals a strategic direction.
  • Funding: the amount and the investors signal ambition and what the next 12 months fund.
  • Pricing and packaging changes: a move up-market, a new usage-based tier, or a price increase is a strategic signal, not just a number.
  • Conference presence and public talks: what they choose to say publicly signals their priorities and messaging bets.
  • Product and engineering velocity (especially for technical and AI-first competitors): release cadence, changelogs, model cards, API/docs updates, status pages, and open-source activity. For these companies, shipping pace and what they ship are often a sharper signal than GTM moves — do not skip them.
  • Sentiment (structured review sites first — G2, Capterra, TrustRadius, Gartner Peer Insights — then forums and communities): what users actually say, which is often the truth the company will not state. Mine for repeated complaints and repeated praise.

The battlecard is a weapon for your side, not neutral coverage

When the brief is written for a side (you vs a competitor), it is a sales weapon for YOUR side — not an even-handed write-up of two companies. The test for whether an event belongs is not "is this recent news about either company?" but "does this change how MY side wins, loses, or handles an objection?" Scan everything happening to both companies, but the output is always asymmetric — every item is framed as "so what for us."

This drives where things go:

  • The competitor's moves are threats or openings → Recent Strategic Moves and the battlecard zones, filtered to those with a real competitive implication for us.
  • Your own side's adverse news that a buyer would raise (a major customer dropping your product, your usage limits, a public setback) → Objection Handling, with an honest, evidence-based answer. Never omit or bury it — the rep will be asked.
  • Your own side's positive/neutral events (your funding, your IPO filing) are NOT standalone Recent-Moves items — you already know your own moves. Include one only where it carries a competitive implication, framed as a so-what (e.g. your IPO filing becomes objection-handling ammunition for "is this vendor stable enough to bet on?"). No competitive so-what → leave it out.
  • Nothing appears as neutral trivia. Everything routes through "what does this mean for our position?"

The battlecard standard

Structure the battlecard in three zones:

  • WHERE THEY WIN: situations and buyer types where this competitor reliably beats alternatives. Be honest. A battlecard that pretends the competitor has no strengths is not trusted or used.
  • WHERE IT IS A FIGHT: contested situations that could go either way, and what tips them.
  • WHERE THEY ARE VULNERABLE: situations and buyer types where they are weak, with the specific reason.

For each zone, include a usable soundbite — something a person could actually say in a conversation, not an abstract bullet.

Objection handling

Ground objections in the real weaknesses and complaints surfaced from sentiment and analysis, not invented ones. For each likely objection a prospect might raise — whether citing the competitor's strength OR citing an adverse development on your own side (a customer dropping your product, your usage limits, a public setback) — provide a specific, evidence-based response that pivots to a genuine strength. The adverse-own-side objections are the ones reps most need and most often lack; surface them honestly with a real answer, never omit them.

Voice and tone

Write like a sharp human analyst briefing a colleague, not like a database emitting rows. The substance stays rigorous and decisive; the language should be natural and readable.

  • Lead with the judgment, then back it. Be direct and confident, but not combative — avoid macho or zero-sum phrasing ("you will lose", "crush them", "they're dead in the water"). Confidence reads as a clear verdict with evidence behind it, not as trash talk.
  • Prefer plain, warm sentences over clipped fragments and noun-stacks. A short paragraph a person would actually say out loud beats a terse bullet that reads like a spec sheet.
  • Keep the "so what" discipline and the specificity — real names, numbers, dates. Warming the tone never means getting vaguer.
  • It is fine to be opinionated about what matters. It is not fine to be glib, snide, or to manufacture drama the evidence doesn't support.

What this methodology cannot see (be honest about it)

This tool works from public sources. Some of the most valuable competitive intelligence is not public, and the brief should not pretend otherwise:

  • Win/loss data and real deal outcomes (the single highest-value CI input) are internal and unavailable here.
  • Actual discounting and negotiated pricing, as opposed to list pricing.
  • Private roadmap and unannounced product direction.

When a question depends on one of these, say the evidence is not publicly available rather than inferring it. Naming the limit is more credible than guessing past it.

What to avoid

  • Feature lists with no so-what.
  • Generic characterizations (“strong product”, “good for enterprises”) with no specifics.
  • Propaganda that hides the competitor’s real strengths.
  • Stating a company’s marketing claim or an analyst estimate as if it were audited fact.
  • Burying the conclusion under comprehensive detail. Distill.