mirror of
https://github.com/hanzoai/skills.git
synced 2026-11-21 09:33:35 +00:00
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]>
465 lines
31 KiB
HTML
465 lines
31 KiB
HTML
<!doctype html>
|
||
<html lang="en"><head>
|
||
<meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1">
|
||
<title>marketing-strategy</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="/marketing-strategy.md">
|
||
|
||
<link rel="icon" href="/favicon.svg">
|
||
<link rel="canonical" href="https://hanzoskills.com/marketing-strategy">
|
||
</head>
|
||
<!-- Reading this with a machine? Every page here is also plain markdown.
|
||
This one: https://hanzoskills.com/marketing-strategy.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>marketing-strategy</h1><p class="lede">Strategic marketing planning, growth frameworks (AARRR, ICE, RICE), positioning, OKRs, campaign planning, content pillars, and market analysis</p><h1>Marketing Strategy Skill</h1>
|
||
<h2>Trigger Conditions</h2>
|
||
<p>Use this skill when the user asks to:</p>
|
||
<ul><li>Create or refine a marketing strategy</li><li>Plan a campaign or launch</li><li>Define marketing OKRs or KPIs</li><li>Analyze market position or competitive landscape</li><li>Build content pillars or editorial calendars</li><li>Prioritize marketing initiatives</li><li>Conduct TAM/SAM/SOM analysis</li><li>Design a growth model or funnel</li></ul>
|
||
<hr>
|
||
<h2>Brand Voice Integration</h2>
|
||
<p><strong>MANDATORY:</strong> Before generating ANY strategy content, load the brand voice configuration.</p>
|
||
<pre><code class="lang-python">from brand_voice.config import load_brand_voice
|
||
brand = load_brand_voice()</code></pre>
|
||
<p>All strategy outputs must align with <code>brand.tone</code>, respect <code>brand.avoid</code> terms, and pass <code>anti_slop</code> validation. Strategy documents that ignore brand voice are invalid.</p>
|
||
<hr>
|
||
<h2>Growth Frameworks</h2>
|
||
<h3>AARRR — Pirate Metrics Framework</h3>
|
||
<p>The AARRR framework (Dave McClure, 500 Startups) maps the full customer lifecycle into 5 measurable stages. Use this as the <strong>primary diagnostic framework</strong> when a user needs to understand where their growth is leaking.</p>
|
||
<p>| Stage | Question | Example Metrics | |-------|----------|-----------------| | <strong>Acquisition</strong> | How do users find us? | Visits, signups, CAC, channel attribution | | <strong>Activation</strong> | Do they have a great first experience? | Onboarding completion, time-to-value, aha-moment rate | | <strong>Retention</strong> | Do they come back? | DAU/MAU, churn rate, cohort retention curves | | <strong>Revenue</strong> | Do they pay? | ARPU, LTV, conversion rate, MRR/ARR | | <strong>Referral</strong> | Do they tell others? | NPS, viral coefficient (k-factor), referral rate |</p>
|
||
<p><strong>How to apply AARRR:</strong></p>
|
||
<ol><li><strong>Diagnose first</strong> — Ask: "Which stage is the biggest bottleneck?" Use data if available, or hypothesize based on product maturity.</li><li><strong>One stage at a time</strong> — Focus resources on the weakest stage. Improving Retention before scaling Acquisition prevents burning budget on users who churn.</li><li><strong>Set stage-specific OKRs</strong> — Each stage gets its own Objective and 2-3 Key Results.</li><li><strong>Measure cohorts, not aggregates</strong> — Weekly or monthly cohorts reveal trends that aggregate numbers hide.</li></ol>
|
||
<p><strong>Stage-specific playbooks:</strong></p>
|
||
<ul><li><strong>Acquisition bottleneck:</strong> Audit channel mix, test 3 new channels with small budget, measure CAC per channel. Consider content marketing (low CAC, slow) vs paid (high CAC, fast).</li><li><strong>Activation bottleneck:</strong> Map the first 5 minutes of user experience. Identify the "aha moment" (the action that correlates with retention). Reduce steps to reach it.</li><li><strong>Retention bottleneck:</strong> Build cohort analysis. Identify the "habit loop" — what makes users return? Add engagement hooks (notifications, digests, streaks). Segment by behavior.</li><li><strong>Revenue bottleneck:</strong> Test pricing tiers. Add annual plans (reduce churn). Identify expansion revenue opportunities (upsell, cross-sell). Optimize trial-to-paid flow.</li><li><strong>Referral bottleneck:</strong> Add referral program with bilateral incentives. Measure k-factor. Make sharing frictionless and contextual (share after a success moment, not randomly).</li></ul>
|
||
<h3>ICE Scoring — Quick Prioritization</h3>
|
||
<p>ICE (Sean Ellis) is a lightweight scoring model for rapid prioritization of growth experiments.</p>
|
||
<p>| Dimension | Score 1-10 | Question | |-----------|-----------|----------| | <strong>Impact</strong> | How much will this move the target metric? | 1 = negligible, 10 = 2x improvement | | <strong>Confidence</strong> | How sure are we this will work? | 1 = wild guess, 10 = proven playbook | | <strong>Ease</strong> | How easy is it to implement? | 1 = months of eng work, 10 = deploy today |</p>
|
||
<p><strong>ICE Score = (Impact + Confidence + Ease) / 3</strong></p>
|
||
<p><strong>When to use ICE:</strong> For backlogs of 10-30 ideas that need quick ranking. Not suitable for strategic decisions requiring deeper analysis.</p>
|
||
<p><strong>Pitfalls to avoid:</strong></p>
|
||
<ul><li>Confidence inflation — teams overestimate confidence on their own ideas. Require evidence links.</li><li>Ease bias — easy tasks get prioritized over high-impact hard tasks. Weight Impact 2x if needed.</li><li>Score anchoring — first scorer sets the range. Use blind scoring then average.</li></ul>
|
||
<h3>RICE Prioritization — Data-Driven Ranking</h3>
|
||
<p>RICE (Intercom) adds Reach to create a more rigorous prioritization model.</p>
|
||
<p>| Dimension | Definition | Unit | |-----------|-----------|------| | <strong>Reach</strong> | How many people will this affect per time period? | Users/quarter | | <strong>Impact</strong> | How much will each person be affected? | 0.25 (minimal) to 3 (massive) | | <strong>Confidence</strong> | How confident are we in estimates? | 50%-100% | | <strong>Effort</strong> | How much work is required? | Person-months |</p>
|
||
<p><strong>RICE Score = (Reach × Impact × Confidence) / Effort</strong></p>
|
||
<p><strong>When to use RICE:</strong> For roadmap prioritization with 5+ competing initiatives. Best when you have data on Reach.</p>
|
||
<p><strong>Confidence calibration:</strong></p>
|
||
<ul><li>100% = have data proving it works</li><li>80% = strong qualitative signal (user interviews, competitor proof)</li><li>50% = intuition only — acceptable but flag it</li></ul>
|
||
<hr>
|
||
<h2>Positioning Frameworks</h2>
|
||
<h3>Category Design</h3>
|
||
<p>Category design (Play Bigger methodology) means defining and owning a new market category rather than competing in an existing one.</p>
|
||
<p><strong>Steps:</strong></p>
|
||
<ol><li><strong>Identify the problem the market doesn't know it has</strong> — Frame a "before" and "after" that shifts perception.</li><li><strong>Name the category</strong> — The name should be intuitive, memorable, and googlable. Test with 5 people outside your industry.</li><li><strong>Lightning strike</strong> — Coordinate a launch event that educates the market on the category and your position as the leader.</li><li><strong>Category POV document</strong> — Write a 2-3 page manifesto explaining why the old way is broken and what the new category enables.</li></ol>
|
||
<p><strong>When NOT to use:</strong> If you're entering an established category with a better/cheaper product, compete on positioning within that category instead.</p>
|
||
<h3>Jobs-to-be-Done (JTBD)</h3>
|
||
<p>JTBD (Clayton Christensen, Tony Ulwick) reframes positioning around the job the customer is hiring your product to do.</p>
|
||
<p><strong>Job statement formula:</strong></p>
|
||
<pre><code>When [situation], I want to [motivation], so I can [expected outcome].</code></pre>
|
||
<p><strong>Example:</strong></p>
|
||
<pre><code>When I'm planning next quarter's content, I want to quickly generate
|
||
platform-specific posts, so I can maintain consistent presence without
|
||
spending 20 hours per week on content.</code></pre>
|
||
<p><strong>Applying JTBD to positioning:</strong></p>
|
||
<ol><li>Interview 10-15 customers about their last purchase decision</li><li>Extract the functional, emotional, and social jobs</li><li>Identify over-served jobs (competitors do this well) and under-served jobs (gap)</li><li>Position your product around the under-served jobs</li><li>Write messaging that directly addresses the job, not your features</li></ol>
|
||
<h3>Positioning Canvas</h3>
|
||
<p>Use this structured canvas to define positioning:</p>
|
||
<pre><code class="lang-yaml">positioning:
|
||
target_customer: "[Specific persona with problem]"
|
||
category: "[Market category you compete in or create]"
|
||
key_differentiator: "[The one thing you do uniquely well]"
|
||
proof_points:
|
||
- "[Data point or case study 1]"
|
||
- "[Data point or case study 2]"
|
||
- "[Data point or case study 3]"
|
||
competitive_alternative: "[What customers use today instead]"
|
||
unique_value: "[The transformation you enable]"</code></pre>
|
||
<hr>
|
||
<h2>Content Pillar Methodology</h2>
|
||
<p>Content pillars are 3-5 core themes that all content maps back to. They ensure consistency, reduce content planning overhead, and build topical authority.</p>
|
||
<h3>Building Content Pillars</h3>
|
||
<p><strong>Step 1: Audit your expertise zones</strong> List everything your team/product knows deeply. Group into 5-8 clusters.</p>
|
||
<p><strong>Step 2: Map to audience jobs</strong> For each cluster, answer: "Does my audience actively seek information about this?" Eliminate clusters with no audience demand.</p>
|
||
<p><strong>Step 3: Narrow to 3-5 pillars</strong> Criteria for a strong pillar:</p>
|
||
<ul><li>You have genuine expertise (not generic takes)</li><li>Your audience has proven demand (search volume, community questions)</li><li>Competitors underserve this topic</li><li>It connects to your product's value proposition</li></ul>
|
||
<p><strong>Step 4: Define sub-topics per pillar</strong> Each pillar should have 10-20 sub-topics. These become individual content pieces.</p>
|
||
<p><strong>Step 5: Map pillars to funnel stages</strong></p>
|
||
<pre><code>Pillar A → TOFU (awareness) + MOFU (consideration)
|
||
Pillar B → MOFU (consideration) + BOFU (decision)
|
||
Pillar C → TOFU (awareness)</code></pre>
|
||
<h3>Content Pillar Template</h3>
|
||
<pre><code class="lang-yaml">pillar:
|
||
name: "[Pillar Name]"
|
||
description: "[1-2 sentence description]"
|
||
target_persona: "[Primary persona]"
|
||
funnel_stages: [awareness, consideration, decision]
|
||
sub_topics:
|
||
- name: "[Sub-topic]"
|
||
format: [blog, video, social, newsletter]
|
||
priority: [high, medium, low]
|
||
search_intent: [informational, navigational, transactional]
|
||
kpis:
|
||
- metric: "[e.g., organic traffic to pillar pages]"
|
||
target: "[e.g., 5,000 visits/month within 6 months]"</code></pre>
|
||
<hr>
|
||
<h2>Campaign Planning Structure</h2>
|
||
<h3>Campaign Brief Template</h3>
|
||
<p>Every campaign should start with a brief that answers these questions:</p>
|
||
<pre><code class="lang-yaml">campaign:
|
||
name: "[Campaign Name]"
|
||
objective: "[Single clear objective — use SMART format]"
|
||
target_audience:
|
||
primary: "[Persona with demographics and psychographics]"
|
||
secondary: "[If applicable]"
|
||
key_message: "[One sentence — what should the audience think/feel/do?]"
|
||
channels:
|
||
- channel: "[e.g., LinkedIn]"
|
||
role: "[e.g., thought leadership, lead gen]"
|
||
budget: "[If applicable]"
|
||
content_types: ["posts", "articles", "ads"]
|
||
timeline:
|
||
start: "YYYY-MM-DD"
|
||
end: "YYYY-MM-DD"
|
||
milestones:
|
||
- date: "YYYY-MM-DD"
|
||
deliverable: "[What ships]"
|
||
success_metrics:
|
||
primary: "[The ONE metric that defines success]"
|
||
secondary:
|
||
- "[Supporting metric 1]"
|
||
- "[Supporting metric 2]"
|
||
budget:
|
||
total: "[Amount]"
|
||
breakdown:
|
||
- category: "[e.g., paid ads, tools, freelancers]"
|
||
amount: "[Amount]"
|
||
risks:
|
||
- risk: "[What could go wrong]"
|
||
mitigation: "[How to prevent or respond]"</code></pre>
|
||
<h3>Campaign Types and Playbooks</h3>
|
||
<p>| Type | Duration | Focus | Example | |------|----------|-------|---------| | <strong>Launch</strong> | 2-4 weeks | Awareness + Activation | Product launch, feature release | | <strong>Evergreen</strong> | Ongoing | SEO + Content authority | Blog series, resource hub | | <strong>Seasonal</strong> | 1-2 weeks | Relevance + Urgency | Black Friday, industry events | | <strong>Nurture</strong> | 4-8 weeks | Education + Conversion | Email sequence, webinar series | | <strong>Referral</strong> | Ongoing | Viral + Retention | Referral program, community |</p>
|
||
<hr>
|
||
<h2>Competitive Positioning Matrix</h2>
|
||
<h3>Building a Competitive Matrix</h3>
|
||
<p><strong>Step 1: Identify competitors</strong></p>
|
||
<ul><li>Direct competitors (same solution, same audience)</li><li>Indirect competitors (different solution, same problem)</li><li>Substitutes (what people use instead, including doing nothing)</li></ul>
|
||
<p><strong>Step 2: Define comparison dimensions</strong> Choose 5-8 dimensions that matter to your target buyer. Examples:</p>
|
||
<ul><li>Price, ease of use, feature depth, integrations, support quality, time-to-value</li></ul>
|
||
<p><strong>Step 3: Score honestly</strong> Rate each competitor 1-5 on each dimension. Be honest — inflating your score undermines the exercise.</p>
|
||
<p><strong>Step 4: Find your wedge</strong> The wedge is the dimension where you score highest AND competitors score lowest. This becomes your primary positioning angle.</p>
|
||
<pre><code class="lang-yaml">competitive_matrix:
|
||
dimensions:
|
||
- name: "[Dimension]"
|
||
weight: [1-5] # How important to buyer
|
||
competitors:
|
||
- name: "[Competitor]"
|
||
scores:
|
||
"[Dimension]": [1-5]
|
||
positioning: "[Their main claim]"
|
||
your_wedge: "[Dimension where you win]"
|
||
messaging_angle: "[How to frame your advantage]"</code></pre>
|
||
<hr>
|
||
<h2>OKR Writing for Marketing</h2>
|
||
<h3>OKR Structure</h3>
|
||
<p><strong>Objective:</strong> Qualitative, inspirational, time-bound. <strong>Key Results:</strong> Quantitative, measurable, challenging but achievable (70% hit rate target).</p>
|
||
<h3>Marketing OKR Templates</h3>
|
||
<p><strong>Growth-stage OKR:</strong></p>
|
||
<pre><code>O: Establish [Brand] as the go-to solution for [Job-to-be-Done]
|
||
KR1: Grow organic traffic from [X] to [Y] monthly visits
|
||
KR2: Achieve [X]% trial-to-paid conversion rate (from [current]%)
|
||
KR3: Reach [X] qualified leads per month via content marketing</code></pre>
|
||
<p><strong>Retention-focused OKR:</strong></p>
|
||
<pre><code>O: Build a community of engaged users who advocate for [Brand]
|
||
KR1: Increase NPS from [X] to [Y]
|
||
KR2: Grow referral-sourced signups from [X]% to [Y]% of total
|
||
KR3: Achieve [X]% monthly active rate among paid users</code></pre>
|
||
<p><strong>Brand-building OKR:</strong></p>
|
||
<pre><code>O: Own the [Category] conversation in [Industry]
|
||
KR1: Publish [X] thought leadership pieces with [Y]+ average shares
|
||
KR2: Secure [X] media mentions or podcast appearances
|
||
KR3: Grow LinkedIn followers from [X] to [Y] with [Z]%+ engagement rate</code></pre>
|
||
<h3>OKR Anti-patterns</h3>
|
||
<ul><li><strong>Vanity KRs:</strong> "Get 10,000 followers" without engagement or conversion context</li><li><strong>Activity KRs:</strong> "Publish 20 blog posts" — measure outcomes, not outputs</li><li><strong>Sandbagging:</strong> KRs you'll hit at 100% aren't ambitious enough</li><li><strong>Too many KRs:</strong> Max 3-4 per Objective. If you need more, split the Objective.</li></ul>
|
||
<hr>
|
||
<h2>TAM/SAM/SOM Analysis</h2>
|
||
<h3>Definitions</h3>
|
||
<p>| Level | Definition | Method | |-------|-----------|--------| | <strong>TAM</strong> (Total Addressable Market) | Total revenue opportunity if you captured 100% of the market | Top-down: industry reports. Bottom-up: # of potential customers × annual value | | <strong>SAM</strong> (Serviceable Addressable Market) | Portion of TAM you can reach with your current product and channels | TAM filtered by geography, segment, and product fit | | <strong>SOM</strong> (Serviceable Obtainable Market) | Realistic share you can capture in 1-3 years | SAM × realistic market share % based on competitive position |</p>
|
||
<h3>Calculation Template</h3>
|
||
<pre><code class="lang-yaml">tam_sam_som:
|
||
tam:
|
||
method: "[top-down or bottom-up]"
|
||
total_potential_customers: "[Number]"
|
||
average_annual_value: "[Amount per customer]"
|
||
total: "[TAM = customers × value]"
|
||
source: "[Where data came from]"
|
||
sam:
|
||
geographic_filter: "[Markets you can serve]"
|
||
segment_filter: "[Customer segments you target]"
|
||
product_fit_filter: "[Who your product actually serves]"
|
||
total: "[SAM after filters]"
|
||
som:
|
||
market_share_target: "[Realistic % — typically 1-5% for startups]"
|
||
timeline: "[1-3 years]"
|
||
total: "[SOM = SAM × share %]"
|
||
assumptions:
|
||
- "[Key assumption 1]"
|
||
- "[Key assumption 2]"</code></pre>
|
||
<h3>Quality Checks</h3>
|
||
<ul><li>TAM should come from at least 2 sources (cross-validate)</li><li>SAM should be less than 50% of TAM (if higher, your filters are too loose)</li><li>SOM should feel uncomfortably small (if it feels easy, you're overestimating)</li><li>Always list assumptions — investors and stakeholders will challenge them</li></ul>
|
||
<hr>
|
||
<h2>Strategy Document Output Format</h2>
|
||
<p>All strategy outputs must follow this format:</p>
|
||
<pre><code class="lang-yaml">---
|
||
type: strategy
|
||
subtype: "[campaign | positioning | growth-model | okr | competitive-analysis | market-sizing]"
|
||
status: draft
|
||
date: "YYYY-MM-DD"
|
||
author: marketing-strategy
|
||
brand: "[from brand-voice.yaml]"
|
||
tags:
|
||
- "[relevant tags]"
|
||
---</code></pre>
|
||
<h3>Anti-Slop Validation</h3>
|
||
<p>Before finalizing any strategy document:</p>
|
||
<ol><li>Scan for banned phrases from <code>brand-voice.yaml → anti_slop.banned_phrases</code></li><li>Replace any matches with specific, evidence-backed language</li><li>Verify active voice is used throughout</li><li>Ensure no superlatives appear without supporting data</li><li>Check that headlines are specific, not generic clickbait</li></ol>
|
||
<hr>
|
||
<h2>Output Contract</h2>
|
||
<h3>Strategy Document Schema</h3>
|
||
<pre><code class="lang-yaml">output_contract:
|
||
format: markdown
|
||
required_sections:
|
||
- frontmatter:
|
||
type: string # "strategy"
|
||
subtype: string # specific strategy type
|
||
status: string # "draft" | "review" | "approved"
|
||
date: string # ISO 8601
|
||
author: string # "marketing-strategy"
|
||
- executive_summary:
|
||
max_words: 150
|
||
must_include: [objective, approach, expected_outcome]
|
||
- analysis:
|
||
frameworks_used: list # which frameworks were applied
|
||
data_sources: list # where data came from
|
||
- recommendations:
|
||
format: prioritized_list
|
||
each_item:
|
||
- action: string
|
||
- rationale: string
|
||
- priority: string # "P0" | "P1" | "P2"
|
||
- effort: string # "low" | "medium" | "high"
|
||
- expected_impact: string
|
||
- success_metrics:
|
||
format: table
|
||
columns: [metric, current, target, timeline]
|
||
- next_steps:
|
||
format: checklist
|
||
max_items: 7
|
||
validation:
|
||
anti_slop: true # must pass anti-slop scan
|
||
brand_voice: true # must align with brand-voice.yaml
|
||
min_word_count: 500
|
||
max_word_count: 5000</code></pre>
|
||
<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="/marketing-strategy.md">This page as plain text</a> · <a href="/llms.txt">Index for agents</a></div>
|
||
</footer>
|
||
</div></body></html> |