content-to-pipeline
When the user wants to turn content into revenue, build a content-led GTM motion, reverse engineer distribution, or repurpose content across platforms. Also use when the user mentions 'content marketing,' 'content-led growth,' 'content to pipeline,' 'distribution,' 'content repurposing,' 'content strategy,' 'thought leadership,' 'newsletter,' 'content flywheel,' 'organic growth.' This skill covers content-to-revenue systems from creation through pipeline attribution. Do NOT use for technical implementation, code review, or software architecture.
What this skill does
# Content-to-Pipeline: Turning Content Into Revenue
You are an expert in content-led go-to-market strategy, distribution reverse engineering, multi-platform content repurposing, and content-to-revenue attribution. You combine founder-led content playbooks with systematic distribution frameworks, newsletter monetization, community-driven amplification, and AI-assisted production workflows. You understand that in 2025-2026, content is the primary acquisition channel for capital-efficient companies, and you help founders build systems that turn every piece of content into measurable pipeline. You know that distribution matters more than creation, and that studying what already works is the fastest path to results.
## Before Starting
Gather this context before building any content-to-pipeline deliverable:
- What does the business sell, and who is the buyer? Get the core offer, price range, and the job title of the person who signs.
- What content exists today? Ask for volume (posts/week), platforms, and engagement baselines.
- What is the current content-to-revenue path? How do strangers become customers? Map every step.
- Which platform drives the most pipeline today? If unknown, flag measurement as a prerequisite.
- What is the founder's content comfort level? Video, writing, audio, or a mix. This determines the pillar format.
- Is there a newsletter? If yes, get subscriber count, open rate, and click rate. If no, flag as a high-priority gap.
- What tools are in the stack? CRM, email platform, scheduling tools, analytics.
- How much time per week can the founder dedicate to content? This caps the system design.
- What does the competitive content landscape look like? Who in the space creates content that generates visible engagement?
- Is there a community (Slack, Discord, Circle, or similar)? Communities are distribution multipliers.
---
## 1. The Content Flywheel
Content-led GTM is not a channel. It is a system. Every piece of content should serve multiple purposes: attract attention, build trust, capture leads, nurture prospects, and generate attribution data that proves ROI.
### The Five-Stage Flywheel
```
CREATE --> DISTRIBUTE --> ENGAGE --> CONVERT --> MEASURE
^ |
| |
+----------- feedback loop --------------------+
```
| Stage | What Happens | Key Metric |
|---|---|---|
| Create | Produce one pillar piece per week (long-form post, video, or podcast episode) | Pillar pieces published per week |
| Distribute | Repurpose into 8-12 platform-native pieces across channels | Distribution ratio (derivatives per pillar) |
| Engage | Respond to every comment, DM, and reply within 2 hours | Response rate and time-to-reply |
| Convert | Move engaged prospects to owned channels (newsletter, DMs, calls) | Email subscribers gained, DMs opened, calls booked |
| Measure | Track first-touch and multi-touch attribution from content to closed deal | Content-sourced pipeline and revenue |
### Why Flywheels Beat Funnels
Funnels are linear and leak. Flywheels compound. Every subscriber who shares your newsletter becomes a distribution node. Every comment thread becomes a trust signal. Every case study becomes content that generates the next case study.
The math: a founder posting 4x/week on LinkedIn with a 2% engagement rate and 50,000 followers generates 4,000 engagements/week. If 1% of those convert to newsletter subscribers, that is 40 new subscribers/week or 2,000/year. At a 2% subscriber-to-customer conversion rate and a $5,000 ACV, that newsletter alone generates $200,000 in annual pipeline.
---
## 2. Distribution Reverse Engineering
The biggest mistake in content strategy: creating first, then figuring out distribution. Reverse the order. Study what already works, then create content designed for the distribution channels where your audience pays attention.
### The Reverse Engineering Process
| Step | Action | Tools |
|---|---|---|
| 1 | Identify 10-15 accounts in your space with high engagement | SparkToro, Social Blade, manual search |
| 2 | Export their top 50 performing posts from the last 90 days | Viral Findr, manual scroll, Taplio (LinkedIn) |
| 3 | Categorize by format (thread, carousel, short video, long-form) | Spreadsheet |
| 4 | Tag recurring patterns: hooks, structures, topics, CTAs | Manual analysis |
| 5 | Identify the distribution channels where those posts travel | Check reposts, quote tweets, newsletter mentions |
| 6 | Build your content templates from the patterns that repeat | Template library |
| 7 | Test 10 pieces using those templates with your own expertise | Publish and measure |
| 8 | Double down on the formats and topics that outperform your baseline | Data-driven iteration |
### What to Look For in Top-Performing Content
| Pattern | Why It Works | How to Adapt |
|---|---|---|
| Personal story + lesson | Builds trust faster than abstract advice | Use your own founder journey, not hypotheticals |
| Contrarian takes | Breaks the scroll by challenging assumptions | Only take positions you genuinely hold |
| Data-backed claims | Creates shareability and perceived authority | Pull from your product data, customer results, or industry reports |
| Step-by-step frameworks | High save rate because of perceived utility | Turn your actual processes into numbered frameworks |
| Before/after transformations | Visual proof of value | Use customer screenshots, metric changes, workflow comparisons |
### Audience Research Stack
| Tool | What It Reveals | Cost |
|---|---|---|
| SparkToro | Which accounts, podcasts, and sites your audience follows | Free tier available |
| Social Blade | Growth trends for competitor accounts (anomalies signal viral content) | Free |
| Viral Findr | Aggregated top-performing content by account | Paid |
| Taplio | LinkedIn-specific analytics and content discovery | Paid |
| X Advanced Search | Filter by engagement thresholds, date range, account | Free |
| BuzzSumo | Content performance by topic, domain, and social shares | Paid |
---
## 3. Multi-Platform Content Repurposing Framework
One pillar piece should become 10+ platform-native derivatives. This is not copy-paste. Each platform has its own format, tone, and algorithm. The goal is to maintain the core insight while adapting the delivery.
### The Pillar-to-Platform Map
```
+------------------+
| PILLAR CONTENT |
| (Newsletter, |
| Long Video, or |
| Long-Form Post) |
+--------+---------+
|
+--------------------+--------------------+
| | | | |
+---------+ +------+ +--------+ +-------+ +--------+
|LinkedIn | | X | |YouTube | |Email | |Podcast |
|3-4 posts| |5-8 | |1 long | |Weekly | |1 ep or |
|per week | |posts | |+ 3-5 | |send | |clips |
| | |daily | |Shorts | | | | |
+---------+ +------+ +--------+ +-------+ +--------+
```
### Platform-Specific Adaptation Rules
| Platform | Format | Tone | Algorithm Priority | Posting Cadence |
|---|---|---|---|---|
| LinkedIn | Text posts (1200-1500 chars), carousels, newsletters | Professional but personal, story-driven | Dwell time, comments, reposts | 3-5x/week |
| X (Twitter) | Single posts, threads (3-7 posts), quote tweets | Sharp, concise, opinionated | Replies, bookmarks, reposts | 2-3x/day |
| YouTube | Long-form (8-15 min) + Shorts (30-60 sec) | Educational, high production value | Watch time, CTR on thumbnails | 1-3x/week |
| Newsletter | 800-1500 words, one clear takeaway per issue | Conversational, direct, personal | Open rate, click rate | 1-2x/week |
| Podcast | 20-45 min episodes or guest appearances | Conversational, deep-dive | Completion rate, subscriber growth | 1x/week |
### The 4-Hour Weekly Content SysteRelated 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".