Your 5-person docs team does not need a $50K CCMS

A 5-person documentation team does not need an enterprise CCMS. Those platforms are built for organizations of 15 or more writers. They cost $50,000 to $200,000 a year and need a dedicated administrator. MadCap IXIA CCMS lists a $3,850 monthly starting rate on Capterra. Heretto is reported at $150 to $250 per author per month. RWS Tridion Docs is quote-only and pitched at "thousands of users in one governed environment." None of that matches a team that fits around one conference table.

The trap is treating "we have outgrown our wiki" as the same problem as "we have outgrown Google Docs." Teams of 2 to 15 writers have real structural needs: reuse, conditional content, multi-channel output. They carry none of the enterprise overhead: audit trails, translation memory, governance workflows for dozens of contributors. The market sells them either too little or too much. This article maps the middle.

The three tiers of documentation tooling

Documentation tools cluster into three tiers, separated by an order of magnitude in both cost and operational overhead. Most teams pick the wrong tier. They evaluate features instead of fit.

The cost figures need context. The 5-person lightweight range starts at Topicary Team, $1,788 a year. It tops out at Document360 Business, roughly $4,800 a month, or $58K a year. The enterprise range is built from published rates and reviewer reports. MadCap IXIA lists a $46,200 a year starting price (Capterra). Heretto is reported at $150 to $250 per author per month for a typical 15 to 50-seat deployment (TrustRadius). RWS Tridion Docs and Vasont contribute reviewer sentiment only, because both are quote-only with no published list pricing.

For a foundation on what a CCMS actually does, see our plain-language CCMS guide. For why structured authoring does not require DITA XML, see the DITA alternative breakdown.

5 signals you have outgrown your wiki

These signals are concrete, not vibes. If three or more describe your team's week, your wiki is the bottleneck.

1. You copy and paste content across pages. The product overview appears in 7 places. The setup prerequisites appear in 4. The legal team updates the disclaimer. You grep for it across 30 markdown files and miss two.
2. You manually reformat content for each output channel. Web help lives in the wiki. PDFs live in a Google Docs folder. Someone updates it from the wiki when a customer asks. The PDF is always three weeks behind.
3. Your review workflow is "please take a look." A subject-matter expert opens the page, reads it, and sends comments in Slack. There is no token-based reviewer access, no comment threading, no approval state on the topic itself.
4. You version content by duplicating pages. The 2024 release notes are at one URL. The 2025 release notes are at another. The shared content (installation, configuration) lives in both. The two copies have already drifted apart.
5. You handle conditional content by maintaining separate copies. The admin guide and the user guide share 60 percent of their content. You maintain two files. Updates land in one and miss the other.

These are the 5 limitations we documented in our analysis of where docs-as-code stops working. Wikis hit the same wall earlier. They lack even version control as a baseline.

5 signals you do NOT need enterprise CCMS

The other side of the framework matters as much. Enterprise CCMS platforms are real software built for real problems. They are also the wrong purchase for most documentation teams.

1. Your team has fewer than 15 writers. Enterprise CCMS platforms assume specialization (writer, information architect, taxonomist, publishing engineer). A 5-writer team cannot specialize. The platform's role-based features become friction instead of an advantage.
2. You do not have a regulatory audit trail requirement. Check for FDA 21 CFR Part 11 compliance, aviation traceability under ATA Spec 1000BR, or pharmaceutical GxP documentation. If your industry requires none of those, you are paying for audit logs you will never read.
3. You do not need translation memory integration. Enterprise CCMS platforms ship with XLIFF export pipelines and segment-level translation memory. They integrate with translation management systems like Trados or memoQ. In an English-only shop, this is dead weight.
4. You have no headcount to dedicate to CCMS administration. Sarah O'Keefe at Scriptorium and Bill Swallow at DITA Strategies both describe the information architect role as a permanent position in DITA shops. It is not a part-time duty. If your documentation lead writes topics and runs the platform, enterprise CCMS is the wrong tier.
5. Your annual content tooling budget is under $50,000. This is the floor for an enterprise CCMS deal, not the typical price. Add implementation services, training, and translation pipeline setup. Most enterprise rollouts cross $100,000 in the first year.

