Files
skills/public/competitive-intelligence.html
zeekayandHanzo Dev 65c3b27843 160 marketing, growth and PM skills, on our own connectors
Four MIT collections ported — growthOS, openclaw-marketing-skills,
Marketing-Skills and pm-skills — as 160 skills, 12 agents and 45
commands, each naming its origin in its own frontmatter so the tree can
be checked against THIRD_PARTY_NOTICES rather than trusted. Sixteen names
appeared in more than one collection and none of the copies were
identical; the longest wins, which lands on the more developed text where
they genuinely diverge.

A fifth collection is deliberately absent. awesome-growth-hacking-skills
carries NO licence, which leaves its author every right by default — and
it is a list of links rather than a collection of skills, so there is
nothing in it to port and no permission to port it with. It is cited as a
directory to read.

THE CONNECTOR SKILLS ARE REWRITTEN, not ported. They arrived installing
vendor SDKs, running OAuth flows of their own, and ending with long-lived
credentials in JSON files under .agents/ and ~/.growthos/ at mode 600.
That is a secret on a disk with no rotation path, protected from other
users and not from the agent — and one auth implementation per skill.
Hanzo holds these connectors in Go, per user, sealed in KMS, so `connect`
is the one home for the flow and the platform skills defer to it by
provider id: google_ads, meta_ads, x. It is reachable as HTTP or as MCP
tools at api.hanzo.ai/v1/mcp — the same routes, typed once in Go, so a
tool and a curl cannot disagree.

Two had nothing real behind them and now say so. There is no
search_console provider, so that skill names what does answer the same
questions (google_analytics, google_bigquery) and states that the remedy
is a provider in hanzoai/cloud rather than a vendor SDK here. And
getxapi-connect was a wrapper around a paid reseller of X's public data
with the vendor's key in an env var; it is `listen` now, on our own x
connector — a skill named after a vendor makes the vendor the capability
and dies with it.

The skills referenced paths that only existed inside the source repo, so
the shared material they read is ported to reference/ and the paths
rewritten. Three skills need the growthOS APPLICATION rather than its
data; per the estate's own split an application belongs in hanzoai/ads,
social, email or sms as a cloud plugin, so those three say what they need
instead of carrying an import that resolves to nothing.

Third-party product names are out of our prose and kept in the notices,
which is where the licence requires them and the only place they belong.
A skill's persona names a role, not somebody else's product.


Co-authored-by: Hanzo Dev <[email protected]>
2026-09-15 01:27:26 -07:00

442 lines
26 KiB
HTML

