Marketing · Specialized agent role

Competitor Research Agent

The Competitor Research Agent investigates a bounded market question using permitted public sources and a comparison framework selected by the research owner.

Get StartedReview the workflow

Best for

  • Product marketing teams comparing positioning, audience, packaging, messaging, content, or public product information
  • Strategy teams that need reproducible research questions, dated sources, and clearly marked unknowns

Typical inputs

  • Named competitors or category, research question, comparison dimensions, audience, geography, and time frame
  • Permitted public sources, internal hypotheses, source freshness rules, output format, and excluded data types

Input quality determines output quality. Source permissions, retention, and field-level access should be settled before the workflow begins.

Core workflow

Each stage has a defined purpose, visible evidence, and a named owner for exceptions.

1

Frame the request

Define the decision the research should inform and the dimensions that can be compared fairly

2

Gather context

Collect relevant public sources with URLs, dates, authorship, and source type

3

Prepare the work

Extract comparable evidence and label company claims, observed facts, interpretation, and missing information

4

Review and hand off

Synthesize patterns, contradictions, and questions without inferring confidential strategy

Actions it can perform

  • Review public websites, documentation, pricing, announcements, content, and other approved materials
  • Build comparison matrices, trace claims to sources, note changes over time, and challenge weak evidence

Actions should be restricted to the systems, records, and channels required for this role. Broader access is not a substitute for a well-designed workflow.

Outputs

  • Dated source library, competitor matrix, positioning summary, difference map, and evidence notes
  • Known-unknown register, contradictory-source list, monitoring questions, and research limitations

Every output should make its status clear: prepared, awaiting approval, completed under policy, or escalated with an explanation.

Role-specific configuration details

Use these role-specific terms to make the implementation brief concrete: resolve the relevant definitions, permissions, routes, and exception conditions before the role touches live work.

  • competitor-research
  • bounded-market
  • market-question
  • permitted-public
  • comparison-framework
  • framework-selected
  • linked-competitor
  • competitor-view
  • view-without
  • without-treating
  • treating-promotional
  • promotional-claims
  • claims-rumors
  • incomplete-public
  • public-information
  • verified-truth
  • truth-named
  • named-competitors
  • category-research
  • research-question
  • question-comparison
  • comparison-dimensions
  • dimensions-audience
  • audience-geography
  • time-frame
  • frame-permitted
  • internal-hypotheses
  • freshness-rules
  • excluded-data
  • data-types
  • types-define
  • compared-fairly
  • fairly-collect
  • collect-relevant
  • relevant-public
  • urls-dates
  • dates-authorship
  • type-extract
  • extract-comparable
  • comparable-evidence
  • label-company
  • company-claims
  • claims-observed
  • observed-facts
  • facts-interpretation
  • missing-information
  • information-synthesize
  • synthesize-patterns
  • patterns-contradictions
  • questions-without
  • without-inferring
  • inferring-confidential
  • confidential-strategy
  • public-websites
  • websites-documentation
  • documentation-pricing

Human approval and escalation

Approval boundary

A research or product marketing owner approves source use, interpretation, publication, sensitive conclusions, and any strategic response.

Escalation rule

Paywalled or restricted sources, personal data, rumors, legal disputes, ambiguous identities, and requests for deceptive collection are rejected or reviewed.

What remains under human control

  • People define competitors, ethical research boundaries, comparison dimensions, evidence quality, freshness, and the decision context
  • Subject experts validate nuances, interpret strategy, consider nonpublic knowledge, and decide what may be shared or acted upon

Teams should review permissions and outcomes over time, especially when policies, data sources, responsibilities, or customer expectations change.

Recommended integrations

Connections are workflow building blocks, not proof of automatic availability. Confirm authentication, permissions, supported actions, and error handling during implementation.

Google WorkspaceReview integration scopeNotionReview integration scopeAirtableReview integration scopeSlackReview integration scope

Example workflow

A product marketer asks how three vendors describe workflow approvals; the agent compares current public pages, dates every source, and marks absent details as unknown.

The implementation should record the source, owner, decision boundary, and recovery route for each important stage. That makes the workflow easier to review and improve without hiding responsibility.

Related agents

Use related roles only when responsibility and handoff boundaries are genuinely distinct.

SEO Agent

See the responsibilities, controls, and handoffs for this related specialist role.

Explore SEO Agent

Related use cases

Explore outcome-led workflows that can combine this role with approved systems and human review.

Design a responsible Competitor Research Agent workflow

Define the sources, controls, connected tools, exceptions, and owners before implementation.

Get Started