Key Intelligence Topics (KITs): How to Focus Competitive Intelligence
Learn how to turn broad business priorities into Key Intelligence Topics and answerable questions that keep competitive intelligence focused, useful, and actionable.
Key Intelligence Topics (KITs) are the few external issues leaders need to understand to make better decisions. A useful KIT names the decision, the uncertainty around it, and the evidence that would change the response. It then breaks that priority into answerable Key Intelligence Questions, owners, sources, and a review cadence—preventing competitive intelligence from becoming an endless collection exercise.
Key takeaways
- ✓ Tie each KIT to a real decision and named stakeholder
- ✓ Turn the topic into a small set of answerable intelligence questions
- ✓ Define evidence, sources, owners, and decision triggers
- ✓ Review the portfolio and retire questions that no longer matter
What are Key Intelligence Topics?
Key Intelligence Topics are a short, prioritized set of external issues that matter to leadership decisions. They give a competitive-intelligence program its agenda. Rather than asking a team to “keep an eye on competitors,” a KIT identifies what the business is trying to decide, what it does not yet know, and why resolving that uncertainty matters now.
The concept is commonly associated with Jan Herring’s work on intelligence requirements in business. Its enduring value is not the acronym; it is the discipline of letting decisions shape collection. Websites, reviews, earnings calls, job postings, sales notes, and market reports are possible sources—not the work itself. A KIT tells the team which evidence deserves attention and what it should be used to decide.
KITs usually sit above Key Intelligence Questions, or KIQs. The topic describes the priority area; the questions make it researchable. A topic such as “a competitor’s enterprise expansion” is still too broad to collect against consistently. Questions such as “Which regulated industries are appearing in new proof?” or “Which capabilities are moving behind enterprise packaging?” create observable research tasks.
KITs, KIQs, and signals are different layers
Teams often mix three layers together. The KIT is the strategic concern. The KIQ is the question that reduces uncertainty. A signal is a piece of evidence that may help answer the question. Keeping those layers separate prevents a dramatic signal from rewriting strategy before it has been interpreted.
Suppose a rival hires a vice president of enterprise sales. The hire is a signal, not a conclusion. It may support a question about an upmarket move, but it becomes more meaningful when paired with enterprise packaging, security investments, partner activity, or customer proof. The KIT holds the pattern together and defines what combination of evidence should trigger a response.
This hierarchy also makes automation safer. Software can detect and organize changes, but the team still needs to decide which question a change informs, how reliable it is, and whether the accumulated evidence crosses a decision threshold.
- KIT: What important external issue could change a business decision?
- KIQ: What specific question must be answered to reduce that uncertainty?
- Signal: What dated, attributable evidence helps answer the question?
- Implication: What does the evidence mean in the company’s context?
- Action: What should change now—or what should the team continue watching?
The three practical types of KIT
A useful planning session can group priorities into three practical types. Strategic-decision KITs support a choice already approaching: entering a segment, changing packaging, repositioning a product, or responding to consolidation. Early-warning KITs look for conditions that could create a threat or opportunity: a new entrant gaining proof, a rival building a channel, or buyer language shifting. Operating KITs keep recurring workflows current, such as competitive deals, launches, pricing reviews, and battlecard maintenance.
The categories are less important than balance. A portfolio made entirely of early warnings produces anxiety without decisions. A portfolio made entirely of immediate deal questions never creates a view of where the market is going. Lean teams usually need only three to five active KITs across these horizons. More priorities often mean none are truly prioritized.
How to write a strong KIT
Start with a decision interview, not a blank template. Ask the stakeholder what decision is approaching, what they currently believe, what uncertainty could change their choice, and when the answer becomes too late to use. This exposes whether the request is an intelligence need or simply a desire for background information.
Write the KIT as a question with a boundary and consequence. “Monitor Acme” has no finish line. “How is Acme changing its offer for midmarket finance teams, and what evidence would require us to adjust our Q4 positioning?” identifies the competitor, segment, type of movement, decision, and time horizon.
Then write three to seven KIQs. Each should be answerable with evidence and useful even if the answer is “we do not know yet.” Avoid questions that require mind-reading, such as “What is the competitor secretly planning?” Ask what direction is supported by observable product, packaging, hiring, partnership, proof, and buyer signals.
Finally, define the response threshold before new evidence arrives. A single landing-page edit might warrant logging. A coordinated change in packaging, sales hiring, and enterprise customer proof might trigger a positioning review. Agreeing on those thresholds early reduces both overreaction and institutional delay.
- Decision: What choice will this intelligence improve?
- Owner: Who can act on the answer?
- Time horizon: When is the answer needed, and when should it be reviewed?
- Current hypothesis: What does the team believe today?
- KIQs: Which specific uncertainties must be resolved?
- Evidence plan: Which primary and secondary sources can answer them?
- Trigger: What finding would cause action, escalation, or retirement?
A complete KIT example for a lean B2B SaaS team
Imagine a five-person marketing team preparing an enterprise launch. Leadership worries that two established rivals are moving downmarket while newer vendors are moving upmarket. The business decision is whether to lead with governance and control, speed to value, or a narrower industry position.
The KIT becomes: “How are competitors changing their offers for enterprise operations teams, and which changes should alter our launch positioning before October?” KIQs cover target industries, packaging fences, security and governance claims, new integrations, implementation promises, customer evidence, partner motion, and the objections appearing in current deals.
The evidence plan assigns public product and pricing changes to automated monitoring, job and partner signals to a monthly review, and buyer language to sales-call and win-loss feedback. Every item keeps its source and date. A weekly brief reports only meaningful movement; a monthly synthesis states what the pattern means for the launch.
The trigger is explicit: if either direct rival adds credible proof in the chosen industry and removes a major implementation objection, product marketing will re-test the lead message and update the competitive talk track. A new feature announcement alone does not cross the threshold. That distinction is the practical benefit of the KIT.
Build a collection plan without creating a surveillance project
Once the questions are clear, map the minimum source set that can answer them. Start with primary evidence: official product documentation, pricing and packaging, release notes, regulatory filings, executive statements, job descriptions, partner directories, and dated customer proof. Add secondary evidence—reviews, analyst coverage, community discussion, sales observations—to challenge or contextualize the company’s own claims.
Match cadence to volatility and cost. Pricing and product pages may justify daily automated checks. Earnings calls arrive quarterly. Review themes need a sample over time, not an alert for every new rating. Buyer feedback belongs in a recurring field loop. Collection should expand only when a question cannot be answered with the current plan.
Preserve the difference between fact and inference. “The enterprise plan now includes audit logs” is an observation. “The company is moving upmarket” is an interpretation that may require corroboration. Record both, but label them correctly and retain the source, capture date, and before-and-after evidence.
Turn answers into decisions, not another research archive
A KIT is successful when its answer reaches the workflow attached to the decision. Deal-related intelligence should update discovery questions and objection guidance. Market-direction intelligence should enter positioning and planning reviews. Pricing evidence should reach the owner of packaging decisions. Early warnings should have a named escalation path.
Use a compact update format: what changed, why it matters to this KIT, confidence, recommended action, owner, and next review condition. If the evidence does not justify action, say so and name what would change that judgment. “Watch and wait” is useful when it is specific; it is avoidance when no trigger is defined.
Retire KITs deliberately. A decision may be complete, the hypothesis may be disproved, or another issue may become more important. Preserve the conclusion and evidence trail, then remove the topic from active collection. A smaller live portfolio creates more trust than a dashboard full of permanently open priorities.
How to measure whether KITs are working
Do not judge a KIT system by the number of sources watched or alerts produced. Those are operating inputs. Measure whether priority questions receive credible answers in time, whether stakeholders use those answers, and whether the resulting actions are completed.
A simple quarterly review can examine decision coverage, answer freshness, time from material signal to action, and the share of updates that produced a decision, workflow change, or explicit no-action call. Also ask stakeholders which important development surprised them. Surprises reveal blind spots in questions or sources more clearly than raw alert volume.
For a lean team, the strongest sign is behavioral: competitive intelligence stops arriving as emergency research and starts appearing as a normal input to positioning, launches, pricing, and sales decisions.
A worked example
A B2B SaaS company plans to move upmarket. Instead of creating the vague watch item “Track enterprise competitors,” the PMM defines a KIT: “How are direct competitors changing their enterprise go-to-market motion, and what would require us to adjust our positioning or launch plan?” The team watches packaging, security documentation, enterprise proof, senior sales hiring, partnerships, and buyer feedback. Each signal answers a specific question; no single signal is treated as proof of a strategy.
Notice what the example does not do: it does not jump directly from observation to imitation. The team first establishes what changed, who is affected, and what tradeoff the competitor’s move creates. That makes the eventual response more specific—and often much smaller—than the first anxious request.
It also leaves a trail another person can audit. If the underlying evidence changes, the recommendation can change with it. That is the difference between a living intelligence system and a confident paragraph that quietly ages inside a slide deck.
What to measure
Common mistakes to avoid
- Starting with a tool or template instead of a decision.
- Repeating a competitor claim without checking the original source and date.
- Confusing a single observation with a durable strategic pattern.
- Publishing research without updating the workflow where someone will use it.
Sources and research notes
Pricing and packaging change. The sources below are the evidence available when this article was updated; they are not a substitute for a current written quote from the vendor.
Frequently asked questions
What does KIT mean in competitive intelligence?
KIT stands for Key Intelligence Topic: a prioritized external issue that an organization must understand to make a better decision. A KIT is normally broken into specific Key Intelligence Questions, evidence sources, owners, timing, and action triggers.
What is the difference between a KIT and a KIQ?
A KIT is the broader strategic priority; a Key Intelligence Question (KIQ) is one answerable question within it. For example, an enterprise-expansion KIT might include KIQs about packaging, security investment, customer proof, sales hiring, and partnerships.
How many Key Intelligence Topics should a team have?
There is no universal maximum, but a lean team is usually better served by roughly three to five active KITs. The constraint should be the team’s capacity to collect reliable evidence, synthesize it, and support an actual decision—not the capacity of a monitoring tool.
How often should KITs be reviewed?
Review active evidence at the cadence the decision requires, and review the KIT portfolio at least quarterly or whenever strategy changes materially. Retire a KIT when the decision is complete, the question is no longer important, or a higher-priority uncertainty replaces it.
Can AI create Key Intelligence Topics?
AI can help structure stakeholder notes, suggest questions, classify signals, and summarize evidence. Leadership and the decision owner still need to choose the priorities, define what would change a decision, and judge whether the evidence is strong enough to act.