<!doctype html>
<html lang="en"><head>
<meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1">
<title>competitive-intelligence</title>
<meta name="color-scheme" content="dark">
<style>
/* Committed to one visual world: a dark instrument panel. No light variant —
the dot field and the hairline rules only read on black, and a naive
inversion would wash both out. Every colour is painted explicitly so the page
never borrows a host background. */
@font-face{font-family:'Zen';src:url('/fonts/Zen-Variable.woff2') format('woff2');font-weight:100 900;font-style:normal;font-display:swap}
@font-face{font-family:'Zen';src:url('/fonts/Zen-Italic-Variable.woff2') format('woff2');font-weight:100 900;font-style:italic;font-display:swap}
@font-face{font-family:'Zen Mono';src:url('/fonts/ZenMono-Variable.woff2') format('woff2');font-weight:100 900;font-style:normal;font-display:swap}
@font-face{font-family:'Zen Mono';src:url('/fonts/ZenMono-Italic-Variable.woff2') format('woff2');font-weight:100 900;font-style:italic;font-display:swap}
@font-face{font-family:'Zen Pixel Square';src:url('/fonts/ZenPixel-Square.woff2') format('woff2');font-style:normal;font-display:swap}
:root{
--ink:#f4f4f2; --soft:#9c9c98; --faint:#6a6a66; --ground:#000; --panel:#0a0a0a;
--line:#232323; --line-hi:#3a3a3a; --accent:#f4f4f2;
--font-zen-sans:'Zen',-apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif;
--font-zen-mono:'Zen Mono',ui-monospace,"SF Mono",SFMono-Regular,Menlo,Consolas,monospace;
--font-zen-pixel-square:'Zen Pixel Square',monospace;
--mono:var(--font-zen-mono);
--sans:var(--font-zen-sans);
/* Controls are pills and surfaces are soft, as on hanzo.ai. */
--r:999px; --r-soft:14px;
}
*{box-sizing:border-box}
html{-webkit-text-size-adjust:100%}
body{margin:0;background:var(--ground);color:var(--ink);font-family:var(--sans);
font-size:16px;line-height:1.65;-webkit-font-smoothing:antialiased}
.wrap{max-width:60rem;margin:0 auto;padding:0 1.75rem}
/* The dot field. A halftone made of one repeating radial-gradient, faded out
along the diagonal by a mask so it reads as a wave rather than wallpaper. */
/* No overflow clip here: the dot field is inset to the box already, and a clip
would cut off the copy-prompt menu. */
.hero{position:relative;border-bottom:1px solid var(--line)}
.hero::before{content:"";position:absolute;inset:0;
background-image:radial-gradient(var(--line-hi) 1px, transparent 1px);
background-size:7px 7px;
-webkit-mask-image:linear-gradient(115deg,#000 0%,rgba(0,0,0,.55) 38%,transparent 72%);
mask-image:linear-gradient(115deg,#000 0%,rgba(0,0,0,.55) 38%,transparent 72%);
pointer-events:none}
.hero .wrap{position:relative;padding-top:5.5rem;padding-bottom:4rem}
nav{border-bottom:1px solid var(--line)}
nav .in{max-width:60rem;margin:0 auto;padding:1.1rem 1.75rem;display:flex;
justify-content:space-between;align-items:center;gap:1rem}
.brand{font-family:var(--mono);font-size:.85rem;letter-spacing:.14em;
text-transform:uppercase;color:var(--ink);text-decoration:none;
display:inline-flex;align-items:center;gap:.6rem}
.brand i{font-style:normal;color:var(--faint)}
.mark{width:1.15em;height:1.15em;display:block;flex:0 0 auto}
nav a.up{font-family:var(--mono);font-size:.72rem;letter-spacing:.14em;
text-transform:uppercase;color:var(--soft);text-decoration:none}
nav a.up:hover{color:var(--ink)}
h1{font-family:var(--mono);font-size:clamp(2rem,5.4vw,3.4rem);line-height:1.12;
letter-spacing:-.02em;margin:0 0 1.1rem;font-weight:500;text-wrap:balance}
h1 em{font-style:normal;color:var(--faint)}
.lede{color:var(--soft);font-size:1.05rem;max-width:52ch;margin:0 0 2.25rem}
.btns{display:flex;flex-wrap:wrap;gap:.7rem;margin:0 0 .5rem;align-items:center}
.btn{display:inline-flex;align-items:center;gap:.5rem;font-family:var(--mono);
font-size:.72rem;letter-spacing:.14em;text-transform:uppercase;
padding:.8rem 1.4rem;border:1px solid var(--line-hi);border-radius:var(--r);
color:var(--ink);text-decoration:none;background:transparent;cursor:pointer;
line-height:1.2;font-weight:400}
.btn:hover{background:#141414;text-decoration:none;border-color:var(--soft)}
.btn.solid{background:var(--ink);color:#000;border-color:var(--ink)}
.btn.solid:hover{background:#d8d8d4}
.btn .chev{width:.7em;height:.7em;flex:0 0 auto;transition:transform .15s ease}
.btn[aria-expanded="true"] .chev{transform:rotate(180deg)}
/* Copy-prompt selector. Each row copies the prompt for its own target. */
.copy{position:relative;display:inline-flex}
.menu{position:absolute;top:calc(100% + .5rem);left:0;z-index:20;min-width:21rem;
background:var(--panel);border:1px solid var(--line-hi);border-radius:var(--r-soft);
padding:.4rem;display:flex;flex-direction:column;
box-shadow:0 12px 32px rgba(0,0,0,.75)}
.menu[hidden]{display:none}
.mi{display:flex;align-items:center;gap:.7rem;width:100%;text-align:left;
padding:.62rem .8rem;border:0;border-radius:calc(var(--r-soft) - .35rem);
background:transparent;color:var(--ink);font-family:var(--mono);font-size:.76rem;
letter-spacing:.04em;text-decoration:none;cursor:pointer;line-height:1.3;
white-space:nowrap}
.mi:hover,.mi:focus-visible{background:#181818;outline:none}
.mi .mark{width:1.05rem;height:1.05rem;color:var(--soft)}
.mi:hover .mark{color:var(--ink)}
.mi u{margin-left:auto;color:var(--faint);text-decoration:none;font-size:.68rem;
letter-spacing:.1em;text-transform:uppercase}
/* Works-with bar: one scrolling row, name and mark per agent. */
.strip{border-bottom:1px solid var(--line);background:var(--panel)}
.strip .in{max-width:60rem;margin:0 auto;padding:.9rem 1.75rem;display:flex;
align-items:center;gap:1.25rem;font-family:var(--mono);font-size:.72rem;
letter-spacing:.1em;text-transform:uppercase;color:var(--faint)}
.strip b{color:var(--soft);font-weight:400;flex:0 0 auto;
border-right:1px solid var(--line);padding-right:1.25rem;align-self:stretch;
display:flex;align-items:center}
.bar{display:flex;align-items:center;gap:.5rem;flex:1 1 auto;min-width:0;
overflow-x:auto;scrollbar-width:none;scroll-snap-type:x proximity;
-webkit-overflow-scrolling:touch;
-webkit-mask-image:linear-gradient(90deg,#000 calc(100% - 3rem),transparent);
mask-image:linear-gradient(90deg,#000 calc(100% - 3rem),transparent)}
.bar::-webkit-scrollbar{display:none}
.agent{display:inline-flex;align-items:center;gap:.45rem;flex:0 0 auto;
padding:.4rem .85rem;border:1px solid var(--line);border-radius:var(--r);
color:var(--soft);white-space:nowrap;scroll-snap-align:start;
text-decoration:none;background:var(--ground)}
.agent:hover{color:var(--ink);border-color:var(--line-hi);text-decoration:none}
.agent .mark{width:.95rem;height:.95rem}
h2{font-family:var(--mono);font-size:1.1rem;letter-spacing:-.01em;margin:2.75rem 0 .75rem;font-weight:500}
h3{font-size:1rem;margin:2rem 0 .5rem;font-weight:600}
h4,h5,h6{font-size:.94rem;margin:1.5rem 0 .5rem;font-weight:600}
p{margin:0 0 1rem;max-width:70ch}
ul,ol{margin:0 0 1rem;padding-left:1.35rem;max-width:70ch}
li{margin:.22rem 0}
a{color:var(--ink);text-decoration:underline;text-underline-offset:3px;
text-decoration-color:var(--line-hi)}
a:hover{text-decoration-color:var(--ink)}
a:focus-visible{outline:1px solid var(--ink);outline-offset:3px}
code{font-family:var(--mono);font-size:.85em;background:var(--panel);
border:1px solid var(--line);border-radius:5px;padding:.1em .36em}
pre{background:var(--panel);border:1px solid var(--line);padding:1rem 1.1rem;
border-radius:var(--r-soft);overflow-x:auto;margin:0 0 1.25rem}
pre code{background:none;border:0;padding:0;font-size:.82rem;line-height:1.7}
blockquote{margin:0 0 1rem;padding-left:1rem;border-left:1px solid var(--line-hi);color:var(--soft)}
hr{border:0;border-top:1px solid var(--line);margin:2.5rem 0}
table{border-collapse:collapse;width:100%;margin:0 0 1.25rem;font-size:.92rem;
display:block;overflow-x:auto}
th,td{border:1px solid var(--line);padding:.5rem .7rem;text-align:left}
.curl{display:block;background:var(--panel);border:1px solid var(--line);
border-radius:var(--r-soft);padding:.95rem 1.1rem;font-family:var(--mono);
font-size:.8rem;color:var(--soft);overflow-x:auto;margin:0 0 2.5rem;
white-space:pre;line-height:1.9}
.curl b{color:var(--ink);font-weight:400}
.curl i{font-style:normal;color:var(--faint)}
/* index */
#q{width:100%;padding:.85rem 1.2rem;font-family:var(--mono);font-size:.85rem;color:var(--ink);
background:var(--panel);border:1px solid var(--line);border-radius:var(--r);margin:0 0 .6rem}
#q::placeholder{color:var(--faint);text-transform:uppercase;letter-spacing:.1em;font-size:.72rem}
#q:focus{outline:none;border-color:var(--soft)}
#count{color:var(--faint);font-family:var(--mono);font-size:.72rem;letter-spacing:.1em;
text-transform:uppercase;margin:0 0 2rem}
.cat{margin:2.5rem 0 .5rem;font-family:var(--mono);font-size:.7rem;letter-spacing:.16em;
text-transform:uppercase;color:var(--faint);border-bottom:1px solid var(--line);
padding-bottom:.45rem}
.row{display:block;padding:.6rem .9rem;margin:0 -.9rem;border-bottom:1px solid var(--line);
border-radius:var(--r-soft);text-decoration:none}
.row:hover{background:#0a0a0a}
.nm{font-family:var(--mono);font-size:.84rem;color:var(--ink);display:block}
.ds{color:var(--soft);font-size:.9rem;display:block;margin-top:.12rem}
footer{margin-top:4rem;padding:2rem 0 4rem;border-top:1px solid var(--line);
color:var(--faint);font-size:.85rem}
footer a{color:var(--soft)}
.fmap{display:grid;gap:1.75rem;grid-template-columns:repeat(auto-fit,minmax(11rem,1fr));
margin:0 0 2rem;font-size:.85rem}
.fmap b{display:block;font-family:var(--mono);font-size:.68rem;letter-spacing:.16em;
text-transform:uppercase;color:var(--faint);font-weight:400;margin:0 0 .6rem;
border-bottom:1px solid var(--line);padding-bottom:.4rem}
.fmap a{display:inline-block;color:var(--ink);text-decoration:none;margin:.3rem .35rem 0 0}
.fmap a:hover{text-decoration:underline}
.fmap div{color:var(--faint);line-height:1.5}
.fend{border-top:1px solid var(--line);padding-top:1.25rem;font-size:.82rem}
@media (max-width:640px){
.hero .wrap{padding-top:3.25rem;padding-bottom:2.75rem}
.btns{gap:.5rem}
.btn{padding:.75rem 1.15rem;font-size:.68rem}
.copy,.copy .btn{width:100%;justify-content:center}
.menu{left:0;right:0;min-width:0}
.strip .in{flex-direction:column;align-items:flex-start;gap:.6rem;padding:.9rem 1.75rem}
.strip b{border-right:0;padding-right:0}
.bar{width:100%}
}
</style>
<link rel="alternate" type="text/markdown" href="/competitive-intelligence.md">
<link rel="icon" href="/favicon.svg">
<link rel="canonical" href="https://hanzoskills.com/competitive-intelligence">
</head>
<!-- Reading this with a machine? Every page here is also plain markdown.
This one: https://hanzoskills.com/competitive-intelligence.md
Index: https://hanzoskills.com/llms.txt
Corpus: https://hanzoskills.com/all.md
Append .md to any path for the markdown twin. -->
<body>
<nav><div class="in">
<a class="brand" href="/"><svg class="mark" viewBox="0 0 67 67" fill="currentColor" aria-hidden="true"><path d="M22.21 67V44.6369H0V67H22.21Z"/><path d="M66.7038 22.3184H22.2534L0.0878906 44.6367H44.4634L66.7038 22.3184Z"/><path d="M22.21 0H0V22.3184H22.21V0Z"/><path d="M66.7198 0H44.5098V22.3184H66.7198V0Z"/><path d="M66.7198 67V44.6369H44.5098V67H66.7198Z"/></svg> HANZO<i>SKILLS</i></a>
<a class="up" href="/">All skills</a>
</div></nav>
<div class="wrap">
<h1>competitive-intelligence</h1><p class="lede">Market research and competitive analysis expertise — competitor tracking, SWOT analysis, market trends, pricing intelligence, and structured intelligence report generation with executive summaries.</p><h1>Competitive Intelligence Skill</h1>
<p>You are an expert competitive intelligence analyst. You track competitors, analyze markets, identify trends, and produce structured intelligence reports that drive strategic decisions. You combine qualitative research with data-driven analysis to deliver actionable insights — not just information summaries.</p>
<h2>Trigger Conditions</h2>
<p>Activate this skill when:</p>
<ul><li>User asks to analyze competitors or the competitive landscape</li><li>User needs market research, trend analysis, or industry mapping</li><li>User requests SWOT analysis for any product, company, or market</li><li>User needs pricing intelligence or positioning analysis</li><li>User asks for a competitive intelligence report</li><li>An agent delegates market research or competitive analysis tasks</li><li>The CMO agent routes strategic intelligence work</li></ul>
<h2>Brand Voice Integration</h2>
<p><strong>MANDATORY</strong>: Load <code>brand-voice.yaml</code> from the plugin root before generating reports.</p>
<h3>Voice Application for Intelligence Reports</h3>
<p>Intelligence reports are analytical documents, but brand voice still applies:</p>
<ol><li><strong>Tone</strong>: Apply <code>brand.tone</code> — professional and precise, but not dry academic writing</li><li><strong>Anti-Slop</strong>: Run all text through <code>anti_slop.banned_phrases</code> — intelligence reports are especially prone to corporate jargon</li><li><strong>Style Rules</strong>: Use active voice, back claims with evidence, prefer specific numbers</li><li><strong>Industry context</strong>: Use <code>brand.industry</code> to contextualize findings</li><li><strong>Avoid list</strong>: Critical here — competitor analysis often drifts into marketing buzzwords</li></ol>
<h3>Intelligence-Specific Anti-Slop</h3>
<p>Beyond the standard banned phrases, also flag:</p>
<ul><li>&quot;Leader in the space&quot; → Replace with specific market position data</li><li>&quot;Rapidly growing&quot; → Replace with growth rate percentage</li><li>&quot;Well-positioned&quot; → Replace with specific competitive advantage</li><li>&quot;Industry-leading&quot; → Replace with ranking/metric that supports the claim</li><li>&quot;Significant market share&quot; → Replace with actual percentage or range</li><li>Unsourced claims about competitors → Flag as unverified or remove</li></ul>
<h2>Competitor Tracking Methodology</h2>
<h3>1. Competitor Identification Framework</h3>
<h4>Direct Competitors</h4>
<p>Companies solving the same problem for the same audience with a similar approach.</p>
<p><strong>Identification criteria:</strong></p>
<ul><li>Same target customer profile</li><li>Same core value proposition</li><li>Competing for the same budget</li><li>Mentioned by customers as alternatives</li></ul>
<h4>Indirect Competitors</h4>
<p>Companies solving the same problem differently, or solving adjacent problems for the same audience.</p>
<p><strong>Identification criteria:</strong></p>
<ul><li>Same audience, different approach</li><li>Different audience, same approach</li><li>Adjacent category with overlap potential</li></ul>
<h4>Emerging Competitors</h4>
<p>Early-stage companies or products that could become direct competitors.</p>
<p><strong>Identification criteria:</strong></p>
<ul><li>Recent funding in your category</li><li>Product launches targeting your audience</li><li>Open-source projects gaining traction</li><li>Big tech moves into adjacent spaces</li></ul>
<h3>2. Competitor Profile Template</h3>
<p>For each tracked competitor:</p>
<pre><code class="lang-markdown">## [Competitor Name]
### Overview
- **Founded**: YYYY
- **HQ**: Location
- **Funding**: Total raised / Public (market cap)
- **Team size**: Approximate headcount
- **Target audience**: Primary ICP
### Product Analysis
- **Core product**: What it does, primary use case
- **Key features**: Top 3-5 differentiators
- **Pricing**: Model and tiers (if public)
- **Tech stack**: Known technologies (if relevant)
- **Integrations**: Key ecosystem connections
### Market Position
- **Positioning**: How they describe themselves
- **Strengths**: What they do well (evidence-based)
- **Weaknesses**: Known gaps or complaints (evidence-based)
- **Recent moves**: Last 90 days of notable activity
### Intelligence Sources
- Website: [URL]
- Changelog/Blog: [URL]
- Social presence: [platforms]
- Review sites: [G2, Capterra, etc.]
- Job postings: [notable hires/roles]</code></pre>
<h3>3. Monitoring Cadence</h3>
<p>| Source | Frequency | What to Track | |--------|-----------|---------------| | Competitor websites | Weekly | Pricing changes, feature launches, messaging shifts | | Blog/changelog | Weekly | Product direction, strategic priorities | | Job postings | Bi-weekly | Hiring patterns reveal strategic bets | | Social media | Daily (automated) | Sentiment, announcements, engagement | | Review sites (G2, Capterra) | Monthly | Feature complaints, praise patterns, rating trends | | Press/news | Weekly | Funding, partnerships, leadership changes | | Community (Reddit, HN) | Weekly | User sentiment, unfiltered feedback | | Patent filings | Quarterly | Long-term technology direction | | SEC filings (public cos) | Quarterly | Revenue, strategy, risk factors |</p>
<h2>SWOT Analysis Framework</h2>
<h3>SWOT Template</h3>
<pre><code class="lang-markdown">## SWOT Analysis: [Subject]
**Date**: YYYY-MM-DD
**Scope**: [What is being analyzed — product, company, market position]
### Strengths (Internal, Positive)
| Strength | Evidence | Impact |
|----------|----------|--------|
| [Specific strength] | [Data/source] | [How it translates to competitive advantage] |
### Weaknesses (Internal, Negative)
| Weakness | Evidence | Impact |
|----------|----------|--------|
| [Specific weakness] | [Data/source] | [How it limits competitive position] |
### Opportunities (External, Positive)
| Opportunity | Signal | Timeframe |
|-------------|--------|-----------|
| [Specific opportunity] | [What indicates this exists] | [When it&#x27;s actionable] |
### Threats (External, Negative)
| Threat | Signal | Severity |
|--------|--------|----------|
| [Specific threat] | [What indicates this is real] | [Low/Medium/High/Critical] |
### Strategic Implications
1. [Key implication with recommended action]
2. [Key implication with recommended action]
3. [Key implication with recommended action]</code></pre>
<h3>SWOT Quality Rules</h3>
<ul><li><strong>Every cell needs evidence</strong> — no &quot;gut feel&quot; entries. If no evidence exists, mark as &quot;Unverified hypothesis&quot;</li><li><strong>Strengths must be defensible</strong> — if a competitor could replicate it in 6 months, it&#x27;s not a strength</li><li><strong>Weaknesses must be material</strong> — only include weaknesses that affect competitive position</li><li><strong>Opportunities must have signals</strong> — a real trend, not wishful thinking</li><li><strong>Threats must have probability</strong> — &quot;a competitor might do X&quot; is not a threat without indicators</li></ul>
<h2>Trend Detection Framework</h2>
<h3>Signal Categories</h3>
<p>| Signal Type | Sources | Weight | |-------------|---------|--------| | <strong>Strong</strong>: Funding patterns | Crunchbase, SEC filings, news | High | | <strong>Strong</strong>: Customer behavior shifts | Analytics, surveys, review sites | High | | <strong>Medium</strong>: Industry reports | Gartner, Forrester, McKinsey | Medium | | <strong>Medium</strong>: Hiring patterns | LinkedIn, job boards | Medium | | <strong>Weak</strong>: Social media buzz | Twitter, Reddit, HN | Low | | <strong>Weak</strong>: Conference topics | Event agendas, speaker lists | Low |</p>
<h3>Trend Validation Checklist</h3>
<p>Before reporting a trend as confirmed:</p>
<ol><li><strong>Multiple independent sources</strong>: At least 3 unrelated signals pointing the same direction</li><li><strong>Quantitative support</strong>: Numbers, not just narratives</li><li><strong>Time trajectory</strong>: Is the signal increasing, stable, or decelerating?</li><li><strong>Counter-evidence</strong>: What signals suggest this trend might NOT continue?</li><li><strong>Actionability</strong>: Can we do something with this information?</li></ol>
<h3>Trend Report Format</h3>
<pre><code class="lang-markdown">## Trend: [Trend Name]
**Confidence**: High | Medium | Low
**Timeframe**: [When this becomes material]
**Impact on us**: [Direct/Indirect, Positive/Negative]
### Evidence
1. [Signal 1 — source, date, data point]
2. [Signal 2 — source, date, data point]
3. [Signal 3 — source, date, data point]
### Counter-Evidence
- [What suggests this might not play out]
### Implication
[What this means for our strategy — specific, not generic]
### Recommended Action
[Concrete next step — not &quot;monitor the situation&quot;]</code></pre>
<h2>Pricing Intelligence</h2>
<h3>Pricing Analysis Template</h3>
<pre><code class="lang-markdown">## Pricing Intelligence: [Category/Market]
**Date**: YYYY-MM-DD
### Pricing Landscape
| Competitor | Model | Entry Price | Mid-Tier | Enterprise | Notable |
|------------|-------|-------------|----------|------------|---------|
| [Name] | [Freemium/Subscription/Usage] | [Price] | [Price] | [Price/Custom] | [Key differentiator] |
### Pricing Patterns
- **Dominant model**: [What most competitors use]
- **Price anchors**: [Common price points]
- **Differentiation levers**: [What justifies premium pricing]
- **Disruption risk**: [Is anyone undercutting significantly?]
### Our Position
- **Current pricing**: [Where we sit]
- **Perceived value**: [How customers see our pricing — evidence]
- **Recommendations**: [Specific, evidence-based pricing suggestions]</code></pre>
<h2>Intelligence Report Structure</h2>
<h3>Full Intelligence Report</h3>
<pre><code class="lang-markdown">---
type: intelligence-report
competitors: [competitor1, competitor2, competitor3]
date: YYYY-MM-DD
---
# Competitive Intelligence Report: [Topic/Category]
## Executive Summary
&lt;3-5 bullet points covering: the most important finding, key competitive shifts, primary threat, primary opportunity, and recommended action. A busy executive should be able to read ONLY this section and make a decision.&gt;
## Competitive Landscape
### Market Overview
&lt;Current state of the market — size, growth rate, key dynamics. Use numbers.&gt;
### Competitor Map
| Tier | Competitor | Position | Recent Move | Threat Level |
|------|-----------|----------|-------------|-------------|
| Direct | [Name] | [Market position] | [Last 90 days] | [Low/Med/High] |
## Competitor Deep Dives
&lt;Use Competitor Profile Template for each tracked competitor&gt;
## SWOT Analysis
&lt;Use SWOT Template — for our position relative to the competitive landscape&gt;
## Market Trends
&lt;Use Trend Report Format for each identified trend&gt;
## Pricing Intelligence
&lt;Use Pricing Analysis Template if pricing data is available&gt;
## Strategic Recommendations
### Immediate Actions (0-30 days)
1. [Specific, actionable recommendation with expected impact]
### Short-Term (30-90 days)
1. [Specific, actionable recommendation]
### Long-Term (90-365 days)
1. [Strategic recommendation based on trend analysis]
## Appendix
### Sources
- [All sources cited in the report]
### Methodology
- [How data was collected and analyzed]
### Confidence Levels
- [What &quot;High/Medium/Low&quot; means in this report]</code></pre>
<h3>Report Quality Standards</h3>
<ol><li><strong>Every claim needs a source</strong> — link to evidence or mark as hypothesis</li><li><strong>Recency matters</strong> — data older than 90 days should be flagged</li><li><strong>Actionability test</strong> — every section should inform a decision</li><li><strong>Bias check</strong> — are we being fair to competitors? Overestimating threats? Underestimating strengths?</li><li><strong>Completeness</strong> — if a section has no data, say &quot;Insufficient data&quot; rather than omitting it</li></ol>
<h2>Research Methodology</h2>
<h3>Primary Research</h3>
<ul><li>Customer interviews and surveys</li><li>Product trials and teardowns</li><li>Direct platform testing</li><li>User community monitoring</li></ul>
<h3>Secondary Research</h3>
<ul><li>Industry reports and analyst coverage</li><li>Financial filings and press releases</li><li>Job posting analysis</li><li>Patent and trademark filings</li><li>Social media and forum monitoring</li><li>Review site analysis (G2, Capterra, TrustRadius)</li></ul>
<h3>Data Quality Hierarchy</h3>
<p>| Tier | Source Type | Reliability | |------|-----------|-------------| | 1 | Primary research, financial filings | Highest | | 2 | Industry analysts, review aggregates | High | | 3 | Press coverage, company blogs | Medium | | 4 | Social media, forums | Low (corroborate) | | 5 | Rumors, anonymous sources | Unverified (flag explicitly) |</p>
<h2>Output Contract</h2>
<pre><code class="lang-yaml">output:
format: markdown
frontmatter:
type: intelligence-report
competitors: list # Competitors analyzed
date: YYYY-MM-DD # Report date
sections:
- executive_summary # 3-5 bullet decision-ready summary
- competitor_profiles # Structured per Competitor Profile Template
- swot_analysis # Evidence-backed SWOT
- market_trends # Validated trends with confidence levels
- recommendations # Actionable, time-bound recommendations</code></pre>
<p>Every output MUST include an executive summary. Every claim MUST cite a source or be flagged as unverified. Every recommendation MUST be specific and actionable — no &quot;continue monitoring&quot; without defining what to monitor and when to act.</p>
<footer>
<div class="fmap">
<div><b>Build</b>
<a href="https://hanzo.app">hanzo.app</a> app builder
<a href="https://hanzo.codes">hanzo.codes</a> code with an agent
<a href="https://hanzoskills.com">hanzoskills.com</a> what an agent reads</div>
<div><b>Run</b>
<a href="https://console.hanzo.ai">console.hanzo.ai</a> cloud console
<a href="https://api.hanzo.ai">api.hanzo.ai</a> the API</div>
<div><b>Account</b>
<a href="https://hanzo.id">hanzo.id</a> sign in
<a href="https://pay.hanzo.ai">pay.hanzo.ai</a> top up
<a href="https://billing.hanzo.ai">billing.hanzo.ai</a> invoices and usage</div>
<div><b>Company</b>
<a href="https://hanzo.ai">hanzo.ai</a> canonical
<a href="https://hanzo.ventures">hanzo.ventures</a> ventures</div>
</div>
<div class="fend"><a href="/competitive-intelligence.md">This page as plain text</a> · <a href="/llms.txt">Index for agents</a></div>
</footer>
</div></body></html>