How to make the case for content investment

Why is content so hard to get funded?

Because content's costs are visible and its value is diffuse. Salaries, tools and agency fees sit in a budget line; the value – trust earned, time saved, support tickets avoided, donors converted, reputations not damaged – is spread across everyone else's results. Work like that gets treated as overhead until something goes publicly wrong.

Three patterns make it harder still:

• Content is assumed finished at publication. If a report is written and the guidance drafted, the project is "done" – so maintenance, governance and improvement look like optional extras rather than the bulk of the actual work.
• Content is read narrowly. For many leaders, "content" still means social posts and marketing copy. The idea that guidance, reports, emails and presentations are content too – and part of the brand experience – hasn't landed, so the remit looks smaller than the responsibility.
• The advocates are the evidence. When the only people explaining content's importance are the content team, the case sounds like a department asking for more of what departments ask for. It's a structural credibility problem, not a personal one – and it's why borrowed voices matter so much below.

If every advancement has needed a business case, negotiations and a lot of pushing, that isn't a sign you're doing it wrong. It's a sign the case has been carried by effort instead of evidence.

Why don't the usual arguments work?

Because they're the wrong kind of evidence for the audience. Craft appeals ("quality matters"), best-practice citations ("organisations like ours have style guides") and traffic dashboards all describe the work; budget holders fund outcomes and risks. The argument has to be translated into their terms before it can land.

The usual three, and why they fail:

• Anecdote – the embarrassing page, the near-miss, the complaint. Vivid but dismissible: every department has anecdotes, and a single story invites a single fix rather than investment in the system.
• Best practice – what good organisations do. Easy to nod at, easy to defer: an appeal to standards is an expense until it's connected to a consequence.
• Traffic – the dashboard. It measures the weather, not the work, and it says nothing about capability: traffic can hold steady while the operation underneath quietly hollows out. (Our sister tool's guide to why quality matters more than traffic takes this apart in full.)

What these share: they're all assertions by the interested party. The case gets dramatically stronger the moment the evidence stops coming from you.

What evidence actually persuades?

Three kinds, in combination: the running cost of the current state, quantified capability gaps, and the organisation describing the problem in its own words. The first makes inaction expensive, the second makes the ask precise, and the third makes the finding impossible to dismiss as special pleading.

• The cost of now. Immature content operations pay for the same work repeatedly: content decays, embarrasses someone, gets rewritten; everything routes through one stretched person; the periodic website rebuild substitutes for maintenance nobody resourced. Tally what rework, bottlenecks and key-person risk already cost, and "do nothing" stops being the cheap option.
• Quantified gaps. "We're weak on operations" is an opinion; "we're at 51% on operations and 72% on substance" is a diagnosis with a shape – it shows leadership you're strong where it shows, fragile where it doesn't, and it tells them precisely where the money goes. A content maturity assessment produces exactly this.
• Their own words. This is the strongest of the three. When an assessment gathers testimony from across the organisation – leadership included – the findings arrive pre-endorsed: it's not the content team claiming there's no clear workflow, it's colleagues from five departments saying so independently, on the record, in quotes. A leadership team can argue with your interpretation; it's much harder to argue with its own staff, quantified and in agreement.

That third effect is why maturity findings unlock conversations that years of advocacy couldn't: the case stops being yours and becomes the organisation's.

How do you build the case?

Measure first, then let the results write the argument: lead with the shape of the scores, attach a specific ask to each gap, translate the benefits into outcomes leadership already owns, and commit to re-measuring. The structure matters less than the discipline of asking for named things to close named gaps.

1. Assess before you ask. Run a maturity assessment across a genuine cross-section – including the sceptics and the leaders. Their participation isn't just data; it's buy-in banked early, because people take findings seriously when their own answers are in them.
2. Lead with the shape, not the number. An overall score is a conversation opener; the spread is the argument. Strong substance and weak infrastructure tells a story any board understands: the work is good, and it's standing on sand.
3. Attach asks to gaps. Weak operations → a content ops role or workflow project. Weak governance → standards, documented and machine-readable. Weak culture → leadership sponsorship and training, not headcount. Vague asks get vague answers; gap-shaped asks get costed.
4. Translate into their outcomes. Risk, cost, reach, mission. "Governance at 45%" means nothing upstairs until it becomes "out-of-date guidance is a regulatory and reputational risk we currently manage by luck."
5. Name the re-measure date. "Fund this; we reassess in twelve months and show you the movement" turns a grant into an investment with a return measure built in. Accountability is persuasive – it signals you expect the numbers to move.

What does this look like in practice?

A typical case, assembled from an assessment (details invented, pattern real): a charity scores 58% overall – substance strong at 72% thanks to recent brand work, operations and infrastructure both at 51%. The qualitative findings say what the numbers can't: no shared workflow from idea to publication, maintenance unowned, one stretched team carrying everything.

The case then writes itself in three sentences. Our content is good despite our systems, not because of them – here's the spread that proves it. The gap costs us in rework, bottlenecks and risk, in our colleagues' own words. We're asking for a content operations role and a governance project; we'll reassess in a year and show you what moved.

That's a different conversation from "the content team would like more resource" – and when the reassessment shows operations up fifteen points, the next conversation is easier still. Pair the annual maturity trend with a monthly content health check and you can show the system improving and the content improving with it – capability and output, moving together.

Frequently asked questions

How do you quantify the value of content work?

Mostly through cost and risk rather than revenue: hours lost to rework and approval bottlenecks, duplicated effort across teams, support demand created by unclear content, the periodic cost of rebuild-instead-of-maintain, and the exposure carried by out-of-date guidance. These are numbers finance recognises – and capability scores show which investments shrink them.

What if leadership says the content is already fine?

Agree – and show them why that's the worrying part. Good output from a weak system is heroics: it depends on individuals, and it leaves when they do. A maturity assessment makes the fragility visible while the content still looks fine, which is precisely the cheapest moment to fix it.

How big should the ask be?

As big as the gaps it's attached to, and no bigger. A focused ask aimed at your two weakest areas, with a re-measure date, beats a transformation programme – it's easier to grant, faster to show returns on, and each demonstrated improvement funds the next conversation.

How do you keep the funding once you've got it?

Show movement. Reassess on the cadence you promised, report the trend alongside output measures, and credit the investment when scores rise. Content funding gets cut when it's invisible; a visible trend line makes the budget self-defending.

---

Tired of making the case on anecdote and effort? Content Maturity gives you the evidence – quantified gaps, in your colleagues' own words. And if you'd like help turning the findings into a plan, Contentious does exactly that.