Building a B2B SaaS Content Programme That Compounds

Industry: B2B SaaS · Engagement: Multi-month content programme · Services: Content strategy, blog writing, SEO content

Last reviewed on 2026-05-12.

About this case study. This is an anonymised, illustrative example of how a content programme of this shape gets built. Client names, exact metrics, and proprietary results have been removed. The value here is in the structure of the engagement, not in the specifics of any one client outcome.

The setup

A mid-market B2B SaaS platform — established product, paying customers, decent technology — that was effectively invisible in organic search. The company's competitors were category leaders with much larger content teams and longer publishing histories. The internal team had tried to run a blog in spurts but had not been able to keep up a consistent cadence, and there was no clear plan for what the blog was supposed to accomplish.

The starting state

A blog with a handful of old posts on broad topics, none of which were ranking
A flat topic structure: every post was a top-level page, none were linked together as a cluster
No keyword research informing what got written
No editorial calendar; posts went up when someone had time
Sales and marketing teams operating in separate worlds, with little signal flowing between them

What was getting in the way

Larger competitors dominated head terms — directly competing on those was unlikely to pay off in any reasonable timeframe.
The product was technical enough that surface-level content would not differentiate it; depth was a requirement, not a nice-to-have.
The sales cycle was long, which meant a single blog post rarely drove a deal, and attribution was muddy.

The approach

Rather than try to outrun the category leaders on broad terms, the programme was built around three principles.

1. Find the cracks larger competitors had not filled

A content gap analysis surfaced hundreds of high-intent, low-competition queries that the big players had left alone — usually because individually they did not look big enough to justify the work, but collectively they represented serious traffic. The patterns that emerged:

Integration content. "How to use [product] with [other tool you already use]" queries. Always specific, always written by someone evaluating a real workflow.
Industry-specific framing. "[Product category] for law firms", "for non-profits", "for agencies". Same core product, but a buyer reading the generic page would not see themselves in it.
Comparison content. "[Competitor] vs [other competitor]", "[Competitor] alternatives". Late-funnel queries that bring in people who are already shopping.
Pain-point content. "Why [common problem] keeps happening" — content that meets the reader before they have decided what tool would even solve it.

2. Build clusters, not orphans

Each pillar topic got a hub page with five to ten supporting posts, all internally linked. This structure makes it easier for search engines to understand topical authority and easier for readers to navigate from a narrow question to the broader answer.

3. Production system, not heroic effort

A four-week production cycle replaced the previous start-stop pattern: keyword research and outlining in week one, expert interviews and drafting in week two, editing and SEO review in week three, publish and promotion in week four. Each role had a single owner. The programme started small (a handful of posts per month) and scaled up only after the workflow proved sustainable.

How execution unfolded

Phase 1 — foundation

Content audit of the existing blog; the worst posts were updated or merged, not deleted, to preserve any equity
A topic map drafted around three pillar areas relevant to the product
First batch of cornerstone articles published, with internal links pointing back to product pages where natural

Phase 2 — scale

Publishing cadence increased once the workflow was running cleanly
The integration content series launched; each piece followed the same template so production stayed efficient
Internal linking was treated as a deliverable on every post, not an afterthought

Phase 3 — optimise

The earliest posts were revisited and improved based on actual ranking data
Comparison and alternatives pages were added once the team had a clearer view of which competitors were drawing search demand
Content upgrades — downloadable templates, calculators — were added to the highest-traffic pages to improve conversion

What worked, in general terms

Long-tail focus. Specific queries brought in fewer visitors per page but a much higher proportion of buyers.
Integration content. Became one of the strongest pillars — quick to write, quick to rank, directly relevant to buying decisions.
Internal linking discipline. The flywheel effect of clusters showed up several months in. Pages started lifting each other.
Consistent publishing. Predictability beat volume. Less swing, more compounding.

What was harder than expected

Translating technical depth without losing readability. The first drafts of some pieces tried to do too much. Editing got firmer about scoping a piece around a single question.
Sales-marketing handoff. Sales had years of objection-handling language that should have been informing content earlier. Building that loop took a deliberate effort.
Defining success. Traffic, MQLs, pipeline, closed revenue — each gives a different picture, and the right framing took time to settle.

Reading this case study

Two things to keep in mind when reading any case study, including this one:

Results are not transferable. The same content strategy, on a different site, in a different category, with different sales motions, produces different outcomes. Use these examples to understand the shape of the work, not as a prediction.
Content is one input. Search outcomes also depend on technical SEO, site authority, link profile, and competitor activity. Content writing is necessary, not sufficient.

Where to read more

For a deeper view into the underlying decisions: