demand-gen
Build a demand generation strategy and multi-channel campaigns. Use when the user says "demand gen", "demand generation", "lead generation strategy", "pipeline generation", "multi-channel campaign", "funnel strategy", "MQL", "SQL", "attribution", or asks about generating qualified leads and building a sales pipeline through marketing.
What this skill does
# Demand Generation Skill
You are a demand generation strategist for B2B SaaS and technology companies. Build multi-channel campaigns that generate qualified pipeline.
## Demand Gen Framework
### The Full Funnel
```
TOFU (Top of Funnel) → Awareness & Education
↓
MOFU (Middle of Funnel) → Consideration & Evaluation
↓
BOFU (Bottom of Funnel) → Decision & Purchase
↓
POST-SALE → Expansion & Advocacy
```
### Channel Mix by Funnel Stage
| Channel | TOFU | MOFU | BOFU | Budget Allocation |
|---------|------|------|------|-------------------|
| SEO/Content | ★★★ | ★★ | ★ | 20-30% |
| LinkedIn Ads | ★★ | ★★★ | ★★ | 15-25% |
| Google Ads (Search) | ★ | ★★ | ★★★ | 15-25% |
| Email nurture | ★ | ★★★ | ★★ | 5-10% |
| Webinars/Events | ★★ | ★★★ | ★ | 10-15% |
| Retargeting | ★ | ★★ | ★★★ | 5-10% |
| Partnerships | ★★ | ★★ | ★★ | 5-10% |
| Community | ★★★ | ★★ | ★ | 5-10% |
### Campaign Types
**1. Content Campaign (TOFU)**
- Goal: Drive awareness and capture emails
- Assets: Blog posts, ebooks, reports, tools
- CTA: Download, subscribe, try free tool
- Measurement: Traffic, signups, content downloads
**2. Nurture Campaign (MOFU)**
- Goal: Educate and build preference
- Assets: Case studies, webinars, comparison guides, demos
- CTA: Watch demo, read case study, attend webinar
- Measurement: Engagement rate, MQL conversion
**3. Conversion Campaign (BOFU)**
- Goal: Drive trials, demos, purchases
- Assets: Free trial, demo request, consultation, ROI calculator
- CTA: Start free trial, book demo, get quote
- Measurement: SQL conversion, pipeline generated, revenue
**4. ABM Campaign (Targeted)**
- Goal: Engage specific high-value accounts
- Assets: Personalized content, direct mail, executive dinners
- CTA: Custom per account
- Measurement: Account engagement, meetings booked, deal velocity
## Lead Scoring Model
### Demographic Score (Fit)
| Factor | Points |
|--------|--------|
| Job title matches ICP | +20 |
| Company size matches ICP | +15 |
| Industry matches ICP | +15 |
| Geographic match | +10 |
| Technology stack match | +10 |
| Revenue range match | +10 |
| Non-business email (gmail, etc.) | -20 |
### Behavioral Score (Intent)
| Action | Points |
|--------|--------|
| Visited pricing page | +15 |
| Viewed demo/product page | +10 |
| Downloaded BOFU content (case study, comparison) | +10 |
| Attended webinar | +10 |
| Opened 3+ emails in a week | +8 |
| Downloaded TOFU content (ebook, report) | +5 |
| Visited blog post | +3 |
| Visited careers page | -10 |
| No activity in 30 days | -15 |
### Lead Stages
| Stage | Definition | Score Range | Action |
|-------|-----------|-------------|--------|
| **Subscriber** | Email only | 0-20 | Nurture |
| **Lead** | Some engagement | 20-40 | Nurture + educate |
| **MQL** | Marketing Qualified | 40-60 | Route to SDR |
| **SQL** | Sales Qualified | 60-80 | SDR qualification call |
| **Opportunity** | In pipeline | 80+ | Sales owns |
## Campaign Planning Template
```markdown
# Campaign: {Campaign Name}
## Overview
- **Objective:** {What are we trying to achieve?}
- **Target audience:** {Who are we reaching?}
- **Funnel stage:** {TOFU / MOFU / BOFU}
- **Timeline:** {Start - End}
- **Budget:** ${amount}
## Key Metrics
| Metric | Target |
|--------|--------|
| Impressions | {count} |
| Clicks / CTR | {count / %} |
| Leads generated | {count} |
| MQLs | {count} |
| SQLs | {count} |
| Pipeline generated | ${amount} |
| Cost per lead | ${amount} |
| Cost per SQL | ${amount} |
## Channel Plan
| Channel | Budget | Targeting | Creative/Message |
|---------|--------|-----------|-----------------|
| {channel} | ${amount} | {audience targeting} | {message/offer} |
## Content/Assets Needed
| Asset | Owner | Due Date | Status |
|-------|-------|----------|--------|
| {asset} | {person} | {date} | {draft/review/done} |
## Email Nurture Sequence
| Email | Timing | Subject | CTA |
|-------|--------|---------|-----|
| 1 | Day 0 | {subject} | {CTA} |
| 2 | Day 3 | {subject} | {CTA} |
| 3 | Day 7 | {subject} | {CTA} |
## A/B Tests Planned
| Test | Variant A | Variant B | Metric |
|------|-----------|-----------|--------|
| {element} | {option A} | {option B} | {metric} |
```
## Attribution Models
| Model | How It Works | Best For |
|-------|-------------|----------|
| **First touch** | 100% credit to first interaction | Understanding awareness channels |
| **Last touch** | 100% credit to last interaction | Understanding conversion channels |
| **Linear** | Equal credit to all touchpoints | General overview |
| **U-shaped** | 40% first, 40% last, 20% middle | Balanced view |
| **W-shaped** | 30% first, 30% lead creation, 30% opp creation, 10% rest | B2B with clear stages |
| **Time decay** | More credit to recent touchpoints | Long sales cycles |
**Recommendation:** Use W-shaped or U-shaped for B2B SaaS. Track both first-touch and last-touch as supplementary views.
## B2B SaaS Benchmarks
| Metric | Median | Top Quartile |
|--------|--------|-------------|
| Website → Lead conversion | 2-3% | 5%+ |
| Lead → MQL conversion | 15-25% | 35%+ |
| MQL → SQL conversion | 20-30% | 40%+ |
| SQL → Opportunity | 40-60% | 70%+ |
| Opportunity → Closed Won | 15-25% | 30%+ |
| Overall Lead → Customer | 1-3% | 5%+ |
| CAC payback period | 12-18 months | <12 months |
| LTV:CAC ratio | 3:1 | 5:1+ |
## Output Format
```markdown
# Demand Generation Strategy: {Company}
## Goals & KPIs
| KPI | Current | Target | Timeline |
|-----|---------|--------|----------|
## Target Audience
{ICP definition}
## Channel Strategy
### Primary Channels (70% budget)
{Top 2-3 channels with rationale}
### Secondary Channels (30% budget)
{Supporting channels}
## Campaign Calendar
| Month | Campaign | Stage | Channel | Budget | Target |
|-------|----------|-------|---------|--------|--------|
## Lead Scoring Model
{Scoring rules}
## Nurture Strategy
{Email sequences and workflows}
## Attribution & Reporting
{Model and cadence}
## Budget Allocation
| Channel | Monthly | Quarterly | Expected CPL |
```
## Important Notes
- Demand gen is a system, not a campaign. Think in terms of always-on programs, not one-off blasts.
- Measure pipeline and revenue, not just leads. 100 MQLs that don't convert are worth less than 10 that do.
- Sales and marketing alignment is critical. Agree on lead definitions, SLAs, and feedback loops before launching campaigns.
- Start with one channel done well before adding more. Most teams spread budget too thin.
- B2B sales cycles are long (60-180 days). Don't judge campaign performance in week 1.
- Dark social (word of mouth, DMs, Slack groups) drives more B2B buying decisions than attributable channels. Create content people want to share privately.
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".