Three tools, one knowledge layer paid for three times
A product team of twelve people can end up paying for three systems that all hold explanations of the same product.
An onboarding tool holds the tour steps. A support platform holds the help centre articles. A documentation site holds the developer guides. Each was bought for a good reason, by a different person, in a different quarter.
The subscriptions are the visible cost. The part that hurts is that the same explanation now exists in three places, maintained by three people who cannot see each other's version.
What is actually duplicated
Not the tools. The knowledge layer underneath them.
Each of those systems does something genuinely different with the content: one shows a step at the right moment, one runs a searchable site, one renders a docs page with code examples. Those are three presentations, and they are not the same job.
What is the same job is deciding what the explanation says, splitting it into pieces that can be reused, keeping it current when the product changes, and publishing it deliberately. That work is done three times, in three editors, with three sets of permissions.
What a single content layer replaces, and what it does not
It does not replace three suites. A content system does not run a help centre with its own theme, an onboarding runtime and a docs site with versioned releases. Anyone who tells you otherwise is selling you a fourth silo.
It does replace the third copy of the knowledge. One place where an explanation is written and published, requested by address from each surface that needs it. The onboarding step, the support panel and the docs page ask for the same content and present it their own way.
The distinction matters when you make the decision. You are not buying a replacement for what those tools do. You are removing the duplication underneath them, and then deciding, per tool, whether what remains is worth its price.
Where the saving is
Rarely on the subscription in the first month. It is in four places that do not show up as line items:
The drift. Three versions of an explanation diverge the moment one of them is improved. Your users meet the difference and write to support about it.
The maintenance nobody scheduled. A feature is renamed. Three teams need to know, and two of them find out later.
The onboarding of your own people. A new writer learns one editor instead of three, and one set of rules about what gets published when.
The decision to change anything. When a fix means three edits in three tools, most fixes do not happen. That is the expensive one, because it is invisible.
What you keep
Your presentation layer, in all three places. The onboarding runtime that shows a step. The panel in your support screen. The docs page with its navigation.
And the logic, which never moves: who sees what, when, in which order. A content system that decides that for you is a content system that decides your product for you. See content or logic for where that line runs.
How to tell whether this applies to you
Take one feature and count the places it is explained. If the answer is one, you have no duplication problem and you can stop reading.
If the answer is three or more, the question is not which tool to cancel. It is where the explanation should live so that all three can ask for it. That is the subject of one explanation, six copies.