Enterprise Content Strategy

You met the A-team in the pitch, then got the C-team on delivery.

1 senior lead

30,000 URLs

2,500+ pages

governance-modelno owner
0 / 24 sections owned
everyone, so no one
Product content?CentralRK
Regional sites?DevolvedJM
Clinical / regulated?CentralAS
Blog & campaigns?DevolvedTP

One senior person does the work, embedded in your team and presented as part of it. Not a team assembled after the pitch, and not an account-management layer relaying your questions to whoever is actually doing the work. The senior person who impressed you is the one who leads it, from kickoff to launch.

What that person solves first is not the content. At enterprise scale the content is not the hard part. The hard part is agreement: dozens of people with real authority, different regulatory obligations, different teams and different technology, all of whom have to end up with one structure they'll actually use.

Which is why the work starts with interviews, not an audit. Dozens of them, recorded and analysed so opinion becomes countable. A structure decision defended with "eleven of the fourteen interviews raised this" survives a room. One defended with "in our professional opinion" does not.

The people who impressed you in the pitch are not the ones doing the work.

The senior people who impressed you in the pitch stay in the room, from kickoff to launch.

One senior person does the work, embedded in your team.

After you signThe team assembled after the pitchOne senior person, embedded
Who does the workThe people you never met in the pitchThe senior person who impressed you, doing it
How you reach themThrough an account-management layer that adds latencyEmbedded in your team, so you talk to the person doing the work
When people changeThree project managers in, the history of decisions is goneOne senior face from kickoff to launch, so the reasoning stays
What you're buyingProduction capacityA partner senior enough to lead you in the right direction

Intermountain Healthcare: four domains into one presence.

  • Dozens of stakeholder interviews across four organisations, made quantifiable with Otter and Airtable.
  • User priorities derived from that data, then flows designed against them rather than against internal assumptions.
  • Content models built with SEO considered during modelling, so rankings held by design rather than by luck.
  • URL mapping across the merging domains, with a migration list so nothing was left behind.
  • An external medical information API from Wolters Kluwer, which removed thousands of pages that would otherwise need maintaining forever.
  • A hybrid governance model, balancing decentralised updates against central oversight.
  • AI-assisted categorisation of blog content into the new taxonomy, saving thousands of hours.
  • A distributed content team coordinated across time zones.

American College of Surgeons: a rescue, not an early delivery.

  • A scored review rubric, so non-specialists, designers and developers included, reviewed against stated criteria rather than personal taste.
  • A binary workflow, so people who did not consider themselves writers could contribute against a voice guide.
  • Airtable tracking the audit and the URLs, so nothing was lost.
  • Batch review, so feedback stopped arriving one piece at a time.

What an enterprise engagement includes.

  • Stakeholder interviews at scale, analysed rather than summarised.
  • Content models and taxonomy that reflect how the organisation actually publishes.
  • Governance, written down, with names against decisions.
  • Editorial standards and a scored review process, so quality does not depend on who wrote it.
  • Migration strategy where consolidation is involved.

What an enterprise engagement is not.

One senior person, not a production team

If what you need is ten writers next week, that is production capacity, and it is not this. One senior person does the work, and that is the point of it.

Scoped work, not a fixed-menu price

Enterprise cost tracks the number of stakeholders and domains rather than the number of pages, so the work is scoped rather than listed. There is no single price on a page.

Usually placed through your agency

Most of this work is subcontracted through the agency already holding your account, embedded in their team. Direct engagements work too, but the common path is through a partner.

What an enterprise engagement costs.

Project engagements start at $10,000, and enterprise work sits well above that.

If it's a different enterprise problem.

Enterprise

Enterprise CMS migration

Healthcare content strategy

Agencies

What enterprise buyers usually ask.

The people who impressed you should be the ones doing the work.

One senior lead, embedded in your team, from the first interview to launch.

One senior person does the work, never a team assembled after the pitch.