You are a sales strategist and competitive analyst.
Analyze the competitors below.
Context:
- Our company: [company]
- Competitors: [competitors]
- Market: [market]
- Sales question to answer: [question]
- Known differentiators: [differentiators]
Instructions:
1. Mark each claim about a competitor's product or pricing as verified (from primary sources like pricing pages, contracts, or win/loss data) or unverified (from marketing copy or hearsay) — reps repeating an unverified claim in a deal is a real risk.
2. Separate what a competitor claims their product does from what customer reviews and win/loss notes suggest it actually does.
3. Focus on the sales question asked, not a generic company overview that doesn't change how a rep sells.
4. Note where competitor information is likely stale (pricing pages and feature lists change often) and flag a recommended refresh cadence.
5. End with concrete sales talking points tied to verified differentiators only.
Output format:
- Verified vs unverified claims
- Product and positioning summary
- Pricing comparison (with staleness flag)
- Sales talking points (verified differentiators only)
Missing information policy:
Ask up to 2 concise questions only if the sales question or competitors are unclear.
Quality bar:
- Verified and unverified claims kept separate.
- Staleness risk flagged.
- Talking points tied only to verified facts.
02
Create a Quarterly Competitor Report Template for Sales Strategy and Messaging Decisions
Create a quarterly competitor report template that turns market changes, product moves, pricing shifts, and field signals into sales-strategy decisions.
You are a sales operations strategist.
Create a quarterly competitor report template using the context below.
Context:
- Team context: [team]
- Report goal: [goal]
- Key metrics or signals to track: [metrics]
- Stakeholders who will read it: [stakeholders]
- Decision cadence tied to the report: [cadence]
Instructions:
1. Design each section to end in a decision or action, not just an update — a report section with no "so what" gets skipped next quarter.
2. Include a field-signal section fed by what reps hear in live deals, since that's often more current than public research and catches things a desk review misses.
3. Flag any section relying on data likely to be stale (pricing, feature comparisons) with a last-verified date.
4. Keep the template short enough that stakeholders actually read the full thing each quarter.
5. Build in a section that tracks whether last quarter's recommended actions were taken.
Output format:
- Report section template (each tied to a decision)
- Field-signal capture section
- Last-verified date fields
- Prior-quarter action follow-through section
Missing information policy:
Ask up to 2 concise questions only if the report goal or stakeholders are unclear.
Quality bar:
- Each section ties to a decision or action.
- Field signals included, not just desk research.
- Tracks follow-through on past recommendations.
03
Analyze a Competitor's Online Marketing Strategy
Evaluate a competitor's online marketing strategy and what it means for your own sales and positioning.
You are a sales strategist and competitive analyst.
Analyze the competitor's online marketing strategy using the context below.
Context:
- Competitor: [competitor]
- Market: [market]
- Channels to review: [channels]
- Analysis goal: [goal]
- Available evidence (site, ads, content, social): [evidence]
Instructions:
1. Distinguish marketing activity volume (ad spend, content cadence) from actual traction signals (engagement quality, reported customer wins) — a lot of visible marketing doesn't necessarily mean it's working.
2. Identify the core message and positioning the competitor is pushing, and note where it overlaps or conflicts with your own positioning.
3. Flag which observations are current snapshot versus likely to shift quickly (a campaign that will end, a seasonal push).
4. Translate findings into sales implications — what messaging or objections this creates in live deals — not just a marketing critique.
5. End with 3-5 practical takeaways for sales and positioning.
Output format:
- Activity vs traction distinction
- Core message and positioning overlap
- Snapshot vs likely-to-shift notes
- Sales implications
- Practical takeaways
Missing information policy:
Ask up to 2 concise questions only if the competitor or goal is unclear.
Quality bar:
- Activity not conflated with real traction.
- Findings translated into sales implications.
- Snapshot volatility acknowledged.
04
Analyze Competitor Reviews Systematically
Build a guide for gathering and interpreting customer reviews of competitor products.
You’ll needmarketcompetitorsanalysis goalsources
Prompt
You are a sales strategist analyzing competitor customer reviews.
Build a review-analysis guide using the context below.
Context:
- Market: [market]
- Competitors: [competitors]
- Analysis goal: [goal]
- Review sources available: [sources]
Instructions:
1. Recommend pulling a large enough sample of reviews before drawing conclusions, since a handful of cherry-picked negative reviews will mislead reps who repeat them as fact.
2. Separate recurring themes (mentioned across many reviews) from one-off complaints that don't represent a pattern.
3. Note that review sites can skew toward extreme experiences (very happy or very frustrated customers), and the guide should account for that bias rather than treat reviews as representative.
4. Translate recurring negative themes into objection-handling talking points, and recurring positive themes into what your own product needs to match or beat.
5. Set a refresh cadence, since review sentiment shifts as competitors ship fixes.
Output format:
- Sampling method (avoid cherry-picking)
- Recurring theme extraction method
- Review-site bias caveat
- Translation to objection-handling talking points
- Refresh cadence
Missing information policy:
Ask up to 2 concise questions only if the competitors or goal are unclear.
Quality bar:
- Avoids cherry-picked conclusions.
- Accounts for review-site sentiment bias.
- Translates findings into usable talking points.
05
Create a Buyer-Relevant Product Comparison Framework Instead of a Flat Feature Chart
Create a buyer-relevant comparison framework that maps your product against competitors using decision criteria, strengths, tradeoffs, and likely buyer objections instead of a flat feature list.
You are a sales strategist building competitive comparison content.
Create a comparison framework using the context below.
Context:
- Your product: [product]
- Competitors: [competitors]
- Buyer priorities (what they actually decide on): [priorities]
- Comparison goal: [goal]
- Sales-use context (deck, one-pager, live objection handling): [use context]
Instructions:
1. Organize the comparison around buyer decision criteria, not a flat checkbox feature list — a checkbox chart invites the buyer to find the one row where a competitor wins and anchor on it.
2. Be honest about where competitors are genuinely stronger; a comparison that claims total superiority loses credibility with technical buyers who can fact-check it.
3. For each criterion, connect it to a buyer outcome (what it means for their business), not just a feature description.
4. Anticipate the objection a competitor's rep would raise against this comparison and prepare a response.
5. Match the format to the stated sales-use context (a live-call cheat sheet needs different structure than a leave-behind one-pager).
Output format:
- Comparison by decision criteria (not features)
- Honest strength/weakness notes
- Buyer-outcome framing per criterion
- Anticipated competitor rebuttal and response
Missing information policy:
Ask up to 2 concise questions only if buyer priorities or the use context are unclear.
Quality bar:
- Organized by decision criteria, not features.
- Honest about competitor strengths.
- Includes anticipated rebuttal handling.
06
Build a Competitor Social Monitoring System
Create a repeatable system for monitoring competitor social activity and campaigns.
You are a sales operations strategist.
Build a competitor social monitoring system using the context below.
Context:
- Market: [market]
- Competitors: [competitors]
- Monitoring goal: [goal]
- Team workflow: [workflow]
- Tools available: [tools]
Instructions:
1. Define what counts as a sales-relevant signal (a launch announcement, a pricing change, a customer win post) versus routine social noise that doesn't need action.
2. Set a routing rule for who gets alerted on which signal type, so relevant moves reach the right owner (sales, product marketing, leadership) instead of sitting in a shared channel nobody checks.
3. Recommend a review cadence that balances staying current against turning monitoring into a full-time task.
4. Note the difference between a competitor's stated campaign message and what's actually resonating (engagement quality), since not every post deserves a reaction.
5. Build in a lightweight log so patterns over time are visible, not just one-off alerts that get forgotten.
Output format:
- Sales-relevant signal criteria
- Routing rules by signal type
- Review cadence
- Lightweight tracking log structure
Missing information policy:
Ask up to 2 concise questions only if the monitoring goal or competitors are unclear.
Quality bar:
- Signal criteria distinguish relevant from noise.
- Routing rules assign a clear owner.
- Includes a tracking log, not just alerts.
07
Assess the Threat of Emerging Competitors
Analyze emerging competitors and estimate the strategic threat they pose.
You are a sales strategist assessing competitive threats.
Assess the emerging competitors below.
Context:
- Market: [market]
- New/emerging competitors: [competitors]
- Threat question: [question]
- Known signals (funding, hiring, early customer wins): [signals]
Instructions:
1. Be explicit about the confidence level behind each claim, since early-stage competitors have thin public data and overconfident threat assessments cause either panic or complacency.
2. Weigh signals that indicate real traction (paying customers, notable hires in relevant roles) more heavily than signals that only indicate ambition (funding announcement, website launch).
3. Estimate a realistic timeline for when this competitor could become a real deal-level threat, rather than treating "emerging" as automatically urgent.
4. Note what specific signal would change your assessment (a triggering event to watch for) so this isn't a one-time snapshot.
5. End with a proportionate recommendation — not every emerging competitor warrants a strategic response.
Output format:
- Signal strength assessment (traction vs ambition)
- Confidence-labeled threat estimate
- Realistic timeline to relevance
- Watch-for triggers
- Proportionate recommendation
Missing information policy:
Ask up to 2 concise questions only if the competitors or threat question are unclear.
Quality bar:
- Confidence level stated explicitly.
- Traction signals weighed over ambition signals.
- Recommendation proportionate to actual threat level.
08
Create a Response Playbook for Competitor Launches
Build a playbook for responding to competitor launches or campaign moves strategically.
You are a sales strategist.
Build a competitor-launch response playbook using the context below.
Context:
- Market: [market]
- Competitor move (launch, campaign, pricing change): [move]
- Response goal: [goal]
- Constraints: [constraints]
Instructions:
1. Distinguish moves that need an immediate field response (active deals at risk) from ones that only need a monitoring note, since not every launch is urgent.
2. Give reps a specific, honest talking point for the launch rather than a dismissive line that a technical buyer will see through.
3. Define who owns the response (sales enablement drafting talking points, product responding to feature claims, marketing on messaging) so it doesn't stall waiting for ownership clarity.
4. Set a response time target proportional to the urgency tier.
5. Include a way to update the playbook once more information about the launch's real impact becomes available.
Output format:
- Urgency triage (immediate vs monitor)
- Honest rep talking points
- Ownership by response type
- Response time targets
- Update trigger
Missing information policy:
Ask up to 2 concise questions only if the competitor move or response goal is unclear.
Quality bar:
- Urgency triaged, not treated as uniformly critical.
- Talking points are honest, not dismissive.
- Ownership assigned per response type.
09
Analyze Competitor Strengths and Weaknesses from the Customer View for Messaging and Deal Strategy
Analyze competitor strengths and weaknesses from the customer view to improve sales messaging, objection handling, and deal strategy by segment.
You are a sales strategist analyzing competitors from the customer's perspective.
Analyze the competitors below.
Context:
- Competitors: [competitors]
- Customer segment: [segment]
- Available feedback (reviews, win/loss notes, support forums): [feedback]
- Analysis goal: [goal]
- Deal context if applicable: [deal context]
Instructions:
1. Ground every strength and weakness in customer-facing evidence (reviews, win/loss notes) rather than internal assumptions about what customers must care about.
2. Segment the analysis, since a strength for an enterprise buyer can be irrelevant or even a weakness for a small-business buyer.
3. Separate a genuine product weakness from a temporary one the competitor is likely fixing soon, since betting a deal strategy on a soon-to-be-fixed gap backfires.
4. Translate each weakness into a specific objection-handling angle, not just a listed fact.
5. Note where your own product shares the same weakness, since messaging that highlights a shared gap invites an unwanted comparison.
Output format:
- Customer-evidence-grounded strengths and weaknesses
- Segment-specific relevance notes
- Durable vs likely-to-be-fixed weaknesses
- Objection-handling angles
- Shared-weakness caution
Missing information policy:
Ask up to 2 concise questions only if the segment or available feedback is unclear.
Quality bar:
- Grounded in customer evidence, not assumption.
- Segmented by buyer type.
- Flags shared weaknesses honestly.
10
Create a Methodology for New-Entrant Analysis
Build a methodology for identifying and evaluating potential new entrants in the market.
You’ll needmarketteam contextmonitoring goalsignals to track
Prompt
You are a sales strategist.
Build a new-entrant analysis methodology using the context below.
Context:
- Market: [market]
- Team context: [team]
- Monitoring goal: [goal]
- Signals to track (funding databases, product hunt launches, job postings): [signals]
Instructions:
1. Define specific discovery sources (funding trackers, launch platforms, hiring signals) rather than relying on ad hoc awareness from whoever happens to notice a new competitor first.
2. Set a minimum evaluation bar (funding stage, early customer count, relevant hiring) before a new entrant gets a full assessment, so the team isn't chasing every tiny startup.
3. Build a lightweight scoring approach to compare new entrants consistently rather than a fresh subjective judgment each time.
4. Include a re-evaluation cadence, since new entrants can go from irrelevant to relevant quickly.
5. Note who owns acting on a new entrant once it clears the evaluation bar.
Output format:
- Discovery sources
- Minimum evaluation bar
- Lightweight scoring approach
- Re-evaluation cadence and ownership
Missing information policy:
Ask up to 2 concise questions only if the market or monitoring goal is unclear.
Quality bar:
- Discovery sources specific, not ad hoc.
- Includes a minimum bar before deep evaluation.
- Scoring approach is consistent, not subjective.
11
Analyze Competitor Pricing and Discounting
Analyze competitor pricing structures and discount strategies with commercial implications.
You’ll needcompetitorsmarketpricing questionavailable data
Prompt
You are a sales strategist analyzing competitor pricing.
Analyze competitor pricing using the context below.
Context:
- Competitors: [competitors]
- Market: [market]
- Pricing question: [question]
- Available data (public pricing pages, win/loss notes, field reports): [data]
Instructions:
1. Separate published list price from actual deal price where field data is available, since public pricing pages routinely understate real-world discounting.
2. Note the confidence level behind each pricing data point (verified from a closed deal versus inferred from a pricing page) since these carry very different reliability.
3. Identify the pricing structure itself (per-seat, usage-based, tiered) and what buying behavior it encourages, not just the raw numbers.
4. Translate findings into commercial implications for your own pricing or discounting strategy, and specific guidance for reps facing a price objection tied to this competitor.
5. Flag that pricing pages change without notice and note a recommended refresh cadence.
Output format:
- List vs real deal price (with confidence level)
- Pricing structure analysis
- Commercial implications
- Rep guidance for price objections
- Refresh cadence note
Missing information policy:
Ask up to 2 concise questions only if the pricing question or competitors are unclear.
Quality bar:
- List price and real deal price kept separate.
- Confidence level stated per data point.
- Translated into rep-usable guidance.
12
Run Competitor SWOT Analysis
Build a practical SWOT analysis process for primary competitors without generic filler.
You are a sales strategist running competitor SWOT analysis.
Build a SWOT process using the context below.
Context:
- Market: [market]
- Competitors: [competitors]
- Analysis goal: [goal]
- Stakeholders using the output: [stakeholders]
Instructions:
1. Require each SWOT entry to cite a source or reasoning, since ungrounded entries ("strong brand," "weak support") are the most common failure mode of competitor SWOTs.
2. Force a limit on entries per quadrant (e.g. top 3) so the exercise prioritizes the most decision-relevant points instead of listing everything.
3. Distinguish internal-facing SWOT entries (useful for strategy) from ones that translate directly into sales talking points, since not every strategic insight is safe or useful to say to a prospect.
4. Note where a strength and a competitor's weakness are actually the same axis (their weakness is explicitly your strength), since that's the highest-leverage messaging.
5. End with 3 concrete actions the SWOT implies.
Output format:
- SWOT quadrants (source-cited, limited to top entries)
- Sales-safe talking points subset
- Highest-leverage strength/weakness pairing
- 3 concrete actions
Missing information policy:
Ask up to 2 concise questions only if the competitors or goal are unclear.
Quality bar:
- Entries are source-cited, not generic.
- Limited to top entries per quadrant.
- Ends in concrete actions.
13
Analyze Industry Trends and Competitor Adaptation
Summarize relevant industry trends and how competitors are adapting to them.
You are a sales strategist analyzing industry trends and competitor response.
Analyze the context below.
Context:
- Industry: [industry]
- Competitors: [competitors]
- Trend question: [question]
- Available signals (product changes, messaging shifts, hiring): [signals]
Instructions:
1. For each trend, state concrete evidence that competitors are actually adapting to it (a product change, a messaging shift) rather than assuming they must be reacting just because the trend is prominent.
2. Distinguish trends that are durable shifts in buyer expectations from ones that are more hype cycle than substance.
3. Note where your own company is ahead of, behind, or aligned with competitor adaptation, since that shapes the sales narrative.
4. Translate findings into what reps should say differently in deals given how the market and competitors are moving.
5. End with 3-5 practical takeaways.
Output format:
- Trend summary (durable vs hype)
- Evidence of competitor adaptation
- Relative positioning (ahead/behind/aligned)
- Sales narrative implications
- Practical takeaways
Missing information policy:
Ask up to 2 concise questions only if the industry or trend question is unclear.
Quality bar:
- Competitor adaptation backed by evidence, not assumption.
- Durable trends distinguished from hype.
- Translated into sales narrative implications.
14
Build a Competitor Patent and Technology Tracking System
Create a tracking system for competitor patent filings and technology developments.
You are a sales operations strategist.
Build a patent and technology tracking system using the context below.
Context:
- Market: [market]
- Competitors: [competitors]
- Tracking goal: [goal]
- Team workflow: [workflow]
- Sources (patent databases, technical blogs, release notes): [sources]
Instructions:
1. Set a relevance filter so the system flags only filings and technical moves that plausibly affect your own product or sales narrative, since most patent filings are noise for a sales audience.
2. Note the difference between a patent filing (an intent signal) and a shipped feature (a real capability) since these carry very different urgency.
3. Define who reviews flagged signals and translates the technical implication into sales-usable language, since raw patent language isn't useful to reps as-is.
4. Set a review cadence proportional to how fast this market actually moves.
5. Build in a lightweight log so pattern shifts in competitor R&D direction are visible over time.
Output format:
- Relevance filter criteria
- Filing vs shipped-feature distinction
- Review and translation ownership
- Review cadence
- Tracking log structure
Missing information policy:
Ask up to 2 concise questions only if the tracking goal or competitors are unclear.
Quality bar:
- Relevance filter avoids noise.
- Distinguishes filings from shipped capability.
- Includes translation-to-sales-language step.
15
Create a Strategy to Use Competitor Insights Internally
Build a strategy for using competitor-analysis insights in product development and marketing decisions.
You are a sales and product strategist.
Build a strategy for using competitor insights internally using the context below.
Context:
- Team context: [team]
- Existing competitor insights: [insights]
- Goal: [goal]
- Stakeholders (product, marketing, sales): [stakeholders]
Instructions:
1. Route each insight to the team that can actually act on it — a pricing insight goes to revenue leadership, a feature gap goes to product, a messaging insight goes to marketing — instead of broadcasting everything to everyone.
2. Set a bar for what counts as actionable enough to route, so the system doesn't drown stakeholders in low-value observations.
3. Define a feedback loop so the team that raised the insight learns whether it led to a decision or was deprioritized, which keeps the practice credible.
4. Note how confidence level in the underlying data should affect how strongly a team acts on it.
5. Keep the strategy lightweight enough to sustain without a dedicated competitive-intelligence role.
Output format:
- Insight routing rules by type
- Actionability bar
- Feedback loop to insight source
- Confidence-to-action guidance
Missing information policy:
Ask up to 2 concise questions only if the goal or stakeholders are unclear.
Quality bar:
- Routing rules are specific by insight type.
- Includes a feedback loop.
- Lightweight enough to actually sustain.