⚡ Promptolis Original · Marketing & Content

📝 Content Marketing Strategy Builder — 90-Day Plan That Actually Drives Pipeline

The structured content marketing strategy — covering audience research, topic cluster selection, content format + cadence design, distribution strategy, and the leading-indicator measurement framework that distinguishes content-generating-revenue from content-for-content's-sake.

⏱️ 6 hours strategy + ongoing execution 🤖 ~2 min in Claude 🗓️ Updated 2026-04-20

Why this is epic

Most content marketing fails because there's no strategy — just 'we should blog more.' This Original produces the structured 90-day content plan: audience research, topic clusters, format + cadence, distribution engine, and measurement that ties content to pipeline.

Names the 5 content-marketing failure patterns (random topics / generic SEO / no distribution / no measurement / founder-centric) + structural fixes. Most companies have 2-3 of these failure patterns simultaneously.

Produces complete strategy: audience personas, topic cluster map (hub + spoke model), 90-day editorial calendar, distribution + repurposing workflow, measurement dashboard, and scaling plan. Based on HubSpot + Ahrefs + empirical patterns from content-led B2B growth.

The prompt

Promptolis Original · Copy-ready
<role> You are a content marketing strategist with 15 years of experience building content programs at SaaS companies $5M-$500M ARR. You've produced content programs that drove $30M+ in attributable pipeline. You draw on HubSpot methodology, Ahrefs SEO research, Animalz content strategy, and empirical patterns from content-led B2B success (Intercom, Wistia, Klaviyo). You are direct. You will name when strategy is 'more blog posts,' when distribution is missing, when measurement is superficial, and when voice is generic company-speak. </role> <principles> 1. 20% creation + 80% distribution. Most teams invert. 2. Topic clusters beat random topics. 3-5 clusters = topical authority. 3. SEO + social + newsletter + community = multiple channels. 4. Leading indicators monthly, pipeline quarterly. 5. Repurpose aggressively. One article → 5+ formats. 6. 90 days: 1-2 clusters deep vs. breadth everywhere. 7. Individual author voices > company blog voice. 8. Consistency > frequency. Weekly forever > 3x/week for 6 months. </principles> <input> <business-context>{stage, ACV, ICP}</business-context> <current-content>{what you publish now, cadence, performance}</current-content> <audience-research}>{what you know about buyers}</audience-research> <competitive-content>{what competitors publish}</competitive-content> <resources>{team size, budget, capacity}</resources> <goals>{pipeline, brand, SEO, specific targets}</goals> <timeline>{launch target}</timeline> <differentiators>{unique perspective, expertise}</differentiators> </input> <output-format> # Content Strategy: [Business summary] ## Audience Research + Personas Buyer understanding. ## Topic Cluster Map 3-5 clusters with hub + spoke. ## Content Format Strategy Blog, newsletter, podcast, video, social. ## 90-Day Editorial Calendar Week-by-week. ## Distribution Engine How content reaches audience. ## Repurposing Workflow One article → multi-format. ## Measurement Dashboard Leading + lagging indicators. ## Team + Workflow Who produces what. ## Scaling Plan Quarter 2 and beyond. ## Key Takeaways 5 bullets. </output-format> <auto-intake> If input incomplete: ask for business context, current content, audience, competitive, resources, goals, timeline, differentiators. </auto-intake> Now, design:
🚀 Open in ChatGPT ✨ Open in Claude 💎 Open in Gemini

Example: input → output

Here's how this prompt actually performs. Real input below, real output from Claude Opus 4.

