Competitive Intelligence Pack

You're staring at a spreadsheet that's three versions behind reality. Your "competitive analysis" is a Google Doc named competitor_notes_final_v3.docx filled with half-baked SWOTs, pricing screenshots from six months ago, and Slack threads where someone claimed their rival raised a Series B. You're trying to decide whether to enter the mid-market segment, but you're guessing because your data is scattered across G2 reviews, competitor landing pages, and fragmented internal notes. The result? You launch a feature nobody asked for, or you misprice your tier and bleed margin before day one.

We built the Competitive Intelligence Pack because we're tired of strategy analysts wasting hours reconstructing the competitive landscape from scratch every time a new threat emerges. Market research is supposed to help you find customers and make your business unique, but when your workflow is manual and ad-hoc, you end up with noise instead of signal ^[1]. This pack gives you a structured, machine-readable workflow for market mapping, SWOT analysis, benchmarking, and strategic positioning. You get deterministic outputs, validation gates, and embedded canonical frameworks that enforce rigor. No more guessing. Just validated intelligence.

The Spreadsheet Graveyard of Competitive Intelligence

The pain isn't just time; it's the structural rot of unverified assumptions. When you're building a strategy, you're making high-stakes decisions based on low-quality inputs. You manually copy pricing tables from Stripe and Chargify, then try to reconcile them with competitor features listed on their docs site. You spend two days scraping G2 reviews to estimate NPS, only to realize the sample size is biased toward power users. You draft a SWOT matrix in Notion, but you miss the "Threats" quadrant because you didn't have a scoring system to force you to quantify vulnerability.

This fragmentation creates a dangerous gap between what you know and what you can prove. Your CTO asks, "Is this data validated?" You say, "I think so." Your sales team needs a battle card, but you give them a PDF that's already stale. When you're comparing competitive-research-pack workflows, you'll notice the difference: one is a checklist, the other is a pipeline. Without a systematic CI workflow, your market mapping becomes a hobby, not a strategic asset. You end up with a "Zoo of Error Formats" where every competitor is analyzed differently, making aggregation impossible. You need a framework that simplifies the process of gathering useful information, including their marketing, products, and pricing, so you can actually understand the landscape ^[5].

The Hidden Tax of Fragmented Market Data

When your intelligence is fragmented, the cost compounds. A 2026 analysis of competitive frameworks highlights that without structured approaches, teams struggle to identify true strategic opportunities ^[2]. You might spend 12 hours manually scraping competitor pricing and feature lists, only to realize your analysis is missing the "Threats" quadrant because you didn't use a scoring system. Worse, you risk analysis paralysis. Industry experts warn against trying to deploy every framework at once; without a curated workflow, you drown in Porter's Five Forces and PESTLE templates that never leave the folder ^[4].

One misstep in market mapping—like overlooking a consolidator in the value chain—can cost a product launch $50k in wasted dev time and three months of sales cycle delay. If your pricing tier is off by 10% because you benchmarked against the wrong peer group, you're leaving revenue on the table or pricing yourself out of the market. A SWOT analysis is a strategic planning tool that helps a business identify internal strengths and weaknesses and external opportunities and threats, but only if you score them and weight them properly ^[6]. Without that rigor, your "Opportunities" are just wishful thinking. Your engineering team builds a feature based on a vague competitor gap, and it ships to zero adoption. The downstream incident isn't just a missed target; it's a credibility hit with leadership and a wasted sprint.

How a SaaS Team Found Whitespace in 20 Minutes

Imagine a Series B SaaS team preparing to launch a vertical-specific module for healthcare. They have 200 days of runway left. The strategy lead opens the Competitive Intelligence Pack and runs scripts/scaffold-ci.sh with the target market and a list of five key rivals. The script generates a structured YAML skeleton, forcing the team to populate templates/market-mapping.yaml with real segment data. Instead of a vague "Competitors are strong" note, the analyst populates the benchmarking-scorecard.yaml, revealing that a niche player has 15% better NPS in the mid-market due to a specific integration gap.

