Competitor Intelligence Workflow

Build a competitive intelligence system via OpenClaw Ultra. From detecting verified competitor signals to producing evidence-backed briefs, manage your entire CI lifecycle from a single chat interface.

Core System Overview

INFO

This is a closed-loop competitor intelligence workflow. OpenClaw Ultra helps you define intelligence needs, detect changes, qualify signals against a clear thesis, analyze competitive moves, and distribute actionable briefs — so you can stop reacting to noise and start making strategic decisions with confidence.

System Layer	Core Function	Final Output
Scoping Layer	Define intelligence questions, qualifying thesis	Intelligence brief, competitor tiers
Detection Layer	Monitor sources for verified changes	Evidence chain with source diffs
Qualification Layer	Filter signals against thesis, classify by type	Scored signal log
Analysis Layer	Synthesize across sources, identify patterns	Competitor profiles, movement detection
Briefing Layer	Produce structured, cited intelligence	Weekly digest, sales battlecards
Distribution Layer	Route to right stakeholders at right cadence	Slack alerts, CRM updates, MCP feed
Review Layer	Measure impact, refine thesis and sources	Quarterly retrospective, ROI report

Prerequisites

Item	Requirement
OpenClaw Ultra	Installed and running
Intelligence Questions	3-5 specific decisions CI will support
Competitor List	3-5 primary competitors to track
Source Access	Competitor websites, pricing pages, changelogs, review sites (G2, Capterra)
Monitoring Tools	(Recommended) Visualping for website change detection, Google Alerts for keyword tracking
Research Tools	(Optional) SimilarWeb for traffic data, G2 for review analysis

Step 0 — Initialize Your Competitive Intelligence System

Set up OpenClaw Ultra as your dedicated CI analyst. The most common failure in competitive intelligence is starting with data collection before clarifying what decisions the intelligence is meant to support. This prompt establishes your focus.

Operation Steps

1. Open OpenClaw Ultra new chat session
2. Prepare your list of 3-5 primary competitors and your top business decisions
3. Paste the initialization prompt below

Ready-to-Use Prompt

Act as my competitive intelligence analyst.

My industry: [Your Industry]
My primary competitors: [Competitor A, Competitor B, Competitor C — include URLs]
My target market: [e.g., B2B SaaS mid-market, DTC e-commerce]