If three or more describe your team, every dollar above the lightweight tier is waste. The features you pay for will sit unused or get in the way.

The team size decision matrix

Pick the tier that matches both team size and content complexity. The matrix below is the same one we recommend in customer calls.

The bold cells are the strong matches. The unbolded cells work with discipline, but they signal a coming migration. The common trap is jumping diagonally across the table. A 4-writer team picks enterprise CCMS because it expects to grow to 30 within two years. That growth frequently does not happen. Meanwhile the platform's overhead drags the team down. Buy for the team you have, not the team you might have in three years.

Where lightweight CCMS lands

Lightweight CCMS pricing is unusually transparent compared to the enterprise tier. The published per-author rates at the team plan for documentation platforms in this band:

Pricing checked June 2026; ClickHelp and Paligo re-checked August 2026. GitBook, Mintlify, and Document360 all charge per project or per site. Teams running multiple documentation properties pay multiples of these figures. Paligo sits at the top of the lightweight band. It acts as a bridge into enterprise capability. Vendr's benchmarking data reports a median annual Paligo contract of $32,680. We compare it directly in Topicary versus Paligo.

The honest pattern: lightweight CCMS costs roughly $25 to $80 per author per month at the team tier for 5 to 10 writers. Topicary sits just under the lower end of that band. None of these tools deliver enterprise capabilities such as 3-way merge, release lifecycle management, XSL-FO print layout, or translation memory. If your team needs any of those, the published pricing is misleading. You are shopping in the wrong band.

When Topicary is NOT the right choice

We sell Topicary. We also have a strong incentive not to waste a prospect's evaluation week. Topicary is the wrong purchase if:

• You are a solo writer. A lightweight CCMS adds overhead that one person rarely recovers in productivity. Use Notion for internal docs, or Markdown plus a static site generator for developer docs. Reuse and conditions are not a real bottleneck at one author.
• You require DITA-native authoring. Topicary uses a structured-content model with topics, components, conditions, and variables. It does not emit native DITA XML. It does not implement conref or conkeyref. If your team or your client mandates DITA, evaluate Paligo, Heretto, or RWS Tridion Docs.
• You are in a regulated industry that requires formal audit trails. Topicary tracks content history and review state. It does not provide FDA 21 CFR Part 11-grade audit logs, electronic signatures, or compliance attestation. If your regulator requires those, you need an enterprise CCMS with a documented compliance posture.
• You have 50 or more writers needing governance at scale. Topicary is built for 2 to 15-writer teams. We can support larger deployments. Role-based governance, multi-team workspaces, and translation memory integration are not the product's strengths. Above 50 writers, the platforms designed for that scale will fit better.

This list will get shorter over time as we ship. It will not become empty. There is a real range of documentation problems, and no single tool covers all of it well.

What changes when you cross 15 writers

The 15-writer threshold is not arbitrary. The State of Docs Report 2025 surveyed 444 documentation practitioners. Team sizes ran from "solo writer at a startup to 250-plus practitioners spread across a global enterprise." It shows the same pattern that vendors report internally. At around 15 writers, teams begin specializing. One person owns the content model. Another owns publishing infrastructure. A third focuses on developer documentation while a fourth handles user-facing guides.

That specialization changes the buying decision. A 5-writer team picks a tool that one person can administer alongside writing. A 20-writer team can afford a dedicated information architect. Enterprise platforms demand that role, and hiring it is what makes their value reachable. Evaluate enterprise CCMS when you can fund the role the platform requires. A feature gap in your lightweight tool is not the trigger.

Frequently asked questions

At what team size does an enterprise CCMS start to make sense? Enterprise CCMS platforms are built for documentation organizations of 15 or more writers, usually with multilingual delivery, regulatory audit trails, and a dedicated information architect. RWS Tridion Docs explicitly markets itself as supporting thousands of users in one governed environment. Below that scale, the per-writer overhead of the platform exceeds the value it delivers.