📝 Input
<business-context>B2B SaaS, $12M ARR, 30% growth target. Product: AI code review platform. ICP: VPs Eng + CTOs at 100-500 employee tech companies. ACV: $60K-$200K.</business-context>
<current-content>Inconsistent blog — 2 posts/month avg. Random topics (tool announcements, generic 'code quality' posts). 800 monthly visitors. Zero attributable pipeline last 6 months.</current-content>
<audience-research>VPs Eng care about: shipping velocity, engineer retention, technical debt, AI tools impact on engineering. They read Lenny's Newsletter, Pragmatic Engineer, Engineering Enablement. Active on LinkedIn. Attend DevOps + eng-leader conferences.</audience-research>
<competitive-content>Competitors: weak content. Space has good technical blogs (thoughtworks, netflix) but few from direct competitors. Big opportunity to own engineering-leadership content.</competitive-content>
<resources>1 content manager (mid-level). $120K annual content budget. CTO + VP Product willing to author. Can hire freelance writers.</resources>
<goals>(1) Source 20% of pipeline from content within 12 months. (2) Drive enterprise-level demand (currently SMB-heavy). (3) Build thought-leadership in eng-leadership space.</goals>
<timeline>Launch new strategy Jan 2026. 12-month ramp to full measurement.</timeline>
<differentiators>CTO (Maria) has unique perspective — previous engineering leader at 2 unicorns. Deep credibility. Currently under-leveraged in content.</differentiators>
🤖 Output

Content Strategy: B2B SaaS AI Code Review, $12M ARR, Engineering-Leader Audience, 90-Day Launch

A content marketing strategy produces structured plan tying content to pipeline rather than 'we should blog more.' Based on content-led B2B growth patterns (Intercom, Klaviyo, Wistia), successful content programs share 4 traits: topic cluster focus (not random), expert author voices (not company blog), distribution-first thinking (20/80 creation/distribution), leading-indicator measurement. Your situation — underused CTO credibility, competitive content gap, audience identified — is ideal for content-led enterprise pipeline build. This strategy produces: 3 topic clusters, CTO-Maria-led authorship, 90-day editorial calendar, distribution engine, measurement dashboard, 12-month ramp to 20% pipeline attribution.

Audience Research + Personas

Primary Persona: VP Engineering (Priya)

  • 35-50 years old, 8-15 years engineering experience
  • Leads 30-100 engineers at 100-500 employee company
  • Cares about: velocity, retention, technical debt, AI tool leverage, career growth
  • Consumes: Lenny's Newsletter, Pragmatic Engineer, podcasts, LinkedIn
  • Buyer behavior: researches for 3-6 months before evaluating tools

Secondary Persona: CTO (Oleg)

  • 40-55 years old, 15+ years experience
  • Oversees VP Engineering, strategic tech decisions
  • Cares about: engineering org effectiveness, talent retention, strategic bets, board narrative
  • Consumes: podcasts, eng-leadership books, industry analyst reports
  • Buyer behavior: influences purchase, approves budget, less hands-on research

Tertiary Persona: Senior Engineer (Rajiv)

  • 5-15 years experience, technical influencer
  • Cares about: code quality, personal growth, tool UX, engineering culture
  • Evaluates tools, has buying influence (not buying power)
  • Consumes: technical blogs, Hacker News, Twitter/X, Discord

Topic Cluster Map

3 Topic Clusters (Hub + Spoke Model):

Cluster 1: Engineering Velocity at Scale (PRIMARY)

Hub article: 'The Complete Guide to Engineering Velocity at 100-500 Engineer Scale'

Spoke articles (10-15 in cluster):

  • 'Why code review is the #1 velocity killer at Series B'
  • '5 signals your PR process is broken'
  • 'How Linear shipped 30% faster: case study'
  • 'The async code review playbook'
  • 'Data: PR merge time benchmarks by team size'
  • 'Killing meetings vs. adding them: engineering velocity'
  • 'The maker-vs-manager schedule for engineering leaders'
  • (and more)

Why this cluster: directly aligned with product value + highest buyer intent + CTO's expertise area.

Cluster 2: Engineering Leadership (SECONDARY)

Hub article: 'The 2026 Engineering Leader's Playbook'

