Five buyer personas, one content marketer: how I built a full-funnel strategy without a team

A multi-persona content strategy for a one-person team comes down to deciding, every quarter, which persona gets most of your time, then protecting that decision when everyone asks for something else. You’ll never serve every persona equally, because Forrester’s 2026 State of Business Buying puts a typical B2B purchase at 13 internal stakeholders plus nine external influencers, and no solo marketer writes for 22 people at once. I ran it for five personas at a B2B SaaS company serving 200+ higher education institutions, and the content operation contributed to 48% of marketing-sourced pipeline in peak months. Fair warning though: five was too many for one person, and I’d start with three.

Most content marketing advice assumes you have a team. “Create persona-specific content journeys.” Great, with what people? “Run A/B tests across segments.” Sure, right after the blog post, the LinkedIn campaign, the product page rewrite and the sales one-pager that were all due yesterday. And the team the advice assumes you have usually doesn’t exist: in the Content Marketing Institute’s 2026 B2B research, 39% of B2B marketers named time, people and budget as a top-three content challenge.

When I joined the company, the content function was me, and instead of “pick a persona and go deep”, the brief was a full-funnel strategy for five buyer personas (IT leaders, Deans and CEOs, Admissions Directors, Marketing Directors and CFOs) across blog, social, website, whitepapers, case studies and sales enablement. Oh, and also build the brand voice and editorial standards, the AEO/LLMO framework, and track 17+ KPIs a quarter.

So I did: on top of the 48% pipeline contribution, the content operation influenced €230K+ in pipeline in a single reporting period, engagement rates ran above 12% and organic traffic grew 33% quarter on quarter; I’ve broken down the pipeline attribution separately. The more useful story is how I decided what to build first and what to let slide, and how five persona strategies kept moving without the work turning mediocre.

Why doesn’t an equal split work in a multi-persona content strategy?

An equal split fails because personas aren’t equally valuable at the same moment, and giving each one 20% of your output means every persona gets a slice too thin to move them. It’s the instinct when you’re handed five personas: rotate through them, be fair. But the Admissions Director evaluating platforms right now is worth more to pipeline this quarter than the CFO who won’t appear until procurement, and the CIO who can block a deal over security needs different content, at a different time, from the Marketing Director who’s excited about your analytics features.

Spread it evenly and pipeline contribution stays flat, because not enough content reaches the people closest to buying. The size of the buying group makes it worse: with 13 internal stakeholders in a typical decision, Forrester also found procurement acting as a decision-maker in 53% of buying cycles, so even the persona you’d happily ignore has a vote.

So the first move I made was to throw out equal distribution.

How do you decide which personas to prioritise?

I ranked the five personas every quarter on three factors (impact, urgency and debt) and split my time by the result instead of by fairness. It’s a different tool from my content prioritisation framework, which scores single ideas on impact, effort and alignment; the persona ranking comes first and decides how much of the calendar each audience gets.

Factor	The question it answers	Where the signal came from	What it changed
Impact	Which persona is closest to a buying decision, and what does sales need most urgently?	Sales conversations, CRM data on active deals, leadership’s read on the pipeline	The biggest share of the quarter
Urgency	Which content gap is costing us deals right now?	Prospect questions sales couldn’t answer	Pieces jumped the queue, overriding the quarterly plan
Debt	Which persona have we ignored long enough that it’ll stall deals later?	Deals reaching budget approval with nothing to hand finance	A small, protected slice every quarter

Impact was always the strongest signal, because it tied production straight to revenue. Urgency was about gaps actively costing us opportunities: if a prospect asks about security and we’ve got nothing credible to send, that’s a this-week problem, and urgency often overrode the plan because deals were at risk right now.

Debt is the one teams skip: even when the CFO isn’t driving deals, having zero content for their concerns means hitting a wall at budget approval. Stijn Hendrikse of T2D3 describes these finance, legal and IT executives as people who can become blockers for procuring your solution unless your main buyer has the arguments to win them over. And they’re under pressure of their own, as Forrester’s Barbara Winters put it:

“B2B buyers are under immense pressure to justify investments and minimize risk.”

Debt also has a long tail: the LinkedIn B2B Institute’s 95:5 rule, developed with Professor John Dawes of the Ehrenberg-Bass Institute, holds that only about 5% of B2B buyers are in market at any time, so the persona you’re neglecting this quarter is often next year’s buyer.

Some quarters the split was 40% IT, 25% Admissions, 20% Leadership, 10% Marketing and 5% CFO, and other quarters looked completely different, because I was choosing where my time went instead of defaulting to whatever felt fair.

What happens to a multi-persona content strategy when the ICP pivots?

When the ideal customer profile pivots, the new primary persona takes the biggest share of capacity immediately, and the others make do with whatever’s left. Halfway through my time at the company, leadership moved the primary target from Admissions Directors to IT leaders (CIOs, CTOs and Heads of Infrastructure). I’ve written up the full ICP pivot separately; here’s what it did to the persona balance.

The Admissions content was polished and in-depth, and it was performing well, while IT buyers had basically nothing: no integration documentation, security content or architecture guides, and nothing I could hand a CIO with any confidence. So I carved out roughly 50% of my capacity for IT and squeezed the other four personas into the remaining half. I told the team plainly that some personas would get less than they were used to, and made the work that did go out for them punch above its weight: bottom-of-funnel pieces, sales enablement and updates to existing content rather than new articles.

