content-strategy-saas
This skill should be used when the user asks to "build a content strategy", "create a content plan for SaaS", "design a content engine", "plan content marketing for B2B", "build a content program", "create a content roadmap", "set up content operations", "plan what content to publish", or any variation of building or designing a content marketing strategy for a B2B SaaS company.
Content Strategy for SaaS
A B2B SaaS content strategy is a system that turns expertise into pipeline. Not a blog calendar. Not a list of topics. A system with clear inputs (ICP pain, search demand, competitive gaps), clear outputs (pages that rank, convert, and get cited), and a feedback loop that tells you what's working.
Most SaaS content programs fail because they produce content without a thesis. They publish "Top 10 Tips" posts that rank for nothing, convert no one, and build no authority. This skill builds the opposite: a focused content engine tied to revenue.
The Content Strategy Stack
Build in this order. Each layer depends on the one below it.
| Layer | What it answers | Output |
|---|---|---|
| 1. ICP Pain Map | What problems does our buyer actually have? | 10-15 pain statements ranked by urgency |
| 2. Query Mapping | What do they search when they have those problems? | Keyword clusters mapped to pain statements |
| 3. Content-Market Fit | Where are the gaps competitors haven't filled? | Priority topic list with difficulty scores |
| 4. Page Architecture | What page types serve each intent? | Page type × topic matrix |
| 5. Production System | How do we produce at quality and pace? | Workflow, roles, cadence, tooling |
| 6. Distribution Plan | How does content reach the buyer? | Channel × content type matrix |
| 7. Measurement | Is it working? | Dashboard with leading and lagging indicators |
Layer 1: ICP Pain Map
Content strategy starts with buyer pain, not keywords. Keywords are an expression of pain — start with the pain itself.
Process:
- Pull 10 recent sales call transcripts (won and lost). Extract every problem the buyer described in their own words
- Interview 3-5 customers. Ask: "What were you doing before us? What was broken? What finally made you look for a solution?"
- Read G2/Capterra reviews of competitors. Negative reviews reveal unmet needs. Positive reviews reveal what the market values
- Scan relevant subreddits, Slack communities, LinkedIn comments for unprompted complaints
Output format:
| Pain statement (buyer's words) | Urgency | Frequency | Our fit |
|---|---|---|---|
| "We're spending 3 hours/day on manual data entry between tools" | High | 8/10 calls | Strong |
| "Our reps don't know which leads to call first" | High | 7/10 calls | Strong |
| "We can't tell which marketing channels actually drive pipeline" | Medium | 5/10 calls | Medium |
Rules:
- Use the buyer's language, not your marketing language. "Manual data entry between tools" not "lack of workflow automation"
- Rank by urgency × frequency. High urgency + high frequency = content priority 1
- Never skip this step. Content built on assumed pain produces content no one searches for
Layer 2: Query Mapping
Map each pain statement to the queries buyers type when they have that pain.
Query types for SaaS:
| Query type | Intent | Example | Content fit |
|---|---|---|---|
| Problem-aware | "I have this problem" | "how to reduce manual data entry" | Blog post, guide |
| Solution-aware | "I know solutions exist" | "best data integration tools" | Listicle, comparison |
| Product-aware | "I'm evaluating specific tools" | "Zapier vs Make" | Comparison page |
| Purchase-ready | "I'm ready to buy" | "Zapier pricing 2026" | Pricing, demo page |
Process:
- Take each pain statement → brainstorm 5-10 queries a buyer might type
- Validate with keyword research (Ahrefs, Semrush, Google Search Console)
- Add AI search queries — what would someone ask ChatGPT or Perplexity? These often differ from Google queries (longer, more conversational, more specific)
- Cluster queries by topic. Each cluster = one content piece or page
Rules:
- Cover all four query types. Most SaaS content programs over-index on problem-aware (blog posts) and ignore solution-aware and product-aware (the queries that actually convert)
- Always include AI search queries. "What's the best tool for X" asked in Perplexity is a different optimization target than the same query in Google
Layer 3: Content-Market Fit
Not every topic is worth publishing. Score each topic cluster before committing resources.
| Factor | Low (1) | Medium (2) | High (3) |
|---|---|---|---|
| Pain alignment | Tangential to ICP | Related to ICP pain | Directly addresses top-3 ICP pain |
| Search demand | < 100 monthly searches | 100-1,000 | 1,000+ |
| Competitive gap | 5+ strong pages exist | 2-4 strong pages | 0-1 strong pages or all are outdated |
| Conversion potential | Awareness only | Consideration stage | Decision stage, high purchase intent |
| AI search potential | AI engines rarely answer this | Sometimes cited | High-frequency AI query with few good sources |
| Internal expertise | We'd need to research from scratch | We know the space | We have proprietary data or unique POV |
Score ≥ 14: Publish immediately. 10-13: Publish in next quarter. Below 10: Skip or deprioritize.
Layer 4: Page Architecture
Different queries need different page types. Never write a blog post when the query needs a comparison page.
| Query intent | Best page type | Structure |
|---|---|---|
| "What is X?" | Definition / glossary page | Definition → subtypes → examples → FAQ |
| "How to do X" | How-to guide | Steps → tools → common mistakes |
| "Best X tools" | Listicle | Ranked list → comparison table → selection criteria |
| "X vs Y" | Comparison page | Summary → feature table → use cases → verdict |
| "X alternatives" | Alternatives page | Why switch → alternatives table → selection criteria |
| "X pricing" | Pricing page | Plans table → what's included → FAQ |
| "X case study" | Case study | Challenge → solution → results (with numbers) |
| "X for [industry]" | Use case page | Industry pain → how product fits → examples |
Rules:
- Match page type to intent exactly. A "what is X?" query answered with a sales page bounces
- One page per query cluster. Don't split a topic across 3 blog posts when one definitive page performs better
- Comparison and alternatives pages convert 3-5x higher than blog posts. Prioritize them
Layer 5: Production System
Content quality at speed requires a system, not heroics.
Roles
| Role | Responsibility | Who |
|---|---|---|
| Strategist | Topic selection, brief writing, editorial calendar | Marketing lead or content lead |
| Writer | First draft from brief | In-house, freelance, or AI + human editor |
| SME reviewer | Accuracy, depth, original insight | Internal expert (product, sales, CS) |
| Editor | Quality, clarity, brand voice, AEO compliance | Content lead or senior writer |
| Publisher | SEO metadata, schema markup, formatting, CMS upload | Content ops or marketing ops |
Cadence
| Company stage | Minimum output | Focus |
|---|---|---|
| Pre-PMF (< $1M ARR) | 2-4 pages/month | Category definition, comparison pages, 1-2 how-tos |
| Growth ($1-10M ARR) | 6-10 pages/month | Full page type coverage, pSEO templates, content refresh |
| Scale ($10M+ ARR) | 10-20 pages/month | pSEO at scale, thought leadership, international/localized content |
AI in the production workflow
| Step | AI role | Human role |
|---|---|---|
| Topic selection | Suggest gaps from competitive analysis | Final prioritization based on strategy |
| Brief writing | Generate draft brief from template | Refine angle, add proprietary insights |
| First draft | Generate 70-80% of the draft | Never publish AI-only. Always add original data, POV, examples |
| Editing | Grammar, clarity, AEO compliance checks | Voice, accuracy, depth, strategic alignment |
| Schema markup | Generate structured data | Validate and test |
Never publish AI-generated content without human review and enrichment. AI produces competent, generic content. What ranks — in both Google and AI search — is content with proprietary data, a distinct POV, or expert insight that AI can't generate on its own.
Layer 6: Distribution Plan
Publishing is not distribution. Every piece needs a distribution plan.
| Channel | Best for | Cadence |
|---|---|---|
| Organic search (SEO + AEO) | Evergreen content, comparison pages, how-tos | Continuous (publish → rank → maintain) |
| LinkedIn (company + founder) | POV content, original research, case studies | 3-5 posts/week repurposing long-form content |
| Email newsletter | Engaged audience, nurture content | Weekly or bi-weekly |
| Sales enablement | Case studies, comparison pages, ROI calculators | On-demand, integrated into CRM |
| Community (Reddit, Slack, Discord) | How-to content, genuine problem-solving | 2-3 thoughtful contributions/week (never spam) |
| Syndication / guest posts | Backlinks, entity building, GEO | 1-2/month on high-DA sites in your space |
Rules:
- Every page gets at least 2 distribution channels beyond organic search
- Comparison pages and case studies go to sales team on publish day
- LinkedIn distribution is not "check out our new blog post." It's taking one insight from the piece and writing a standalone post around it
Layer 7: Measurement
Leading indicators (weekly)
| Metric | Target | Action if below |
|---|---|---|
| Pages published vs plan | 90%+ of planned output | Diagnose bottleneck: briefs, writing, review, or publishing |
| Avg time from brief to publish | < 10 business days | Tighten review loops |
| Pages with schema markup | 100% of new pages | Add to publishing checklist |
Lagging indicators (monthly)
| Metric | Target | Action if below |
|---|---|---|
| Organic traffic growth | 10-15% MoM for first year | Audit keyword targeting, refresh underperforming pages |
| AI search citations | Top-3 cited for 10+ core queries | Run AEO audit on uncited pages |
| Content-sourced pipeline | 20-30% of total pipeline | Check conversion paths, add CTAs to high-traffic pages |
| Conversion rate (page → demo/signup) | 1-3% for blog, 5-10% for comparison pages | CRO audit on high-traffic low-converting pages |
Never measure content by volume alone. 50 blog posts that generate zero pipeline is worse than 10 comparison pages that generate 30% of pipeline.
Pre-Launch Checklist
Before launching or relaunching a content program:
- [ ] ICP pain map completed from real sales calls and customer interviews
- [ ] Query map covers all four intent types (problem, solution, product, purchase)
- [ ] Content-market fit scored for top 20 topics
- [ ] Page type mapped to each priority topic
- [ ] Production workflow defined with clear roles and SLAs
- [ ] AI content policy defined (where AI helps, where humans own)
- [ ] Distribution channels identified per content type
- [ ] Measurement dashboard built with leading and lagging indicators
- [ ] AEO checklist integrated into publishing workflow
- [ ] Sales team knows where to find content for deals
- [ ] Content calendar built for first 90 days
- [ ] Competitive content audit completed (what are competitors publishing, what's missing?)
Anti-Pattern Check
- Publishing 3 blog posts/week with no strategic framework → Stop. Build the pain map and query map first. Volume without direction is noise
- All content is TOFU (top of funnel) → Shift 40-50% of output to MOFU/BOFU page types: comparisons, alternatives, case studies, use case pages. These convert
- No one from product or sales reviews content → Content without SME input is generic. Build a 15-minute SME review into every production cycle
- Content strategy doc exists but no one follows it → Strategy is the system, not the doc. If the production workflow isn't running, the strategy is decoration
- Measuring success by organic traffic alone → Traffic without pipeline is a vanity metric. Track content-sourced pipeline and conversion rate by page type
- Treating AI search as separate from content strategy → AEO is not a separate initiative. It's a quality standard applied to every page. Integrate AEO checks into the publishing workflow
- Never refreshing published content → 30% of content value comes from updates. Build a quarterly refresh cycle for top-performing pages
- No content for the sales team → If sales can't use your content in deals, you're only doing marketing, not revenue content. Publish comparison pages and case studies that sales sends to prospects
Want agents that use skill files like this?
We customize skill files for your brand voice and methodology, then run content agents against them.
Book a call