Spoke articles:

  • 'First-time VP Engineering: 90-day plan'
  • 'Scaling engineering teams from 30 to 300'
  • 'How to build an engineering culture that retains senior talent'
  • 'The 1:1 framework for engineering leaders'
  • 'Dealing with engineering attrition: patterns + interventions'
  • (more)

Why this cluster: top-of-funnel engagement with VP Engineering audience + positions CTO Maria as thought leader.

Cluster 3: AI in Engineering Workflows (STRATEGIC)

Hub article: 'How AI Is Reshaping Engineering Workflows in 2026'

Spoke articles:

  • 'AI code review: state of the art + practical reality'
  • 'GitHub Copilot vs. dedicated AI tools: what works where'
  • 'Building an AI-augmented engineering team'
  • 'The AI coding tool buyer's checklist'
  • (more)

Why this cluster: positions product in AI conversation + captures AI-tool research intent + forward-looking brand.

Content Format Strategy

Primary format: Long-form essays (2,500-4,000 words)

  • Why: high-trust audience rewards depth
  • Cadence: weekly
  • Author mix: CTO Maria (50%), CTO Maria + guest (30%), freelance expert (20%)

Secondary format: Data-driven research posts (3,000-5,000 words, quarterly)

  • Why: benchmarks + data highly shareable + linkable
  • Cadence: quarterly
  • Example: 'PR merge time benchmarks across 200 Series B-C engineering teams'

Tertiary formats:

  • Podcast ('Engineering Velocity' — launch Q2): CTO interviews peer CTOs. Bi-weekly.
  • Newsletter ('The Engineering Leader'): curated + original content. Weekly.
  • Video (YouTube): 10-min explanations of complex topics. Bi-weekly from Q2.
  • LinkedIn posts: daily from CTO (3x/week) + company page (2x/week)

90-Day Editorial Calendar

Week 1-4 (Foundation)

Week 1: Hub article Cluster 1 ('Complete Guide to Engineering Velocity at Scale') — 4,500 words, CTO Maria authored

Week 2: Spoke — 'Why code review is the #1 velocity killer' (author: CTO Maria, 2,500 words)

Week 3: Spoke — 'Data: PR merge time benchmarks by team size' (3,500 words, original research)

Week 4: Guest post — interview with Linear's CTO on their velocity story (2,500 words, guest-CTO voice)

Week 5-8 (Cluster 1 depth)

Week 5-8: 4 more Cluster 1 spokes — async review playbook, PR process audit, 5 signals PR broken, maker-vs-manager for eng leaders

Week 9-12 (Start Cluster 2)

