Content strategy for B2B tech: where to start

Most B2B tech companies do not need more content. They need a strategy that decides what to stop writing, what to write deliberately and what to expand into a long-running asset. Without that, you end up with a blog full of one-off posts, a few stale whitepapers and a sales team that quietly stopped sharing the link to the resource hub.

We have built content programmes for MSPs, SaaS vendors and ERP consultancies, and the brief almost always lands in the same place. The marketing team is busy. Output is steady. Pipeline contribution from organic and earned channels is hard to explain. The fix is not a fresh content calendar. It is a sharper definition of what the programme exists to do, who it is for and how it gets measured. Here is where we start.

Anchor the programme to a business question

Before we write a brief, we ask the marketing lead to finish one sentence. “Our content programme exists to help us…” The honest answers are usually some version of: shorten the sales cycle for mid-market deals, win more inbound demos from technical buyers, or build credibility with IT directors so the brand stops being a stranger when sales reaches out.

That single sentence shapes everything else. A programme that exists to shorten the sales cycle leans into comparison content, technical case studies and pricing guidance. A programme that exists to build credibility leans into opinion pieces, original research and long-form explainers. We have seen plenty of teams try to do both with the same six pieces of content a month, and the work ends up serving neither audience well.

Audit what you already have, ruthlessly

Most of the content programmes we inherit have between 80 and 400 pages of legacy content. About a fifth of it is doing real work. The rest is either thin, off-strategy or duplicating something better elsewhere on the site.

Our editorial team typically starts with a spreadsheet pulled from GA4 and Search Console. We score each URL on three things: does it rank for something a buyer would search, does it speak to a specific audience and is it factually current. Pages that fail all three get archived or redirected. Pages that fail one get rewritten. Pages that pass all three become the spine of the new programme. We covered the wider workflow in our guide to editorial calendars for tech marketing teams, and the audit is the first column in that calendar.

Decide who you are actually writing for

“B2B tech buyer” is not a useful audience definition. The IT director evaluating a managed service contract reads very differently from the CFO signing it off, and both read differently from the head of operations who will live with the choice for five years. A content programme that pretends those three are one persona ends up producing content that lands with none of them.

We tend to define two primary readers and one secondary. For an MSP that might be IT director (primary), CTO of a 200-seat firm (primary) and finance director (secondary). For a SaaS vendor it might look entirely different. The point is that every brief should name the reader and the question they arrived with. We dig into the differences between technical and commercial readers in content for technical buyers vs business buyers.

Build pillars before you build posts

A pillar is a topic the company wants to be known for, broad enough to support 15 to 30 supporting articles and narrow enough that the team can credibly own it. For a cyber-focused MSP a pillar might be “incident response for mid-market firms”. For a SaaS analytics vendor it might be “attribution for long sales cycles”. The pillar gives the editorial calendar a centre of gravity, so the work compounds rather than scattering.

When we plan a pillar, we map the cluster of supporting articles in advance. The pillar page answers the broad question. Each cluster post answers a sub-question and links back. Done well, a pillar can carry a programme for 12 to 18 months. We walk through the model in detail in the pillar-and-cluster model for SaaS content, and the same architecture sits behind our wider thinking on topic clusters for tech companies.

Set the cadence to what the team can sustain

Strategy decks love to talk about weekly publication. Real teams ship one solid long-form piece a fortnight and a couple of supporting assets in between. We would rather see a client publish twice a month for two years than four times a month for a quarter before burning out. We’ve explored the right content mix for B2B tech in more detail.

We tend to recommend a rhythm that looks like this:

• One pillar or long-form article every two weeks.
• One short supporting piece (comparison page, FAQ, glossary entry) each week.
• One repurposed asset (LinkedIn post, newsletter excerpt, sales enablement card) for every long-form article.

That is enough volume to move organic numbers within six months and not so much that quality slips.

Decide how you will measure it

Content programmes get cut when nobody can explain what they did. We set up GA4, Search Console and HubSpot reporting before the first new article goes live, with a small number of metrics that the team can defend in a board meeting. Organic traffic to pillar pages, assisted conversions on long-form content, demo requests sourced from blog sessions and pipeline influenced by gated assets are the four we lean on most. We go deeper into measurement in measuring content marketing ROI in B2B tech.

Plug content into the rest of the marketing stack

A content strategy that lives in isolation underperforms. The articles you publish should feed the keyword targets in your SEO programme, the headlines you test in paid media and the sales enablement library your AEs reach for on a discovery call. We brief our writers with that ecosystem in mind, so a new pillar on incident response is also a landing page candidate for a LinkedIn campaign and a section in the next sales deck.

Build the systems before you scale the output

The teams who succeed with content strategy are the ones who build the underlying systems first. A clean editorial calendar in Notion or Asana. A briefing template that captures audience, query and intent. A reporting view in GA4 that surfaces the metrics the marketing lead actually defends in a board meeting. A simple workflow in HubSpot that ties content touches to deal records. None of those systems is glamorous. All of them are what stop a programme falling over in month four.

We tend to spend the first month of any new client engagement on those systems before any new article gets commissioned. It feels slow at the time. It is what makes everything that follows compound rather than scatter. For teams running this on a single in-house marketer, our notes on running a content engine with one person cover the trade-offs honestly.

If you are trying to build a content programme that compounds rather than treads water, we’d be glad to talk through it. The first hour is usually about deciding what to stop doing.