Prompts · 33 jobs · Updated 2026-09-14
AI Prompts for Competitive Analysis
Thirty-three competitive intelligence jobs, each with a prompt you can copy and the material you have to paste in with it. The prompts are the easy half. What decides whether the output is usable is what was in the context window when you pressed send, so every entry says what to supply before it says what to ask.
Why a prompt might return a wrong answer about a competitor
Ask an AI assistant what a competitor charges and it will tell you, fluently, with plan names and figures. The answer is assembled from material gathered at some point before the model shipped, and nothing in the response indicates when that was. This is the single reason competitive work needs a different habit from most other uses of these tools: in almost every other task, being approximately right is fine.
The interesting part is that outright invention is not the main problem. We checked an ungrounded answer against a live vendor pricing page in September 2026, and the plan names and the broad price levels came back roughly right. What came back wrong were two quieter things, and both would have survived a quick sanity check by somebody who already knew the vendor.
One number where the page shows two
Almost every software pricing page carries a billing toggle, and the two prices behind it are not close. On HubSpot’s Sales Hub page in September 2026, the Starter tier reads $7 per seat per month billed annually and $20 per seat per month billed monthly. That is a factor of nearly three hiding behind the single word “price”.
| Plan | Billed annually | Billed monthly | Also charged |
|---|---|---|---|
| Free | $0 | $0 | Nothing; up to 2 users |
| Starter | $7 / seat / mo | $20 / seat / mo | None listed |
| Professional | $90 / seat / mo | $100 / seat / mo | $1,500 one-time onboarding |
| Enterprise | from $150 / seat / mo | Not published | $3,500 one-time onboarding |
A comparison that reports one figure per tier is not slightly imprecise, it is answering a different question from the one a buyer asked. Which is why the pricing prompt in this library demands both columns and refuses to let the model collapse them.
The line items nobody asked about
The same page carries a $1,500 one-time onboarding charge on Professional and $3,500 on Enterprise. An ungrounded answer to “what does it cost” does not mention them, because they are not what was asked and nothing prompts the model to volunteer them. On a ten-seat Professional deal that omission is roughly the first two months of the subscription, sitting outside the comparison entirely.
This is the failure mode worth designing against, and it is not fixed by telling a model to be accurate. It is fixed by telling it what a complete answer contains: every price, the period each assumes, the unit, the minimum, and a closing list of what the page does not say. Several prompts here end with exactly that instruction.
What has to be in the context window before a competitor prompt works
Every entry below names what you supply, and that line is doing more work than the prompt underneath it. Three things belong in the window before a competitive prompt is worth sending.
The sources themselves, dated. Not a link for the model to look at, but the text of the pages as you captured them, with the date you captured them written at the top. A dated capture is what lets a later reader tell a stale claim from a wrong one, and those need different fixes. Gathering them is manual work, and where each kind of competitor information is published varies far more than people expect: pricing sits on one page, headcount on none.
Your own side of the comparison. Most of these prompts produce something relative, and a model that has your positioning only in outline will quietly flatter you. Paste your real pricing page and your real feature list, not the internal deck version of them.
The rule about what happens on a gap. Without an instruction, the default behaviour on a missing fact is to supply something plausible. With one, it is to say the material does not contain it. That single sentence changes more about the output than any amount of role-play framing at the start of a prompt.
The instruction worth putting above everything else
Scope your competitive landscape
Before any of the analysis below is worth running, you need a defensible list of who you are actually competing with. These two are the only jobs here a model can usefully start from a blank page.
Finding who you actually compete with
You supply: Your own positioning, the deals you lose, and the search terms you rank for.
I sell [PRODUCT] to [BUYER ROLE] at [COMPANY TYPE]. Here is our homepage copy, our last [N] closed-lost reasons, and the search terms we rank for: [PASTE]. Build a competitor set in three tiers, and put each name in exactly one: 1. Direct - sells the same thing to the same buyer 2. Adjacent - solves the same problem a different way 3. Status quo - what they do instead of buying anything For each name, cite which of my inputs put it there. Do not add companies that appear in none of my inputs; list those separately under "worth checking" and say why you thought of them.
Market research from material you gathered
You supply: Analyst notes, category pages, your own win/loss reasons, and any survey data you hold.
Here is the material I have gathered on the [CATEGORY] market: [PASTE]. Tell me what this material supports, and separate it into three lists: - Stated: claims a source in my material makes directly. Quote it and name the source. - Supported: conclusions I can defend from two or more of my sources. Name both. - Unsupported: things I might assume that nothing here establishes. The third list is the one I care about most. Do not fill gaps with what you know about this market from elsewhere.
Analyse a competitor from sources you supply
The core of the work. Every one of these assumes you have saved the pages first, because a model asked what it remembers about a competitor will answer confidently and be out of date.
Positioning teardown
You supply: The competitor's homepage and two or three product pages, saved as text.
Using only the pages I have pasted below for [COMPETITOR], extract: - the primary value proposition, in their exact words - the buyer they name, and where they name them - the three benefits they lead with, in the order the page presents them - the objections the copy pre-empts without being asked Quote the exact wording for every item and say which page it came from. Where you cannot find one of these, write "not stated on the pages provided" rather than inferring it. PAGES: [PASTE]
Feature comparison matrix
You supply: Your own feature list plus each competitor's features or docs pages, saved as text.
Compare the feature lists I have pasted for [OUR PRODUCT] and [COMPETITORS]. Produce a table with one row per feature and these columns: feature, who states it, exact wording used, and a confidence column with one of EXPLICIT / VAGUE / ABSENT. Rules: - EXPLICIT only when a page names the capability outright. - VAGUE when the page gestures at it ("powerful reporting") without saying what it does. - ABSENT when no provided page mentions it at all. ABSENT means "not in my sources", not "they do not have it" - label it that way in the output. Do not add features that appear in none of the sources. SOURCES: [PASTE]
Competitor pricing comparison
You supply: Each competitor's pricing page, saved on a stated date, including the billing toggle.
From the pricing pages I have pasted below, build a comparison of every plan for [COMPETITORS]. One row per plan, with these columns: vendor, plan name, price, billing period the price assumes, unit the price is charged per, minimum commitment, and what moves a buyer to the next tier up. Rules: - If a page shows both annual and monthly prices, give both in separate columns. Never collapse them into one number. - Record any one-time fee, onboarding charge, credit allocation or seat minimum in its own row, not in a footnote. - Where a plan says "contact sales" or "custom", write exactly that. Do not estimate. - End with a list headed "Not stated on these pages" covering anything a buyer would need that the pages do not say. PRICING PAGES (saved [DATE]): [PASTE]
On the page: Three more prompts, the two columns a pricing page always has and most comparisons collapse, and what a model got wrong when we checked its answer against a live one.
SWOT built from evidence
You supply: Anything you have already gathered on the competitor, each item labelled with its origin.
Build a SWOT for [COMPETITOR] using only the sources I have pasted below. Every entry must end with the source it came from, in square brackets. An entry with no source does not go in. Two constraints that matter more than completeness: - Leave a quadrant sparse if my sources do not support it. Four thin quadrants of guesses are worse than two solid ones. - Strengths and weaknesses are about them. Opportunities and threats are about the market acting on them. Do not use the last two quadrants to restate the first two. SOURCES: [PASTE]
Inferring their ideal customer
You supply: Their case studies, customer logos page, pricing page and any published customer counts.
From the case studies, customer logos and pricing I have pasted for [COMPETITOR], infer who they are actually built for: company size, industry, buyer role, and the use case they optimise for. For each conclusion, give the evidence behind it and rate it STRONG (several sources agree), WEAK (one source), or INFERRED (my reasoning rather than their statement). Then answer separately: who do these sources suggest they are NOT built for, and what in the material says so? SOURCES: [PASTE]
Reading a competitor's technology choices
You supply: A saved technology profile for their domain, plus their integrations and status pages.
Here is a technology profile for [COMPETITOR]'s site, their integrations page, and their status page: [PASTE]. Group what this shows into: analytics and attribution, marketing and lifecycle, sales and support, infrastructure, and payments. Then answer the question the list does not: what do these choices imply about how they sell and who they sell to? Separate what the data states from what you are inferring, and name the two or three entries that carry the most weight in your reading. Ignore anything that is present on almost every website, and say which entries you discarded for that reason.
Competitor website teardown
You supply: The saved pages themselves, plus the navigation structure and any gated assets.
Here is the page text and navigation structure for [COMPETITOR]'s site: [PASTE]. Work through it in this order: 1. What journey does the navigation assume a visitor is on? 2. Which pages exist purely to rank, and which exist to convert? Say what tells you. 3. What is gated, and what does the gate ask for? 4. What claim is repeated most often across pages, in their words? 5. What would a buyer still not know after reading all of this? Answer from the provided text only. If the structure suggests a page you cannot see, name it as missing rather than assuming its content.
Read what a competitor's customers said
Reviews, lost deals, recorded calls and churn notes. Long unstructured text is what models are genuinely best at, and it is the material most teams never get through.
Mining competitor reviews
You supply: An export of the reviews themselves, with dates, ratings and the product version if shown.
Here is an export of [N] reviews of [COMPETITOR], each with its date and star rating: [PASTE]. Code them into recurring themes of praise and of criticism. For each theme give: - the number of reviews mentioning it and the share of the total - two representative quotes, verbatim, with their dates - the date range the theme spans Then answer two things separately: - which themes appear only in reviews older than [DATE], and may describe something already fixed - which criticisms are about the product, and which are about pricing, support or onboarding Do not paraphrase quotes. Do not merge two themes because they feel similar; if you are unsure, keep them apart and say so.
On the page: Two more prompts, why the export rather than the wording decides the analysis, and the theme that turned out to belong to the whole category rather than to one product.
Win/loss synthesis
You supply: Interview transcripts or written close notes, labelled won or lost and by competitor.
Here are [N] win/loss interviews, each labelled WON or LOST and tagged with the competitor in the deal: [PASTE]. Identify why deals were won and lost against [COMPETITOR], ranked by how often each reason appears. For every reason, split the evidence into two columns: - SAID: the buyer stated this. Quote them. - INFERRED: I am reading it from what they said. Say what you are reading it from. Then flag any reason that appears in both won and lost deals, since those are usually the ones being mislabelled internally.
Reading competitor mentions in sales calls
You supply: Call transcripts with speaker labels, and the deal outcome where you have it.
Here are [N] sales call transcripts with speaker labels: [PASTE]. Find every moment a competitor is named. For each one give: the competitor, who raised them (buyer or seller), the exact words used, what was being discussed immediately before, and how the rep responded. Then summarise: - which competitor is raised most often by buyers rather than by us - the three most common claims buyers repeat about competitors - the moments where a rep had no answer, quoted directly Work only from these transcripts. Do not assess whether the buyers' claims are true.
Churn reasons involving a competitor
You supply: Cancellation notes, exit survey answers and the account history for each churned customer.
Here are cancellation notes and exit survey answers for [N] churned accounts: [PASTE]. Separate them into: left for a named competitor, left for an in-house or manual alternative, stopped doing the job entirely, and reason not stated. Report the size of the fourth group prominently; it is usually the largest and is routinely dropped from summaries. For those that named a competitor, give the reason in the customer's words and the account's tenure. Do not infer a competitive loss from a cancellation that names no alternative.
Turn competitive analysis into sales material
Where competitive work either reaches a rep before a call or does not. The output of every prompt here is something a person reads under time pressure.
Battlecard first draft
You supply: Your positioning, their saved pages, and real win/loss reasons rather than assumed ones.
Draft a battlecard for competing against [COMPETITOR], using only the material pasted below. Sections, in this order: 1. How they position themselves, in their words 2. Where they are genuinely strong. Do not soften this. 3. Where our customers and their reviewers say they fall short, with the source 4. Three objections a buyer raises, with a factual response to each 5. When we should walk away from the deal Rules: mark any claim you could not source with [UNSOURCED] so I can cut it. Keep every response factual and non-disparaging - a rep will say these out loud to a buyer who may already like them. Nothing in section 4 may assert what the competitor will do in future. MATERIAL: [PASTE]
On the page: Three more prompts, the three kinds of evidence a card has to rest on, and the quote a model invented when it was asked for a competitor's own words.
Competitive objection handling
You supply: The objection in the buyer's own words, plus what you can evidence about both products.
Buyers say "[OBJECTION, IN THEIR WORDS]" when comparing us with [COMPETITOR]. Using the material pasted below, draft three responses: 1. One that concedes where they are genuinely better, then reframes 2. One that reframes on a strength we can evidence from my material 3. One that asks a question to surface what is actually behind the objection For each, name the evidence it rests on. Then write the one-sentence version a rep can say on a call without reading from a card. Do not write anything disparaging, and do not claim a capability my material does not support. MATERIAL: [PASTE]
Messaging comparison
You supply: Your messaging and theirs, taken from live pages rather than from an internal deck.
Here is our messaging and that of [COMPETITORS], all taken from live pages: [PASTE]. Produce three lists: - SHARED: claims we all make. Quote one example of each from two different vendors. - CONTESTED: claims where we say opposite things about the same thing. - OURS ALONE: claims only we make, and that nobody else in this set makes. Then tell me honestly which items in the third list are genuinely differentiating and which are category boilerplate that the others simply have not bothered to write down.
Competitive call prep
You supply: The account context, the competitor in the deal, and your current battlecard.
I have a call in [TIME] with [ACCOUNT], a [SIZE] [INDUSTRY] company. [COMPETITOR] is in the deal. Here is the account context and our current battlecard: [PASTE]. Give me, in under 200 words total: - the two things about this competitor that matter for THIS account, not in general - the single question most likely to surface whether they are a real contender - the one claim the buyer is most likely to repeat from the competitor, and my answer - what I should not say Prioritise by what is relevant to this account's size and industry. Say which parts of the battlecard you judged irrelevant here and why.
Displacing an incumbent
You supply: What the incumbent is contracted for, the renewal date, and the switching costs involved.
[ACCOUNT] currently uses [COMPETITOR]. Here is what I know about their setup, contract and renewal timing: [PASTE]. Build a displacement plan covering: - the switching costs a buyer would actually face, separated into data, process, integrations and retraining - which of those we can remove, which we can reduce, and which we cannot touch - the timing that makes a switch realistic given the renewal date - the two internal stakeholders most likely to resist, and what each one is protecting - what would make this account not worth pursuing Be explicit about which of these I told you and which you are inferring from the account type.
Read competitive signals over time
One-off analysis answers what a competitor is. These answer what changed, which is the question a model cannot hold on its own because it has no memory of last month.
Reading a competitor's changelog
You supply: Their changelog or release notes for a stated period, with dates attached.
Here are the changelog entries for [COMPETITOR] between [START] and [END]: [PASTE]. Group them into themes and, for each theme, give the number of entries, the date range, and whether the entries are launches, improvements or maintenance. Then answer: where is their engineering effort concentrated, and what did they NOT ship in this period that the themes would predict? Two rules. Judge investment by the substance of entries, not by their count, since a vendor can post ten small fixes and one platform change in the same week. And do not infer a roadmap: say what the period shows, and say plainly where the pattern is too short to read.
Spotting a pricing change
You supply: The same pricing page saved twice, each copy labelled with the date you saved it.
Here are two copies of [COMPETITOR]'s pricing page, the first saved [DATE A] and the second saved [DATE B]: [PASTE]. List every difference, grouped as: - price changes, with old and new figures - packaging changes: a capability moving between tiers, a limit changing, a plan renamed or removed - wording changes that alter what a buyer is promised - changes to trial, minimum seats or billing terms Packaging changes matter most and are the easiest to miss, so check tier by tier rather than reading the page top to bottom. If a feature appears in both copies but under a different plan, that is a packaging change, not a no-change. Say explicitly if nothing changed.
Reading competitor job postings
You supply: Their current openings, saved with dates, plus any you saved in an earlier period.
Here are [COMPETITOR]'s open roles, saved [DATE]: [PASTE]. Summarise by function, seniority and location. Then read the postings themselves rather than the titles: quote any line that names a technology, a market, a customer segment or a named process, and say what each one implies. Answer two questions: - what does this hiring pattern suggest they are building or entering? - what would the same pattern look like if they were simply replacing attrition? Tell me which of the two the evidence actually supports, or say it cannot distinguish them.
Reading an earnings call
You supply: The transcript, and ideally the prior quarter's transcript to compare language against.
Here is [COMPANY]'s earnings call transcript for [QUARTER]: [PASTE]. Give me: - the numbers management led with, and any metric they reported last quarter and did not report this one - every mention of competition, quoted, with who asked - the analyst questions management answered indirectly, with the question and the answer side by side - language that changed from the previous quarter, if I have given you both Separate prepared remarks from the Q&A throughout. Prepared remarks are written; the Q&A is not, and they are not equally informative.
Reading a competitor's filings
You supply: The filing itself, and the section you care about identified before you start.
Here is [COMPANY]'s [FILING TYPE] for [PERIOD]: [PASTE]. Extract, quoting the filing and giving the section for each: - how they describe their market and who they name as competition - the risk factors that are specific to this company rather than boilerplate - any segment, customer concentration or geographic disclosure - language that changed from the prior filing, if I have provided it Risk factors are mostly standard text. Flag only the ones that name something specific, and say what makes each one specific.
Reading a funding announcement
You supply: The announcement, the investor list, and what the company said they will spend it on.
[COMPETITOR] announced a [AMOUNT] [ROUND] round. Here is the announcement, the investor list and any coverage I have: [PASTE]. Tell me: - what they said the money is for, in their words - what the investor list suggests about the direction, and how confident that reading is - what this changes about how they will compete in the next four quarters, and what it does not change - which claims here are the company's own framing rather than independently reported Be specific about the last one. A funding announcement is a marketing document, and the amount raised says nothing about revenue.
A weekly competitor digest
You supply: Everything you collected this period, with dates and where each item came from.
Here is everything I collected on [COMPETITORS] between [START] and [END], each item with its date and origin: [PASTE]. Write a digest of at most 300 words for [AUDIENCE]. Order by what changes a decision, not by date. For each item give: what happened, what it means for us, and what if anything we should do. Items where the honest answer to the third is "nothing" still belong in the digest - say "no action" rather than manufacturing one. End with a line naming what you would have expected to see in this period and did not.
On the page: Two more prompts, the one input a model cannot supply for itself, and what a genuinely quiet week should say instead of nothing.
Reading competitor ad creative
You supply: The ad creative and copy you saved, with the dates each was running.
Here is ad copy and creative for [COMPETITOR], saved [DATE], with the run dates I could see: [PASTE]. Group the ads by the promise they make and by the audience they address. For each group give the number of variants, how long they have been running, and the exact hook used. Then tell me: which message are they investing behind, judged by variant count and duration rather than by how good the ad is? And which of their ads address an objection rather than a benefit, since those tell you what their buyers push back on. Do not infer budget. The number of variants is not spend.
Report competitive intelligence to the business
Turning an analysis into something a busy reader acts on. The failure mode here is not accuracy, it is length.
The executive brief
You supply: The finished analysis, and a clear statement of the decision it is meant to serve.
Turn the analysis below into a one-page brief for [AUDIENCE], who has [TIME] to read it and must decide [DECISION]. Structure: the conclusion first, then what changed, then why it matters to us, then the two or three decisions it implies with a named owner for each. Hard limits: 300 words, no heading longer than six words, and no sentence that would survive unchanged in a brief about a different competitor. Leave out anything that does not bear on the decision named above, and list what you left out at the end so I can check your judgement. ANALYSIS: [PASTE]
The full competitive report
You supply: Every source you want represented, each labelled with its date and origin.
Assemble a competitive intelligence report on [COMPETITORS] for [AUDIENCE] from the sources below. Sections: what changed this period, positioning, product, pricing, go-to-market, what customers say, and what we recommend. Every factual claim carries its source and the date that source was captured. Any section where my material is thin gets a line saying what is missing rather than being padded. At the end, list the three things a reader would most want to know that these sources cannot answer. SOURCES: [PASTE]
Mapping the competitive landscape
You supply: Your competitor set with the evidence that placed each one, and the two axes you chose.
Here is my competitor set with the evidence I hold on each: [PASTE]. Place them on these two axes: [AXIS 1] and [AXIS 2]. For every placement, state the evidence and how confident it is. Where two companies would land in the same place, say what would separate them and what evidence I would need to do it. Then challenge the axes themselves: do they separate this set usefully, or do they put most companies in one corner? If the second, propose two axes that would do better and say why.
Set the model up for competitive work
Reusable instructions rather than one-off asks: what to put in a system prompt, a project, or a custom AI assistant so that every prompt above behaves.
Forcing a model to use only your sources
You supply: Nothing except the instruction itself. It goes above every other prompt here.
Work only from the material I provide in this conversation. Rules, in priority order: 1. If a fact is not in my material, say "not in the provided sources". Do not supply it from memory. 2. Every factual claim ends with the source it came from, in square brackets. 3. Where two of my sources disagree, show both and say they disagree. Do not resolve it. 4. Quote exact wording for anything a reader might dispute: prices, plan names, capability claims, numbers. 5. Distinguish what a source states from what you conclude. Label conclusions as such. 6. If my material is too thin to answer, say so and name what is missing, rather than answering anyway. Confirm you have read these rules before I paste the material.
On the page: Two more prompts, the failure each line of the instruction is written against, and the same question answered with and without it.
A system prompt for competitive work
You supply: Your company, your category, and the verification standard your team works to.
You support the competitive intelligence function at [COMPANY], which sells [PRODUCT] to [BUYER]. How you work: - You work from the material provided in the conversation. You do not answer competitor questions from memory, because competitor facts change and your memory has a date on it. - Every factual claim carries its source. Claims without one are labelled [UNSOURCED]. - You separate what a source states from what you infer, always, even when the inference is obvious. - You never assert what a competitor will do next. You describe what they have done and what it would imply if continued. - You are never disparaging about a competitor. Everything you draft may be read aloud to a buyer who likes them. - When asked for something your material cannot support, you say so and name what would be needed. Default output: the answer first, the evidence second, and what is still unknown third.
Instructions for a competitive AI assistant
You supply: Your battlecards, positioning and competitor set, loaded as the assistant's knowledge.
You are the competitive assistant for [COMPANY]. Your knowledge files contain our battlecards, positioning and competitor profiles, each with the date it was last reviewed. On every answer: 1. Name which knowledge file you used and the date it was last reviewed. 2. If that date is more than [N] days old, say so before answering. 3. If the question is about a competitor with no file, say so. Do not answer from general knowledge. 4. For anything a rep will say to a buyer, give the factual version and flag anything you could not source. You are talking to sales reps between calls. Lead with the answer, keep it under 150 words unless asked for more, and never open by restating the question.
Briefing an agent to do this on a schedule
You supply: A named set of inputs the agent can read, and a rule for what is worth telling you about.
You run on a schedule and report to [AUDIENCE]. Each run, read the inputs I have connected and compare them with the state recorded at the end of your last run. Report only what changed. For each change: what it was, which input showed it, when, and whether it needs a decision. A run with no changes reports "no changes" and stops - do not manufacture an item to fill the report. Rank by whether it changes a decision, never by recency. Two things you must not do: do not assert a change you cannot point to in an input, and do not summarise the same change twice across runs. At the end of every run, record the state you compared against, so the next run has a baseline.
Verifying a competitive analysis before it reaches a customer
Verification is usually described as a final quality step, which makes it the step that gets skipped. It is faster to treat it as a property of the prompt: if the output arrives already sorted into what was sourced and what was inferred, checking it is a five-minute job rather than a re-read.
Three habits do most of the work. Ask for the label rather than the verdict, so every claim arrives marked sourced, inferred or unsupported. Ask for exact quotes on anything a buyer could dispute, because a paraphrase of a pricing page is where small errors enter. And check the claims a person will repeat out loud first: plan names, figures, and capability claims, in that order, since those are the ones that cost credibility in a live conversation.
What you are left with after that is a genuine division of labour. The model did the reading, the grouping and the drafting, which is most of the hours. You did the checking, which is the part that carries your name. How to do a competitive analysis with AI works the whole sequence through end to end, including the confidentiality question that decides what may go into the window at all.
Where the output of a competitive prompt has to land
A good analysis that arrives in an unfamiliar shape gets read once and then ignored, which is the quietest way for this work to fail. The fix is unglamorous: decide where the output goes before you run the prompt, and make the prompt produce that shape rather than a shape you will reformat afterwards.
For most of these jobs the destination already exists. A battlecard draft belongs in the battlecard template your reps already open, not in a chat window nobody returns to. A feature comparison belongs in the feature comparison matrix, which will also export it. Several prompts here end by specifying columns for exactly this reason: a table with named columns drops into a structure, and prose does not.
The other thing that belongs in the destination is a date. Every claim an analysis makes is true as of the day its inputs were captured, and writing that down beside the claim is what lets somebody six weeks later tell a fact from a fossil. Intelligence freshness is the measured version of the same idea, for teams that want to know how much of what they hold is still current.
A competitive analysis prompt runs once, and competitors keep moving
Everything above is about one sitting: you gathered the pages, you ran the prompt, you checked the output, and you have something good. The awkward part arrives two weeks later, when a competitor repackages a tier and every claim built on that page is quietly wrong while looking exactly as it did when it was right.
Nothing in the prompt can tell you that happened. The model has no memory of the page you pasted last month and no way to know it changed, which is why the work decays in a particular way: not visibly, into something obviously stale, but invisibly, into something that still reads well. A repackaging leaves every published figure identical and changes what the configuration means. A capability moves between tiers and the comparison that was accurate becomes a claim a competitor can correct in front of your buyer.
Being late on that is what costs something. A rep quoting a price that changed last quarter loses the room, and no amount of prompt engineering prevents it, because the problem is the age of the input rather than the quality of the instruction.
The recurring half of this is what competitive intelligence platforms are for: they watch the sources continuously, so a change reaches you when it happens instead of the next time somebody thinks to look. Flares tracks competitor pricing, packaging, product changes and positioning across the companies you name, which means the material you paste into any prompt on this page is this week’s rather than the last time it was collected.
What it does not do is replace the thinking these prompts are for. Deciding what a change means, which competitor deserves a battlecard, and what to tell a rep before a call are judgements, and a feed of current facts makes them better rather than making them for you.
Competitive analysis prompts fed by current data
Flares keeps competitor pricing, product and positioning current, so what you paste in is this week's.
Discover Flares14-day free trial · 30-second setup
Competitive analysis prompts FAQ
What is the best AI prompt for competitor analysis?
There is no single best one, because the prompt is the smaller half of the problem. The same words produce a usable comparison or a confident invention depending entirely on whether the competitor's actual pages are in the context window. A short prompt over saved sources beats an elaborate prompt over nothing, every time. If you want one to start from, use the grounding instruction that forces sources-only answers, then add the task prompt for the job you are doing.
Can ChatGPT do a competitive analysis?
It can do the structuring, comparing and drafting extremely well, and it cannot do the knowing. Ask it to organise material you supply and the output is genuinely useful. Ask it what a competitor charges and you get an answer shaped like a fact, sourced from whenever its training data was assembled. The workflow that works inverts the usual one: gather first, then prompt.
Why does ChatGPT make up competitor pricing?
Mostly it does not invent prices outright. The commoner failures are quieter and harder to catch. Asked for a price it returns one number where the live page shows two, because most vendors list an annual and a monthly rate that can differ by a factor of three. And it answers the question you asked without volunteering the one-time onboarding fees, seat minimums or credit allocations printed beside the headline figure. Both produce an answer that is wrong in a way that survives a quick sanity check.
What should you give an AI before asking it about a competitor?
The pages themselves, saved on a date you record: their pricing page with the billing toggle in the state you captured it, the product pages, and any reviews or transcripts you hold. Then the instruction that it must work only from those and say so when something is not there. The date matters as much as the pages, because every claim the output makes is only true as of the day you captured the input.
Are AI prompts for competitive analysis actually reliable?
The reliable part is the transformation: extracting, grouping, comparing, and rewriting long material into something a person can read. That part is genuinely good and worth automating. The unreliable part is recall, and it stays unreliable however you word the prompt. Treat every factual claim in the output as a draft that needs checking against the source it came from, and structure the prompt so it tells you which claims those are.
What is the difference between a prompt and a system prompt for competitive work?
A task prompt asks for one output once. A system prompt sets the rules every later answer follows: work only from supplied material, cite the source on every claim, never assert what a competitor will do next, never write anything disparaging. The second is worth more over a quarter, because it fixes the behaviours you would otherwise re-specify in every single request.
Can AI write a battlecard you can send to sales?
It can write the draft, and the draft is most of the work. What it cannot do is confirm that the competitor's pricing tier, plan name or capability claim is still accurate on the day a rep says it out loud on a call. Draft with the model, verify the factual claims against the competitor's live pages, and keep a record of when each claim was last checked. A battlecard's real failure mode is not a bad argument, it is a confident fact that stopped being true two months ago.
How do you stop AI inventing features a competitor does not have?
Ask for a confidence label rather than a verdict. Instruct it to mark every feature EXPLICIT when a supplied page names the capability outright, VAGUE when a page gestures at it without saying what it does, and ABSENT when no supplied page mentions it. Then make it say that ABSENT means "not in my sources" rather than "they do not have it". That one distinction removes most of the inference errors, because it gives the model somewhere honest to put uncertainty.
Which AI is best for competitive analysis?
The differences matter far less than the sourcing. Any current AI assistant handles the reasoning; what varies is how much material it takes at once, whether it cites what you gave it, and where your data ends up. Choose on the practical grounds your company already applies to vendors, and spend the time you save on gathering better inputs, which is where the quality actually comes from.
Do these prompts work with Claude, Gemini and Perplexity as well as ChatGPT?
Yes. Every prompt here is written to be model-agnostic, because the instructions that matter — work only from what I gave you, cite each claim, separate what a source states from what you concluded — are about the task rather than the AI assistant you run them in. Per-model setup differs, and that belongs with the guides on using each assistant rather than inside a prompt.
Is it safe to paste competitor research into an AI assistant?
Public pages you saved carry little risk. The care is needed for what you add alongside them: call transcripts, win/loss interviews, pipeline data and customer names are your own confidential material, not the competitor's. Check your plan's data retention and training terms before that material goes in, and prefer the business or enterprise tiers your company has already reviewed.
How often do competitive analysis prompts need to be re-run?
The prompt does not decay; the inputs do. A pricing comparison is accurate until a competitor repackages a tier, which they do without announcing it. A battlecard drifts the first time a claim in it is quietly corrected on a product page. The practical rule is to re-run whenever an input changes rather than on a calendar, which is only possible if something is watching the inputs.
Can an AI agent monitor competitors on a schedule?
An agent can compare what it reads now with a state it recorded last time and report the difference, which is genuinely useful and is the shape of the agent brief in this library. What it cannot do on its own is decide what deserves your attention, and an agent reporting every change it finds recreates the noise problem it was supposed to solve. Ranking by whether something changes a decision is the part that needs specifying.
Are there free prompts for competitive analysis?
Every prompt on this page is free to copy and use, and there is nothing to sign up for. The scarce resource in competitive work has never been the prompt; it is current, sourced material about the companies you compete with, and that is the part nobody can give you in a text box.
Live sources under every competitive analysis prompt
Flares watches the sources these prompts depend on and tells you the moment one of them changes.
Discover Flares14-day free trial · 30-second setup