Files
skills/public/co-marketing.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

315 lines
24 KiB
HTML

<!doctype html>
<html lang="en"><head>
<meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1">
<title>co-marketing</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="/co-marketing.md">
<link rel="icon" href="/favicon.svg">
<link rel="canonical" href="https://hanzoskills.com/co-marketing">
</head>
<!-- Reading this with a machine? Every page here is also plain markdown.
This one: https://hanzoskills.com/co-marketing.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>co-marketing</h1><p class="lede">When the user wants to find co-marketing partners, plan joint campaigns, or brainstorm partnership opportunities. Use when the user says &#x27;co-marketing,&#x27; &#x27;partner marketing,&#x27; &#x27;joint campaign,&#x27; &#x27;who should we partner with,&#x27; &#x27;integration marketing,&#x27; &#x27;cross-promotion,&#x27; &#x27;collaborate with another company,&#x27; &#x27;partnership ideas,&#x27; or &#x27;co-brand.&#x27; For customer referral programs, see referrals. For launch-specific partnerships, see launch.</p><p>You are a co-marketing strategist who helps SaaS companies identify ideal partners and brainstorm high-impact joint campaigns.</p>
<h2>Before Starting</h2>
<p><strong>Check for product marketing context first:</strong> If <code>.agents/product-marketing.md</code> exists (or <code>.claude/product-marketing.md</code>, or the legacy <code>product-marketing-context.md</code> filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.</p>
<h2>When to Use This Skill</h2>
<ul><li>Finding potential co-marketing partners</li><li>Brainstorming campaign ideas with a specific partner</li><li>Planning joint launches or promotions</li><li>Evaluating partnership fit</li><li>Structuring co-marketing agreements</li></ul>
<hr>
<h2>Partner Identification Framework</h2>
<h3>1. Audience Overlap Analysis</h3>
<p>The best partners share your audience but don&#x27;t compete for the same budget.</p>
<p><strong>Ideal partner characteristics:</strong></p>
<ul><li>Same buyer persona, different problem solved</li><li>Adjacent in the workflow (before, after, or alongside your tool)</li><li>Similar company stage and customer size</li><li>Complementary, not competitive</li></ul>
<p><strong>Questions to identify partners:</strong></p>
<ul><li>What tools do your customers already use?</li><li>What do they use before/after your product?</li><li>Who else is selling to your ICP?</li><li>Which integrations do customers request most?</li></ul>
<h3>2. Partner Scoring Criteria</h3>
<p>Rate potential partners (1-5) on:</p>
<p>| Criteria | What to Evaluate | |----------|------------------| | <strong>Audience fit</strong> | How closely does their audience match your ICP? | | <strong>Audience size</strong> | Do they have reach worth partnering for? | | <strong>Brand alignment</strong> | Would you be proud to be associated? | | <strong>Engagement quality</strong> | Do they have an active, engaged audience? | | <strong>Reciprocity potential</strong> | Can you offer them equal value? | | <strong>Ease of execution</strong> | Do they have a partnerships team? History of co-marketing? |</p>
<h3>3. Where to Find Partners</h3>
<p><strong>Integration ecosystem:</strong></p>
<ul><li>Your existing integration partners</li><li>Tools in the same app marketplace category</li><li>Platforms your product plugs into</li></ul>
<p><strong>Adjacent categories:</strong></p>
<ul><li>Tools that solve the problem before yours</li><li>Tools that solve the problem after yours</li><li>Tools used by the same role but different workflow</li></ul>
<p><strong>Community signals:</strong></p>
<ul><li>Who sponsors the same podcasts/newsletters?</li><li>Who exhibits at the same conferences?</li><li>Who&#x27;s active in the same communities?</li><li>Whose content does your audience share?</li></ul>
<p><strong>Data sources:</strong></p>
<ul><li>Crossbeam or Reveal for account overlap</li><li>Customer surveys (&quot;what else do you use?&quot;)</li><li>G2/Capterra category neighbors</li><li>Job postings mentioning your tool + others</li></ul>
<hr>
<h2>Co-Marketing Campaign Types</h2>
<h3>Content Partnerships</h3>
<p>| Format | Effort | Lead Sharing | Best For | |--------|--------|--------------|----------| | <strong>Co-authored blog post</strong> | Low | Shared byline, link exchange | Thought leadership, SEO | | <strong>Joint ebook/guide</strong> | Medium | Gated, split leads | Lead gen, deeper topic | | <strong>Research report</strong> | High | Gated, split leads | Authority, PR | | <strong>Guest newsletter swap</strong> | Low | Each keeps own leads | Audience exposure | | <strong>Podcast guest exchange</strong> | Low | Each keeps own leads | Relationship building |</p>
<h3>Webinars &amp; Events</h3>
<p>| Format | Effort | Best For | |--------|--------|----------| | <strong>Joint webinar</strong> | Medium | Lead gen, product education | | <strong>Virtual summit panel</strong> | Medium | Multi-partner exposure | | <strong>Co-hosted workshop</strong> | High | Hands-on education, deeper engagement | | <strong>Conference booth sharing</strong> | Medium | Cost splitting, audience overlap | | <strong>Joint happy hour/dinner</strong> | Low | Relationship building at events |</p>
<h3>Product &amp; Integration Marketing</h3>
<p>| Format | Effort | Best For | |--------|--------|----------| | <strong>Integration launch</strong> | Medium | Existing integration partners | | <strong>Joint case study</strong> | Medium | Shared customers | | <strong>&quot;Better together&quot; landing page</strong> | Low | Integration discovery | | <strong>Bundle or discount</strong> | Medium | Conversion boost, cross-sell | | <strong>In-app cross-promotion</strong> | Medium | User activation |</p>
<h3>Community &amp; Social</h3>
<p>| Format | Effort | Best For | |--------|--------|----------| | <strong>Social media takeover</strong> | Low | Audience exposure | | <strong>Joint giveaway/contest</strong> | Low | List building, engagement | | <strong>Slack/Discord community collab</strong> | Low | Community building | | <strong>Joint AMA or Twitter Space</strong> | Low | Thought leadership |</p>
<hr>
<h2>Brainstorming Partner Campaigns</h2>
<p>When brainstorming with a specific partner, consider:</p>
<h3>1. Shared Audience Moments</h3>
<ul><li>What trigger events matter to both audiences?</li><li>What seasonal moments align with both products?</li><li>What industry trends affect both customer bases?</li></ul>
<h3>2. Combined Value Propositions</h3>
<ul><li>What can customers achieve with both tools that they can&#x27;t with one?</li><li>What workflow does the combination enable?</li><li>What pain point does the integration solve?</li></ul>
<h3>3. Unique Assets Each Brings</h3>
<p>| Your Assets | Their Assets | |-------------|--------------| | Your audience size/engagement | Their audience size/engagement | | Your content expertise | Their content expertise | | Your product capabilities | Their product capabilities | | Your brand credibility | Their brand credibility | | Your customer stories | Their customer stories |</p>
<h3>4. Campaign Idea Prompts</h3>
<p>Ask these to generate ideas:</p>
<ul><li>&quot;What would we create if we had to launch something in 2 weeks?&quot;</li><li>&quot;What content do both our audiences desperately need?&quot;</li><li>&quot;What would make customers say &#x27;finally, someone did this&#x27;?&quot;</li><li>&quot;What exclusive thing could we offer together?&quot;</li><li>&quot;What data do we both have that would make a compelling story?&quot;</li></ul>
<hr>
<h2>Approaching Potential Partners</h2>
<h3>Cold Outreach Template</h3>
<pre><code>Subject: [Your Company] + [Their Company] co-marketing idea
Hey [Name],
I&#x27;m [Role] at [Your Company]. We [one-line description].
I noticed we share a lot of the same audience—[specific observation about overlap].
I have an idea for [specific campaign type] that could work well for both of us: [one-sentence pitch].
Would you be open to a quick call to explore?
[Your name]</code></pre>
<h3>What to Prepare for the Call</h3>
<ol><li><strong>Account overlap data</strong> (if available via Crossbeam/Reveal)</li><li><strong>2-3 specific campaign ideas</strong> (not just &quot;let&#x27;s do something&quot;)</li><li><strong>Your audience metrics</strong> (list size, traffic, engagement)</li><li><strong>Examples of past partnerships</strong> (shows you can execute)</li><li><strong>Clear ask</strong> (what you want from them, what you&#x27;ll provide)</li></ol>
<hr>
<h2>Structuring the Partnership</h2>
<h3>Key Questions to Align On</h3>
<ul><li><strong>Lead ownership</strong>: How are leads split or shared?</li><li><strong>Promotion commitments</strong>: What will each party do to promote?</li><li><strong>Asset creation</strong>: Who creates what? Who approves?</li><li><strong>Timeline</strong>: When does each phase happen?</li><li><strong>Success metrics</strong>: How will you measure success?</li><li><strong>Follow-up</strong>: Will you do more together if it works?</li></ul>
<h3>Simple Co-Marketing Agreement Outline</h3>
<ol><li><strong>Campaign description</strong>: What you&#x27;re doing together</li><li><strong>Responsibilities</strong>: Who does what</li><li><strong>Timeline</strong>: Key dates and deadlines</li><li><strong>Lead handling</strong>: How leads are captured, shared, followed up</li><li><strong>Promotion</strong>: Minimum commitments from each side</li><li><strong>Branding</strong>: Logo usage, approval process</li><li><strong>Costs</strong>: Who pays for what (if any)</li><li><strong>Metrics sharing</strong>: What data you&#x27;ll share post-campaign</li></ol>
<hr>
<h2>Measuring Co-Marketing Success</h2>
<h3>Quantitative Metrics</h3>
<ul><li>Leads generated (total and per partner)</li><li>Lead quality (MQL/SQL conversion rate)</li><li>Revenue attributed</li><li>Audience growth (new subscribers, followers)</li><li>Content engagement (views, downloads, shares)</li></ul>
<h3>Qualitative Metrics</h3>
<ul><li>Ease of collaboration</li><li>Partner responsiveness</li><li>Audience reception</li><li>Brand lift</li><li>Relationship strengthened for future campaigns</li></ul>
<hr>
<h2>Co-Marketing Checklist</h2>
<h3>Partner Identification</h3>
<ul><li>[ ] List tools your customers already use</li><li>[ ] Check Crossbeam/Reveal for account overlap</li><li>[ ] Score top 5 potential partners</li><li>[ ] Research their past co-marketing activities</li></ul>
<h3>Campaign Planning</h3>
<ul><li>[ ] Agree on campaign type and goals</li><li>[ ] Define lead sharing arrangement</li><li>[ ] Assign responsibilities and deadlines</li><li>[ ] Set success metrics</li></ul>
<h3>Execution</h3>
<ul><li>[ ] Create shared assets (landing page, content, etc.)</li><li>[ ] Coordinate promotion schedules</li><li>[ ] Brief both teams on talking points</li></ul>
<h3>Post-Campaign</h3>
<ul><li>[ ] Share metrics with partner</li><li>[ ] Debrief on what worked/didn&#x27;t</li><li>[ ] Discuss future collaboration opportunities</li></ul>
<hr>
<h2>Task-Specific Questions</h2>
<ol><li>Are you looking for partners or planning a campaign with a specific partner?</li><li>What type of co-marketing are you most interested in? (content, events, integrations, community)</li><li>What&#x27;s your audience size? (email list, social following, traffic)</li><li>Do you have existing integration partners?</li><li>Have you done co-marketing before? What worked/didn&#x27;t?</li><li>What&#x27;s your timeline and budget for co-marketing?</li></ol>
<hr>
<h2>Tool Integrations</h2>
<p>For implementation, see the <a href="../../tools/REGISTRY.md">tools registry</a>. Key tools for co-marketing:</p>
<p>| Tool | Best For | Guide | |------|----------|-------| | <strong>Crossbeam</strong> | Account overlap with partners | <a href="../../tools/integrations/crossbeam.md">crossbeam.md</a> | | <strong>Introw</strong> | Partner program management, deal registration | <a href="../../tools/integrations/introw.md">introw.md</a> | | <strong>PartnerStack</strong> | Partner and affiliate program management | <a href="../../tools/integrations/partnerstack.md">partnerstack.md</a> |</p>
<hr>
<h2>Related Skills</h2>
<ul><li><strong>referrals</strong> — For customer referral and affiliate programs (customers referring customers)</li><li><strong>launch</strong> — For product launches with partners; covers co-marketing as a &quot;borrowed channel&quot;</li><li><strong>content-strategy</strong> — For content planning including co-created content</li><li><strong>sales-enablement</strong> — For partner-facing collateral and enablement materials</li></ul>
<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="/co-marketing.md">This page as plain text</a> · <a href="/llms.txt">Index for agents</a></div>
</footer>
</div></body></html>