The 3-5 strategic decisions my team needs CI to support:
1. [e.g., Should we match Competitor A's new pricing tier?]
2. [e.g., Which feature gaps are costing us deals?]
3. [e.g., Is Competitor B entering our core segment?]

My core pain points:
- Too much raw data, not enough actionable intelligence.
- No system for tracking competitor changes — we react, not anticipate.
- Intelligence lives in documents nobody reads.

Your job is to help me build a systematic CI practice: define what to track, detect verified changes, separate signals from noise, and produce briefs that drive decisions.

Confirm you understand my context and are ready to start.

Step 1 — Define Your Intelligence Questions & Qualifying Thesis

The single most common mistake in competitive intelligence is gathering data before clarifying what questions you need to answer. A program that tries to answer every possible question about competitors answers none of them well. This step produces your qualifying thesis — a short written filter that everything downstream tests against.

1.1 Write Your Qualifying Thesis

Prompt

Based on my industry ([Your Industry]), primary competitors ([List]), and the strategic decisions I need CI to support ([List from Step 0]), help me write a short qualifying thesis — one or two paragraphs describing what my team cares about and why.

The thesis must answer:
- What types of competitor moves matter most to us? (pricing, product, messaging, hiring, go-to-market)
- What would change a decision we're currently facing?
- Which competitors warrant the closest attention and why?

Output: a clear qualifying thesis that will serve as the filter for all incoming signals.

1.2 Prioritize Competitors Into Tiers

Prompt

Given my qualifying thesis and industry, classify my competitors into three tiers:

Tier 1 — Direct competitors we face in deals every week. Full monitoring.
Tier 2 — Adjacent competitors that occasionally overlap. Selective monitoring.
Tier 3 — Emerging or tangential. Watchlist only.

Output a table:
| Tier | Competitor | Why This Tier | Monitoring Level |
|---|---|---|---|
| 1 | [Name] | [e.g., They appear in 60% of our sales cycles] | Full (daily/weekly) |
| 2 | [Name] | [e.g., Different segment but expanding toward us] | Selective (weekly) |
| 3 | [Name] | [e.g., Early-stage, could become threat in 12 months] | Watchlist (monthly) |

Step 1 Output

Qualifying thesis with tiered competitor list and clear monitoring focus.

Step 2 — Set Up Signal Sources & Monitoring Cadence

A working CI program draws from four categories of sources: competitor websites, review platforms, job postings, and social channels. Each source type runs at a different cadence. The goal is change detection — surfacing what's different since last time, not re-reading everything.

2.1 Identify High-Signal Sources Per Competitor

Prompt

For each of my Tier 1 competitors, identify the specific pages and sources that would reveal strategic changes first:

For each competitor, list:
- Pricing page URL — pricing shifts are the highest-signal change. Check daily.
- Product changelog URL — reveals what they're building and how fast they ship. Daily.
- Blog URL — new content categories often precede new features. Weekly.
- LinkedIn company page — executive moves, fundraising announcements. Weekly.
- G2 / Capterra profile — new reviews expose customer pain points and feature gaps. Weekly.
- Careers page — hiring patterns reveal roadmap priorities. Weekly.
- Crunchbase profile — funding rounds indicate growth trajectory. Monthly.

Output a source table per competitor with URL, signal type, and recommended check frequency.

2.2 Build Your Monitoring Calendar

For tracking competitor SEO keywords and content strategy shifts, set up monitoring in parallel with your SEO Content Workflow.

Prompt

Based on my competitor source list, build a monitoring cadence calendar:

Daily or near-daily:
- Pricing page changes (pricing tier restructure, new plans)
- Product page / changelog updates (new features, deprecations)
- LinkedIn company announcements (product launches, acquisitions)

Weekly:
- Blog and content strategy — new topics signal new feature investment
- Job postings — GTM hiring means growth push, engineering hiring means product build
- G2/Capterra reviews — new reviews, rating shifts, recurring complaints
- Competitor homepage and landing page messaging changes

Monthly:
- Full pricing page audit — track trends over time, not single changes
- Feature matrix comparison — update against your roadmap
- Social media content strategy — positioning and messaging shifts

Quarterly:
- Full competitive landscape review
- Update competitor tiers based on market changes
- Refresh qualifying thesis
- Measure CI program impact

Output: a monitoring calendar table with source, cadence, and what to watch for.

Step 2 Output

Source stack with verified URLs per competitor and monitoring cadence schedule.

Step 3 — Detect Changes & Build Your Evidence Chain

Every intelligence signal must trace to a specific, inspectable source. An evidence chain means: a specific URL was captured at a specific time, compared against a stored baseline, and produced a before-and-after excerpt. No evidence chain means the intelligence is not trustworthy enough to inform a decision.

3.1 Log Detected Changes With Evidence

Prompt

I have detected the following competitor changes this week. For each, build an evidence chain:

Change 1: [Describe what changed — e.g., Competitor A added an Enterprise pricing tier at $999/mo]
Source URL: [Full URL where the change was observed]
Detection date: [Date]
Before: [What the page showed before the change]
After: [What the page shows now]
Confidence: [High / Medium / Low — can you verify from another source?]

Change 2: [Competitor B published a blog post about AI-powered reporting]
Source URL: [URL]
Detection date: [Date]
Implication: [What this means for their strategy — e.g., They are investing in AI features to compete on analytics]

For each change, classify:
- Signal type: pricing / product / messaging / hiring / positioning / other
- Urgency: critical (act this week) / important (address this month) / monitor (track over time)
- Recommended action: [What to do with this intelligence]

Output an evidence log table.

3.2 Qualify Signals Against Your Thesis

Prompt

Review the evidence log against my qualifying thesis (from Step 1). For each signal, answer:

1. Does this change affect a decision we're currently facing?
2. Does this signal confirm or contradict our competitive positioning?
3. Is this signal important (changes our strategy) or just interesting (doesn't change anything)?
4. Which team should act on it — product, marketing, sales, or leadership?

Separate signals into:
- CRITICAL — changes a decision within 48 hours. Flag for immediate distribution.
- NOTEWORTHY — informs ongoing strategy. Include in weekly brief.
- NOISE — logged but no action needed. Archive for trend tracking.

Output: qualified signal log with urgency classification and recommended owner.

Step 3 Output

Verified evidence chain with qualified signals classified by urgency and owner.

Step 4 — Analyze Competitors & Detect Movement Patterns

A single signal tells you something happened. Multiple signals over a time window tell you a competitor is making a strategic move. The analysis layer is about pattern detection: grouping related changes into a coherent picture of competitor direction.

4.1 Build a Competitor Profile

Prompt

Synthesize the qualified signals from the past 30 days for [Competitor Name] into a structured competitor profile:

| Dimension | Assessment | Evidence |
|---|---|---|
| Pricing & Packaging | [Summary of pricing changes] | [Link to evidence chain] |
| Product Strategy | [What they're building, what they deprecated] | [Link to changelog diffs] |
| Messaging & Positioning | [How they're framing their value proposition] | [Link to homepage/blog changes] |
| GTM & Sales | [Hiring patterns, channel strategy] | [Link to job posting analysis] |
| Customer Sentiment | [Review trends, common complaints] | [Link to G2 review analysis] |
| Strategic Direction | [Overall read — where are they going?] | [Synthesis of above] |

For each dimension, include:
- What changed in the monitoring period
- What's consistent (no change is also a signal)
- A confidence score for each assessment (full / partial / empty — show gaps rather than guess)

Output: a single-competitor profile brief.

4.2 Detect Coordinated Movement

Prompt

Review the past 30-90 days of signals across all tracked competitors. Look for coordinated movement patterns:

- Clusters of similar changes within a 7-14 day window across competitors (e.g., two competitors raised prices in the same week = market trend)
- A competitor making multiple related changes (e.g., price drop + enterprise hiring + new integration page = upmarket push)
- Signals that one source confirms another (e.g., review complaints about support + competitor hiring support staff = credible signal)

For each detected pattern, answer:
- Isolated event or directional shift?
- If directional, what is the competitor signaling?
- How does this affect our positioning?

Output: movement detection brief — patterns, implications, and recommended positioning response.

Step 4 Output

Updated competitor profiles with movement detection and strategic implications.

Step 5 — Distribute Intelligence to Stakeholders

A signal that is qualified but never delivered is wasted work. Different teams need intelligence in different formats and at different cadences. The distribution layer routes the right intelligence to the right people at the right time.

5.1 Generate Weekly Intelligence Brief

Prompt

Generate a weekly competitive intelligence brief for [current week].

Structure:
1. EXECUTIVE SUMMARY (3-5 bullets — what matters this week)
   - [Critical change requiring action]
   - [Noteworthy development]
   - [Noise to ignore]

2. CRITICAL ALERTS (needs action within 48 hours)
   - What changed
   - Evidence chain (with source links)
   - Recommended action and owner

3. COMPETITOR-BY-COMPETITOR UPDATES
   - [Competitor A]: [What changed, what it means]
   - [Competitor B]: [What changed, what it means]

4. SALES AMMUNITION
   - New talking points from competitor weaknesses revealed this week
   - Updated positioning against competitor claims

5. NEXT WEEK'S WATCH LIST
   - Specific pages and signals to monitor closely

Format: Concise brief readable in 5-10 minutes. Every claim must link to its source evidence.

5.2 Update Sales Battlecards

For integrating updated battlecards directly into your sales enablement stack, see the CRM Workflow.

Prompt

Based on the latest intelligence on [Competitor Name], update our sales battlecard:

Current battlecard section to update: [Pricing / Features / Positioning / Common Objections]

New intelligence to incorporate:
- [Describe what changed, with source evidence]

Update the following:
- "How we win" talking points
- "Common competitor claims and our response"
- Feature comparison table (if outdated)
- Pricing comparison (if competitor changed pricing)

Output: updated battlecard section with change log (what changed, when, source).

Step 5 Output

Weekly intelligence brief distributed to stakeholders, with updated sales battlecards.

Step 6 — Measure Impact & Refine Your CI Program

A CI program is a living system. It gets better the more consistently you run it. Every cycle produces better questions, sharper analysis, and more actionable intelligence.

6.1 Measure CI Program Effectiveness

Prompt

Run a quarterly retrospective on our CI program.

Measure:
1. Stakeholder feedback — survey key teams (product, sales, marketing, leadership):
   - "Is the intelligence you receive useful? Rate 1-10."
   - "What's missing that would help you make better decisions?"
   - "What format works best for you?"

2. Time to response — when a competitor made a major move this quarter:
   - How fast did we produce an updated battlecard, revised positioning, or sales alert?
   - Target: within 48 hours for critical signals.

3. Source quality — which sources produced the highest-value signals this quarter?
   - Rank sources by: signals generated ÷ signals acted on.

4. Win rate correlation — are teams that use CI winning at higher rates?
   - Compare win rates for reps who consume intelligence vs. those who don't.

Output: CI program health scorecard with improvement recommendations.

6.2 Refresh Your Qualifying Thesis

Prompt

Given this quarter's intelligence outcomes, refresh our qualifying thesis:

Review:
- Are the right competitors being tracked? Any Tier 2 competitors that should move to Tier 1?
- Are we monitoring the right sources? Any new high-signal sources discovered this quarter?
- Are the strategic decisions we're supporting still the right ones?

Update:
- Qualifying thesis for the next quarter
- Competitor tier assignments
- Monitoring cadence and source list
- Intelligence questions to focus on

Output: updated CI program plan for next quarter.

Step 6 Output

Quarterly CI program retrospective with refreshed thesis and updated plan.

Final Closed-Loop Workflow

Questions Defined → Sources Mapped → Evidence Detected →
Signals Qualified → Profiles Analyzed → Briefs Distributed →
Decisions Made → Questions Refined → Next Cycle

Practical Usage Tips

1. Start with 3 competitors, not 10. Depth beats breadth in the first quarter — add more only after the process is running.
2. A qualifying thesis is your most important tool. Without it, CI degenerates into noise capture. Spend time getting this right before collecting any data.
3. Every intelligence claim must trace to a specific source URL, detection time, and before-and-after excerpt. No evidence chain means the signal isn't ready to share.
4. Set a weekly distribution cadence and defend it. When cadence breaks, trust in the CI stream drops quickly. A consistent weekly brief beats an exhaustive quarterly report no one reads.
5. Use the cadence calendar: daily checks for pricing pages and changelogs, weekly for reviews and job postings, monthly for full landscape reviews.
6. Not every competitor move is significant. A homepage redesign is cosmetic. A pricing restructure is strategic. Classify signals before acting on them.
7. For integrating competitive intelligence with your sales tech stack, see the CRM Workflow.
8. To track how competitor analysis influences product positioning and feature prioritization, see the Product Feedback Workflow.