What you'll learn: The four layers of competitive intelligence, how to chain skills into an always-on system, and why updating a competitor profile should take 15 minutes instead of a full afternoon.
Most PM teams do competitive intelligence in bursts. A new competitor raises funding. A sales rep gets blindsided on a call. The CEO asks "what's our differentiation?" at a board prep meeting. Someone scrambles to pull together a competitor profile in a few hours, shares it in Slack, and everybody moves on.
Three months later, the profile is outdated. Nobody updates it because building the first version took an entire afternoon. The next time someone needs competitive context, they start from scratch.
This is competitive intelligence as a project. What you actually need is competitive intelligence as a system — one that stays current, covers consistent dimensions, and connects back to your product decisions.
This is the deep dive on the Competitive Intelligence category from 7 Types of PM Work You Can Automate with Claude Code. If you haven't read that overview, it covers all seven PM automation categories. This article focuses on the one where most PM teams have the biggest gap between what they need and what they have.
I've worked with teams who thought they had solid competitive intelligence — until we asked basic questions. Who launched what last quarter? How does their pricing compare to yours? Where are they winning deals you're losing? The answers were scattered across Slack threads, old decks, and individual PMs' heads. Nobody had a system. That's the gap competitive skills fill: not replacing human intelligence gathering, but making sure what you learn actually gets structured and stays current.
Why Competitive Intelligence Breaks Down
Most product teams face a specific version of this problem. Nobody owns competitive intelligence full-time. It's something every PM does occasionally, inconsistently, and in their own way.
The result is predictable: fragments instead of intelligence.
One PM has a detailed Google Doc on Competitor A from six months ago. Another PM has bookmarks and a mental model of Competitor B. A third PM heard something about Competitor C's pricing change from a sales rep but didn't write it down. Ask the team for a competitive landscape view, and you'll get silence or a patchwork that nobody trusts.
This matters because competitive context shapes every downstream product decision. Positioning is competitive. Pricing is competitive. Feature prioritization is competitive — or should be. When the competitive picture is fragmented, decisions that should account for market context don't.
The PM Team Maturity Assessment scores teams across nine dimensions, and Competitive is consistently one of the lowest-scoring for PM teams. Not because PMs don't value it. Because the overhead of maintaining competitive intelligence exceeds what a team can absorb alongside shipping product.
AI doesn't make competitive intelligence effortless. It makes it sustainable. When a profile takes 15 minutes instead of 3 hours, PMs actually keep them updated. The intelligence stays fresh instead of becoming a stale artifact nobody trusts.
The Four Layers of Competitive Intelligence
Competitive intelligence isn't one activity. It's four distinct layers, and most PM teams only do the first one. A complete system covers all four and connects them.
Layer 1: Competitor Profiles
This is where everyone starts. Who is Competitor X? What do they do? How much do they charge? What's their positioning?
The problem isn't building the first profile. It's building it consistently and keeping it current.
The /competitive-profile-builder skill produces a structured competitor profile covering positioning, features, pricing, target market, strengths, weaknesses, and market trajectory. Because the output follows the same dimensions every time, profiles are comparable across competitors. And because each profile takes minutes instead of hours, PMs actually update them.
A typical profile covers: what the competitor does and who they serve, their core differentiators and how they position against alternatives, pricing model and tier structure, feature set mapped to your categories, known strengths and weaknesses based on reviews, customer signals, and market presence, and recent moves — funding, launches, partnerships, hiring patterns.
The skill reads your competitors.md context file, so it knows your existing competitive landscape and positions each new profile relative to what you already track.
Layer 2: Landscape Mapping
Individual profiles tell you about competitors. Landscape mapping tells you about the market.
This is the view that shows where competitors cluster, where positioning gaps exist, where the market is heading, and where your product sits relative to the field. It's the strategic altitude that turns "we know about our competitors" into "we know where the opportunities are."
The /landscape-mapper skill takes your full competitive context and produces a structured landscape analysis. It maps competitors across multiple dimensions — market segment, pricing tier, feature depth, go-to-market approach — and identifies whitespace. Where are competitors crowding? Where is nobody competing? What market shifts are creating new openings?
Landscape mapping is where competitive intelligence connects to strategy. Your positioning decisions, your pricing decisions, your roadmap bets — they're all informed by where the market stands and where it's heading. Without a current landscape view, those decisions happen with an incomplete map.
Layer 3: Win/Loss Analysis
Profiles and landscapes tell you what competitors look like from the outside. Win/loss analysis tells you what happens in the field — which competitors you beat, which ones beat you, and why.
The /win-loss-analysis skill processes deal outcomes and customer feedback to identify competitive patterns. Which competitor comes up most often in lost deals? What specific features or capabilities tip the decision? Where does pricing lose the deal versus product gaps?
Win/loss analysis is the feedback loop that makes competitive intelligence actionable. A profile tells you what Competitor X charges. Win/loss tells you whether their pricing actually wins deals against you or whether it's the product that decides.
For deeper interview-based analysis, the /win-loss-interview-analyzer skill processes recorded win/loss interviews to extract competitive signals that don't show up in CRM data. The stated reason for a loss and the real reason are often different — interviews surface the real one.
Layer 4: Strategic Implications
Raw intelligence is useful. Intelligence connected to your product decisions is powerful.
This is the layer where competitive data flows into your PRDs, your positioning, your pricing strategy, and your roadmap. When your PRD references specific competitive pressures, it's more convincing. When your positioning articulates differentiation against named alternatives, it's sharper. When your roadmap accounts for competitive moves, it's more strategic.
The /swot-analysis-generator skill produces a structured SWOT analysis against a specific competitor, connecting their strengths and weaknesses to your product's opportunities and threats. The output isn't a generic framework fill-in — it references your actual product context from your context files and your actual competitive landscape from your competitors.md.
This is where context files make the difference. A SWOT analysis without product context produces generic observations. A SWOT analysis that reads your positioning, your roadmap, and your existing competitive map produces analysis your team can act on.
What the Full Workflow Looks Like
Here's how the four layers chain together in practice, from first competitor profile to strategic decision.
Starting point: Your team is entering a new market segment or preparing for a major positioning refresh. You need a current, structured view of the competitive landscape.
Step 1: Profile the field. Run /competitive-profile-builder for each key competitor. Start with 3-5 direct competitors and 2-3 indirect alternatives. Each profile takes minutes. You now have structured, comparable profiles with consistent dimensions.
Step 2: Map the landscape. Run /landscape-mapper with your full competitive context. The skill produces a market map showing positioning clusters, pricing tiers, feature gaps, and whitespace. You can see where competitors crowd and where they don't.
Step 3: Layer in field data. Run /win-loss-analysis against recent deal data. Overlay the competitive intelligence with what actually happens in sales conversations. Which competitors show up? Which features decide deals? Where is perception different from reality?
Step 4: Connect to decisions. Run /swot-analysis-generator against your top 2-3 competitors. The output connects competitive intelligence to your product's strategic position. Use the output to inform your next PRD, your positioning refresh, or your pricing review.
Ongoing: When a competitor makes a move — a new launch, a pricing change, a funding round — update the profile with /competitive-profile-builder. The landscape view stays current because the individual profiles stay current.
This entire cycle, for five competitors, takes a PM a few hours instead of a few weeks. And because every output follows the same structure, any PM on the team can read and build on the work.
The Before and After
Before: A PM decides to refresh the competitive landscape before quarterly planning. They spend two days researching five competitors: reading websites, checking G2 reviews, scanning LinkedIn, asking sales for anecdotes. The output is a 15-page Google Doc that's comprehensive but in a format only the author can navigate. Other PMs skim it. Three months later, it's stale. Nobody updates it because the effort was too large.
After: The same PM runs /competitive-profile-builder for each of the five competitors. In two hours, they have five structured profiles with consistent dimensions. They run /landscape-mapper to see the full picture. They run /swot-analysis-generator against the top two threats. Total time: half a day. Total output: a structured competitive system that any PM can read, reference, and update. When a competitor launches something new next month, updating the profile takes 15 minutes.
Example — Before: two days researching five competitors, output in a 15-page Google Doc that's stale in three months. After: half a day, five structured profiles with consistent dimensions. Updating any profile next month takes 15 minutes.
Key Skills for Competitive Intelligence
Six skills form the core competitive intelligence toolkit. Here's what each one does and when to use it.
Competitive Profile Builder is the foundation. It produces structured competitor profiles covering positioning, features, pricing, strengths, weaknesses, and market trajectory. Use it whenever you need to document a competitor, whether it's a new entrant or an established player you haven't profiled in a while. This is the skill most PMs start with.
Landscape Mapper produces a strategic view of the competitive landscape. It maps competitors across dimensions and identifies positioning gaps, market trends, and whitespace opportunities. Use it quarterly or before major strategic decisions like positioning refreshes or new market entry.
Win/Loss Analysis extracts competitive patterns from deal outcomes. It identifies which competitors you beat, which ones beat you, and what factors decide the outcome. Use it when you have enough deal data to spot patterns — typically quarterly.
Win/Loss Interview Analyzer processes recorded win/loss interviews to extract competitive signals that don't show up in CRM data. Use it when you're doing dedicated win/loss research and need structured analysis of interview transcripts.
SWOT Analysis Generator produces structured SWOT analysis against a specific competitor, connecting their position to your product's opportunities and threats. Use it when you need to translate competitive intelligence into strategic implications for a specific decision.
Pricing Strategy Analyzer analyzes competitor pricing models and positions them against your pricing structure. Use it before pricing decisions, during competitive positioning reviews, or when a competitor changes their pricing.
How Context Files Make Competitive Intelligence Better
Every competitive analysis skill reads your context files. Your competitors.md describes your current competitive landscape. Your product.md describes your positioning and features. Your company.md describes your strategic direction.
When /competitive-profile-builder researches a competitor, it positions them relative to your existing competitive map — not in a vacuum. When /swot-analysis-generator produces analysis, it connects competitor strengths to your actual weaknesses, not generic ones. When /landscape-mapper identifies whitespace, it frames it against your product's capabilities.
Without context files, competitive skills produce generic analysis. With them, every output is grounded in your specific market position. The difference is visible immediately: competitive analysis that says "they compete on price" versus analysis that says "their $29/month tier undercuts your $49/month tier specifically for the solo PM segment you're targeting."
Tip — The context compounds over time. Each competitor profile enriches your competitors.md. Six months of maintained competitive intelligence means your AI has six months of accumulated market knowledge — and every subsequent analysis is richer.
Watch out — AI competitive analysis relies on publicly available information. It can't surface intelligence from sales calls, user conversations, or industry relationships that haven't been documented. The most valuable competitive insights often come from human conversations — skills structure and scale the analysis, but they don't replace the sources.
Getting Started
Don't try to build the full four-layer system on day one. Start with one competitor and one skill.
If you're evaluating a specific competitor right now, run /competitive-profile-builder. See what comes back. Edit it, add what the skill missed, and save the output. You'll have a structured profile in minutes that would have taken hours manually.
If you have deal data but no structured analysis, run /win-loss-analysis. The patterns it surfaces often surprise PMs who thought they knew why they were winning and losing.
If you haven't set up Claude Code yet, the setup guide walks through installation and context file creation step by step. Your competitors.md context file is especially important for competitive skills — it's what turns generic analysis into analysis grounded in your market.
For the full picture of what's possible across all seven PM automation categories, the hub article covers everything from discovery to stakeholder communication. And if you want to see where your team's competitive intelligence stands relative to other dimensions, the PM Team Maturity Assessment pinpoints exactly where the gaps are.
Build this for your team → We set up and manage PM Operating Systems for product teams — competitive intelligence infrastructure that stays current without consuming your team's bandwidth. See how it works →
The complete competitive intelligence skill set — along with 70+ other PM skills across discovery, strategy, specs, planning, data, and communication — is available in the PM Operating System.
About the Author
Ron Yang is the founder of mySecond — he builds and manages PM Operating Systems for product teams. Prior to mySecond, he led product at Aha! and is a product advisor to 25+ companies.