Week 9: Hub Cluster 2 ('2026 Engineering Leader's Playbook')

Week 10-12: 3 Cluster 2 spokes — first-time VP Eng, scaling eng teams, retaining senior talent

Cadence: 1 article/week. 90-day total: 12 articles.

Distribution Engine (80% of Effort)

Per-article distribution (every article):

Immediate (Day 0-7):

  • Publish on company blog
  • Email to newsletter subscribers
  • LinkedIn post from CTO Maria (with key quote + link)
  • LinkedIn post from company page
  • Cross-post on Medium/Substack
  • Twitter/X thread (5-7 tweets with key insights)
  • Slack groups where VP Eng audience hangs out (with value framing, not spam)

Week 2:

  • Newsletter feature in next edition
  • Mention in LinkedIn comments on relevant posts

Week 3-4:

  • Repurpose into short video (Loom or YouTube)
  • Reddit discussion (r/ExperiencedDevs, r/programming) if genuinely relevant
  • Hacker News submission (carefully timed)

Ongoing:

  • Monthly: top 3 articles of past quarter featured in email blast
  • Integrate into sales enablement materials

Paid amplification:

  • Best-performing articles: $500-2000 LinkedIn promotion
  • Target VP Engineering + CTO at target account list

Repurposing Workflow

One 3,000-word article → 8+ pieces of content:

1. Long-form blog post

2. Newsletter feature (excerpt)

3. LinkedIn post from CTO (key quote + CTA)

4. LinkedIn post from company (summary + graphic)

5. Twitter thread (7-10 tweets)

6. Short video (5-10 min talking through article)

7. Podcast episode discussion (when relevant)

8. Sales enablement asset (1-page summary for AEs)

Time investment: article 8-12 hrs + repurposing 2-4 hrs = ~15 hrs total for 8 pieces of content.

Most teams only do #1 + #3. 8x leverage missed.

Measurement Dashboard

Leading indicators (monthly):

  • Traffic: unique monthly visitors (target: 800 → 5,000 in 12 months)
  • Engagement: avg time on page (target: 3+ min), scroll depth (target: 65%+)
  • Distribution reach: LinkedIn impressions, newsletter opens, podcast downloads
  • Subscriber growth: newsletter subs, LinkedIn followers
  • Domain authority: Ahrefs DR or similar (target: 30 → 50)

Middle indicators (quarterly):

  • MQLs from content (target: 50 → 200/quarter by Q4)
  • Content-sourced pipeline contribution (target: 10% → 25%)
  • Brand mentions + backlinks
  • Email list growth (target: 500 → 3,000)

Lagging indicators (quarterly/annual):

  • Content-attributable ARR
  • CAC contribution
  • Time-to-first-contact (content should accelerate this)

Dashboard tools:

  • Google Analytics / Plausible
  • HubSpot (for MQL attribution)
  • Ahrefs (SEO)
  • LinkedIn Analytics
  • Newsletter platform (Substack/Beehiiv metrics)

Team + Workflow

Team structure:

  • Content Manager (you): strategy + editorial + quality + distribution oversight
  • CTO Maria: primary author, 1-2 articles/month (~15 hrs/month)
  • VP Product (Alex): guest author, 1 article/quarter
  • Freelance writers (2-3 on retainer): research + draft support, ghostwriting from CTO interviews
  • Designer (contract): graphics + visualizations, $30/article
  • Video editor (contract): starting Q2

Workflow per article:

1. Week -3: Topic selection (from cluster map) + outline review with author

2. Week -2: Draft by author (or ghostwriter from interview)

3. Week -1: Editorial review + graphics design + SEO optimization

4. Week 0: Publish + distribution launch

5. Week +1: Amplification + engagement

6. Week +2: Repurposing into other formats

7. Week +4: Performance review + learnings

Scaling Plan (Beyond 90 Days)

Quarter 2 (Months 4-6):

  • Add podcast ('Engineering Velocity')
  • Start YouTube channel
  • Begin Cluster 3 (AI in Engineering)
  • Total content output: 13 blog articles + 6 podcast episodes + 6 videos

Quarter 3 (Months 7-9):

  • Launch newsletter-specific original content
  • First major research report
  • Speaker circuit for CTO (3-5 conferences/year)
  • Content cadence: 15 articles + 6 podcast + 12 videos

Quarter 4 (Months 10-12):

  • Annual research report (industry benchmarks)
  • Sponsored content partnerships with complementary brands
  • 2-week 'content sprint' for strategic topic
  • Measure + report 12-month outcomes

Year 2+:

  • Expand team: dedicated content writer + video producer
  • Event content strategy
  • Paid content distribution at scale
  • Target: 30%+ of pipeline from content

Key Takeaways

  • 3 topic clusters: engineering velocity at scale (primary), engineering leadership (secondary), AI in engineering (strategic). Depth in clusters vs. breadth in random topics.
  • CTO Maria as primary author voice. Her 2-unicorn background + expertise is the differentiator. Individual author voice outperforms 'company blog' voice 3-5x.
  • Distribution is 80% of effort. Every article gets 8-piece repurposing (blog + newsletter + LinkedIn + Twitter thread + video + podcast + sales enablement + paid amplification).
  • 90-day foundation: 12 articles, Cluster 1 depth + start Cluster 2. Leading indicators monthly (traffic + engagement + subs), pipeline attribution quarterly.
  • 12-month target: 20% of pipeline from content + 5,000 monthly visitors + thought-leadership position in eng-leadership space. Structural investment in CTO's expertise + consistent execution.

Common use cases

  • B2B SaaS companies launching content marketing
  • Existing content programs underperforming
  • Startups pre-revenue wanting content-led growth
  • Marketing teams redesigning content strategy
  • Solo founders building thought-leadership presence
  • Agencies serving client content strategy needs

Best AI model for this

Claude Opus 4 or Sonnet 4.5. Content strategy requires audience research + SEO + editorial + distribution thinking. Top-tier reasoning matters.

Pro tips

  • Content marketing is 20% creation, 80% distribution. Most teams invert this. Great content with no distribution = zero value.
  • Topic clusters beat random topics. Pick 3-5 clusters = your topical authority. Random blog posts fragment signal.
  • SEO alone isn't content strategy. SEO is one channel. Social, newsletter, podcast, community = other channels.
  • Measure leading indicators (time-on-page, scroll depth, shares, subscribes) monthly. Pipeline metrics quarterly. Don't only measure conversion.
  • Repurpose aggressively. One great article → newsletter, LinkedIn, tweet thread, podcast episode, 3 short videos. 5x leverage.
  • First 90 days focus on 1-2 topic clusters. Scaling breadth before depth = shallow everywhere.
  • Author voice matters. 'Company blog voice' is dead. Individual expert voices perform 3-5x better in 2026.
  • Publishing consistency beats publishing frequency. 1 great article/week forever > 3 mediocre articles/week for 6 months.

Customization tips

  • Start with 1-2 clusters, not 5. Depth beats breadth in early content marketing. Year 2+ expand to more clusters.
  • Invest in CTO/founder content authorship. Individual voice outperforms company voice. Budget for ghostwriter support to remove time burden.
  • Measure distribution carefully. Track which channels produce MQLs. Double-down on working channels, kill failing ones.
  • Publish consistently. 1 article/week forever beats 3 articles/week for 6 months. Rhythm matters for audience trust.
  • After 6 months, do full content audit. Which articles drove pipeline? Double down on similar topics. Which failed? Understand why.

Variants

B2B SaaS Mode

For SaaS content marketing. Emphasizes topic clusters + SEO + enterprise audiences.

DTC/E-commerce Mode

For consumer brands. Emphasizes social + influencer + lifestyle content.

Thought-Leader Mode

For founders building personal brand + company content.

Technical/Developer Mode

For developer audiences. Emphasizes technical depth + community + code.

Frequently asked questions

How do I use the Content Marketing Strategy Builder — 90-Day Plan That Actually Drives Pipeline prompt?

Open the prompt page, click 'Copy prompt', paste it into ChatGPT, Claude, or Gemini, and replace the placeholders in curly braces with your real input. The prompt is also launchable directly in each model with one click.

Which AI model works best with Content Marketing Strategy Builder — 90-Day Plan That Actually Drives Pipeline?

Claude Opus 4 or Sonnet 4.5. Content strategy requires audience research + SEO + editorial + distribution thinking. Top-tier reasoning matters.

Can I customize the Content Marketing Strategy Builder — 90-Day Plan That Actually Drives Pipeline prompt for my use case?

Yes — every Promptolis Original is designed to be customized. Key levers: Content marketing is 20% creation, 80% distribution. Most teams invert this. Great content with no distribution = zero value.; Topic clusters beat random topics. Pick 3-5 clusters = your topical authority. Random blog posts fragment signal.

Explore more Originals

Hand-crafted 2026-grade prompts that actually change how you work.

← All Promptolis Originals
P

Curated by

Every Promptolis Original is hand-crafted and reviewed before publishing — built from scratch for 2026-grade LLMs.

Last reviewed on · About Promptolis