AI Competitor Intelligence Analyst Agent Template

• What it does: Discovers relevant competitors and turns sourced positioning, SEO, content, and offer evidence into growth opportunities.
• Best for: marketing teams, startups, small businesses, ecommerce teams, product leaders, and agencies.
• Apps used: DataForSEO, Apify, web_search.
• Setup time: 10 to 15 minutes before the first controlled research run.

Last verified from workflow config on 2026-08-20. Includes exact connector scopes, common failure modes, and fixes.

The AI Competitor Intelligence Analyst turns sourced market, SEO, positioning, content, and offer evidence into defensible opportunities. This template acts as a starting point: open any agent and use Use AI to help draft or update its instructions—adding new agents or connecting new tools is done manually in the canvas.

The problem this template solves

• Competitor lists mix direct: rivals, search competitors, and aspirational brands without explaining the difference.
• Research reports repeat public: claims but do not trace conclusions to URLs and dates.
• Broad scrapes run before: the comparison set and cost cap are approved.

How do you build a competitor analysis agent yourself?

A reliable competitor analysis agent needs market boundaries, competitor discovery, SERP and keyword data, controlled public collection, a source ledger, comparison logic, and an opportunity brief. The method must keep source evidence, calculations, recommendations, and external actions distinct so a user can review what happened.

You can build this with Claude Code, Codex, or a custom stack. You would own authentication, schemas, retries, storage, approval state, testing, and ongoing connector maintenance. This template starts with those workflow decisions already represented in an editable Agent Build.

If the adjacent job is a better fit, the SEO Optimized Blog Writer template provides a related starting point without forcing this agent beyond its actual scope.

Setup guide

Step 1: Clone the template into the right Project

Open the template gallery from Agent Space, choose AI Competitor Intelligence Analyst, and clone it into the Project that holds the relevant customer context. The workflow opens as an editable draft with its agents, notes, tools, and installed skills.

Step 2: Review Project context and complete first-run setup

Open Run and start a new conversation with Competitor Intelligence Analyst. The agent checks read-only Project files and its reusable setup record before asking only for unresolved choices from the installed Build an Evidence-Backed Competitor Brief method.

Step 3: Connect only the apps this workflow needs

Open Agent Build, inspect each tool node, and connect the required accounts for DataForSEO, Apify, web_search. Review the allowlisted actions shown in the Apps used table below, and avoid granting broader write access than the template needs.

Step 4: Confirm goals, limits, and approval policy

Review the saved setup fields, reporting window, output preferences, cost limits, and any external-write policy. Keep analysis and draft work available by default, and require explicit approval for any live side effect described in the workflow guardrails.

Step 5: Test a normal prompt and an edge case

Run Find our strongest UK competitors and identify defensible content and positioning gaps. Then open a clean conversation and test Propose the competitor set first and wait before running a larger Apify actor. Inspect tool calls, files, human-input pauses, and the final answer in the trace before changing instructions.

Step 6: Publish the tested draft

Return to Build, save the final configuration, then publish it from Deploy after the draft test behaves as expected. Use Playground for ongoing work and Agent Space to watch live status or requests that need human input.

Common issues and fixes

• A required connector is disconnected: Open Tools and Skills, connect the account in the same Project, and confirm the intended actions remain allowlisted.
• Project context is incomplete: Add or update the relevant brand, goal, policy, glossary, or source file at Project scope, then ask the agent to refresh setup instead of guessing.
• The requested action is unsupported: Keep the local analysis or draft, state the connector gap, and do not claim a live write without a returned identifier.
• The result uses the wrong window or target: Confirm the saved setup, source period, locale, identity, and output goal before rerunning a cost-bearing or external step.

Customization knobs

• company/domain and products: Review and update this value through the first-run setup flow when the Project changes.
• market, geography, and customer segment: Review and update this value through the first-run setup flow when the Project changes.
• known competitors and exclusions: Review and update this value through the first-run setup flow when the Project changes.
• comparison dimensions: Review and update this value through the first-run setup flow when the Project changes.
• decision the research must support: Review and update this value through the first-run setup flow when the Project changes.
• depth, freshness, and cost limits: Review and update this value through the first-run setup flow when the Project changes.

Who this template is for

• Marketing and strategy teams: Ranked from competitor analysis for marketing (320 US searches/month in the evaluated dataset). The workflow fits because it can identify the competitors that matter and translate their observable positioning, search footprint, content, offers, and market activity into defensible opportunities.
• Startups: Ranked from competitor analysis for startups (10 US searches/month in the evaluated dataset). The workflow fits because it can identify the competitors that matter and translate their observable positioning, search footprint, content, offers, and market activity into defensible opportunities.
• Small businesses: Ranked from competitor analysis for small business (10 US searches/month in the evaluated dataset). The workflow fits because it can identify the competitors that matter and translate their observable positioning, search footprint, content, offers, and market activity into defensible opportunities.
• Ecommerce teams: Ranked from competitor analysis for ecommerce (0 US searches/month in the evaluated dataset). The workflow fits because it can identify the competitors that matter and translate their observable positioning, search footprint, content, offers, and market activity into defensible opportunities.

What the agent does

This template can:

