Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
5b2c000776 | ||
|
|
5cd4a7eae3 | ||
|
|
88de9fd15d | ||
|
|
4fbe11fd0a | ||
|
|
d4ff28a9c8 | ||
|
|
e55de886fe | ||
|
|
b1aaa3619e | ||
|
|
2b92a8f924 | ||
|
|
0d12b95752 | ||
|
|
e90dd3ba6c | ||
|
|
becd60ee9d | ||
|
|
b6fc21ef94 | ||
|
|
997ab1a351 | ||
|
|
cf7a1f741f | ||
|
|
f557c546c8 | ||
|
|
8d8098d023 | ||
|
|
eb7f72faa3 | ||
|
|
8907942a47 | ||
|
|
cc8c948b70 | ||
|
|
da0213fc66 | ||
|
|
694f9b6fe6 | ||
|
|
abae3fcdc3 |
@@ -6,13 +6,13 @@
|
||||
},
|
||||
"metadata": {
|
||||
"description": "Marketing skills for AI agents — conversion optimization, copywriting, SEO, paid ads, and growth",
|
||||
"version": "2.10.5",
|
||||
"version": "2.11.1",
|
||||
"repository": "https://github.com/coreyhaines31/marketingskills"
|
||||
},
|
||||
"plugins": [
|
||||
{
|
||||
"name": "marketing-skills",
|
||||
"description": "49 marketing skills for technical marketers and founders: CRO, copywriting, cold email, prospecting, SEO, AI SEO, paid ads, SMS, ad creative, video production, image generation, co-marketing, churn prevention, pricing, referrals, revenue operations, sales enablement, customer research, site architecture, comprehensive AARRR-structured marketing plans, public relations and earned media, offer design, and more",
|
||||
"description": "50 marketing skills for technical marketers and founders: CRO, copywriting, cold email, prospecting, SEO, AI SEO, paid ads, SMS, ad creative, video production, image generation, co-marketing, churn prevention, pricing, referrals, revenue operations, sales enablement, customer research, site architecture, comprehensive AARRR-structured marketing plans, public relations and earned media, offer design, event marketing and webinars, and more",
|
||||
"source": "./"
|
||||
}
|
||||
]
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
{
|
||||
"name": "marketing-skills",
|
||||
"description": "Marketing skills for AI agents — conversion optimization, copywriting, SEO, paid ads, ad creative, and growth",
|
||||
"version": "2.10.5",
|
||||
"version": "2.11.1",
|
||||
"author": {
|
||||
"name": "Corey Haines"
|
||||
},
|
||||
|
||||
@@ -0,0 +1,71 @@
|
||||
name: Release on version bump
|
||||
|
||||
# Auto-creates a git tag + GitHub Release whenever the repo version in
|
||||
# .claude-plugin/plugin.json changes on main. Release notes are pulled from
|
||||
# the matching `### x.y.z` block in VERSIONS.md. Idempotent: if the tag
|
||||
# already exists, it does nothing (safe to re-run / backfill manually).
|
||||
|
||||
on:
|
||||
push:
|
||||
branches: [main]
|
||||
paths:
|
||||
- ".claude-plugin/plugin.json"
|
||||
- "VERSIONS.md"
|
||||
|
||||
permissions:
|
||||
contents: write
|
||||
|
||||
jobs:
|
||||
release:
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- uses: actions/checkout@v4
|
||||
with:
|
||||
fetch-depth: 0
|
||||
|
||||
- name: Determine version and whether it's already tagged
|
||||
id: ver
|
||||
run: |
|
||||
VERSION=$(python3 -c "import json;print(json.load(open('.claude-plugin/plugin.json'))['version'])")
|
||||
echo "version=$VERSION" >> "$GITHUB_OUTPUT"
|
||||
if git rev-parse -q --verify "refs/tags/v$VERSION" >/dev/null; then
|
||||
echo "exists=true" >> "$GITHUB_OUTPUT"
|
||||
echo "v$VERSION already tagged — nothing to do."
|
||||
else
|
||||
echo "exists=false" >> "$GITHUB_OUTPUT"
|
||||
fi
|
||||
|
||||
- name: Extract release notes + title from VERSIONS.md
|
||||
if: steps.ver.outputs.exists == 'false'
|
||||
run: |
|
||||
python3 - "${{ steps.ver.outputs.version }}" <<'PY'
|
||||
import re, sys
|
||||
v = sys.argv[1]
|
||||
text = open("VERSIONS.md").read()
|
||||
parts = re.split(r"\n### (\d+\.\d+\.\d+) \([^)]*\)\n", text)
|
||||
blocks = {}
|
||||
for i in range(1, len(parts), 2):
|
||||
blocks[parts[i]] = parts[i + 1].split("\n### ")[0].strip()
|
||||
body = blocks.get(v, f"Release {v}")
|
||||
open("release-notes.md", "w").write(body + "\n")
|
||||
# title = first non-empty line, stripped of markdown, truncated
|
||||
first = next((l for l in body.splitlines() if l.strip()), "")
|
||||
first = re.sub(r"[*`_]|^- |\[([^\]]+)\]\([^)]+\)", r"\1", first).strip()
|
||||
title = f"v{v} — {first}"
|
||||
if len(title) > 100:
|
||||
title = title[:99].rstrip() + "…"
|
||||
open("release-title.txt", "w").write(title)
|
||||
print("Title:", title)
|
||||
PY
|
||||
|
||||
- name: Create tag + release
|
||||
if: steps.ver.outputs.exists == 'false'
|
||||
env:
|
||||
GH_TOKEN: ${{ github.token }}
|
||||
run: |
|
||||
VERSION="${{ steps.ver.outputs.version }}"
|
||||
gh release create "v$VERSION" \
|
||||
--target "${{ github.sha }}" \
|
||||
--title "$(cat release-title.txt)" \
|
||||
--notes-file release-notes.md
|
||||
echo "Created release v$VERSION"
|
||||
@@ -28,3 +28,4 @@ skills-lock.json
|
||||
*~
|
||||
.idea/
|
||||
.vscode/
|
||||
.partners-pending/
|
||||
|
||||
@@ -65,6 +65,19 @@ skills/your-skill-name/
|
||||
3. Keep changes focused and minimal
|
||||
4. Update the version in metadata if making significant changes
|
||||
|
||||
## Mentioning Tools (the integrity rubric)
|
||||
|
||||
This library is open source and contributions are welcome from **anyone — including the makers of tools, and paid partners.** We gate on the *content*, not the contributor. A contribution that names a tool (yours or anyone's) is fine as long as it makes an agent **aware** of the right option at the moment it's relevant, without manufacturing a recommendation. Concretely:
|
||||
|
||||
- **Options, not one answer.** Present a tool alongside the real alternatives for the same job (including the free / DIY path), so the agent picks on fit — not because only one is named.
|
||||
- **At the point of relevance.** Surface a tool where an agent genuinely needs it (e.g. the implementation step), not injected into unrelated sections.
|
||||
- **No forced endorsement.** No "best," "recommended," or "use X instead." Describe what each option does and when it fits.
|
||||
- **Facts over framing.** Recipes, code, capabilities, and honest tradeoffs (cost, effort, lead time) — verifiable, not marketing copy.
|
||||
- **Disclose self-interest.** If you're the tool's maker or a partner, say so. Partner tools are marked ◆ in [`tools/REGISTRY.md`](tools/REGISTRY.md#verified-partners); house tools (built by the maintainer) carry stricter disclosure.
|
||||
- **The swap test.** If you swapped your tool for a competitor, the section should still read as fair. If removing it breaks the guidance, it was shilling — rework it.
|
||||
|
||||
The maintainer holds final editorial control and may edit or cut anything for neutrality and accuracy. Core skills stay editorially independent: sponsorship and contributions add content, they never buy a recommendation. Full program rules and boundaries — the tool taxonomy, what sponsorship buys and never buys, disclosure, and the partner lifecycle — are in [`tools/PARTNERS.md`](tools/PARTNERS.md).
|
||||
|
||||
## Submitting Your Contribution
|
||||
|
||||
1. Fork the repository
|
||||
@@ -83,6 +96,7 @@ skills/your-skill-name/
|
||||
- [ ] Instructions are clear and actionable
|
||||
- [ ] No sensitive data or credentials
|
||||
- [ ] Follows existing skill patterns in the repo
|
||||
- [ ] Any tool mentions follow the [integrity rubric](#mentioning-tools-the-integrity-rubric) — options not one answer, disclosed, passes the swap test
|
||||
|
||||
## Questions?
|
||||
|
||||
|
||||
@@ -10,6 +10,18 @@ New to the terminal and coding agents? Check out the companion guide [Coding for
|
||||
|
||||
Run into a problem or have a question? [Open an issue](https://github.com/coreyhaines31/marketingskills/issues) — we're happy to help.
|
||||
|
||||
## Partners
|
||||
|
||||
The library is free and MIT-licensed. [Verified Partners](tools/REGISTRY.md#verified-partners) fund the work — vetted, disclosed tool integrations, listed alongside the neutral options and never influencing what the core skills recommend. The full rules and boundaries are in [tools/PARTNERS.md](tools/PARTNERS.md). [Become a partner →](https://marketing-skills.com/sponsorship)
|
||||
|
||||
<!-- PARTNERS:START -->
|
||||
> ◆ **[Converly](https://converly.io?ref=marketingskills)** — *Conversion tracking / attribution.* Server-side conversion tracking that fires when someone submits a form, books a meeting, or starts a chat — passing click IDs and identifiers for Enhanced Conversions (Google) and high EMQ match rates (Meta), across 100+ tools. CLI + MCP so your agent sets it up in minutes. → [Integration guide](tools/integrations/converly.md)
|
||||
|
||||
> ◆ **[Ploy](https://ploy.ai?ref=marketingskills)** — *AI website & growth platform.* AI marketing platform built around a Webflow-grade website builder — site optimization, SEO/AEO, visitor identification, and ad creative in one, with WebMCP to expose site actions to AI assistants. → [Integration guide](tools/integrations/ploy.md)
|
||||
<!-- PARTNERS:END -->
|
||||
|
||||
<!-- The Partners block above is generated from partners.json — run `node scripts/sync-partners.mjs` after editing it. -->
|
||||
|
||||
## What are Skills?
|
||||
|
||||
Skills are markdown files that give AI agents specialized knowledge and workflows for specific tasks. When you add these to your project, your agent can recognize when you're working on a marketing task and apply the right frameworks and best practices.
|
||||
@@ -76,6 +88,7 @@ See each skill's **Related Skills** section for the full dependency map.
|
||||
| [customer-research](skills/customer-research/) | When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer... |
|
||||
| [directory-submissions](skills/directory-submissions/) | When the user wants to submit their product to startup, SaaS, AI, agent, MCP, no-code, or review directories for... |
|
||||
| [emails](skills/emails/) | When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email... |
|
||||
| [events](skills/events/) | When the user wants to plan, run, sponsor, speak at, or get pipeline from events — webinars, conferences, trade shows,... |
|
||||
| [free-tools](skills/free-tools/) | When the user wants to plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or... |
|
||||
| [image](skills/image/) | When the user wants to create, generate, edit, or optimize images for marketing — blog heroes, social graphics, product... |
|
||||
| [influencer-marketing](skills/influencer-marketing/) | When the user wants to run influencer, creator, or ambassador partnerships to promote their product — finding and... |
|
||||
@@ -292,6 +305,7 @@ You can also invoke skills directly:
|
||||
|
||||
### Paid & Distribution
|
||||
- `ads` - Google, Meta, LinkedIn ad campaigns
|
||||
- `events` - Webinars, conferences, sponsorships, speaking
|
||||
- `ad-creative` - Bulk ad creative generation and iteration
|
||||
- `social` - Social media scheduling and strategy
|
||||
|
||||
|
||||
+11
-1
@@ -6,7 +6,7 @@ Current versions of all skills. Agents can compare against local versions to che
|
||||
|-------|---------|--------------|
|
||||
| ab-testing | 2.0.0 | 2026-05-05 |
|
||||
| ad-creative | 2.8.2 | 2026-08-23 |
|
||||
| ai-seo | 2.4.0 | 2026-08-21 |
|
||||
| ai-seo | 2.5.0 | 2026-09-04 |
|
||||
| analytics | 2.0.1 | 2026-07-22 |
|
||||
| aso | 2.0.1 | 2026-08-19 |
|
||||
| attribution | 1.1.0 | 2026-07-23 |
|
||||
@@ -23,6 +23,7 @@ Current versions of all skills. Agents can compare against local versions to che
|
||||
| customer-research | 2.0.2 | 2026-08-23 |
|
||||
| directory-submissions | 2.0.0 | 2026-05-05 |
|
||||
| emails | 2.0.0 | 2026-05-05 |
|
||||
| events | 1.0.0 | 2026-08-23 |
|
||||
| free-tools | 2.0.1 | 2026-08-23 |
|
||||
| image | 2.0.1 | 2026-05-18 |
|
||||
| influencer-marketing | 1.1.0 | 2026-08-19 |
|
||||
@@ -56,6 +57,15 @@ Current versions of all skills. Agents can compare against local versions to che
|
||||
|
||||
## Recent Changes
|
||||
|
||||
### 2.11.1 (2026-09-04)
|
||||
|
||||
- **ai-seo** (2.4.0 → 2.5.0): new `references/format-volatility.md` — the citation-*format* volatility axis, companion to agent-readiness.md's citation-*source* volatility. Anchored on the **ChatGPT 5.6 format shift** (Aug 2026, Peec AI data via Tomek Rudzki and Lily Ray): fan-out queries dropped the "vs / comparison / top / best / reviews" modifiers while `site:` and "official" searches surged, and citations by page type fell −50.5% for listicles (15.77% → 7.80%) and −32.1% for comparison pages (9.08% → 6.17%) — the two formats companies scaled for GEO, demoted in one release. Covers what changes (stop justifying scaled listicle/comparison production with "wins AI citations"; owned "official" pages rising as the citable class) and what doesn't (comparisons still convert humans and still earn citations on Google AIO / Gemini / Perplexity — a per-platform format table replaces one-size-fits-all advice). Adds **LinkedIn as a citation surface** from LinkedIn's own AEO guide (via Chris Long, platform-reported: most-cited outlet for professional searches; Articles out-cite Posts ~60/40; first words of a post become the URL slug — front-load the target phrase), a **DIY ChatGPT fan-out extraction** diagnostic (DevTools → network payload → literal background queries; explicitly warned against as a mass-generation content-spam input), and a **measurement-rigor** section (AI answers are non-deterministic: 3–5 runs per query, mention *rate* with sample size, rates-over-time not run-vs-run, technical/comprehension/trust cause split; framing credited to Initial Commit's AEO audit skill, Josh Pigford). SKILL.md: Content Types section rewritten around the volatility (stale ~33%-comparison-share table retired to context), ChatGPT fan-out + extraction pointer added to the fan-out section, LinkedIn added to the Presence pillar, non-determinism rule added to DIY monitoring, new triggers ('do listicles still work for AI,' 'ChatGPT stopped citing comparison pages,' 'AI citation format shift'). New eval (id 10) covers the scaled-comparison-roadmap prompt that must get the 5.6 pushback plus the one-run-anecdote measurement correction.
|
||||
|
||||
|
||||
### 2.11.0 (2026-08-23)
|
||||
|
||||
- Added the **`events`** skill (1.0.0) — event marketing across all four roles: **hosting** (webinar → workshop → dinner → meetup → virtual summit → user conference, governed by "the topic is the targeting" and recurring-beats-one-off), **sponsoring/exhibiting**, **speaking**, and **attending** (target list → pre-booked meetings → the side-event play). Built on the universal arc — **20% event, 80% before-and-after** — with the 24–48h tiered follow-up, capture-context-not-just-contact discipline, an event-as-recording-studio content arc (transcripts compound in AI answers → ai-seo, public-relations), and a three-tier measurement model (vanity / real / decisive) with multi-touch honesty via attribution. Four references: **webinar-funnel.md** (the flagship funnel, closes #485), **sponsorship-roi.md** (ICP-overlap + cost-per-qualified-meeting math, side-event play, tiered follow-up), **speaking.md** (CFP craft, talk storyboard, the recording as the real audience), and **event-portfolio-strategy.md** (which events to invest in: in-person-necessity by segment, the 80/20 of selection, size↔ROI inverse, the owned/trade-show/community frame + economics — distilled from Corey's *Founding Marketing* ch.9). Seven evals. New skill = repo y release; total skills: 50. Closes #485.
|
||||
|
||||
### 2.10.5 (2026-08-23)
|
||||
|
||||
Batch enrichment across 15 existing skills, distilled from Corey Haines's *Founding Marketing* book (full 19-chapter scan). Each is a patch bump; no new skills.
|
||||
|
||||
@@ -0,0 +1,31 @@
|
||||
{
|
||||
"_comment": "Canonical partner registry — single source of truth. Fill one object per partner from their onboarding packet, then run `node scripts/sync-partners.mjs` to regenerate the README Partners section and the Verified Partners table in tools/REGISTRY.md. The marketing-skills.com site fetches this file directly (raw GitHub). Deactivate a lapsed partner with active:false (keeps history, removes it everywhere).",
|
||||
"partners": [
|
||||
{
|
||||
"id": "converly",
|
||||
"name": "Converly",
|
||||
"url": "https://converly.io",
|
||||
"category": "Marketing analytics & attribution",
|
||||
"categoryShort": "Conversion tracking / attribution",
|
||||
"tier": "skill-partner",
|
||||
"tagline": "Server-side conversion tracking",
|
||||
"blurb": "Server-side conversion tracking that fires when someone submits a form, books a meeting, or starts a chat — passing click IDs and identifiers for Enhanced Conversions (Google) and high EMQ match rates (Meta), across 100+ tools. CLI + MCP so your agent sets it up in minutes.",
|
||||
"logoUrl": "/logos/converly.png",
|
||||
"integration": "tools/integrations/converly.md",
|
||||
"active": true
|
||||
},
|
||||
{
|
||||
"id": "ploy",
|
||||
"name": "Ploy",
|
||||
"url": "https://ploy.ai",
|
||||
"category": "Website & landing page builders",
|
||||
"categoryShort": "AI website & growth platform",
|
||||
"tier": "skill-partner",
|
||||
"tagline": "Turns your website into a growth engine",
|
||||
"blurb": "AI marketing platform built around a Webflow-grade website builder — site optimization, SEO/AEO, visitor identification, and ad creative in one, with WebMCP to expose site actions to AI assistants.",
|
||||
"logoUrl": "/logos/ploy.png",
|
||||
"integration": "tools/integrations/ploy.md",
|
||||
"active": true
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -0,0 +1,77 @@
|
||||
#!/usr/bin/env node
|
||||
// Regenerate every partner surface from the canonical partners.json.
|
||||
//
|
||||
// node scripts/sync-partners.mjs # write the generated blocks
|
||||
// node scripts/sync-partners.mjs --check # fail if anything is out of date (CI)
|
||||
//
|
||||
// Owns the marked blocks in:
|
||||
// - README.md → the Partners section list
|
||||
// - tools/REGISTRY.md → the Verified Partners table
|
||||
// Everything outside the <!-- PARTNERS:START --> / <!-- PARTNERS:END --> markers
|
||||
// is left untouched. The marketing-skills.com site reads partners.json directly.
|
||||
|
||||
import { readFileSync, writeFileSync } from "node:fs";
|
||||
import { resolve, dirname } from "node:path";
|
||||
import { fileURLToPath } from "node:url";
|
||||
|
||||
const HERE = dirname(fileURLToPath(import.meta.url));
|
||||
const ROOT = resolve(HERE, "..");
|
||||
const REPO = "https://github.com/coreyhaines31/marketingskills/blob/main";
|
||||
const REF = "?ref=marketingskills";
|
||||
|
||||
const START = "<!-- PARTNERS:START -->";
|
||||
const END = "<!-- PARTNERS:END -->";
|
||||
const check = process.argv.includes("--check");
|
||||
|
||||
const { partners } = JSON.parse(readFileSync(resolve(ROOT, "partners.json"), "utf8"));
|
||||
const active = partners.filter((p) => p.active);
|
||||
|
||||
const readmeBlock = active.length
|
||||
? active
|
||||
.map(
|
||||
(p) =>
|
||||
`> ◆ **[${p.name}](${p.url}${REF})** — *${p.categoryShort || p.category}.* ${p.blurb} → [Integration guide](${p.integration})`
|
||||
)
|
||||
.join("\n\n")
|
||||
: "_No active partners yet. [Become a partner →](https://marketing-skills.com/sponsorship)_";
|
||||
|
||||
const registryBlock = [
|
||||
"| Partner | Category | Guide |",
|
||||
"|---------|----------|-------|",
|
||||
...active.map(
|
||||
(p) =>
|
||||
`| ◆ ${p.name} | ${p.categoryShort || p.category} | [${p.integration.split("/").pop()}](${p.integration.replace(/^tools\//, "")}) |`
|
||||
),
|
||||
].join("\n");
|
||||
|
||||
const targets = [
|
||||
{ file: "README.md", block: readmeBlock },
|
||||
{ file: "tools/REGISTRY.md", block: registryBlock },
|
||||
];
|
||||
|
||||
let stale = false;
|
||||
for (const { file, block } of targets) {
|
||||
const path = resolve(ROOT, file);
|
||||
const src = readFileSync(path, "utf8");
|
||||
const i = src.indexOf(START);
|
||||
const j = src.indexOf(END);
|
||||
if (i === -1 || j === -1 || j < i) {
|
||||
console.error(`✗ ${file}: missing ${START} / ${END} markers`);
|
||||
process.exitCode = 1;
|
||||
continue;
|
||||
}
|
||||
const next = src.slice(0, i + START.length) + "\n" + block + "\n" + src.slice(j);
|
||||
if (next === src) {
|
||||
console.log(`✓ ${file} up to date`);
|
||||
continue;
|
||||
}
|
||||
if (check) {
|
||||
console.error(`✗ ${file} is out of date — run: node scripts/sync-partners.mjs`);
|
||||
stale = true;
|
||||
continue;
|
||||
}
|
||||
writeFileSync(path, next);
|
||||
console.log(`↻ ${file} updated (${active.length} partner${active.length === 1 ? "" : "s"})`);
|
||||
}
|
||||
|
||||
if (check && stale) process.exitCode = 1;
|
||||
+10
-18
@@ -1,8 +1,8 @@
|
||||
---
|
||||
name: ai-seo
|
||||
description: "When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'generative engine optimization,' 'LLM optimization,' 'AI Overviews,' 'optimize for ChatGPT,' 'optimize for Perplexity,' 'AI citations,' 'AI visibility,' 'zero-click search,' 'how do I show up in AI answers,' 'LLM mentions,' 'optimize for Claude/Gemini,' 'llms.txt,' 'llms-full.txt,' 'OKF,' 'Open Knowledge Format,' 'knowledge bundle,' 'agent-readable site,' 'agent readiness,' 'is my site agent-ready,' or 'WebMCP.' Use this whenever someone wants their content to be cited or surfaced by AI assistants and AI search engines. For traditional technical and on-page SEO audits, see seo-audit. For structured data implementation, see schema."
|
||||
description: "When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'generative engine optimization,' 'LLM optimization,' 'AI Overviews,' 'optimize for ChatGPT,' 'optimize for Perplexity,' 'AI citations,' 'AI visibility,' 'zero-click search,' 'how do I show up in AI answers,' 'LLM mentions,' 'optimize for Claude/Gemini,' 'llms.txt,' 'llms-full.txt,' 'OKF,' 'Open Knowledge Format,' 'knowledge bundle,' 'agent-readable site,' 'agent readiness,' 'is my site agent-ready,' 'WebMCP,' 'do listicles still work for AI,' 'ChatGPT stopped citing comparison pages,' or 'AI citation format shift.' Use this whenever someone wants their content to be cited or surfaced by AI assistants and AI search engines. For traditional technical and on-page SEO audits, see seo-audit. For structured data implementation, see schema."
|
||||
metadata:
|
||||
version: 2.4.0
|
||||
version: 2.5.0
|
||||
---
|
||||
|
||||
# AI SEO
|
||||
@@ -105,6 +105,8 @@ Google's own example: a user asking "how to fix lawns" triggers fan-out queries
|
||||
|
||||
**Action**: when planning content, brainstorm the 5–10 related queries the AI is likely to fan out to and make sure your content (or your site as a whole) covers them.
|
||||
|
||||
ChatGPT fans out too — and you can extract its *literal* background queries for your niche via DevTools (method in [references/format-volatility.md](references/format-volatility.md)). Post-5.6, ChatGPT's fan-outs shifted away from "best/vs/top" modifiers toward `site:` and "official" searches — use the extraction to see where your category's fan-outs stand today.
|
||||
|
||||
---
|
||||
|
||||
## AI Visibility Audit
|
||||
@@ -253,6 +255,7 @@ AI systems don't just cite your website — they cite where you appear.
|
||||
- Wikipedia mentions (7.8% of all ChatGPT citations)
|
||||
- Reddit discussions (volatile: ~1.8% of ChatGPT citations historically, but nearly wiped from ChatGPT by Aug 2026 retrieval changes — still retrieved elsewhere; see the volatility section in [references/agent-readiness.md](references/agent-readiness.md))
|
||||
- Industry publications and guest posts
|
||||
- LinkedIn — per LinkedIn's own AEO guide, the most-cited outlet for professional-topic searches; Articles out-cite Posts ~60/40, and a post's first words become its URL slug, so front-load the target phrase (details in [references/format-volatility.md](references/format-volatility.md))
|
||||
- Review sites (G2, Capterra, TrustRadius for B2B SaaS)
|
||||
- YouTube (frequently cited by Google AI Overviews)
|
||||
- Podcasts (episodes get transcribed, show notes published — both get crawled and cited)
|
||||
@@ -366,24 +369,11 @@ For ecom and local business specifically, Google highlights:
|
||||
|
||||
## Content Types That Get Cited Most
|
||||
|
||||
Not all content is equally citable. Prioritize these formats:
|
||||
Not all content is equally citable — and the format mix is **volatile**. The long-standing baseline had comparison articles (~33%) and listicles (~10%) among the top citation earners, but **ChatGPT 5.6 (Aug 2026) demoted the exploited formats: listicle citations fell −50.5% and comparison-page citations −32.1%, while `site:` and "official" retrieval surged** — a shift toward primary sources and owned pages. Format strategy is now per-platform (comparisons still work on Google AIO/Gemini/Perplexity). See [references/format-volatility.md](references/format-volatility.md) for the shift data, the per-platform format table, LinkedIn's citation numbers, and the ChatGPT fan-out extraction diagnostic.
|
||||
|
||||
| Content Type | Citation Share | Why AI Cites It |
|
||||
|-------------|:------------:|----------------|
|
||||
| **Comparison articles** | ~33% | Structured, balanced, high-intent |
|
||||
| **Definitive guides** | ~15% | Comprehensive, authoritative |
|
||||
| **Original research/data** | ~12% | Unique, citable statistics |
|
||||
| **Best-of/listicles** | ~10% | Clear structure, entity-rich |
|
||||
| **Product pages** | ~10% | Specific details AI can extract |
|
||||
| **How-to guides** | ~8% | Step-by-step structure |
|
||||
| **Opinion/analysis** | ~10% | Expert perspective, quotable |
|
||||
**Evergreen winners across platforms:** original research and data, definitive guides, and owned "official" pages — product, docs, pricing — with extractable structure.
|
||||
|
||||
**Underperformers for AI citation:**
|
||||
- Generic blog posts without structure
|
||||
- Thin product pages with marketing fluff
|
||||
- Gated content (AI can't access it)
|
||||
- Content without dates or author attribution
|
||||
- PDF-only content (harder for AI to parse)
|
||||
**Underperformers:** generic unstructured posts, thin or gated or PDF-only content, and anything undated without author attribution.
|
||||
|
||||
**Citation ≠ recommendation.** Getting cited means your content was useful to consult; getting *recommended* — onto the buyer's actual shortlist — is governed by web-wide consensus (reviews, forums, analysts, press) and is largely independent of your own content. Self-promotional "best [category]" listicles can even backfire for emerging brands: in one 100-query B2B study, 69% of the AI Overview citations that self-promotional listicles earned came in answers that recommended competitors instead of the publishing brand. See [references/citations-vs-recommendations.md](references/citations-vs-recommendations.md) for the visibility ladder (retrieved → cited → mentioned → recommended), stage-dependent buyer's-guide strategy, what earns recommendations, and the attribution blind spot.
|
||||
|
||||
@@ -419,6 +409,8 @@ Monthly manual check:
|
||||
3. Record: Are you cited? Who is? What page?
|
||||
4. Log in a spreadsheet, track month-over-month
|
||||
|
||||
AI answers are **non-deterministic** — one run is an anecdote, not a measurement. Run each query 3–5 times per platform and track the mention *rate* with its sample size ("cited 3/5, n=5"), comparing rates over time rather than single runs. Full rigor checklist in [references/format-volatility.md](references/format-volatility.md).
|
||||
|
||||
### Search Console expectations
|
||||
|
||||
Google's guide is explicit: **there is no AI-specific Search Console reporting**. AI Overviews and AI Mode use core Search ranking, so the standard Search Console reports (Performance, Coverage, Core Web Vitals) are still what you measure with for Google. The third-party tools above are the only way to see cross-platform AI citation behavior.
|
||||
|
||||
@@ -125,6 +125,11 @@
|
||||
"Does not present citation-share statistics as stable facts; recommends verifying against the user's own citation monitoring"
|
||||
],
|
||||
"files": []
|
||||
},
|
||||
{
|
||||
"id": 10,
|
||||
"prompt": "We're a B2B SaaS planning our 2026 content roadmap. The plan is 40 comparison pages ('us vs competitor') and 20 'best tools' listicles, mainly to win ChatGPT citations. Also, how do I know if it's working — I checked ChatGPT once last week and we weren't mentioned.",
|
||||
"expected_output": "Should load references/format-volatility.md and push back on the rationale with the ChatGPT 5.6 shift (Aug 2026, Peec AI data): listicle citations fell ~50% and comparison-page citations ~32% post-5.6, with fan-out queries dropping 'best/vs/top/comparison' modifiers in favor of site: and 'official' searches — so 'win ChatGPT citations' no longer justifies scaled comparison/listicle production. Should NOT say comparison pages are dead: they still convert humans and still earn citations on Google AI Overviews, Gemini, and Perplexity — format strategy is per-platform. Should steer investment toward owned 'official' pages (product, docs, pricing, original research), which are rising as the citable class and dominate Gemini (~60% business sites). May suggest extracting ChatGPT's real fan-out queries via the DevTools method for coverage planning (while warning against mass-generating a page per query — scaled content abuse). On measurement: one ChatGPT check is an anecdote — AI answers are non-deterministic; run each query 3–5 times per platform, track mention rate with sample size (e.g. 'cited 3/5'), and compare rates over time. Numbers should be treated as dated snapshots to verify against own monitoring."
|
||||
}
|
||||
]
|
||||
}
|
||||
|
||||
@@ -0,0 +1,98 @@
|
||||
# Format Volatility — Which Content Formats AI Cites (and How Fast That Changes)
|
||||
|
||||
Citation-*source* volatility (Reddit wiped overnight, Gemini favoring owned sites) is covered in [agent-readiness.md](agent-readiness.md). This reference covers the second volatility axis: citation-*format* — which page types AI engines retrieve and cite, and the August 2026 evidence that heavily-exploited formats get demoted.
|
||||
|
||||
Read this before recommending comparison pages, listicles, or "best X" content for AI visibility. The advice changed materially with ChatGPT 5.6.
|
||||
|
||||
## The ChatGPT 5.6 format shift (August 2026)
|
||||
|
||||
Data from Peec AI (shared by Tomek Rudzki via Lily Ray, Aug 2026), comparing ChatGPT retrieval behavior before and after the 5.6 launch:
|
||||
|
||||
**Fan-out queries** — the modifiers that declined most as a share of ChatGPT's background searches:
|
||||
|
||||
- "vs"
|
||||
- "comparison"
|
||||
- "top"
|
||||
- "best"
|
||||
- "reviews"
|
||||
|
||||
At the same time: a surge in `site:` searches and modifiers like **"official"**.
|
||||
|
||||
**Citations by page type** — share of total ChatGPT citations:
|
||||
|
||||
| Page type | Pre-5.6 | Post-5.6 | Change |
|
||||
|---|---:|---:|---:|
|
||||
| Listicles ("Top 10 X," "8 best Y") | 15.77% | 7.80% | **−50.5%** |
|
||||
| Comparison pages ("X vs Y," alternatives) | 9.08% | 6.17% | **−32.1%** |
|
||||
|
||||
The interpretation (Lily Ray's, and it fits the fan-out data): these are exactly the two formats companies scaled for GEO over the prior 18 months, and ChatGPT adjusted retrieval to mitigate the spam. The `site:`/"official" surge points the same direction — **toward primary sources and owned domains, away from aggregator formats**.
|
||||
|
||||
## What this changes (and what it doesn't)
|
||||
|
||||
**It does NOT mean "stop making comparison pages."** Comparison and best-of content still:
|
||||
|
||||
- Converts human buyers (its original job)
|
||||
- Gets cited by Google AI Overviews (which follow core rankings, not ChatGPT's retrieval)
|
||||
- Feeds Gemini and Perplexity, which haven't shown the same demotion
|
||||
- Answers real mid-funnel queries on your own site
|
||||
|
||||
**It DOES mean:**
|
||||
|
||||
1. **Stop justifying scaled listicle/comparison production with "it wins AI citations."** On ChatGPT — the largest AI answer surface — that rationale lost half its force in one release.
|
||||
2. **The "official"/primary-source shift favors your owned pages.** Product pages, docs, pricing pages, original research — the pages only you can publish — are rising as the citable class. This compounds the Gemini finding (business-owned sites ≈ 60% of citations).
|
||||
3. **Format strategy is now per-platform.** Check which engines matter for your category before choosing formats:
|
||||
|
||||
| Format | ChatGPT (post-5.6) | Google AIO | Gemini | Perplexity |
|
||||
|---|---|---|---|---|
|
||||
| Listicles / best-of | Demoted | Rankings-dependent | OK | OK |
|
||||
| Comparison / vs pages | Demoted | Rankings-dependent | OK | OK |
|
||||
| Original research + data | Strong | Strong | Strong | Strong |
|
||||
| Product/docs/pricing (owned, "official") | **Rising** | Strong | **Dominant** | Strong |
|
||||
| How-to / guides | Steady | Strong | OK | Strong |
|
||||
|
||||
*(Table caveat: the demotion was measured on ChatGPT only. "OK" for Gemini/Perplexity means no demotion has been reported there — not that stability was measured. Any engine can ship its own 5.6-style shift.)*
|
||||
|
||||
4. **Treat every number above as a dated snapshot.** Same doctrine as source volatility: these are Aug 2026 measurements of a moving system. Verify against your own citation monitoring before betting budget.
|
||||
|
||||
## LinkedIn as a citation surface (from LinkedIn's own AEO guide)
|
||||
|
||||
LinkedIn quietly published its own AEO/AI-search guidance (surfaced by Chris Long, Sep 2026). The platform-reported numbers:
|
||||
|
||||
- LinkedIn is the **most-cited outlet for professional-topic searches**
|
||||
- **~60% of LinkedIn citations come from Articles**, ~40% from Posts
|
||||
- Post URLs use the **first words of the post as the slug**
|
||||
|
||||
**Tactics:**
|
||||
|
||||
- For professional/B2B topics, LinkedIn Articles are a first-class Presence-pillar surface — treat long-form Articles (not just feed posts) as citable assets with the same extractable structure as blog content.
|
||||
- **Front-load the target phrase in a post's opening words** — they become the URL slug, which is retrieval surface.
|
||||
- This is platform-reported data (LinkedIn grading its own homework); weight accordingly, but the Articles > Posts split matches the general pattern that long-form structured content out-cites feed content.
|
||||
|
||||
## DIY diagnostic: extract ChatGPT's real fan-out queries
|
||||
|
||||
You don't need a tool to see what ChatGPT actually searches for in your niche (method circulating publicly, Aug 2026):
|
||||
|
||||
1. Run an important query for your category in ChatGPT (with search).
|
||||
2. Open DevTools → Network tab, refresh the conversation (URL id after `/c/`).
|
||||
3. Find the conversation response payload and search it for `queries`.
|
||||
4. You'll see the literal background searches ChatGPT fanned out to.
|
||||
|
||||
**Use it for:** building your query-test list from *real* fan-out behavior instead of guesses; checking whether your category's fan-outs still use "best/vs" modifiers or have shifted to `site:`/"official" patterns; finding sub-topics your content doesn't cover.
|
||||
|
||||
**Do not use it for:** auto-generating and mass-publishing an article per fan-out query. That's the exact scaled-content pattern 5.6 demoted (and Google's scaled content abuse policy names). The diagnostic is for coverage planning, not content spam.
|
||||
|
||||
## Measurement rigor: AI answers are non-deterministic
|
||||
|
||||
A single ChatGPT answer is an anecdote, not a measurement — the same prompt returns different sources run-to-run. (The statistical-rigor framing here is popularized by Initial Commit's AEO audit skill, Josh Pigford, Aug 2026; the practice stands on its own.)
|
||||
|
||||
When auditing or monitoring:
|
||||
|
||||
- **Run each query 3–5 times per platform**, fresh session each time.
|
||||
- **Track mention/citation *rate*** ("cited in 3 of 5 runs"), never a yes/no from one run.
|
||||
- **Report the sample size** with every number ("40% mention rate, n=5") so future-you knows how much to trust it.
|
||||
- **Compare rates over time, not runs.** A drop from 4/5 to 3/5 is noise; a drop from 4/5 to 0/5 sustained across a month is signal.
|
||||
- Before diagnosing *why* you're not cited, split causes the way an audit should: **technical** (can't be crawled/parsed — see agent-readiness.md), **comprehension** (AI describes you inaccurately or vaguely), or **trust** (understood but not selected — see citations-vs-recommendations.md).
|
||||
|
||||
---
|
||||
|
||||
*Sources, all labeled and dated: Peec AI pre/post-5.6 citation data via Tomek Rudzki and Lily Ray (Aug 2026); LinkedIn's AEO guide numbers via Chris Long (Sep 2026, platform-reported); fan-out extraction method as publicly circulated (Aug 2026); measurement-rigor framing credited to Initial Commit's AEO audit skill (Josh Pigford, Aug 2026). All snapshots of a volatile system — verify against your own monitoring.*
|
||||
@@ -0,0 +1,131 @@
|
||||
---
|
||||
name: events
|
||||
description: "When the user wants to plan, run, sponsor, speak at, or get pipeline from events — webinars, conferences, trade shows, meetups, dinners, workshops, virtual summits, or user conferences. Also use when the user mentions 'event marketing,' 'field marketing,' 'run a webinar,' 'webinar funnel,' 'show-up rate,' 'should we sponsor,' 'sponsor a conference,' 'trade show booth,' 'booth strategy,' 'event ROI,' 'badge scans,' 'event follow-up,' 'speaking slot,' 'CFP,' 'conference talk,' 'host a dinner,' 'user conference,' or 'virtual summit.' Covers all four roles: hosting, sponsoring/exhibiting, speaking, and attending. For product launch moments, see launch. For the partnership side of joint webinars, see co-marketing. For ongoing community programs, see community-marketing. For podcast appearances, see public-relations. For the email sequences themselves, see emails."
|
||||
metadata:
|
||||
version: 1.0.0
|
||||
---
|
||||
|
||||
# Event Marketing
|
||||
|
||||
You are an expert in event-driven marketing — using webinars, conferences, dinners, and talks to create pipeline, authority, and compounding content. Your job is to make events produce measurable business outcomes, not just attendance.
|
||||
|
||||
## Before Starting
|
||||
|
||||
**Check for product marketing context first:**
|
||||
If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` 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.
|
||||
|
||||
Then establish, in one batch:
|
||||
|
||||
1. **Which role?** Hosting your own event, sponsoring/exhibiting at someone else's, speaking, or attending?
|
||||
2. **What outcome?** Pipeline/meetings, authority/brand, community, or content production? (Pick a primary — events that try to do everything measure nothing.)
|
||||
3. **Who must be in the room?** The ICP segment, and roughly how many of them exist at this event.
|
||||
4. **Budget and team** — money, and who can actually work the event.
|
||||
|
||||
## Pick Your Role
|
||||
|
||||
| You are… | Core motion | Depth |
|
||||
|---|---|---|
|
||||
| **Hosting** | Own the audience end to end — webinar, workshop, dinner, meetup, summit, user conference | This file + [webinar-funnel.md](references/webinar-funnel.md) for the flagship format |
|
||||
| **Sponsoring / exhibiting** | Buy access to someone else's audience — evaluate, negotiate, work the floor, follow up | [sponsorship-roi.md](references/sponsorship-roi.md) |
|
||||
| **Speaking** | Trade expertise for stage time — get booked, design the talk, compound the recording | [speaking.md](references/speaking.md) |
|
||||
| **Attending** | No booth, no stage — engineer meetings anyway | Section below |
|
||||
|
||||
Mixed roles are normal (sponsor + speak, attend + host a dinner). Plan each role's motion separately; they share the follow-up system.
|
||||
|
||||
## Which Events to Invest In (Portfolio First)
|
||||
|
||||
Before roles and tactics: events are the most expensive, riskiest, hardest-to-measure channel — the leverage is in **selection**, not execution. Never write off "events" from one bad conference; each event is its own ecosystem (judging all events on one conference is like judging all paid media on a single Google Ads test). Full framework, the three event types, and cost benchmarks in [event-portfolio-strategy.md](references/event-portfolio-strategy.md).
|
||||
|
||||
- **Is in-person even necessary?** It earns its cost mainly for high-trust, high-ACV motions: enterprise/multi-stakeholder deals, regulated buyers (health/finance/gov), heavy customization, conservative industries, and 6+ month cycles. If your ICP isn't there, spend on digital first.
|
||||
- **The 80/20 of selection.** A handful of events generate most event pipeline. Find them, double down (speaking slots, side events, more people, better placement), and cut the tail.
|
||||
- **Bigger isn't better.** Mega-conferences mean more noise, higher cost, and audience dilution (students, press, vendors, tourists). Niche/regional events (50–200 attendees) often deliver more qualified leads per dollar.
|
||||
- **Three types, three risk profiles:** **Owned** (max control/max risk — roadshows, summits, user conferences), **Trade shows** (someone else's arena — 120 days of prep beats the 4 days on the floor), **Community** (compound interest — small regular gatherings that spawn more, measured by the "Saturday Test").
|
||||
|
||||
## The Universal Arc: 20% Event, 80% Before-and-After
|
||||
|
||||
The event itself is the smallest part of event marketing. Every format follows the same arc, and most failures are arc failures, not event failures:
|
||||
|
||||
**Before (where pipeline is actually made)**
|
||||
- Build the target list: who's attending that matches your ICP? (Attendee lists, speaker lists, "who's going" posts, past-year attendees.)
|
||||
- **Book meetings before you arrive.** A meeting booked two weeks out is worth ten hopeful hallway collisions. Outreach angle: specific, low-friction, time-boxed ("15 min at the coffee bar Tuesday").
|
||||
- Announce your presence where your audience already is (email list, social, communities) with a reason to find you — not "we'll be at booth 402" but what they get.
|
||||
|
||||
**During**
|
||||
- Optimize for *qualified conversations*, not raw contacts. One real conversation with an ICP buyer beats fifty badge scans.
|
||||
- Capture context, not just contact: after each conversation, record what they said, what they care about, and the agreed next step. The follow-up writes itself from this; without it, follow-up is generic and dies.
|
||||
- Create content while there (see Content Arc below) — the event is a recording studio you already paid for.
|
||||
|
||||
**After (where pipeline is won or lost)**
|
||||
- **The 24–48 hour window.** Follow up while the conversation is still warm, referencing what was actually discussed. Every day of delay roughly halves response rates (directional, not a law — but the decay is real and fast).
|
||||
- Tier the follow-up: hot conversations get a personal note + concrete next step; warm get a relevant asset tied to their stated problem; scans-with-no-conversation get one light touch or nothing — don't burn your domain on people who don't remember you.
|
||||
- Route to systems: CRM with event source tagging (→ **revops**), nurture for the not-nows (→ **emails**).
|
||||
|
||||
## Hosting: Choose the Format for the Job
|
||||
|
||||
| Format | Best for | Effort | Notes |
|
||||
|---|---|---|---|
|
||||
| **Webinar** | Lead gen + education at scale | Low-mid | The flagship repeatable format — full funnel in [webinar-funnel.md](references/webinar-funnel.md) |
|
||||
| **Workshop** | Product-qualified leads, activation | Mid | Hands-on beats presentation for conversion; smaller and deeper than a webinar |
|
||||
| **Dinner / small gathering** | Exec relationships, ABM accounts | Mid | 8–14 seats, no pitch, curated guest mix — the highest meetings-per-dollar format in B2B |
|
||||
| **Meetup series** | Local community, recurring presence | Mid | Consistency beats production value; hand hosting duties to community members over time (→ **community-marketing**) |
|
||||
| **Virtual summit** | List building via partner audiences | High | Multi-speaker = built-in distribution; every speaker promotes (→ **co-marketing** for the partner mechanics) |
|
||||
| **User conference** | Retention, expansion, category authority | Very high | Don't attempt before you have a community that would attend without being begged |
|
||||
|
||||
Two hosting rules that outrank format choice:
|
||||
|
||||
- **The topic is the targeting.** "State of [category] 2026" attracts your ICP; "All about [your product]" attracts existing customers only. Pick topics your buyer would attend even if they'd never buy.
|
||||
- **Recurring beats one-off.** A monthly webinar or quarterly dinner compounds — audiences, promotion muscle, and content libraries build. A single big event evaporates.
|
||||
|
||||
## Attending (No Booth, No Stage)
|
||||
|
||||
The zero-budget motion, and often the best ROI in the building:
|
||||
|
||||
1. **Target list first** — 15–30 named people you want to meet, built from the attendee/speaker list and social chatter.
|
||||
2. **Pre-book** — outreach 1–3 weeks ahead; the ask is 15 minutes, anchored to a specific time and place.
|
||||
3. **The side-event play** — host a dinner or breakfast adjacent to the conference for 8–12 target accounts. You get host status without sponsor pricing; often out-generates a booth at a tenth of the cost (see [sponsorship-roi.md](references/sponsorship-roi.md)).
|
||||
4. **Work sessions strategically** — go where your targets are speaking, ask a real question, follow up on it.
|
||||
5. Same 24–48h follow-up discipline as every other role.
|
||||
|
||||
## The Content Arc: Every Event Is a Content Engine
|
||||
|
||||
Events produce your highest-proof content — capture it deliberately:
|
||||
|
||||
- **Record everything you're allowed to record.** Talks, webinars, panels. The recording is the durable asset; the live audience is just its first viewer.
|
||||
- **Transcripts compound in AI answers.** Published recordings and show notes get crawled and cited by AI assistants — the same logic as podcast guesting (→ **public-relations** podcast prep) and the YouTube text layer (→ **ai-seo**). Say the quotable lines cleanly: your company name next to your category, numbers out loud.
|
||||
- Slice the recording: clips (→ **video**), a recap post per session (→ **content-strategy**), pull-quotes for social (→ **social**), proof points for sales (→ **sales-enablement**).
|
||||
- Photograph/collect social proof: testimonials captured at the event are the most natural you'll ever get.
|
||||
|
||||
## Measurement: Pipeline, Not Applause
|
||||
|
||||
| Metric tier | Examples | Verdict |
|
||||
|---|---|---|
|
||||
| **Vanity** | Registrations, badge scans, foot traffic, impressions | Track, never optimize for, never report as success |
|
||||
| **Real** | Qualified conversations, meetings booked, opportunities created, pipeline influenced | The actual scoreboard |
|
||||
| **Decisive** | Cost per qualified meeting, cost per opportunity, closed-won influenced | What decides whether you do it again |
|
||||
|
||||
- Compare cost-per-qualified-meeting against your other channels (ads, outbound) — that's the go/no-go math, worked through in [sponsorship-roi.md](references/sponsorship-roi.md).
|
||||
- Events are multi-touch by nature: use source tagging + self-reported attribution ("heard us at X") and influence windows, and never claim last-click credit for a deal the event merely touched (→ **attribution**).
|
||||
- Judge a recurring event program on a 2–3 event trend, not one instance — the first run of anything underperforms its steady state.
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- **Sponsoring for "brand awareness" with no conversation target.** If nobody owns a meetings number, the booth is décor.
|
||||
- **The follow-up gap.** Leads captured, then first touch two weeks later from a generic sequence. The event was fine; the follow-up killed it.
|
||||
- **Optimizing show-up rate after picking a topic nobody wants.** Reminder cadence can't save weak demand — fix topic and promise first.
|
||||
- **One-off thinking.** Budget for the third instance before running the first.
|
||||
- **Doing the event, skipping the recording.** Full production effort, zero durable assets.
|
||||
- **Counting badge scans as leads.** A scan is a person who walked slowly. Qualify before it enters the pipeline.
|
||||
- **Writing off "events" after one bad conference.** Each event is its own ecosystem — judge them individually, not as a single channel.
|
||||
- **Chasing the biggest conferences.** Size correlates with noise and audience dilution, not ROI — niche and regional events often win on cost-per-qualified-meeting.
|
||||
|
||||
## Related Skills
|
||||
|
||||
- **launch** — the event is a launch moment (announcement, Product Hunt, go-live)
|
||||
- **co-marketing** — joint webinars and partner summits: partnership mechanics live there, event execution here
|
||||
- **community-marketing** — ongoing community programs; events can seed or serve one
|
||||
- **public-relations** — podcast guesting and press at events
|
||||
- **lead-magnets** — gated replays and event content as magnets
|
||||
- **emails** / **sms** — the reminder and follow-up sequences themselves
|
||||
- **cold-email** — pre-event meeting-booking outreach
|
||||
- **revops** — routing, scoring, and source-tagging event leads
|
||||
- **attribution** — measuring multi-touch event influence honestly
|
||||
@@ -0,0 +1,92 @@
|
||||
{
|
||||
"skill_name": "events",
|
||||
"evals": [
|
||||
{
|
||||
"id": 1,
|
||||
"prompt": "We're a B2B SaaS with a $30k opportunity to sponsor our industry's biggest annual conference (5,000 attendees). Marketing wants to do it for brand awareness. Should we?",
|
||||
"expected_output": "Should load references/sponsorship-roi.md and run the evaluation before answering. Pushes back on 'brand awareness' as the goal without a conversation/meetings target and an owner. Asks for or estimates audience-ICP overlap in absolute numbers (how many of the 5,000 are actual buyers), works the meetings math backwards to cost per qualified meeting (sponsorship + travel + staff), and compares against what a meeting costs from their other channels (the counterfactual check). Should surface the side-event alternative (curated dinner adjacent to the conference at a fraction of the cost) and the negotiation levers if they do sponsor (speaking slot over bigger booth, side-event rights, realistic attendee-data terms). Verdict framed as conditional on the overlap math, not a yes/no from vibes.",
|
||||
"assertions": [
|
||||
"Does not accept 'brand awareness' as sufficient justification; requires a qualified-conversations or meetings target with an owner",
|
||||
"Computes or requests the inputs for cost per qualified meeting and compares against alternative channels",
|
||||
"Asks about audience-ICP overlap in absolute numbers rather than accepting total attendance",
|
||||
"Mentions the side-event (curated dinner/breakfast) play as an alternative or complement",
|
||||
"If sponsoring, recommends negotiating for a speaking slot and/or side-event rights over booth size"
|
||||
],
|
||||
"files": []
|
||||
},
|
||||
{
|
||||
"id": 2,
|
||||
"prompt": "Plan our first webinar. We sell an expense-management tool for startup CFOs and want it to generate demo requests.",
|
||||
"expected_output": "Should load references/webinar-funnel.md and work the four stages in order, starting with topic & offer: a problem-aware topic for startup CFOs (not a product demo), title as the ad, and the demo request decided as the single offer before content is written. Registration: landing page structure with outcome bullets, short form, replay registration. Show-up system: calendar add at registration, reminder cadence ending with a T-5-minute join link, close the registration-to-event gap, pre-engagement question. Live structure: the open that names the pitch upfront, 3 teachable points with proof, the scripted one-minute transition where the product enters as the implementation of the content, one offer, seeded Q&A. Post: behavior-segmented follow-up (engaged / left early / no-show / replay), replay strategy choice, recycling the recording into content. Metrics: reg -> show -> hold -> convert funnel with the diagnostic mapping (which stage failing means which fix), benchmarks presented as directional.",
|
||||
"assertions": [
|
||||
"Starts with topic and offer selection (problem-aware topic, one offer decided upfront), not logistics",
|
||||
"Includes a show-up system: calendar add, escalating reminders including a T-5-minute join link, and gap management",
|
||||
"Structures the live arc with an upfront-named pitch, scripted transition, and single offer",
|
||||
"Segments post-webinar follow-up by behavior including a no-show replay sequence",
|
||||
"Presents benchmark numbers as directional ranges, not targets"
|
||||
],
|
||||
"files": []
|
||||
},
|
||||
{
|
||||
"id": 3,
|
||||
"prompt": "I got accepted to speak at SaaStr next quarter — 25-minute slot. Help me make the most of it.",
|
||||
"expected_output": "Should load references/speaking.md and cover all three jobs. Talk design: outline first (one named audience member, a Monday takeaway they can act on, blocks each with point + proof), then storyboard the emotional beats (5-8 beats for the length, each with energy/feel/hit; the journey must earn the takeaway; one contrarian take stands out on consensus stages). Recording as the real audience: confirm recording rights before/when accepting, speak the key numbers and company-next-to-category aloud rather than leaving them on slides, put the quotable line on a peak beat (transcripts get cited by AI assistants). Around the talk: pre-event promotion and speaker-to-speaker networking, a single low-friction closing pointer/asset, publishing the recording + written version after, following up with question-askers within 24-48h, and rolling the talk forward across the season.",
|
||||
"assertions": [
|
||||
"Separates outline (audience, Monday takeaway, blocks with proof) from emotional storyboarding (beats with energy/feel/hit)",
|
||||
"Treats the recording as the durable asset: confirm rights, speak key numbers and positioning aloud, quotable line on a peak beat",
|
||||
"Connects the transcript to AI-citation compounding",
|
||||
"Includes post-talk motions: publish recording and written version, follow up with question-askers in the 24-48h window",
|
||||
"Recommends speaker-to-speaker networking and a single clear closing pointer"
|
||||
],
|
||||
"files": []
|
||||
},
|
||||
{
|
||||
"id": 4,
|
||||
"prompt": "A partner wants to do a joint webinar with us — they'd bring their list, we'd bring ours. How do we structure the partnership and who gets the leads?",
|
||||
"expected_output": "Should recognize the boundary: partnership mechanics (partner selection, value exchange, list/lead sharing terms, co-promotion commitments) belong to the co-marketing skill, while the webinar execution (funnel, show-up system, live structure, follow-up) belongs here. Should hand the partnership-structure question to co-marketing rather than improvising deal terms, note the consent requirement for sharing registrant data between parties (registrants must explicitly opt in to both), and offer the events-side execution: co-hosted format, both speakers promote with pre-written assets, and each party follows up with its own consented segment.",
|
||||
"assertions": [
|
||||
"Routes partnership structure and lead-sharing terms to co-marketing rather than answering them as event logistics",
|
||||
"Flags explicit registrant consent as required for sharing registration data between both parties",
|
||||
"Retains and offers the webinar-execution layer (funnel, promotion by both speakers, follow-up) from this skill",
|
||||
"Does not invent specific legal or contractual terms"
|
||||
],
|
||||
"files": []
|
||||
},
|
||||
{
|
||||
"id": 5,
|
||||
"prompt": "We just got back from a trade show with 412 badge scans. Marketing is calling it a huge success and wants to load them all into our sales cadence tomorrow. Thoughts?",
|
||||
"expected_output": "Should push back on both claims using the measurement tiers and follow-up discipline. Badge scans are vanity-tier activity, not leads or success — success is qualified conversations, meetings, and pipeline. Dumping all 412 scans into a sales cadence burns domain reputation and brand on people who do not remember the interaction; instead, tier the list: hot (real conversation + agreed next step) gets personal same/next-day follow-up referencing the conversation, warm (conversation, no commitment) gets a personal note plus a relevant asset, scan-only gets one light touch or nothing. The 24-48 hour window applies to the hot/warm tiers, follow-up should be written or reviewed by whoever had the conversations, and the event should be judged on cost per qualified meeting and pipeline influenced, with source tagging and an influence window - not scan count.",
|
||||
"assertions": [
|
||||
"Rejects badge-scan count as a success metric, distinguishing vanity from real and decisive metrics",
|
||||
"Advises against loading all scans into a sales cadence, citing domain/brand risk and no-context outreach",
|
||||
"Provides the tiered follow-up model (hot/warm/scan-only) with the 24-48h window for the top tiers",
|
||||
"Recommends measuring the show on cost per qualified meeting and pipeline influenced with source tagging"
|
||||
],
|
||||
"files": []
|
||||
},
|
||||
{
|
||||
"id": 6,
|
||||
"prompt": "We want to announce our new product at our own launch event. Walk me through everything.",
|
||||
"expected_output": "Should recognize the launch/events boundary: the announcement strategy itself (positioning the release, launch channels, Product Hunt, press timing, go-live QA) belongs to the launch skill, while the event as a vehicle (format choice, invite/registration mechanics, show-up system, recording and content capture, post-event follow-up) belongs here. Should offer the events-side plan and explicitly point the announcement/GTM layer to launch rather than duplicating it, and may note the content-arc opportunity (the launch event recording becomes demo assets, clips, and citable content) and press angle (public-relations).",
|
||||
"assertions": [
|
||||
"Identifies that announcement/launch strategy routes to the launch skill while event execution stays here",
|
||||
"Provides event-side substance: format, registration/show-up mechanics, recording capture, follow-up",
|
||||
"Does not duplicate launch-channel strategy (Product Hunt, press embargo timing) inside the event plan",
|
||||
"Mentions capturing the recording for downstream content"
|
||||
],
|
||||
"files": []
|
||||
},
|
||||
{
|
||||
"id": 7,
|
||||
"prompt": "We're a B2B SaaS with $80k ACV enterprise deals. Should we even do events, and if so which ones? There's a huge 10,000-person industry conference coming up and everyone says we have to be there.",
|
||||
"expected_output": "Should load references/event-portfolio-strategy.md and reason at the portfolio level before tactics. Should confirm in-person is warranted here (enterprise, high-ACV, multi-stakeholder trust-building is exactly where events earn their cost). Should apply the 80/20 of event selection (a few events drive most pipeline — find and concentrate on those). Should push back on the assumption that the 10,000-person conference is a must: bigger is often inverse to ROI because of noise and audience dilution (students, press, vendors, tourists), so effective cost-per-qualified-lead balloons; niche/regional events (50-200) or a curated side event (private dinner, coffee meetups) may out-produce a big booth at a fraction of the cost. Should frame the three event types (owned/trade-show/community) and tie the decision to economics — a significant show needs ~5-10 solid opportunities to justify a team — comparing cost-per-qualified-meeting against other channels (sponsorship-roi.md).",
|
||||
"assertions": [
|
||||
"Confirms in-person events fit this ICP (enterprise, high-ACV, multi-stakeholder / complex deals)",
|
||||
"Applies the 80/20 event-selection principle — concentrate on the few highest-yield events rather than attending broadly",
|
||||
"Challenges the 'must attend the 10,000-person conference' assumption: bigger correlates with noise and audience dilution, not ROI; suggests niche/regional or a curated side event",
|
||||
"Grounds the decision in economics (needs ~5-10 solid opportunities to justify a team, or cost-per-qualified-meeting vs other channels)"
|
||||
],
|
||||
"files": []
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -0,0 +1,80 @@
|
||||
# Event Portfolio Strategy — Which Events, Why, and the Economics
|
||||
|
||||
The layer that sits *above* role and tactics. Events are the most expensive, riskiest, hardest-to-measure channel you can run — so the leverage is in **selection and portfolio design**, not execution. The single most common failure is treating "events" as one channel: attend two bad conferences, get few leads, and write the whole channel off — the same mistake as running Google Ads once, seeing poor results, and concluding all paid media is broken. **Each event is its own ecosystem.** Judge them individually.
|
||||
|
||||
## Is in-person even necessary? (segment fit first)
|
||||
|
||||
Digital scales efficiently; in-person builds trust that digital can't. In-person earns its cost mainly for high-trust, high-consideration motions. Prioritize events when your ICP looks like:
|
||||
|
||||
- **Enterprise / multi-stakeholder** — high ACV, several people must build trust before a big commitment
|
||||
- **Regulated buyers** — healthcare, finance, government have strict vendor-evaluation norms
|
||||
- **High-touch / heavy customization** — significant integration or configuration work
|
||||
- **Conservative industries** — manufacturing, utilities still run on traditional relationship-building
|
||||
- **Long cycles** — 6+ month sales cycles get disproportionate acceleration from face time
|
||||
|
||||
Reality check: a cybersecurity company found $500k+ ACV deals almost never closed without at least one in-person meeting — the trust to switch security vendors couldn't be built over Zoom. If your ICP is *not* in these buckets, spend on digital first and treat events as a small experiment.
|
||||
|
||||
## The 80/20 of event selection
|
||||
|
||||
A small number of events generate the majority of event-attributed pipeline (one B2B SaaS program found **3 conferences drove ~70%** of it). The job is to find those and concentrate:
|
||||
|
||||
- Increase presence at the winners — secure **speaking slots**, host **larger side events**, send **more of the right people**, buy **better placement**
|
||||
- Cut or minimize the long tail of low-yield events
|
||||
- Re-rank yearly; the 20% shifts as your ICP and market move
|
||||
|
||||
## Bigger isn't better (size ↔ ROI is often inverse)
|
||||
|
||||
Major conferences look can't-miss and frequently deliver the *worst* returns:
|
||||
|
||||
- **Big events = more noise** — higher cost on everything (booth, hotels, travel), more competing vendors, attendees spread thin across tracks, endless competing side events
|
||||
- **Audience dilution** — you're paying to reach a crowd padded with students, investors, press, other vendors, consultants, and industry tourists; your ICP is a thin slice, so effective cost-per-qualified-lead balloons
|
||||
- **Small-event advantage** — a 50-person niche meetup can out-produce a 5,000-person conference; highest ROI is often **regional events of 100–200** where you can reach every qualified prospect in the room
|
||||
|
||||
## The three event types (three risk profiles)
|
||||
|
||||
### 1. Owned events — maximum control, maximum risk
|
||||
You control everything from content to coffee breaks, and you carry all the risk. Range: exec dinners → roadshows → summits → user conferences.
|
||||
- **User conferences** turn customers into a community and a product into a movement (Dreamforce). Don't attempt before you have an audience that would come unbegged.
|
||||
- **Regional roadshows** take the message to scattered markets — one company generated more pipeline from a **6-city roadshow than its annual conference, at a third of the cost**.
|
||||
- **Industry summits** build thought leadership by tackling category problems, not product pitches — they pull in partners and influencers who amplify.
|
||||
- **Workshops / certifications** tie the event directly to customer success and can pay for themselves via fees.
|
||||
- **Three success factors:** ruthless **audience focus** (a clear "who," even at the expense of broader appeal), a **value proposition** attendees can't get elsewhere, and **strategic timing** (align to buyer budget/bandwidth — one company moved its conference Q4→Q1 and lifted attendance 40%).
|
||||
- **Model case — Drift HYPERGROWTH:** killed badges and sponsor booths, chose storytelling over product pitches, felt like TED not a software show → 3x pipeline acceleration for attendees, starting at 1,000 people year one.
|
||||
|
||||
### 2. Trade shows & conferences — someone else's arena
|
||||
Less control, less risk — you rent instant access to an audience but work inside their format. **Success is 120 days of prep, not the 4 days on the floor.**
|
||||
- **Pre-show (starts ~120 days out):** mine the attendee list for *stories*, not just names (recent funding, press, job posts) → hooks far better than "want a demo?"; **book ~70% of meeting slots before anyone flies out** ("saw you opened a Singapore office — we helped 3 companies with APAC expansion last quarter, coffee at the show?")
|
||||
- **On the floor:** turn the booth into a **story-collection hub** — senior staff at the edges (not behind a counter), no physical barriers, customer success stories on screens, and bring real customers to tell their story. (One security company ran a live "Security Operations Center" that sparked real technical sales conversations.)
|
||||
- **The hidden game — satellite events:** morning coffee meetups and curated private dinners routinely out-generate the booth
|
||||
- **Post-show (where most teams fail):** tier leads and reference *specific conversation details* — hot → same-day, warm → personalized within 48h, general → nurture within a week; turn booth conversations into content (video testimonials, FAQ → blog/email)
|
||||
|
||||
### 3. Community events — the compound interest of event marketing
|
||||
Small, regular investments that grow exponentially — often started on a tiny budget (monthly meetups for ~$500 of pizza and beer).
|
||||
- **Regular rhythm beats flash** — same format, same venue, every month builds momentum; chasing a bigger/flashier event each time burns teams out
|
||||
- **Never pitch — facilitate.** A "Tech Leaders Dinner" grew 8 → 40+ CTOs because it solved their real problems; the product came up naturally
|
||||
- **Turn customers into advocates** — support customer-run user groups but let them stay independent; they become a reference network prospects trust *because* they're not on your payroll
|
||||
- **The multiplier effect** — arm your most engaged attendees with playbooks, speaker connections, and seed funding to launch their own city events (one meetup spawned 12 across 3 countries)
|
||||
- **Metrics that fit** — monthly active members, conversation depth, community-initiated events, relationship velocity, member→customer conversion. The gut check is the **"Saturday Test": would people show up on a Saturday morning?** If yes, you built something real.
|
||||
- **Payoff** — prospects who attended **3+ community events showed an 85% higher close rate and 40% shorter cycle**; they understood the value in context before ever buying
|
||||
|
||||
## Economics — real cost benchmarks
|
||||
|
||||
Budget the full investment (money *and* time/opportunity cost) against pipeline, not just the sticker price.
|
||||
|
||||
| Line item | Typical range |
|
||||
|---|---|
|
||||
| Conference ticket | $1,500–3,000 / person (major shows) |
|
||||
| Booth space (10×10, top-tier) | $15,000–40,000 |
|
||||
| Flights | $300–1,000 / person |
|
||||
| Hotel | $300–400 / night / person |
|
||||
| Booth staff | 3–4 people minimum at any significant show |
|
||||
| Private dinner (15–20 ppl) | $150–200 / person |
|
||||
| Breakfast meetup | $30–50 / person |
|
||||
| Happy hour | $50 / person |
|
||||
| Private meeting room | $500–1,500 / day |
|
||||
|
||||
**Rule of thumb:** a significant show needs to generate **~5–10 solid opportunities** to justify sending a team. For the sponsor-specific go/no-go math and cost-per-qualified-meeting comparison against other channels, see [sponsorship-roi.md](sponsorship-roi.md).
|
||||
|
||||
---
|
||||
|
||||
*Distilled from Corey Haines's* Founding Marketing *(chapter: "Events create memorable experiences with potential customers"). Benchmarks are directional and pre-inflation-adjust as needed; re-verify current show pricing.*
|
||||
@@ -0,0 +1,49 @@
|
||||
# Speaking — Get Booked, Design the Talk, Compound the Recording
|
||||
|
||||
Speaking is the highest-leverage event role per dollar: stage time confers borrowed authority no booth can buy, and the recording compounds for years — including in AI answers. Treat it as three separate jobs: getting booked, designing a talk that lands, and harvesting the asset.
|
||||
|
||||
## Getting Booked (CFPs and pitches)
|
||||
|
||||
Organizers optimize for their audience's experience, not your reach. Pitch accordingly:
|
||||
|
||||
- **Pitch the audience takeaway, not your company.** A CFP that reads like a case study of the *attendee's* problem gets accepted; a product story gets filtered. Your product can appear as evidence inside the talk, never as its subject.
|
||||
- **Title formula**: specific outcome + specific audience + a tension or number. "How we cut CAC 40% by killing our best channel" beats "Rethinking Growth."
|
||||
- **The abstract carries three things**: the problem as the audience feels it, the specific things they'll walk away knowing (2–3, concrete), and why *you* — the proof you've actually done it (numbers, scars). Keep it under 150 words; organizers skim hundreds.
|
||||
- **Track and ladder**: local meetups → niche conference tracks → main stages. Recordings of small talks are your CFP portfolio for bigger ones. Podcast appearances feed the same ladder (→ **public-relations** podcast prep — same evidence discipline, same context file).
|
||||
- Off-cycle path: many events fill panels and replacement slots late — a short note to organizers with a tight topic + proof of speaking ability lands surprisingly often.
|
||||
|
||||
## Designing the Talk: Outline First, Then Feelings
|
||||
|
||||
A talk is a journey you take the room on, not a document you read at them. Two passes:
|
||||
|
||||
**Pass 1 — the outline.** Before slides, lock four things (write them down; mush here becomes mush on stage):
|
||||
|
||||
1. **Who this is for** — one person, their situation, what they already believe walking in
|
||||
2. **The Monday takeaway** — what they can *do or decide* on a specific next day; a talk without one is content, not a talk
|
||||
3. **What you get** — your win (pipeline, credibility, hiring) so the close can carry it without a swerve
|
||||
4. **The blocks** — each with a point and a proof (a story or a number). No proof, no block.
|
||||
|
||||
**Pass 2 — storyboard the feeling.** Map how the room should *feel* beat by beat — a beat is a change in energy or emotion, not a slide heading. A 20-minute talk is usually 5–8 beats. For each beat, name:
|
||||
|
||||
- **Energy** — the room, in directable words: quiet lean-in, rising unease, laugh-release, peak, still
|
||||
- **Feel** — the emotion in the audience's own mouth: "that's me," "wait, we're the problem," "I can try this Monday"
|
||||
- **The hit** — the one thing this beat must land, in one sentence
|
||||
|
||||
Then check the journey: does the sequence of feelings *earn* the Monday takeaway, or is the takeaway merely stated at the end? If a load-bearing block produces no feeling change, cut or merge it — two blocks that feel the same are one beat. If the close needs a feeling that never appeared, the outline isn't done. One well-placed contrarian take stands out most on stages that have converged on a consensus.
|
||||
|
||||
*(This outline → emotional-storyboard method is distilled from Knowatoa's `talk-storyboard` and `presentation-outline` skills — [ai-visibility-skills](https://github.com/Knowatoa/ai-visibility-skills), MIT, credited.)*
|
||||
|
||||
## The Recording Is the Real Audience
|
||||
|
||||
The room holds 200 people for 25 minutes; the recording works for years. Design for both at once:
|
||||
|
||||
- **Talks get transcribed, and transcripts get crawled and cited by AI assistants** — the same compounding as podcast guesting. Say the important things in liftable form: your company name next to your category ("we build X, the Y for Z"), numbers spoken aloud rather than gestured at on a slide, and your quotable one-liner delivered *on a beat the room will feel* — the sentence you want quoted needs to sit where the energy peaks, or it dies in the transcript too (→ **ai-seo**'s text-layer logic).
|
||||
- **Slides are not the asset.** Anything that exists only visually (the key number, the framework name) doesn't exist for the transcript, the podcast version, or the attendee retelling it — speak it.
|
||||
- **Get the recording.** Confirm before accepting the slot that you'll receive it and may republish. If the event doesn't record, record your own re-delivery of the talk within a week while it's tight.
|
||||
|
||||
## Around the Talk
|
||||
|
||||
- **Before**: post the *why this topic now* angle; invite specific people to your session; make plans to meet the other speakers — speaker-to-speaker is the strongest networking lane at any event.
|
||||
- **During**: end with one clear, low-friction pointer (a memorable URL to the slides + a related asset — which doubles as a lead magnet, → **lead-magnets**). Q&A questions are content research; note every one.
|
||||
- **After**: publish the recording + a written version of the talk (→ **content-strategy**), clip the peak beats (→ **video**), follow up with everyone who asked a question or approached you — same 24–48h window as every event motion, and these are the warmest leads an event produces.
|
||||
- Roll the talk forward: the same core talk, sharpened by each delivery's Q&A, can run a full conference season. Retire it when the Q&A stops surprising you.
|
||||
@@ -0,0 +1,57 @@
|
||||
# Sponsorship & Exhibiting — Evaluate, Negotiate, Work the Floor, Follow Up
|
||||
|
||||
Sponsorships are the most expensive way to do event marketing and the easiest to waste. The discipline: treat every sponsorship as a paid-acquisition channel with a cost-per-qualified-meeting, and make it beat your alternatives or don't buy it.
|
||||
|
||||
## Should We Sponsor? (the evaluation)
|
||||
|
||||
Run this before looking at the prospectus pricing:
|
||||
|
||||
1. **Audience–ICP overlap, in absolute numbers.** Not "5,000 attendees" but *how many attendees are your buyer*. Ask organizers for the attendee breakdown by role/company type; check last year's attendee/speaker lists and social chatter. A 5,000-person event with 200 ICP attendees is a 200-person event for you.
|
||||
2. **Do the meetings math backwards.** Realistic qualified conversations = a small fraction of ICP attendees (a well-worked booth might convert 10–20% of relevant walk-bys into real conversations — directional, varies wildly by event). Then: total cost (sponsorship + travel + staff time + booth build) ÷ expected qualified meetings = **cost per qualified meeting**. Compare against what a meeting costs you from outbound or ads. If the event is 3× your outbound cost with no strategic upside, pass.
|
||||
3. **Strategic multipliers that justify a premium**: your exact buyers concentrated nowhere else, a category-defining event where absence is conspicuous (late-stage), or access you genuinely can't buy elsewhere (exec attendees who ignore cold outreach).
|
||||
4. **The counterfactual check**: what would the same budget produce in your best-performing channel? Sponsorship must beat that, not zero.
|
||||
|
||||
Red flags in prospectuses: attendee counts without composition, "impressions" as the headline metric, leads defined as badge scans, and last year's sponsor logos heavy on companies that didn't return.
|
||||
|
||||
## Negotiation: The Prospectus Is a Starting Point
|
||||
|
||||
Sponsorship pricing is soft, especially inside 8 weeks. What to negotiate for (in rough order of value):
|
||||
|
||||
1. **A speaking or panel slot** — worth more than a bigger booth; stage time converts better than floor space (see [speaking.md](speaking.md)).
|
||||
2. **Side-event rights** — permission/space to host a dinner, breakfast, or workshop for a curated list during the event.
|
||||
3. **Attendee list reality check** — full lists are increasingly rare (privacy); negotiate for opt-in scans, the registration-page question, or sponsored-session registrant lists. Get what's actually deliverable in writing.
|
||||
4. **Placement and timing** — booth position near traffic (coffee, entrances, main stage exit); demo-day timing if the event has one.
|
||||
5. **Price** — last, after the package is right. Unsold inventory close to the date discounts heavily.
|
||||
|
||||
## The Side-Event Play (often better than the booth)
|
||||
|
||||
The highest-leverage move in field marketing: skip or downgrade the booth, and **host a curated dinner or breakfast adjacent to the conference**.
|
||||
|
||||
- 8–14 seats, hand-picked ICP attendees + a couple of magnetic guests (a respected practitioner draws acceptances)
|
||||
- Invite via personal outreach 2–4 weeks out (→ **cold-email** for craft); "join 10 [role]s for dinner during [event]" converts far better than any booth pull
|
||||
- No pitch. The host halo and the conversations are the product; follow-up carries the commercial weight
|
||||
- Economics: a dinner typically costs a fraction of a mid-tier sponsorship and produces *deeper* meetings with *chosen* accounts. This is also the play when you can't afford (or aren't allowed) to sponsor at all — you don't need the event's permission for your own dinner across the street.
|
||||
|
||||
## Working the Booth (if you buy one)
|
||||
|
||||
- **Staff it with people who can qualify and demo**, not whoever was free. Two energetic people beat five tired ones; write a shift schedule — floor fatigue is real and visible.
|
||||
- **A 30-second qualifying question** beats a pitch: "what does your team use for X today?" sorts buyers from swag collectors instantly. Have a graceful fast exit for non-ICP traffic.
|
||||
- **Capture context, not just scans**: after every real conversation, 15 seconds of notes — what they said, what they care about, the agreed next step. Voice memo or CRM app, same-hour. This is the raw material of follow-up that converts; a bare badge scan is a name with amnesia.
|
||||
- Demo stations for depth, one clear message on the booth itself (the category problem, not your feature list), and book-a-meeting QR that goes to a calendar, not a form.
|
||||
- **Book meetings before the event** with target attendees — the booth is a venue for pre-booked meetings, not just a net for walk-bys.
|
||||
|
||||
## Follow-Up: Where the Sponsorship Is Won or Lost
|
||||
|
||||
- **24–48 hour SLA**, tiered:
|
||||
- **Hot** (real conversation, next step agreed): personal email referencing the conversation, calendar link, same or next day.
|
||||
- **Warm** (conversation, no commitment): personal note + one relevant asset matched to what they said.
|
||||
- **Scan-only**: one light "we were both at [event]" touch or nothing. Never dump scans into a sales sequence — it burns domain reputation and brand on people who don't remember you (→ **revops** for routing/scoring).
|
||||
- Whoever worked the booth writes or reviews the follow-up — the context lives in their heads and their notes.
|
||||
- Sequence the not-nows into nurture with event source tags (→ **emails**).
|
||||
|
||||
## Measuring the Sponsorship
|
||||
|
||||
- Log every touched contact with an event source tag; measure **qualified conversations → meetings → opportunities → pipeline → closed-won influenced**, on an influence window that matches your sales cycle (90 days is common for B2B; long cycles need longer windows).
|
||||
- Report **cost per qualified meeting and cost per opportunity** against your other channels — this is the renewal decision for next year, made with data instead of vibes.
|
||||
- Self-reported attribution ("met you at [event]") catches influence that source tags miss (→ **attribution**); badge-scan counts and booth traffic are activity, not outcomes — track for logistics, never report as results.
|
||||
- Judge a first-time event against a discount: your team's first run of any event underperforms its potential. A promising-but-unprofitable first year is a redesign signal, not necessarily a no.
|
||||
@@ -0,0 +1,88 @@
|
||||
# The Webinar Funnel — Registration → Show-Up → Live-to-Close → Nurture
|
||||
|
||||
The webinar is the flagship hosted format because it's the whole event arc in miniature, repeatable monthly, and every stage is measurable. Work the four stages in order — each stage's conversion rate is a separate lever with separate fixes.
|
||||
|
||||
**The funnel at a glance** (typical B2B ranges — directional benchmarks, not targets; your own trend line is the real baseline):
|
||||
|
||||
| Stage | Metric | Typical range |
|
||||
|---|---|---|
|
||||
| Registration page | Visitor → registrant | 30–50% (warm traffic), 10–25% (cold) |
|
||||
| Show-up | Registrant → attendee | 35–45% live; lower for cold/ads traffic |
|
||||
| Hold | Attendee stays past minute 40 | 50–70% |
|
||||
| Convert | Attendee → next step (trial, demo, offer) | 5–15% of attendees for a soft CTA; 1–5% direct purchase |
|
||||
|
||||
## Stage 0: Topic & Offer (decided before anything else)
|
||||
|
||||
The topic does the targeting and most of the selling:
|
||||
|
||||
- **Pick a problem-aware topic, not a product topic.** "How [ICP] does X without Y" out-registers "Intro to [Product]" — the audience you want shows up for their problem, not your roadmap.
|
||||
- **Name the transformation in the title**: specific outcome + specific audience + (optionally) a number or timeframe. Test titles the way you'd test ad headlines — the title *is* the ad.
|
||||
- **Decide the offer before writing the content.** What's the next step for an attendee who loved it — trial, demo, audit, purchase? The entire live structure builds toward that one step. A webinar with no decided offer becomes a lecture with an awkward ending.
|
||||
- One topic, one promise, one offer. Stack more and every rate drops.
|
||||
|
||||
## Stage 1: Registration
|
||||
|
||||
**The registration page** is a landing page (→ **copywriting** for craft); webinar-specific rules:
|
||||
|
||||
- Headline = the promise from the title; subhead = who it's for and what they'll walk away able to do
|
||||
- 3–5 "you'll learn" bullets written as outcomes, not agenda items
|
||||
- Speaker credibility in one tight block (why should they listen to *you* on this)
|
||||
- Date/time with timezone handling; "can't make it? register anyway for the replay" — replay-registrants are real leads
|
||||
- Short form: name + email (+ one qualifying field max if sales needs it)
|
||||
|
||||
**The promo plan** — start 2 weeks out, not 6 (urgency compresses better than it stretches):
|
||||
|
||||
- **Email list** — 3 sends: announcement, value-add reminder (share a preview insight), last-call day-of (→ **emails**)
|
||||
- **Social** — founder/host personal posts outperform brand posts; share the *why this topic now* angle (→ **social**)
|
||||
- **Partners** — a co-hosted webinar doubles reach for free; partnership mechanics → **co-marketing**, but note: co-hosted registrant lists need explicit consent handling for both parties
|
||||
- **Paid** — only after the topic is proven organically; retargeting warm traffic to a reg page works, cold-to-webinar ads are an expensive way to buy no-shows (→ **ads**)
|
||||
- **Speakers' own audiences** — for panels/summits, every speaker promotes; make it effortless (pre-written posts, custom links)
|
||||
|
||||
## Stage 2: Show-Up (the hardest metric)
|
||||
|
||||
Registrants are cheap; attendance is the funnel's leakiest joint. The show-up system:
|
||||
|
||||
- **Calendar add at registration** — the single highest-leverage fix. A registrant with a calendar entry is a different species from one with a confirmation email.
|
||||
- **Reminder cadence**: confirmation (immediately, with calendar links) → value reminder T-1 day (tease a specific insight, not "don't forget!") → T-1 hour → **T-5 minutes with the join link** (this last one moves attendance more than the rest combined). SMS reminders where consented lift show-up meaningfully (→ **sms**).
|
||||
- **Close the gap between registration and event.** Show-up decays with distance: someone who registered 6 weeks out has forgotten you existed. If promoting long-range, add a mid-window touchpoint (a related asset, a poll shaping the content).
|
||||
- **Pre-engagement**: ask a question at registration ("what's your biggest challenge with X?") — you get content input, segmentation data, and a micro-commitment that lifts attendance.
|
||||
- Time slot: mid-week, late morning or early afternoon in your audience's dominant timezone; avoid Mondays/Fridays. Test against your own data.
|
||||
|
||||
## Stage 3: Live-to-Close (sell without being salesy)
|
||||
|
||||
The arc that converts without feeling like a pitch:
|
||||
|
||||
1. **Open (0–5 min)** — restate the promise, preview the payoff, tell them the offer is coming ("at the end I'll show how we do this — first, the practice you can use regardless"). Naming the pitch upfront *removes* the salesy feeling; the ambush is what people hate.
|
||||
2. **Content (5–35 min)** — teach the real thing. The #1 conversion lever is genuine value: an attendee who learned something trusts the product behind it. Structure as 3 teachable points, each with a proof (story, number, live example). Use attendee questions/polls to keep hold rate up.
|
||||
3. **The transition (1 min, scripted)** — the hardest 60 seconds; write it word for word. The honest bridge: "everything I showed you can be done manually — here's what it looks like when [product] does it for you." The product enters as the *implementation* of the content, not a topic change.
|
||||
4. **Offer (5–8 min)** — one offer, concretely: what they get, what it costs (or what the next step is), why now (a real reason — expiring bonus, cohort start, limited seats; never fake scarcity, → **offers** for legitimate urgency design).
|
||||
5. **Q&A (10+ min)** — conversion happens here; questions are objections in disguise. Seed 2–3 starter questions for cold starts, answer the objection behind the question, and re-state the offer + link once mid-Q&A and once at close.
|
||||
|
||||
Hold-rate mechanics throughout: deliver on a specific promise made in minute 1 at minute ~35 (announced), use pattern breaks every ~7 minutes (poll, story, screen change), and never front-load housekeeping.
|
||||
|
||||
## Stage 4: Post-Webinar (half the revenue is here)
|
||||
|
||||
Segment by behavior, then sequence (→ **emails** for craft):
|
||||
|
||||
| Segment | Play |
|
||||
|---|---|
|
||||
| **Attended, engaged** (stayed for offer, asked questions) | Personal follow-up within 24h referencing their question; direct next step |
|
||||
| **Attended, left early** | Replay + timestamp to what they missed; softer CTA |
|
||||
| **No-show** | "Sorry we missed you" + replay with a deadline. No-shows are warm — they raised their hand once; a 2–3 email replay sequence recovers a meaningful fraction |
|
||||
| **Replay-registrants** | Same as no-shows, minus the apology |
|
||||
|
||||
- **Replay strategy**: time-limited replay (72h–1 week) preserves urgency for the offer; evergreen replay converts the offer to a standing CTA and becomes a lead magnet (→ **lead-magnets**). Pick per goal — limited for launches/offers, evergreen for education-led capture.
|
||||
- **Cart/offer close**: if the offer had a deadline, run a real close sequence (deadline reminder → objection email → final hours). All urgency claims must be true.
|
||||
- **Recycle the asset**: transcript → recap post (→ **content-strategy**), clips (→ **video**), quotable stats for AI-citable content (→ **ai-seo**). A monthly webinar run this way is a content engine with a lead-gen side effect.
|
||||
|
||||
## Metrics That Diagnose
|
||||
|
||||
- **Low registration** → topic/title/promise problem (or traffic quality). Fix the offer of the webinar itself before touching promo volume.
|
||||
- **Low show-up** (<30%) → reminder system or reg-to-event gap; check calendar-add rate first.
|
||||
- **Low hold** → content front-loading or promise mismatch; find the drop-off timestamp.
|
||||
- **High hold, low conversion** → transition or offer problem; the audience liked the class but wasn't shown a reason to act.
|
||||
- Cost per qualified attendee and per opportunity — comparable against your other channels, and the number that decides the program's future.
|
||||
|
||||
---
|
||||
|
||||
*Skill category identified via 2026-07 competitive research (webinar-marketing in alirezarezvani/claude-skills, MIT — idea credited; content authored from scratch to this repo's standard). Benchmarks are directional industry ranges — treat your own trend line as the baseline.*
|
||||
@@ -0,0 +1,108 @@
|
||||
# Partner Program & Tools Registry — Rules & Boundaries
|
||||
|
||||
The single source of truth for how tools and partners work in this repository. If anything elsewhere is ambiguous, this document governs.
|
||||
|
||||
- **Public pitch & pricing:** [marketing-skills.com/sponsorship](https://marketing-skills.com/sponsorship)
|
||||
- **Content rules for mentioning any tool:** [CONTRIBUTING.md → Mentioning Tools](../CONTRIBUTING.md#mentioning-tools-the-integrity-rubric)
|
||||
- **The tool index itself:** [REGISTRY.md](REGISTRY.md)
|
||||
- **The legal terms:** the Partner Agreement, provided to each partner (accepted at checkout)
|
||||
|
||||
## The one principle
|
||||
|
||||
**Sponsorship funds the work, never the recommendations.** Money buys a *disclosed presence*, never a bias. Every rule below follows from this. The library is free and MIT-licensed; sponsors and partners fund maintenance and new skills so the core stays free, open, and editorially independent — whoever is paying.
|
||||
|
||||
## Three kinds of tool entries
|
||||
|
||||
Every tool in [REGISTRY.md](REGISTRY.md) is exactly one of these:
|
||||
|
||||
| Kind | What it is | Who | Marker | Disclosure | Placement |
|
||||
|---|---|---|---|---|---|
|
||||
| **Tool integration** | A neutral integration guide for a real marketing tool with a programmatic surface | Anyone (incl. non-partners) can contribute one via PR | none | none required | Listed in the Tool Index / By Category |
|
||||
| **◆ Verified Partner** | A tool whose maker funds the library (Skill or Category Partner) | Vetted, application-only, paid | ◆ | Disclosure header in its integration guide + ◆ in the registry + entry in `partners.json` | Verified Partners section + README + site + launch announcement |
|
||||
| **House tool** | A tool built by the maintainer (e.g. Truelist) | The repo author | (noted) | **Stricter** than a partner — its guide states the repo author owns the tool | Held as a category House Tool; that slot is not for sale |
|
||||
|
||||
A partner integration is the *same* neutral integration guide as any other tool, plus disclosure and placement. It is not a different kind of content — it earns no softer editorial treatment.
|
||||
|
||||
## What sponsorship buys — and never buys
|
||||
|
||||
**Buys:**
|
||||
- A dedicated, disclosed integration guide for the tool (◆).
|
||||
- Featured placement — logo, link, blurb — on the README and the site.
|
||||
- A launch announcement (tweet + LinkedIn + Swipe Files newsletter mention).
|
||||
- For Category Partners: a category *slot* exclusivity + an "Official [Category] Partner" title/badge.
|
||||
|
||||
**Never buys:**
|
||||
- A recommendation. No skill is edited to prefer a partner.
|
||||
- Bias in any existing skill. Skills recommend the right tool for the job, partner or not.
|
||||
- Exclusivity over what agents recommend. Category exclusivity is a *sponsorship-slot* exclusivity, never a recommendation exclusivity — a skill may still name a competitor when it's the right answer.
|
||||
- Removal or demotion of any other tool. Partner entries are additive.
|
||||
- A claim of "best in category." The badge means "paid, disclosed, vetted for fit."
|
||||
|
||||
## Tiers (summary)
|
||||
|
||||
Full pricing and perks live on the [sponsorship page](https://marketing-skills.com/sponsorship). In brief:
|
||||
|
||||
| Tier | Price | Billing | Gets |
|
||||
|---|---|---|---|
|
||||
| Supporter | $1–199/mo | GitHub Sponsors | README + site listing |
|
||||
| Sponsor | $200/mo | GitHub Sponsors | Featured logo + link + blurb on README and site |
|
||||
| **Skill Partner** | $500/mo | Stripe · 6-mo min | A disclosed ◆ integration + launch announcement + everything in Sponsor. **Non-exclusive.** |
|
||||
| **Category Partner** | $1,500/mo | Stripe · 6-mo min | Category-slot exclusivity + official-partner title/badge + top category placement + quarterly Swipe Files feature + YouTube description slot + dual launch. Everything in Skill Partner. |
|
||||
|
||||
Partner tiers are **application-only** (vetted, then paid) and carry a **6-month minimum**. Annual prepay = two months free.
|
||||
|
||||
## Disclosure travels with the file
|
||||
|
||||
Disclosure is on the artifact, not just the site — skills and guides get forked and re-indexed across the ecosystem, so the disclosure must survive that.
|
||||
|
||||
A Verified Partner integration guide opens with this header:
|
||||
|
||||
```markdown
|
||||
> **◆ Verified Partner integration.** [Tool] sponsors Marketing Skills. This integration
|
||||
> is disclosed and vetted for fit; it does **not** change what any skill recommends. It's
|
||||
> listed alongside the neutral options for the same job — use it when it's the right fit,
|
||||
> not because it's a partner. See [Verified Partners](../REGISTRY.md#verified-partners).
|
||||
```
|
||||
|
||||
Plus a ◆ marker in [REGISTRY.md](REGISTRY.md) and an entry in [`../partners.json`](../partners.json). A **House tool** additionally states in its guide that the repo author owns the tool.
|
||||
|
||||
## Editorial control & the integrity rubric
|
||||
|
||||
- **The maintainer holds final editorial control** and may edit or cut anything for neutrality and accuracy, at any time.
|
||||
- **Any content that names a tool — partner or not — must pass the [integrity rubric](../CONTRIBUTING.md#mentioning-tools-the-integrity-rubric):** options not one answer, at the point of relevance, no forced endorsement, facts over framing, disclosed, and the *swap test* (swap the tool for a competitor and it should still read fair).
|
||||
- **Partner integrations surface only at the point of relevance** — when a user is implementing or working with that tool. They never hijack generic queries and never insert themselves into a skill's recommendation as the answer.
|
||||
|
||||
## Category exclusivity (precise definition)
|
||||
|
||||
- **Skill Partner is non-exclusive.** Competitors may hold Skill Partner placements in the same category.
|
||||
- **Category Partner buys a slot, not the answer.** No competing tool receives a Verified Partner integration or partner slot in that category while the agreement is active. It does **not** mean core skills only recommend that partner, and it does not restrict what any skill says. Categories are defined in writing in the agreement; a multi-category tool claims one category.
|
||||
- **House-tool categories are not for sale** (e.g. email verification is held by Truelist).
|
||||
|
||||
## The partner lifecycle
|
||||
|
||||
1. **Apply** — application via the sponsorship page (vetted for fit).
|
||||
2. **Agreement** — the Partner Agreement (6-month minimum), accepted at checkout.
|
||||
3. **Pay** — Stripe; acceptance (version + timestamp) recorded with the subscription. Nothing publishes until the first payment clears.
|
||||
4. **Onboard** — the partner submits logo, blurb, docs, and setup specifics via the onboarding form.
|
||||
5. **Author** — the integration guide is drafted collaboratively; **the maintainer holds the pen** and final editorial control.
|
||||
6. **Publish** — add the partner to [`../partners.json`](../partners.json), run [`../scripts/sync-partners.mjs`](../scripts/sync-partners.mjs) to regenerate the README + registry blocks, commit. The site reads `partners.json` directly.
|
||||
7. **Renewal / lapse** — renewal is an explicit conversation, never an automatic charge. On lapse there's a **30-day notice period** where the integration is flagged as unmaintained before removal — installs are never silently broken. Deactivate with `"active": false` (keeps history, removes it from every surface).
|
||||
|
||||
## `tools/integrations/` spec (any tool, partner or not)
|
||||
|
||||
**What qualifies:** a real marketing tool with a programmatic surface an agent can use — an API, MCP server, and/or CLI. Neutral integrations are welcome from anyone via PR.
|
||||
|
||||
**Format** (match the existing guides, e.g. [`integrations/resend.md`](integrations/resend.md)):
|
||||
- `# Tool Name` + a one-line description
|
||||
- `## Capabilities` table — API / MCP / CLI / SDK availability with notes
|
||||
- `## Authentication` — auth type; secrets go in env vars / a secret manager, never in the repo
|
||||
- Setup + common operations (with real command/code examples)
|
||||
- Links to official docs
|
||||
|
||||
**CLIs** (`../clis/*.js`) are zero-dependency Node 18+ scripts: show usage with no args, support `--dry-run`, and never require credentials just to print help. See [AGENTS.md](../CLAUDE.md) build/verify rules.
|
||||
|
||||
**A partner integration** is all of the above **plus** the disclosure header, the ◆ marker, and the `partners.json` entry.
|
||||
|
||||
## Single source of truth
|
||||
|
||||
The partner data lives once in [`../partners.json`](../partners.json). `sync-partners.mjs` generates the README Partners section and the Verified Partners table from it; the site fetches the same file. Edit one place, run the script, commit — every surface updates together. Run `node scripts/sync-partners.mjs --check` to verify nothing has drifted.
|
||||
@@ -10,10 +10,34 @@ Quick reference for AI agents to discover tool capabilities and integration meth
|
||||
|
||||
---
|
||||
|
||||
## Verified Partners
|
||||
|
||||
> **Full rules & boundaries:** [PARTNERS.md](PARTNERS.md) — the canonical governance doc (tool taxonomy, what sponsorship buys and never buys, disclosure, the partner lifecycle, and the `integrations/` spec).
|
||||
|
||||
◆ **Verified Partners** are tools whose makers fund Marketing Skills through the [partner program](https://marketing-skills.com/sponsorship). What the marker means — and doesn't:
|
||||
|
||||
- **Disclosed + vetted for fit.** Each carries a disclosure header in its integration guide and is marked ◆ in the index below.
|
||||
- **Additive, never biasing.** A partner is listed *alongside* the neutral options for the same job, never instead of them. Partner status never removes or demotes another tool and **never changes what any skill recommends** — if a non-partner is the right answer, that's the answer. The badge means "paid, disclosed, vetted for fit," not "best in category."
|
||||
|
||||
Anyone — including tool makers and partners — may contribute content that names a tool, as long as it makes an agent *aware* of the right option without manufacturing a recommendation. The bar is the [integrity rubric in CONTRIBUTING.md](../CONTRIBUTING.md#mentioning-tools-the-integrity-rubric) (options not one answer, disclosed, passes the swap test).
|
||||
|
||||
<!-- PARTNERS:START -->
|
||||
| Partner | Category | Guide |
|
||||
|---------|----------|-------|
|
||||
| ◆ Converly | Conversion tracking / attribution | [converly.md](integrations/converly.md) |
|
||||
| ◆ Ploy | AI website & growth platform | [ploy.md](integrations/ploy.md) |
|
||||
<!-- PARTNERS:END -->
|
||||
|
||||
<!-- The table above is generated from partners.json — run `node scripts/sync-partners.mjs`. -->
|
||||
|
||||
---
|
||||
|
||||
## Tool Index
|
||||
|
||||
| Tool | Category | API | MCP | CLI | SDK | Guide |
|
||||
|------|----------|:---:|:---:|:---:|:---:|-------|
|
||||
| ◆ converly | Conversion Tracking | ✓ | ✓ | ✓ | - | [converly.md](integrations/converly.md) |
|
||||
| ◆ ploy | Website | ✓ | ✓ | ✓ | - | [ploy.md](integrations/ploy.md) |
|
||||
| ga4 | Analytics | ✓ | ✓ | [✓](clis/ga4.js) | ✓ | [ga4.md](integrations/ga4.md) |
|
||||
| mixpanel | Analytics | ✓ | - | [✓](clis/mixpanel.js) | ✓ | [mixpanel.md](integrations/mixpanel.md) |
|
||||
| amplitude | Analytics | ✓ | - | [✓](clis/amplitude.js) | ✓ | [amplitude.md](integrations/amplitude.md) |
|
||||
|
||||
@@ -0,0 +1,48 @@
|
||||
# Converly
|
||||
|
||||
> **◆ Verified Partner integration.** Converly sponsors Marketing Skills. This integration is disclosed and vetted for fit; it does **not** change what any skill recommends. It's listed here alongside the neutral options for the same job — use it when it's the right fit, not because it's a partner. See [Verified Partners](../REGISTRY.md#verified-partners).
|
||||
|
||||
Server-side conversion tracking: sends conversions to ad platforms and analytics tools when a visitor completes an action on your site — a form submit, a booked meeting, a started chat.
|
||||
|
||||
## Capabilities
|
||||
|
||||
| Integration | Available | Notes |
|
||||
|-------------|-----------|-------|
|
||||
| API | ✓ | REST API — [developers.converly.io](https://developers.converly.io) |
|
||||
| MCP | ✓ | Converly MCP server — [converly.io/mcp](https://converly.io/mcp) — lets an agent set up tracking end to end |
|
||||
| CLI | ✓ | Configure conversions and destinations from the terminal |
|
||||
| SDK | – | Single site snippet + drag-and-drop flow builder |
|
||||
|
||||
## What it does
|
||||
|
||||
Server-side delivery bypasses ad blockers and browser privacy limits that silently drop browser-pixel events — which is what recovers "missing" conversions and lifts match rates. Converly passes name, email, phone, click IDs, and IP, enabling **Enhanced Conversions** on Google Ads and high **EMQ** (Event Match Quality) scores on Meta.
|
||||
|
||||
- **Destinations:** Google Ads, Meta Ads, LinkedIn Ads, TikTok Ads, Google Analytics.
|
||||
- **Sources (100+):** form builders (Gravity Forms, WPForms, Contact Form 7, Fluent Forms, Formidable, Ninja Forms, Typeform, Jotform, Tally, Webflow, Elementor, Wix) and CRM/scheduling/chat (HubSpot, Salesforce, Pipedrive, Calendly, HighLevel, Intercom, LiveChat).
|
||||
- **Build:** one site snippet installed once, then drag-and-drop conversion flows; add/remove destinations in one click.
|
||||
- **Reported lift (vendor-supplied — verify with your own holdout):** ~19% more conversions on Google Ads, ~23% on Meta Ads with server-side tracking.
|
||||
|
||||
## Authentication
|
||||
|
||||
- **Type:** API key. Store it in an environment variable / secret manager — never in the repo. `TODO: exact env var name from developers.converly.io`
|
||||
|
||||
## Setup (agent-driven via CLI or MCP)
|
||||
|
||||
1. **Authenticate** to Converly (CLI login or MCP). `TODO: exact auth command / MCP tool name`
|
||||
2. **Install the site snippet** once on all pages; confirm it's in the initial HTML.
|
||||
3. **Define the conversion** — pick the trigger (form submit / meeting booked / chat started) and source tool, and map the fields to capture (email, phone, name, click IDs). `TODO: create-flow command + field-mapping schema`
|
||||
4. **Connect destinations** — add the ad platforms/analytics tools to send to; one conversion can fan out to several. `TODO: destination-add command + per-platform credentials (e.g. Google Ads conversion action + customer ID; Meta dataset/pixel ID + CAPI token)`
|
||||
5. **Verify a real conversion** — fire a test action, confirm it lands in each destination with identifiers attached (Enhanced Conversions diagnostics on Google; EMQ on Meta). Don't call tracking done until a real conversion is observed downstream.
|
||||
|
||||
> The `TODO` lines are placeholders for Converly's exact syntax; fill from [developers.converly.io](https://developers.converly.io) + [converly.io/mcp](https://converly.io/mcp) during the accuracy review, then remove this note.
|
||||
|
||||
## How it fits the skills
|
||||
|
||||
- Converly is one way to **implement** the server-side send described in `attribution` → `references/first-party-tracking.md`. The *strategy* (what to count, source of truth, how to read the numbers) still comes from `attribution` and `analytics`; Converly handles the browser→server→platform hop and identity fields.
|
||||
- After conversions flow, judge results with `ads` discipline: never sum conversions across attribution windows, and treat vendor lift figures as a hypothesis to verify with a holdout.
|
||||
|
||||
## Links
|
||||
|
||||
- Site: https://converly.io
|
||||
- Developer docs / API: https://developers.converly.io
|
||||
- MCP: https://converly.io/mcp
|
||||
@@ -0,0 +1,48 @@
|
||||
# Ploy
|
||||
|
||||
> **◆ Verified Partner integration.** Ploy sponsors Marketing Skills. This integration is disclosed and vetted for fit; it does **not** change what any skill recommends. It's listed here alongside the neutral options for the same job — use it when it's the right fit, not because it's a partner. See [Verified Partners](../REGISTRY.md#verified-partners).
|
||||
|
||||
AI marketing platform built around a website builder: one system for building the site, optimizing it (SEO/AEO, CRO), identifying and engaging visitors, and generating ad creative with attribution. An in-app agent builds pages, writes copy, analyzes performance, and manages deploys through conversation.
|
||||
|
||||
## Capabilities
|
||||
|
||||
| Integration | Available | Notes |
|
||||
|-------------|-----------|-------|
|
||||
| API | ✓ | Workspace-scoped API tokens for CI/headless use; inbound [webhooks](https://docs.ploy.ai/webhooks) trigger Ploybooks; OpenAPI spec published at `/.well-known/api-catalog` |
|
||||
| MCP | ✓ | **WebMCP** — exposes selected website actions to compatible AI assistants while preserving the site's existing interface, permissions, and application logic |
|
||||
| CLI | ✓ | Standalone binary (macOS/Linux) — workspaces, sites, domains, publishing, PloyDB, Ploybooks, variables/secrets, Code Sync — [docs.ploy.ai/cli](https://docs.ploy.ai/cli) |
|
||||
| SDK | – | Agent-first instead: the CLI ships [agent skills + site inspection](https://docs.ploy.ai/cli/local-development) for coding agents working in a checked-out site |
|
||||
|
||||
## What it does
|
||||
|
||||
- **Site builder** — pages, sections, components on a design system; publish, deploy history, rollback, custom domains. Can serve alongside an existing site via [routing rules](https://docs.ploy.ai/routing-rules).
|
||||
- **Analytics & visitors** — traffic tracking, visitor identification, GA4 and Google Search Console connections.
|
||||
- **PloyDB** — structured content database; [CMS migration](https://docs.ploy.ai/database/cms-migration) imports existing CMS content and builds pages from the imported tables.
|
||||
- **Ploybooks** — scheduled/triggered marketing playbooks; fire them from external systems via webhooks.
|
||||
- **WebMCP** — expose chosen site actions (forms, booking, etc.) to AI assistants via the Model Context Protocol without rebuilding the interface.
|
||||
- **Integrations** — GitHub, Figma, Google Analytics, Search Console, Notion, Slack, HubSpot, and more.
|
||||
|
||||
## Authentication
|
||||
|
||||
- **Type:** sign-in via Ploy for interactive use; **workspace-scoped API token** for CI and headless environments ([docs](https://docs.ploy.ai/cli/authentication)). Store tokens in an environment variable / secret manager — never in the repo.
|
||||
|
||||
## Setup (agent-driven via CLI)
|
||||
|
||||
1. **Install the CLI** — macOS/Linux binary ([install docs](https://docs.ploy.ai/cli/install)).
|
||||
2. **Authenticate** — interactive sign-in, or set a workspace API token for [remote agents & CI](https://docs.ploy.ai/cli/remote-development) (non-interactive commands, explicit IDs, safe secret handling).
|
||||
3. **Select context** — workspace and site.
|
||||
4. **Build or migrate** — create pages via the agent/builder, or import existing CMS content into PloyDB and generate pages from it.
|
||||
5. **Publish** — push production, connect a custom domain, verify the deploy; roll back if needed.
|
||||
6. **Optionally enable WebMCP** — choose which site actions to expose to AI assistants.
|
||||
|
||||
## How it fits the skills
|
||||
|
||||
- Ploy is one way to **implement** the site itself — an alternative to a Webflow/Framer or hand-coded stack. The strategy layer (what pages, what copy, what structure) still comes from `site-architecture`, `copywriting`, and `cro`.
|
||||
- Its SEO/AEO surface pairs with `seo-audit`, `ai-seo`, and `schema`; judge its analytics, visitor-identification, and attribution output with `analytics` / `attribution` discipline.
|
||||
|
||||
## Links
|
||||
|
||||
- Site: https://ploy.ai
|
||||
- Docs: https://docs.ploy.ai
|
||||
- CLI reference: https://docs.ploy.ai/cli/reference
|
||||
- Support: support@ploy.ai
|
||||
Reference in New Issue
Block a user