Field Guide
Buying Publishing Software One Department at a Time
The Pattern
Pain Arrives Locally. Platforms Don't.
Publishing pain is departmental: the reports team hits Word's ceiling this quarter, the policy team hit it last year, the web team has been drowning in the media library all along. So the buying is departmental too — separate budgets, separate evaluations, sometimes the same vendor and nobody knows. But the software being evaluated is an enterprise platform: its entire economic case is shared content, shared workflows, and one delivery point. Bought separately, you get two half-platforms: double the licensing at half the negotiating leverage, two configurations encoding two content models, and an integration that now never happens — the exact benefit that justified the purchase, foreclosed by how it was purchased.
The Fix
One Decision, Staged Delivery
The fear that drives separate purchases is the big-bang project — every team migrating at once, nobody's deadline survives. It's a false choice. Enterprise publishing platforms are built to be sliced: each department gets its own workspace, document types, permission model, and workflows inside one system, sharing sign-on, infrastructure, and the delivery platform. The urgent team pilots first; the rest onboard in sequence, inheriting a proven configuration instead of a blank page. One procurement, one integration, staged risk.
What that requires is a moment of coordination the org chart won't supply on its own: someone with cross-departmental authority owning the decision, with the practitioners in the room for every demo — because the platform choice is an enterprise call, but the configuration choices that make it livable belong to the people who know the documents. When a vendor discovers two of your teams evaluating separately, watch what they do: the ones worth buying from will tell you to get in one room and come up with something together. It's what we tell ours.
FAQ
Questions We Hear
Why do departments end up evaluating the same platform separately?
Because pain arrives locally. The reports team hits Word's ceiling this quarter; the policy team hit it last year; the web team has been quietly drowning in the media library the whole time. Each team budgets from its own cost center, runs its own evaluation, and often doesn't know the others are looking — sometimes at the same vendor. Nothing nefarious: the org chart splits the problem before anyone sees its shape.
What does the one-department-at-a-time approach actually cost?
Twice the licensing (negotiated at half the leverage), twice the implementation, two configurations that encode two different content models, and — the expensive one — no integration. The reuse, shared workflows, and single delivery platform that justified the software in the first place only exist when the instances are one instance. Separate purchases don't just duplicate cost; they foreclose the benefit.
Does buying together mean one giant big-bang project?
No — that's the false choice that scares teams into buying alone. Enterprise platforms are built for slices: each department gets its own workspace, document types, permissions, and workflow inside one system, and departments onboard in sequence, each on its own timeline. One decision, staged delivery. The urgent team goes first as the pilot; the rest inherit a proven configuration instead of a blank one.
Who should own the shared evaluation?
Someone with cross-departmental authority — a head of digital, an operations executive — with the affected teams in the room from the first demo. The failure mode to avoid is the opposite one, where an enterprise function buys 'for everyone' without the publishing teams present and delivers a system nobody's workflow fits. The evaluation needs both altitudes: the enterprise view for the platform decision, the practitioners for the configuration decisions that make it usable.
Get In Touch
Get in One Room
If more than one of your teams is feeling publishing pain, run the evaluation once, together. We'll help you structure it — including telling you when one department genuinely should go alone.