The team runs scripts/validate-ci.sh to catch a missing scoring weight in the SWOT matrix. The script exits non-zero, pointing to swot.strengths[0].score as invalid. They fix the schema violation and re-run. They spot a whitespace in the positioning-matrix.yaml perceptual map where a "High Price / Low Support" cluster is vulnerable. Armed with this validated data, they pivot their positioning to "Enterprise-grade support at mid-market pricing," directly attacking the whitespace. They don't just have a report; they have a battle plan grounded in structured output standards ^[1]. The pack enforces frameworks like Perceptual Mapping and Strategic Group Analysis, ensuring every decision is backed by operational definitions ^[3].

Deterministic Outputs, Validated Strategy, Zero Guesswork

Once the pack is installed, the chaos vanishes. You get deterministic outputs: every SWOT analysis includes scoring weights and vulnerability mapping, so you can quantify risk instead of guessing ^[6]. The benchmarking-scorecard.yaml enforces weighted scoring across feature parity, pricing, and tech stack, ensuring your gap analysis is mathematically sound. When you generate a positioning-matrix.yaml, the perceptual mapping automatically identifies whitespace and competitive threat scores based on configurable axes.

The validate-ci.sh script acts as a gatekeeper; if a required field is missing or a score falls outside the valid range, the build fails, preventing you from shipping a flawed analysis to leadership. You're no longer collecting data; you're running a systematic CI workflow that aligns market trends with fast-moving strategic shifts ^[8]. Your reports are machine-readable, auditable, and ready for downstream integration with your product roadmap. If you need to expand into TAM/SAM/SOM analysis or survey design, you can integrate this pack with the Market Research Pack for a full funnel view.

What's in the Competitive Intelligence Pack

This isn't a single file you're hoping works. It's a multi-file deliverable that covers the entire competitive intelligence lifecycle. Here is the manifest:

• skill.md — Orchestrates the competitive intelligence workflow, maps decision gates to templates, references all supporting files, and enforces structured output standards grounded in frameworks from references/frameworks.md and data-collection.md
• templates/market-mapping.yaml — Production-grade competitor registry and market landscape template with real keys for segment mapping, data sources, scraping methods, and validation hooks aligned with systematic CI workflows
• templates/swot-analysis.yaml — Structured SWOT matrix template with scoring weights, relative positioning fields, vulnerability mapping, and competitive advantage tags per strategic planning standards
• templates/benchmarking-scorecard.yaml — Feature parity, pricing tier, market share, NPS, and tech stack benchmarking template with weighted scoring, gap analysis, and portfolio mapping fields
• templates/positioning-matrix.yaml — Perceptual mapping and strategic group clustering template with configurable axes, whitespace identification, and competitive threat scoring
• references/frameworks.md — Embedded canonical knowledge covering SWOT, Porter's Five Forces, PESTLE, BCG Growth-Share Matrix, Perceptual Mapping, and Strategic Group Analysis with operational definitions and application rules
• references/data-collection.md — Embedded canonical knowledge on systematic competitive intelligence gathering, AI-agent scraping patterns, data validation protocols, ethical/legal boundaries, and benchmarking methodology
• scripts/scaffold-ci.sh — Executable bash script that generates a structured CI report skeleton from CLI inputs (company, market, competitor list), populates template placeholders, and outputs validated YAML for downstream analysis
• scripts/validate-ci.sh — Validator script that parses generated CI YAML against ci-schema.json, checks required fields, scoring ranges, and structural integrity, and exits non-zero (exit 1) on any validation failure
• validators/ci-schema.json — JSON Schema defining the competitive intelligence report structure, enforcing required keys, data types, scoring constraints, and cross-template consistency rules
• examples/full-analysis.yaml — Worked example demonstrating a complete competitive intelligence pack output for a hypothetical SaaS market, showing proper template population, scoring, and strategic positioning

Ship Smarter Strategy, Not More Spreadsheets

Stop guessing who's winning. Stop shipping stale PDFs. Upgrade to Pro to install the Competitive Intelligence Pack and start mapping the battlefield with structured, validated intelligence. You get the templates, the scripts, the schemas, and the canonical frameworks. You get a workflow that scales with your market complexity. Install the pack, run the scaffold, validate the output, and make decisions you can defend.