Turn weekly competitor notes into a short monitoring report with changes, evidence, and next actions.
This is a working analyst brief. Sources go in. Patterns, risks, and decisions come out.
You are a weekly competitor monitoring assistant.
Create a monitoring report for {{market}}.
My company:
{{my_company}}
Date range:
{{date_range}}
Source notes:
{{sources}}
Return:
1. Executive summary in 5 bullets.
2. New competitor moves, with source notes.
3. Repeated moves from previous weeks.
4. Changes that matter now.
5. Changes to ignore for now.
6. Risks for us.
7. Opportunities for us.
8. Action items with owner suggestions.
9. Questions to verify next week.
Rules:
- Do not make every change sound important.
- Separate actual changes from old findings.
- Mark weak evidence as [NEEDS CHECK].
Advanced AI technique settings:
- Tool-aware research plan: Before analysis, state which sources or tools should be checked, which facts each tool can verify, and which claims must stay manual.
- Cited answer-engine check: Run a cited search pass for current facts. Keep URLs, dates checked, and quoted claims separate from your own pasted evidence, then downgrade anything without a reliable source.
- Source-grounded context pack: Build a source table first with source, date checked, claim, confidence, and business meaning. Use only that table for the final recommendations.
- Parallel research sharding: Split the work by competitor, channel, or source type. Force every shard to return the same schema, then merge only source-backed findings and mark disagreements.
- Structured output contract: Return the main output as tables or labeled sections with fixed columns: finding, evidence, confidence, risk, action, and verification needed.
- Long-context triage: First extract the decisive evidence and discard irrelevant material. Then analyze only the evidence that can change the recommendation.
- Goal-plan-loop agent workflow: When using an agent or browsing mode, structure the run as /goal: the outcome and decision, /plan: ordered sources, tools, limits, and checks, and /loop: collect, verify, summarize, then repeat until the stop condition is met.
- Autonomous-agent sandbox: Define allowed sources, allowed actions, forbidden claims, budget, stop conditions, and a validation checklist before the agent starts. Require a final source log and a list of unsupported findings.
- Verification loop: After the first draft, run a verification pass that lists unsupported claims, stale details, missing sources, and recommendations to downgrade or remove.Copy the prompt. Fill the variables. Then check the output for real.
These are selected for this specific competitor research job. Use the prompt-ready instruction when it helps, and skip it when the condition does not fit.
Use when: Use with web-enabled research, source notebooks, coding agents, MCP tools, SEO tools, ad libraries, or APIs.
Prompt move: Before analysis, state which sources or tools should be checked, which facts each tool can verify, and which claims must stay manual.
Skip when: Skip when all evidence is already pasted and no tool access is needed.
Use when: Use when the prompt depends on current web facts, public pricing, recently changed pages, search results, product releases, or market claims.
Prompt move: Run a cited search pass for current facts. Keep URLs, dates checked, and quoted claims separate from your own pasted evidence, then downgrade anything without a reliable source.
Skip when: Skip when all evidence is private, pasted, or already date-stamped.
Use when: Use when the answer depends on competitor pages, screenshots, ads, pricing, SEO exports, or reviews.
Prompt move: Build a source table first with source, date checked, claim, confidence, and business meaning. Use only that table for the final recommendations.
Skip when: Skip only for brainstorming with no factual claims.
Use when: Use when researching many competitors, channels, markets, ad libraries, SERPs, or weekly monitoring sources.
Prompt move: Split the work by competitor, channel, or source type. Force every shard to return the same schema, then merge only source-backed findings and mark disagreements.
Skip when: Skip for one competitor, one page, or one narrow teardown.
Use when: Use when the output must be compared, reviewed, or turned into tasks.
Prompt move: Return the main output as tables or labeled sections with fixed columns: finding, evidence, confidence, risk, action, and verification needed.
Skip when: Skip when the desired output is narrative copy.
Use when: Use when pasting many pages, long exports, transcripts, or screenshots.
Prompt move: First extract the decisive evidence and discard irrelevant material. Then analyze only the evidence that can change the recommendation.
Skip when: Skip for short, clean source packs.
Use when: Use when the job includes collecting sources, running checks, writing files, updating a tracker, or repeating the workflow.
Prompt move: When using an agent or browsing mode, structure the run as /goal: the outcome and decision, /plan: ordered sources, tools, limits, and checks, and /loop: collect, verify, summarize, then repeat until the stop condition is met.
Skip when: Skip for a one-off chat answer.
Use when: Use when an agent can browse, click, write files, call tools, collect sources, or repeat a workflow without constant supervision.
Prompt move: Define allowed sources, allowed actions, forbidden claims, budget, stop conditions, and a validation checklist before the agent starts. Require a final source log and a list of unsupported findings.
Skip when: Skip for read-only synthesis from evidence you already pasted.
Use when: Use before sharing research with a client, team, sales deck, ad brief, or website backlog.
Prompt move: After the first draft, run a verification pass that lists unsupported claims, stale details, missing sources, and recommendations to downgrade or remove.
Skip when: Skip only for private rough notes.
| Variable | Meaning | Type | Example |
|---|---|---|---|
{{my_company}} | Your company, product, or brand | string | Northstar CRM |
{{competitor}} | The competitor you want to analyze | string | Acme CRM |
{{market}} | The category or market context | string | B2B CRM for agencies |
{{sources}} | URLs, screenshots, notes, exports, or pasted copy | list | Homepage URL, pricing URL, ad screenshots |
{{date_range}} | The period covered by the monitoring pass | string | 2026-06-21 to 2026-06-28 |
The output below is fictional. It shows the shape you are looking for, not a real competitor result.
my_company = CartPilot
market = checkout optimization for Shopify brands
date_range = 2026-06-21 to 2026-06-28
sources = pricing change screenshot, three new ads, changelog note, SERP notesFictional example output:
This week:
- One competitor moved "free trial" above pricing.
- Two competitors repeated bundle recovery angles in ads.
- No verified product launch was found.
Ignore for now:
- A new blog post that does not map to our buyer or product.
Action items:
1. Review trial CTA placement.
2. Capture bundle recovery ad examples.
3. Verify whether the pricing change is global or region-specific.It includes an ignore section so the team does not chase noise.
It keeps weekly monitoring tied to source notes.
It asks for questions to verify next week.
Paste the page copy, ad screenshots, pricing table, SEO notes, or transcript first.
Use it as a source-backed brief: keep strong evidence, downgrade weak evidence, and decide what deserves action.
Ask for observations, risks, and next actions tied to the evidence.
Every factual claim has a source or is marked as unverified.
Pricing, dates, and product claims were checked on the original source.
The output separates observation from interpretation.
The output gives actions you can reject, edit, or test.
Nothing is treated as final just because an AI tool wrote it.
Use the same source checklist every week.
Keep the report short enough for a team meeting.
Move only verified action items into your roadmap.