How much does a lightweight CCMS cost compared to enterprise? Lightweight CCMS pricing for team-tier plans lands between $25 and $80 per author per month based on published rates from GitBook, Mintlify, ClickHelp, and Document360 (checked June 2026). Enterprise platforms like RWS Tridion Docs, Vasont, and Astoria are quote-only with no published figures. MadCap IXIA CCMS lists a $3,850 monthly starting price on Capterra, and Heretto is reported at $150 to $250 per author per month, putting a 25-seat deployment between $45K and $90K a year before implementation costs.

Can we just use a wiki forever? You can use a wiki forever if you write fewer than 50 topics, publish to one output format, never repeat the same paragraph across pages, and only serve a single audience. Once you cross any of those lines, the maintenance cost of duplicate content begins compounding. Most teams notice the pain around 100 topics or the second product launch.

What is a CCMS administrator and do we need one? A CCMS administrator owns the content model, taxonomy, publishing pipelines, user roles, and ongoing platform tuning. Bill Swallow at DITA Strategies describes the role as a permanent position, routinely titled information architect, in enterprise DITA deployments. Lightweight CCMS platforms are designed for the documentation lead to administer the system part time alongside writing. If you do not have headcount to dedicate, enterprise CCMS is the wrong tier.

When is Topicary not the right tool? Topicary is the wrong choice if you are a solo writer (use Notion or a docs-as-code workflow), if your organization requires DITA-native authoring with conref and conkeyref (use Paligo, Heretto, or RWS Tridion Docs), if you need regulatory audit logs for FDA or aviation compliance (use an enterprise CCMS), or if you have 50 or more writers needing role-based governance and translation memory integration. We say this in the article rather than the sales call because it saves both parties a wasted week.

Is the answer always to upgrade tooling? No. The honest answer depends on whether your bottleneck is the tool or the process. If your team has no editorial review, no taxonomy, and no maintenance plan, a CCMS will not fix that. A wiki with a strong editorial workflow outperforms a CCMS that nobody uses correctly. Audit the process before you audit the toolchain.

How to pick a tier in one afternoon

1. Count your writers, including part-time contributors who actually touch content. If under 2, stop here and use Notion or docs-as-code.
2. List your output formats. If you publish to one format only, you do not need multi-channel features. If you publish to two or more, lightweight CCMS earns its cost.
3. List your audiences. If you have one audience, you do not need conditional content. If you have two or more (admins and end users, free and paid, by platform), you do.
4. Audit your top 20 most-read pages for duplication. If any block of content appears in more than 3 pages, you have a reuse problem. A lightweight CCMS solves it.
5. Check whether your industry mandates an audit trail. If yes, you are shopping enterprise. If no, do not pay for the audit logs.
6. Check your budget. Under $5K a year is wiki territory. $5K to $50K is lightweight CCMS. $50K-plus is enterprise CCMS plus implementation services.

If the framework points you to lightweight CCMS, evaluate two or three options in the $25 to $80 per-author band. Run a structured trial with one real documentation set. Pick based on editor ergonomics and publishing output quality, not feature checklists. The feature lists are largely the same in this band. The author experience is not.

Sources

• DITA CMS pricing — Capterra (accessed 2026-06-06)
• Heretto pricing — TrustRadius (accessed 2026-06-06)
• RWS Tridion Docs product page (accessed 2026-06-06)
• GitBook pricing (accessed 2026-06-06)
• Mintlify pricing (accessed 2026-06-06)
• Document360 pricing (accessed 2026-06-06)
• ClickHelp pricing (accessed 2026-06-06)
• Vendr — Paligo pricing intelligence (accessed 2026-06-06)
• State of Docs Report 2025 (accessed 2026-06-06)
• The role of an information architect in a DITA implementation — Bill Swallow, DITA Strategies (accessed 2026-06-06)
• Buyer's guide to CCMS evaluation — Sarah O'Keefe, Scriptorium (accessed 2026-06-06)
• Write the Docs salary survey 2020 (accessed 2026-06-06)