• Research the company first: and define the market boundary and competitor types.
• Build a candidate set: from DataForSEO, SERPs, user evidence, and web discovery; separate direct, search, and aspirational competitors.
• Confirm the comparison set: before any broad paid scrape.
• Collect only approved public: pages or actor datasets with explicit item/page caps.
• Compare positioning, audience, offers: proof, pricing visibility, search footprint, content themes, backlinks/signals, and observable channel activity.
• Maintain a source ledger: with URL, collection method, and date; distinguish absence of evidence from evidence of absence.
• Score only dimensions supported: by comparable evidence.
• Return threats, whitespace, testable: opportunities, uncertainties, and a monitoring plan.

How the workflow works

1. Research the company first and define the market boundary and competitor types.
2. Build a candidate set from DataForSEO, SERPs, user evidence, and web discovery; separate direct, search, and aspirational competitors.
3. Confirm the comparison set before any broad paid scrape.
4. Collect only approved public pages or actor datasets with explicit item/page caps.
5. Compare positioning, audience, offers, proof, pricing visibility, search footprint, content themes, backlinks/signals, and observable channel activity.
6. Maintain a source ledger with URL, collection method, and date; distinguish absence of evidence from evidence of absence.
7. Save the evidence, approvals, files, and final result for review.

This is a single-agent workflow. The main agent owns research, planning, tool use, approvals, files, and the final response without passing routine stages between specialists.

Requirements and setup inputs

Use the template in a Project that contains the relevant business context. Connect only the accounts required for DataForSEO, Apify, web_search. The agent reads Project files before asking questions and stores confirmed reusable setup at agent scope.

• company/domain and products: Confirm this only when it is not already available from Project context, public evidence, or a saved setup record.
• market, geography, and customer segment: Confirm this only when it is not already available from Project context, public evidence, or a saved setup record.
• known competitors and exclusions: Confirm this only when it is not already available from Project context, public evidence, or a saved setup record.
• comparison dimensions: Confirm this only when it is not already available from Project context, public evidence, or a saved setup record.
• decision the research must support: Confirm this only when it is not already available from Project context, public evidence, or a saved setup record.
• depth, freshness, and cost limits: Confirm this only when it is not already available from Project context, public evidence, or a saved setup record.
• approved Apify actors and reporting format: Confirm this only when it is not already available from Project context, public evidence, or a saved setup record.

No template-wide sample-data artifact is installed. The template installs its reusable methods and setup.md through skills, then creates customer-specific profiles, reports, charts, exports, and receipts from authorized evidence. Generated files can be inspected in Playground.

Apps and tools used

Connector actions are scoped to this Agent Build. A Project connection does not automatically grant every agent or every action access.

Practical use cases

First setup and baseline

Marketing and strategy teams can use the template to identify the competitors that matter and translate their observable positioning, search footprint, content, offers, and market activity into defensible opportunities. The saved setup and evidence files reduce repeated onboarding while keeping unknowns visible.

Best for: marketing and strategy teams.

Focused analysis or production run

Startups can use the template to identify the competitors that matter and translate their observable positioning, search footprint, content, offers, and market activity into defensible opportunities. The saved setup and evidence files reduce repeated onboarding while keeping unknowns visible.

Best for: startups.

Ongoing review and iteration

Small businesses can use the template to identify the competitors that matter and translate their observable positioning, search footprint, content, offers, and market activity into defensible opportunities. The saved setup and evidence files reduce repeated onboarding while keeping unknowns visible.

Best for: small businesses.

Safe edge-case handling

Ecommerce teams can use the template to identify the competitors that matter and translate their observable positioning, search footprint, content, offers, and market activity into defensible opportunities. The saved setup and evidence files reduce repeated onboarding while keeping unknowns visible.

Best for: ecommerce teams.

Example prompts and outputs

Example prompt: core workflow

Find our strongest UK competitors and identify defensible content and positioning gaps.

Example output: A sourced competitor brief separating facts, estimates, inferences, threats, whitespace, and testable opportunities. The actual numbers, sources, files, and connector receipts depend on the user's authorized data.

Example prompt: safety or limitation check

Propose the competitor set first and wait before running a larger Apify actor.

Expected behavior: the agent follows this boundary, preserves useful local work, and does not claim an unsupported or unapproved external action.

Why use this template

• Research happens before questions: the agent inspects Project context, saved setup, and available evidence before requesting unresolved choices.
• The method stays maintainable: detailed repeatable steps live in human-readable skills instead of one oversized agent prompt.
• External actions stay reviewable: connector scopes, approval boundaries, and returned identifiers are explicit.
• Files carry the detail: reports, evidence, drafts, charts, and receipts remain inspectable instead of being lost in a long chat response.
• The workflow remains editable: teams can refine one agent, skill, tool scope, or handoff at a time and retest it.

Related templates

• SEO Optimized Blog Writer: Creates original, source-backed B2B articles through a ten-stage research, writing, editing, SEO, and delivery method.
• Google Ads Performance Manager: Audits live Google Ads performance, checks search demand, and turns evidence into approval-controlled optimization actions.
• AI Brand Content Creator: Creates researched campaign copy and inspected visual assets from verified project brand context.
• Google Maps Web Lead Extractor: Finds local businesses through Google Maps data, then cleans, deduplicates, scores, and exports outreach-ready leads.