Competitive intelligence program · 14 min read · Updated 2 Aug 2026
Competitive Intelligence Program Charter Template (Free)
A blank competitive intelligence program charter you can fill in today, plus the guidance for what belongs in each field. It is the founding document for a CI function: what it is for, what it will not do, who it serves, what it delivers and on what cadence, and the ethical boundaries it operates inside.
Copy pastes straight into Google Sheets or Excel with the columns intact. Downloads are free with a work email.
The competitive intelligence program charter template
This is exactly what you get when you copy or download. Blank fields are yours to fill in; each table ships with one example row to show the pattern, which you delete.
Charter details
Fill this in first. A charter without a named executive sponsor is a proposal, and proposals do not survive their first budget cycle.
- Program nameWhat this function is called internally
- Executive sponsorNamed, and senior enough to defend the budget
- Program ownerThe person accountable day to day
- Effective dateWhen this charter takes effect
- Review dateAnnually at minimum, or after any reorganisation
- Version and approvalWho approved it, and when
1. Mandate and objectives
First row is an example, delete it. Three to five objectives. Each one must be something a person outside the team could tell you had happened.
| Objective | What it means in practice | How we will know it is working |
|---|---|---|
| ExampleCompetitive losses are understood, not guessed at | Every lost deal above a threshold gets a buyer-sourced reason within 30 days | Loss reasons come from buyers rather than reps in most closed deals |
2. In scope and out of scope
First row is an example, delete it. The out-of-scope rows matter more than the in-scope ones. Write at least three of them.
| Area | In or out | Rationale | Who owns it instead |
|---|---|---|---|
| ExamplePricing decisions | Out | We supply the competitive input; we do not set price | The pricing group |
3. Stakeholders and what each receives
First row is an example, delete it. One row per function. If a stakeholder cannot name a decision they make, they are an audience rather than a stakeholder.
| Stakeholder | Decisions they make | What we provide | How often |
|---|---|---|---|
| ExampleSales | How to position against a named competitor in a live deal | Battlecards and one-pagers, kept current | Updated within 5 working days of a material change |
4. Deliverables, cadence and service levels
First row is an example, delete it. Commit only to what you can sustain with current headcount. An unmet cadence damages the program more than a modest one.
| Deliverable | Audience | Frequency | Owner | Service level |
|---|---|---|---|---|
| ExampleCompetitive intelligence report | Product, marketing and sales leadership | Quarterly | CI program owner | Delivered within 5 working days of quarter end |
5. Ethical and legal boundaries
First row is an example, delete it. Write the prohibited practices explicitly. A boundary that exists only in someone's judgement is not a boundary.
| Practice | Permitted? | Why | What to do instead |
|---|---|---|---|
| ExampleSigning up for a competitor's public trial under our own company name | Yes | Public offer, honest identity, terms observed | Not applicable |
6. Sources and tooling
First row is an example, delete it. List what you actually use, with the cost. This table is what a budget conversation will ask for first.
| Source or tool | What it covers | Annual cost | Owner |
|---|---|---|---|
| ExampleCompetitor website and pricing monitoring | Pricing, packaging and positioning changes across 6 competitors | Stated figure | CI program owner |
7. How the program is measured
First row is an example, delete it. Four to six measures. Avoid anything that rewards producing more documents.
| Measure | Target | How it is collected | Why this and not volume |
|---|---|---|---|
| ExampleCompetitive win rate against named rivals | Improve by 4 points over 4 quarters | CRM, on deals where a competitor was tagged | It is the outcome the program exists to move |
8. Approval, review and open decisions
First row is an example, delete it. Record what was agreed and what was deliberately left open, so the next review starts from the right place.
| Item | Decision | Owner | Date | Revisit at |
|---|---|---|---|---|
| ExampleHeadcount for the first year | One full-time owner plus 0.4 of a sales enablement partner | Elena V., CEO | 1 Sep | Annual charter review |
How to fill in your competitive intelligence program charter
How to scope a competitive intelligence program charter
A charter is the founding document for a competitive intelligence function, and its most important field is the executive sponsor. Programs without one are proposals, and proposals do not survive their first budget cycle regardless of how good the work is. The document exists to answer three questions before anyone asks them under pressure: what is this function for, what will it deliberately not do, and how will we know whether it worked.
Program name
Whatever it is called internally. Worth noting that competitive intelligence, market intelligence and competitive enablement describe overlapping but different remits, and picking the name is partly picking the scope.
Executive sponsor
Named and senior enough to defend a budget line. The sponsor's function shapes the program more than anything else in this document: sponsored by sales it becomes enablement, by product it becomes roadmap input, by strategy it becomes market analysis. None is wrong; drifting between them without noticing is.
Program owner
The person accountable day to day, which is frequently a fraction of one person's time in the first year. Say so if that is the case, since a charter implying a full-time function that does not exist sets expectations nobody can meet.
Effective date and review date
Annually at minimum, and immediately after any reorganisation. Charters go stale when the organisation around them changes, and an unreviewed charter is the reason a function ends up serving a stakeholder map that no longer exists.
Version and approval
Who approved it and when. This matters more than it appears: the approval is what you point at when a stakeholder asks for something the charter explicitly places out of scope.
Write it early, even if it is short
A one-page charter agreed in the first month is worth more than a comprehensive one written in year two, by which point the expectations it was meant to set have already formed informally.
How to write the mandate of a competitive intelligence program
Three to five objectives, each one something a person outside the team could confirm had happened. This is the section most likely to be filled with statements that sound purposeful and commit to nothing: enable the business, provide insight, drive competitive advantage. None of those can be delivered or failed, which means none of them will protect the program when its budget is questioned.
Objective
Phrased as an outcome in the organisation rather than an activity inside the team. "Competitive losses are understood rather than guessed at" is an outcome. "Produce quarterly competitive reports" is an activity, and activities are what a function does when nobody has agreed what it is for.
What it means in practice
The operational translation: "every lost deal above a threshold gets a buyer-sourced reason within 30 days". This is the row that makes the objective testable, and writing it usually reveals whether the objective is achievable with the resourcing on offer.
How we will know it is working
Observable and preferably already collected. If measuring an objective requires a new data collection exercise, either simplify the objective or accept that it will go unmeasured, which is a decision worth taking consciously.
Three to five, not ten
A charter listing ten objectives is describing a department rather than a program, and it guarantees that the two which mattered get the same attention as the eight that did not.
There is no canonical set of CI objectives
You will find pages listing the three basic objectives of a competitive intelligence program, usually along the lines of gaining insight, spotting opportunities and threats, and supporting decisions. That framing is reasonable and it does not come from a standards body: it traces largely to homework-answer sites rather than to SCIP or any professional institution. Write objectives that fit your organisation rather than adopting a list because it is numbered.
How to define what is in and out of scope
The out-of-scope rows matter more than the in-scope ones, and most charters have none. A competitive intelligence function attracts adjacent requests constantly: market sizing, analyst relations, pricing decisions, product research, sales coaching. Each is reasonable in isolation and collectively they consume a small team entirely. Writing three explicit exclusions, agreed by the sponsor, is what makes it possible to decline later without it being a negotiation every time.
Area
Be specific about the boundary cases rather than the obvious ones. Nobody needs telling that CI does not run payroll. The rows that earn their place are the genuinely adjacent ones: market sizing, customer research, analyst relations, pricing.
In or out
Binary where possible. Partly is occasionally honest, in which case the rationale column has to carry the detail, but a charter full of partly is a charter that will be argued with.
Rationale
One line, and phrase it as a division of labour rather than a refusal: "we supply the competitive input; we do not set price". This is a statement about where a decision belongs, which is much easier to defend than a statement about capacity.
Who owns it instead
The row that makes exclusions constructive. Sending a requester to the right team is a service; telling them it is not your job is not. If nothing owns an excluded area, that is a genuine finding for the sponsor rather than a reason to absorb it.
Revisit exclusions annually, not never
Scope that was right for a one-person program in year one may be wrong at year three. The point of writing exclusions down is not permanence, it is that expansion becomes a decision somebody takes rather than something that happens.
How to map stakeholders in a competitive intelligence charter
One row per function, and apply a simple test: if a stakeholder cannot name a decision they make, they are an audience rather than a stakeholder. Audiences consume output and generate no value from it, and serving them is how a small function ends up producing a widely-circulated report that changes nothing. Distinguishing the two at charter time is uncomfortable and it is the difference between a program with impact and one with distribution.
Stakeholder
By function rather than by individual, since individuals move. Typically sales, product, marketing, and the executive team, with customer success and partnerships appearing in some organisations.
Decisions they make
The test. Sales decides how to position in a live deal; product decides what to build; the executive team decides where to invest. A function that consumes competitive material and makes no decision with it does not need a standing deliverable.
What we provide
Named artifacts rather than categories: battlecards, a quarterly report, an executive brief, a tracker. Each one should also appear in the deliverables table with an owner and a cadence, or it is an aspiration.
How often
Different stakeholders need genuinely different rhythms. Sales needs currency measured in days after a material change; the executive team needs quarterly synthesis. Serving both on one cadence fails one of them, and it is usually sales.
Fewer stakeholders served properly
A first-year program serving two functions well is in a far stronger position than one serving five thinly, because the two can testify that it works. Expansion is easy once something is demonstrably valuable.
How to set deliverables and service levels
Commit only to what you can sustain with the headcount you actually have. An unmet cadence damages a program more than a modest one, because a quarterly report that arrives twice becomes evidence that the function cannot deliver, whereas a twice-yearly report that always arrives becomes evidence that it can. The service level column is what turns a list of documents into something a stakeholder can rely on and plan around.
Deliverable
Named artifacts with a defined shape, ideally one you have a template for. Vague commitments such as ad hoc analysis expand without limit and cannot be resourced.
Frequency
Honest, and deliberately conservative in the first year. Halving a promised cadence after three months reads as failure; increasing it after six reads as success, and the underlying output can be identical.
Owner
Named per deliverable, including where it is the same person on every row. Seeing one name against six deliverables is itself a useful signal to a sponsor about resourcing.
Service level
Time-bound and specific: battlecards updated within five working days of a material change, the quarterly report within five days of quarter end. Service levels are what make the function feel dependable rather than responsive, and they are what stakeholders remember.
Include a triage commitment for ad hoc requests
Most of a CI team's demand arrives unplanned. Committing to triage every request within two working days, even when the answer is no or later, prevents the silent-queue problem that causes stakeholders to route around the process entirely.
How to write the ethical and legal boundaries of a competitive intelligence program
Write the prohibited practices explicitly, because a boundary that exists only in someone's judgement is not a boundary. This is the section that distinguishes a serious charter, and it protects three things at once: the company from legal exposure, individual employees from being asked to do something they should refuse, and the program's findings from being unusable because nobody can explain where they came from.
The legal line is clearer than people expect
In the United States, the Economic Espionage Act of 1996, codified at 18 U.S.C. sections 1831 to 1839, makes trade secret theft a federal crime, covering both economic espionage and ordinary commercial misappropriation. Information assembled from public sources triggers none of it. That split is the whole architecture: how the information was obtained matters far more than what it contains.
Honest identity is the practical test
The SCIP code of ethics requires disclosing your identity and organisation before interviews. That single rule resolves most difficult cases in practice: signing up for a public trial under your own company name is fine, doing it under a false one is not, and the distinction is easy to apply without a lawyer in the room.
Practices to name explicitly as permitted
Published pricing pages, documentation, changelogs, filings, job postings, conference talks, review sites, public trials under your own identity, and conversations with customers who use both products. Listing these matters as much as listing prohibitions, because teams operating without a charter often avoid entirely legitimate research out of vague unease.
Practices to name explicitly as prohibited
Misrepresenting who you are, approaching a competitor's employees under a pretext, inducing anyone to breach a confidentiality obligation, accessing systems you are not authorised to use, and asking a new hire from a competitor for confidential material. That last one is the most common real-world exposure and the one most often left unwritten.
Say what to do instead
Every prohibition should have an alternative route beside it. If a question can only be answered by a prohibited method, it is answered instead from win/loss interviews, customers who use both products, or an explicit statement that it could not be determined.
Get it reviewed and make it findable
Have counsel read this section, particularly if you operate across jurisdictions, since rules differ. Then put it where a new analyst will actually encounter it in their first week, because the boundary only works if the people doing the collecting know it exists.
How to record sources and tooling in a CI charter
List what you actually use, with the cost, because this is the table a budget conversation will ask for first. It also surfaces something charters otherwise hide: how much of the program depends on one person's manual routine. A function whose monitoring consists of an individual checking twelve websites every Monday has a continuity problem that becomes visible the week they are on leave, and it is far better to name it here than to discover it then.
Source or tool
Everything, including the free and manual ones. Review sites, job boards, changelogs and filings are sources even when nobody pays for them, and they carry a real time cost that belongs in the picture.
What it covers
Be specific about coverage: which competitors, which signals, how frequently. Gaps become obvious when written out, and the most common gap is that monitoring covers the two competitors everyone talks about rather than the four that appear in deals.
Annual cost
Including internal time where it is substantial. A source requiring four hours a week is a meaningful cost even at zero licence fee, and expressing it that way is what makes an automation case.
Owner
Per source. Sources with no named owner stop being checked, usually without anybody noticing until a competitor move is missed and someone asks how.
Note what you deliberately do not use
Paid analyst subscriptions and expert networks are legitimate and expensive. Recording that you have chosen not to buy them, and why, prevents the same conversation recurring every budget cycle.
How to measure a competitive intelligence program
Four to six measures, and avoid anything that rewards producing more documents. Output volume is the easiest thing to count and the most misleading: a team publishing forty battlecards nobody opens will score better than one maintaining six that reps use daily. The measures worth committing to in a charter are the ones that would still look good if the team produced less material and changed more outcomes.
Outcome measures
Competitive win rate against named rivals, movement in loss reasons, deals influenced. These are what the program exists to move. They are noisy at low deal volumes, so state the sample size alongside them rather than reporting a rate over nine deals as though it were stable.
Usage measures
Battlecard views before competitive calls, request volume by function, how many decisions cited a CI input. Usage is a leading indicator: it moves before outcomes do, which makes it useful in a first year when outcome data is thin.
Quality measures
Share of claims traceable to a dated primary source, corrections issued, freshness of standing artifacts. These are internal but worth committing to, since they are what makes the outcome measures believable.
Avoid volume measures
Reports published, competitors tracked, alerts processed. Each rewards activity over impact and each is trivially gamed. If a stakeholder insists on one, pair it with a usage measure so the two are read together.
Name the attribution problem rather than hiding it
Competitive intelligence rarely has a clean causal line to revenue, and claiming one invites a challenge you will lose. Stating openly that the program is measured on contribution and usage rather than on attributed revenue is more credible and, in practice, more persuasive to a sponsor.
How to record approval and open decisions in a CI charter
Record what was agreed and, just as importantly, what was deliberately left open. Charters are approved in a meeting where two or three questions are consciously deferred, and those deferrals vanish from the record unless someone writes them down. A year later the same questions surface as though new, and the reasoning that led to deferring them has to be reconstructed from memory by people who may no longer be there.
Item
Headcount, budget, reporting line, scope boundaries and tooling are the ones that typically need an explicit decision. Anything argued about during approval belongs here whether or not it was resolved.
Decision
As agreed, including the conditions. "One full-time owner plus 0.4 of a sales enablement partner" is a decision; "resourcing to be confirmed" is a deferral and should be recorded as one rather than dressed as agreement.
Owner
The person accountable for the decision, not the person who will do the work. For charter-level items this is usually the sponsor.
Date and revisit at
When it was decided and when it comes back. Time-boxed decisions without a return date quietly become permanent, which is how a deliberately narrow first-year scope turns into an unexamined constraint in year three.
Keep old versions
The charter's history is the program's history. Comparing this year's scope, deliverables and measures against last year's is the clearest evidence available of whether the function grew or drifted.
Sourcing and upkeep: keeping a competitive intelligence charter useful
These rules apply to every section above. A charter fails by becoming decorative: written once, approved, filed, and never referenced while the program does whatever the loudest stakeholder asked for most recently. The habits below keep it operational, and the test is simple. If nobody has cited the charter in six months to decline something or to justify a deliverable, it is not doing its job.
One page beats ten
A charter nobody reads protects nothing. Everything here fits on a page or two if the objectives are genuinely three to five and the exclusions are genuinely three.
The exclusions are the operative half
In-scope statements are easy to agree and rarely contested. The out-of-scope rows are what you point at when the fifth adjacent request arrives, and a charter without them will not survive contact with demand.
Commit to a cadence you can sustain understaffed
Promised-and-missed is materially worse than modest-and-met. Increase the cadence once it is boring; do not start where you hope to end up.
Write the ethics section explicitly and get it reviewed
The legal line turns on how information was obtained rather than on what it contains. Honest identity resolves most cases in practice, and the section protects employees as much as the company.
Measure outcomes and usage, never volume
Document counts reward activity over impact and are trivially gamed. If a volume measure is unavoidable, pair it with a usage measure so nobody reads it alone.
Review annually and after any reorganisation
Charters go stale when the organisation changes shape around them, and a stakeholder map that no longer matches the company is worse than none.
Cite it, or it is decorative
The charter should be referenced when declining work, when justifying a deliverable and when a budget is questioned. A charter never invoked is a charter nobody agreed to in any meaningful sense.
A competitive intelligence program charter example
You are standing up a competitive intelligence function at Pipedrive. It is one person plus a fraction of a sales enablement partner, and the CEO wants to know what she is approving. This is that charter, filled in.
Published pricing and packaging verified 2 August 2026, from the companies’ own pages rather than third-party round-ups, which frequently conflate annual and monthly prices. Pricing changes without notice, so re-check before quoting any of it.
Sections marked illustrative are invented for this example. Win rates, deal counts, discounting behaviour, customer quotes, owners and internal dates are not published by HubSpot, Pipedrive or anyone else, so those rows are a plausible fictional scenario rather than reported fact, and should not be read as claims about how either company performs or negotiates. Everything else comes from the two pricing pages linked below, read on the date shown.
Charter detailsIllustrative
| Field | Example entry |
|---|---|
| Program name | Competitive Intelligence, sitting inside Product Marketing |
| Executive sponsor | Elena V., CEO |
| Program owner | Tom A., Competitive Intelligence, full time |
| Effective date | 1 Sep 2026 |
| Review date | 1 Sep 2027, or immediately after any reorganisation |
| Version and approval | v1.0, approved by Elena V. on 28 Aug 2026 |
1. Mandate and objectivesIllustrative
| Objective | What it means in practice | How we will know it is working |
|---|---|---|
| Competitive losses are understood rather than guessed at | Every lost deal above 20k gets a buyer-sourced reason within 30 days | Loss reasons come from buyers rather than reps in most closed deals |
| Sales never carries stale competitor material into a call | Battlecards for the top 3 rivals updated within 5 days of a material change | No battlecard older than one quarter, checkable at any moment |
| Pricing and packaging decisions have competitive evidence attached | A dated competitor pricing picture available whenever pricing is discussed | Pricing decisions cite it rather than commissioning fresh work each time |
| Leadership sees competitive movement quarterly, with what changed | An eight-minute competitive section in every QBR | The section produces at least one recorded decision per quarter |
2. In scope and out of scopeIllustrative
| Area | In or out | Rationale | Who owns it instead |
|---|---|---|---|
| Competitor monitoring, profiles, battlecards and win/loss analysis | In | The core of the mandate | This program |
| Pricing decisions | Out | We supply the competitive input; we do not set price | The pricing group, chaired by the CFO |
| Market sizing and TAM work for fundraising | Out | Different discipline, different sources, and it would consume the whole function | Finance, with Strategy |
| Analyst relations | Out | Relationship management rather than intelligence, though we supply input | Corporate Marketing |
| Customer research and user interviews | Out | We use the outputs; we do not run the programme | Product Research |
| Sales coaching and objection training delivery | Partly | We write the material; we do not run the sessions | Sales Enablement runs delivery |
3. Stakeholders and what each receivesIllustrative
| Stakeholder | Decisions they make | What we provide | How often |
|---|---|---|---|
| Sales | How to position against a named competitor in a live deal | Battlecards, one-pagers and call prep support | Updated within 5 working days of a material change |
| Product | What to build, and which gaps to close, neutralise or concede | Feature gap analysis and competitor teardowns | Quarterly, plus after any significant competitor launch |
| Product Marketing | Positioning and messaging against competitive alternatives | Differentiation matrix and messaging input | Twice yearly, refreshed on demand |
| Executive team | Where to invest, and how to respond to competitive moves | QBR competitive update and event-triggered executive briefs | Quarterly, plus within 5 days of a material event |
4. Deliverables, cadence and service levelsIllustrative
| Deliverable | Audience | Frequency | Owner | Service level |
|---|---|---|---|---|
| Battlecards for the top 3 competitors | Sales | Continuous | Tom A. | Updated within 5 working days of a material change |
| Competitive intelligence report | Product, marketing and sales leadership | Quarterly | Tom A. | Delivered within 5 working days of quarter end |
| QBR competitive update | Executive team | Quarterly | Tom A. | Draft circulated 3 working days before the meeting |
| Win/loss analysis | Sales and Product leadership | Quarterly | Tom A. with Sales Enablement | Covers all losses above 20k in the period |
| Executive brief on a material competitor event | Executive team | As triggered | Tom A. | Within 5 working days of the event becoming known |
| Ad hoc request triage | Anyone | Continuous | Tom A. | Every request triaged within 2 working days, including declines |
5. Ethical and legal boundariesIllustrative
| Practice | Permitted? | Why | What to do instead |
|---|---|---|---|
| Signing up for a competitor's public trial under our own company name | Yes | Public offer, honest identity, terms observed | Not applicable |
| Reading published pricing, documentation, changelogs, filings and job postings | Yes | Public information, no misrepresentation involved | Not applicable |
| Speaking to customers who use both our product and a competitor's | Yes | Our own customers, our own identity, their own experience | Not applicable |
| Signing up under a false name or a personal address to hide who we are | No | Misrepresentation, and it makes any finding uncitable internally | Use the public trial under our own name, or their documentation |
| Approaching a competitor's employees under a pretext | No | Misrepresentation, and it risks inducing a breach of their obligations | Conference talks, published interviews and their own documentation |
| Asking a new hire from a competitor for confidential material or documents | No | Risks inducing breach of their obligations and exposes both them and us | Ask about publicly known market context only, never internal specifics |
| Accessing any system, environment or document we are not authorised to use | No | Unauthorised access, with exposure under trade secret and computer misuse law | Public sources, or record the question as undeterminable |
6. Sources and toolingIllustrative
| Source or tool | What it covers | Annual cost | Owner |
|---|---|---|---|
| Automated competitor website, pricing and messaging monitoring | Pricing, packaging and positioning changes across 6 competitors | Stated licence figure | Tom A. |
| Review sites | Customer sentiment themes for us and the top 3 rivals | Free tier | Tom A. |
| Job boards and competitor careers pages | Hiring signals indicating investment areas | Free, roughly 1 hour a week | Tom A. |
| CRM competitor tagging and loss reasons | Where rivals appear in deals, and why we lose | Existing system | Sales Ops, consumed by CI |
| Paid analyst subscriptions | Not purchased | Zero, deliberately | Revisit at the annual charter review |
7. How the program is measuredIllustrative
| Measure | Target | How it is collected | Why this and not volume |
|---|---|---|---|
| Competitive win rate against the top 3 rivals | Improve by 4 points over 4 quarters | CRM, on deals where a competitor was tagged | It is the outcome the program exists to move |
| Competitor tagging coverage on closed deals | Above 85% by Q2 2027 | CRM | Every other measure is drawn from this data, so it gates their credibility |
| Battlecard views in the 7 days before a competitive close | Rising quarter on quarter | Enablement platform | Usage moves before outcomes do, which matters in year one |
| Share of competitor claims traceable to a dated primary source | 100% of published material | Sourcing logs | It is what makes the outcome numbers believable |
| Requests triaged within 2 working days | 95% | Request log | Silent queues are why stakeholders route around a CI function |
8. Approval, review and open decisionsIllustrative
| Item | Decision | Owner | Date | Revisit at |
|---|---|---|---|---|
| Headcount for the first year | One full-time owner plus 0.4 of a sales enablement partner | Elena V., CEO | 28 Aug 2026 | Annual charter review |
| Reporting line | Into Product Marketing, with a standing executive slot each quarter | Elena V., CEO | 28 Aug 2026 | Annual charter review |
| Paid analyst subscriptions | Deferred, not rejected. Revisit once tagging coverage is above 85% | Elena V., CEO | 28 Aug 2026 | 1 Sep 2027 |
| Whether market sizing stays out of scope | Left open deliberately. Finance owns it today and may not want it | Elena V., CEO | 28 Aug 2026 | 1 Mar 2027 |
How to roll out your competitive intelligence program charter
- 1Copy or download the blank charter. Use Copy to paste it straight into Google Sheets or Excel with the columns intact, or download the CSV, Notion or PDF version.
- 2Get a named executive sponsor before anything else. A charter without one is a proposal, and the sponsor's function will shape the program's remit more than any other single choice.
- 3Delete the example rows. Each table ships with one example row so the pattern is obvious. Remove it before you circulate the charter.
- 4Write three to five outcome objectives, not activities. Each must be something a person outside the team could confirm had happened. Enable the business cannot be delivered or failed.
- 5Write at least three out-of-scope rows. These matter more than the in-scope ones. Name who owns each excluded area instead, so declining is a redirection rather than a refusal.
- 6Commit only to a cadence you can sustain understaffed. Promised-and-missed damages a program more than modest-and-met. Increase it once it is boring.
- 7Write the ethical boundaries explicitly and have counsel read them. Name permitted practices as well as prohibited ones, and give every prohibition an alternative route beside it.
- 8Measure outcomes and usage, never document volume. Then record what was deliberately left open at approval, with a date for when it comes back.
Competitive intelligence program charter FAQ
What is a competitive intelligence program charter?
A competitive intelligence program charter is the founding document for a CI function. It records the mandate and objectives, what is deliberately in and out of scope, which stakeholders are served and what each receives, the deliverables with their cadence and service levels, the ethical and legal boundaries the team operates inside, the sources and tooling, and how the program will be measured. Its practical purpose is to settle expectations before they form informally, which they will otherwise do within the first quarter.
What is a competitive intelligence program?
A competitive intelligence program is the standing function that gathers, analyses and distributes information about competitors and the market so the organisation can make better decisions. The word program matters: it distinguishes an ongoing capability with owners, cadence and service levels from the ad hoc research most companies actually do, where someone builds a competitor deck when a deal goes badly and nobody maintains it afterwards. The charter is what turns the second into the first.
What are the three basic objectives of a competitive intelligence program?
The formulation you will find most often is gaining insight into competitors, identifying opportunities and threats, and supporting decision-making. That is a reasonable summary and it is worth being direct about its provenance: it traces largely to homework-answer sites rather than to SCIP or any professional body, so there is no canonical trio to adopt. Write objectives that fit your organisation instead, phrased as outcomes someone outside the team could confirm had happened, and keep it to three to five.
Is competitive intelligence legal?
Yes, when the information is obtained through legitimate means, and the legal line is clearer than most people expect. In the United States the Economic Espionage Act of 1996, codified at 18 U.S.C. sections 1831 to 1839, makes trade secret theft a federal crime, covering both espionage for a foreign power and ordinary commercial misappropriation. Information assembled from public sources triggers none of it. So published pricing, documentation, filings, job postings, conference talks, review sites and product trials under your own identity are all available with no exposure. What creates liability is how information is obtained: misrepresentation, bribery, unauthorised system access, or inducing someone to breach a confidentiality obligation. Rules differ by jurisdiction, so have counsel review your charter if you operate in several.
Is competitive intelligence ethical?
The discipline has a professional code, which is a useful anchor for a question that otherwise dissolves into opinion. SCIP's code of ethics requires practitioners to comply with applicable law and to disclose their identity and organisation before interviews. That single requirement, honest identity, resolves most difficult cases in practice: signing up for a public trial under your own company name is fine, doing it under a false one is not, and no legal training is needed to apply the distinction. The practical test worth writing into a charter is whether you would be comfortable describing how you obtained a finding, to your own board and to the competitor.
What is the main purpose of competitive intelligence?
To change decisions. Not to produce reports, monitor competitors or accumulate knowledge, all of which are activities rather than purposes and all of which a function can do indefinitely without affecting anything. The practical test for any competitive intelligence output is whether somebody did something different because of it. That is also why the objectives section of a charter should be written as outcomes: activity-shaped objectives cannot be failed, which sounds comfortable and means the program cannot be defended when its budget is questioned.
Why is competitive intelligence important?
Because decisions get made about competitors whether or not anyone has looked. Pricing gets set against an assumed competitor position, roadmaps get shaped by whichever rival was mentioned most recently in a deal review, and reps improvise positioning from memory. The alternative to a competitive intelligence function is not neutrality, it is the same decisions taken on worse information, usually sourced from the loudest recent anecdote. The function's value is the difference between those two, which is why it is measured on decisions rather than on documents.
What are the disadvantages of competitive intelligence?
Four are real and worth writing into a charter as risks. Competitor obsession, where a company optimises against a rival rather than for its customers, which is how two products converge and neither differentiates. Cost, since the function consumes headcount and produces no directly attributable revenue. Analysis that arrives after the decision, which is an audit rather than an input. And ethical or legal exposure if boundaries are left to individual judgement. The first is the most damaging and the least discussed: a program that never asks what customers want, only what competitors do, will make the company worse.
What is another name for competitive intelligence?
Competitor intelligence, competitive insights and business intelligence are all used loosely as synonyms, though the last one usually means something different: business intelligence typically refers to internal reporting on your own data. Market intelligence is broader, covering customers, category and macro trends as well as rivals. Strategic intelligence usually implies a longer horizon and an executive audience. Since these overlap rather than match, the name you choose in a charter is partly a scope decision, and it is worth defining the term in the document rather than assuming it is shared.
Can competitive intelligence be automated?
The collection can be, and largely should be. Monitoring pricing pages, changelogs, job postings and review sites is repetitive, high-volume work that software does more reliably than a person checking twelve sites every Monday. What does not automate is the judgement: deciding which change matters, what it implies about a competitor's priorities, and what your company should do about it. Programs that automate collection and keep the interpretation human tend to work. Programs that automate the whole pipeline generate alert volume, which is the category's most persistent complaint.
How do you conduct competitive intelligence?
Start from decisions rather than from competitors. Establish what the organisation is deciding, work out which questions are genuinely answerable from public sources, and collect from primary sources with dates while keeping observation separate from inference. Deliver something short to the person making the decision, with confidence levels and an explicit statement of what could not be determined. Then record whether it changed anything. The step almost everyone skips is the last one, and it is the only one that tells you whether the rest was worth doing.
What are the 5 competitive strategies?
The underlying model is Porter's, and he set out three generic strategies: cost leadership, differentiation, and focus. Because focus splits into cost focus and differentiation focus, it is frequently presented as four. The five-strategy version comes from Thompson, Strickland and Gamble, who add a best-cost provider strategy. All three counts describe the same lineage, so none is wrong, and the substantive point matters more than the arithmetic: Porter's argument is that a firm failing to commit to one ends up stuck in the middle, competing on everything and winning at nothing.
Who should own a competitive intelligence program?
Most commonly product marketing, which sits between product, sales and market and needs the output for its own work. The sponsor matters more than the reporting line, and it shapes the remit substantially: sponsored by sales, the program becomes enablement and optimises for battlecards; by product, it becomes roadmap input; by strategy, it becomes market analysis. None is wrong, and drifting between them without noticing is. Whichever you choose, write it in the charter along with the sponsor's name, because the reporting line will be questioned during the first reorganisation.
How big should a competitive intelligence team be?
Most programs start as a fraction of one person's role and the first genuine milestone is a single full-time owner. That is enough to maintain battlecards for the top three competitors, run quarterly win/loss, and produce a quarterly report, provided collection is automated and scope is genuinely bounded. Teams beyond that tend to appear when the company serves multiple segments or geographies with different competitive sets. The failure pattern is not being small, it is being small with an unbounded scope, which is why the out-of-scope rows in a charter matter more than the headcount number.
What should a competitive intelligence charter include?
Eight things. A named executive sponsor and program owner. Three to five outcome objectives. What is in and, more importantly, out of scope. The stakeholders served and the decisions each makes. Deliverables with cadence and service levels. The ethical and legal boundaries, written explicitly. Sources and tooling with costs. And how the program is measured. If it runs beyond two pages it will not be read, and a charter nobody reads protects nothing when the fifth adjacent request arrives.
How do you measure a competitive intelligence program?
On outcomes and usage, never on volume. Outcome measures: competitive win rate against named rivals, movement in loss reasons, decisions that cited a competitive input. Usage measures: battlecard views before competitive closes, request volume by function, triage response times. Quality measures: share of claims traceable to a dated primary source. Avoid reports published and competitors tracked, which reward activity over impact and are trivially gamed. And name the attribution problem openly rather than claiming a clean causal line to revenue, which invites a challenge you will lose.
How much do competitive intelligence tools cost?
Most established vendors in this category do not publish pricing, which is itself worth knowing when budgeting: expect a sales process rather than a checkout, and expect annual commitments. That opacity is one reason our own research went to review data instead. We analysed 500 verified G2 reviews across the four leading competitive intelligence tools and coded them into 340 themes, which gives a picture of what buyers actually experience rather than what vendors advertise. The most useful finding for a charter: the one complaint shared by all four at material frequency was too many irrelevant alerts, so budget for the judgement layer rather than assuming the tool supplies it.
What is the difference between a CI charter and a CI request brief?
Scope and lifespan. The charter is the standing document defining the function: its mandate, boundaries, stakeholders, deliverables and measures, reviewed annually. A request brief is per-request, filled in by a stakeholder before a specific piece of research, naming the decision and the questions. The charter says what the program does in general; the brief says what this particular piece of work is for. Programs that have a charter and no intake process end up with a clear mandate and a chaotic queue, which is the more common of the two failure modes.
What is an example of a competitive intelligence program charter?
Sponsor: the CEO. Owner: one full-time person inside product marketing, plus 0.4 of a sales enablement partner. Objectives: competitive losses understood rather than guessed at, with every loss above 20k carrying a buyer-sourced reason within 30 days; sales never carrying stale material, with battlecards for the top three rivals updated within five working days of a material change; pricing decisions having dated competitive evidence attached; and leadership seeing quarterly competitive movement that produces at least one recorded decision. Out of scope, explicitly: pricing decisions, market sizing for fundraising, analyst relations and customer research, each with the team that owns it named instead. Ethics: public trials under our own name, published sources and conversations with our own customers are permitted; false identities, pretexting competitor employees, asking new hires for confidential material and unauthorised system access are prohibited, each with an alternative route beside it. Measures: competitive win rate, tagging coverage, battlecard usage before competitive closes, sourcing traceability and triage response time. Open decisions recorded at approval: paid analyst subscriptions deferred rather than rejected, and whether market sizing stays out of scope revisited in six months.
What are the most common mistakes in a competitive intelligence charter?
Six recur. Objectives written as activities rather than outcomes, so the program cannot be failed and therefore cannot be defended. No out-of-scope rows, which leaves the function absorbing every adjacent request until it has no capacity for anything strategic. A cadence promised at full staffing and missed at real staffing. No written ethical boundaries, leaving individual analysts to judge case by case. Measuring document volume, which rewards activity over impact. And writing the charter once and never citing it, which makes it decorative: if it has not been invoked in six months to decline something or justify a deliverable, it is not doing its job.
Your competitive intelligence program charter, delivered
Flares runs the monitoring a charter commits to, so the program hits its cadence from the first quarter.
Discover Flares14-day free trial · 30-second setup