For IT, I started with whatever would unblock deals fastest:

• Integration blueprints, because sales was already fielding technical questions it couldn’t answer.
• Security documentation, since it’s a dealbreaker for IT buyers evaluating any SaaS platform.
• Architecture overviews, so CIOs could see how the platform fit their existing stack before agreeing to a demo.

It wasn’t smooth, though: writing technical content for CIOs with a content marketing background took a lot of internal research and stakeholder interviews, plus being upfront about what I didn’t know yet.

What does a content calendar for five personas look like?

You plan a calendar that survives a multi-persona content strategy one quarter at a time, in tiers, so you decide what to drop before the fire drill instead of during it. I’ve seen colour-coded calendars that are works of art, twelve months planned with every persona in perfect rotation, and they never survive contact with a sales pipeline.

Mine had three tiers:

1. Committed: content going out no matter what, tied to pipeline priorities, deal support or initiatives leadership was tracking. It usually ran to five to eight pieces a month across all formats, protected from fire drills.
2. Planned pieces were the ones I expected to make but could move, like blog posts on the editorial calendar, sequenced LinkedIn campaigns and website updates that were useful but not urgent.
3. Opportunistic, the “if I have capacity” list: thought leadership, experiments, repurposing and longer SEO plays. Useful stuff, but never time-sensitive, so it was the first to go when something urgent landed.

When a fire drill hit (and in B2B SaaS, they hit constantly), I already knew what to protect and what to bump. Mid-quarter reviews kept it on track in the other direction: I’d pull performance data at the halfway mark, and if an Admissions post was wildly outperforming, I’d give it a follow-up piece or a LinkedIn campaign; if an IT topic was underperforming, I’d work out why (wrong angle? too technical? not technical enough?) before moving to the next brief. The tiered calendar is one part of the wider content system I ran, and the quarterly review questions are in how to keep a full-funnel content strategy alive past 90 days.

How do you run LinkedIn for five personas at once?

You run LinkedIn inside a multi-persona content strategy by giving every post one primary persona and batching the writing by persona rather than by week. LinkedIn was its own beast: 39+ posts a quarter across concurrent campaigns, aimed at audiences with very different expectations.

The mistake I see most often is generic posting that tries to speak to everyone and lands with nobody. A post about “digital transformation in higher education” sounds relevant to all five personas on paper, but the IT leader wants APIs and the Admissions Director wants application workflows, and smashing both into one post means neither stops scrolling. So each post had a primary persona even when it was broadly relevant, and that target decided the hook, the language, how specific I got and what I asked people to do at the end. I tracked the persona mix across posts, too, so I didn’t accidentally spend three weeks talking to one audience.

The shortcut that saved me was batching: instead of planning post by post, day by day, I’d write a cluster of IT posts, then one for Admissions, then Leadership. Staying in one audience’s headspace made the writing faster, because I wasn’t context-switching five times a day. The full LinkedIn playbook, including the engagement figures, is in how I hit 12% engagement on B2B SaaS LinkedIn.

Why does sales enablement belong in a multi-persona content strategy?

Sales enablement belongs in the strategy because the personas you’re writing blog posts for are the same people your sales team is talking to, and a gap between the two messages is a credibility problem for both. It also does more of the selling than it used to: Gartner found 75% of B2B buyers prefer a sales experience without a rep, so the one-pager often has to make the case on its own.

I built persona-specific sales material alongside the content calendar: one-pagers, competitive positioning docs, pitch decks and prospect-facing collateral. When the pivot changed the primary persona, I rewrote the sales material before I touched the blog calendar, because sales needed new ammunition that week and the blog could wait.

The other piece that made a big difference was prospect soundbites, short pre-written responses sales could drop into conversations or emails:

“When the prospect asks about security, here’s what you say.”

“When they compare us to [competitor], here’s the framing.”

They barely took any time and earned far more than they cost, because suddenly every sales conversation used the same language as the website and the blog, and that consistency across channels builds the kind of trust that shows up in pipeline.

What would I do differently?

Mostly I’d have cut the scope of the multi-persona content strategy sooner, plus a few smaller fixes:

1. I’d push back on five personas from day one. Five for one person is ambitious, and three primary plus two secondary would have been realistic. I could have made that case at the start instead of trying to serve all five at equal depth and adjusting once it was clearly unsustainable.
2. Content brief templates should have come first. I standardised briefs about three months in, and those first three months were messier than they needed to be because too much of the strategy lived in my head. The briefs made everything faster and more consistent, and I wish I’d built them in week one alongside the editorial standards, which is why they’re the first thing on my list in the 90-day plan for building a content function now.
3. Reactive work needed a harder boundary. “Can you just write a quick…” became a daily occurrence, and early on I said yes to too many ad hoc requests that ate time I’d set aside for strategic content. A clear intake process from the start would have fixed it, which is a big part of why I argue for a content system over a content team.
4. I’d have built repurposing in sooner. I made a lot of original content when a whitepaper could have become a few blog posts, a LinkedIn series and an FAQ page. I did some of it, but never systematically enough, and the way I’d run it now is in my content repurposing strategy.