Service vs platform: choosing how to build your knowledge base.

Three companies have the same documentation problem. Their docs are a mix of stale Confluence pages, README files, support macros, and a Notion wiki nobody updates. Their team's AI tools cite the wrong articles. Their support team answers the same questions every week. Their new hires onboard from a deck written eighteen months ago.

Each company picks a different path to fix it. Each path is the right answer for someone, and each is the wrong answer for someone else. Here is the honest breakdown.

Path 1: buy a documentation platform

Companies in this lane choose Mintlify, Document360, GitBook, Notion, or Confluence. The platforms are good. They give you a hosted UI, search, version control, branching, and increasingly, AI-search add-ons.

The price is modest. Most teams can stand up a docs site for $200 to $1,500 a month depending on seat count and add-ons.

What a platform does not give you is anyone to actually write the content. The blank page is still your problem. The platform will host whatever you put in it. If what you put in it is rough, fragmented, or out of date, the platform faithfully delivers rough, fragmented, out-of-date docs.

Best fit: teams that already have a technical writer in-house, or teams whose engineers are willing and able to maintain documentation as a steady part of their work.

Path 2: hire a technical writer

This is the highest-quality outcome and the highest commitment. A senior technical writer in the United States runs $90,000 to $140,000 per year, plus benefits, plus the recruiting cost, plus the three to six months it takes to find the right one.

Once they are in seat, you have a person who owns the editorial standard, knows your product, and can build a real knowledge base over time. You also have a salary to justify and management overhead to absorb.

If you also need a hosted platform, that cost is on top.

Best fit: companies of 100+ employees with steady, ongoing documentation volume across multiple product surfaces. Below that, the math gets hard to justify.

Path 3: managed editorial service

This is the path AgileDocs occupies, and it is the newest of the three. The pitch is simple: you get a senior editor and a hosted, AI-readable workspace as one bundled service. You do not hire anyone. You do not learn a platform. You send raw content; we send back governed articles.

Pricing runs $299 to $1,499 per month for most teams, scaling up for enterprise. Starter comes with a 30-day money-back guarantee, so teams can try the work product without long-term commitment.

What you do not get is a dedicated full-time employee on payroll. The editor is shared across a small number of customers. For teams that need a writer on call every hour of every day, that is a constraint. For teams that need a regular weekly editorial cadence, it is more capacity than they would get from hiring junior in-house.

Best fit: SMBs and growing teams (10 to 200 employees) that need real editorial discipline but do not have the volume or the budget to justify a full-time hire, or regulated companies that need audit-grade documentation without the recruiting timeline.

An honest matrix

Here is how I would actually advise a buyer:

• Solo founder, no docs yet, want to start somewhere. Try AgileDocs Starter at $299/month with a 30-day money-back guarantee. Cheaper than a Mintlify trial that ends with you still writing it yourself.
• 10 to 50 employees, growing fast, no in-house writer. AgileDocs Team. The math against a freelance writer ($3,000 to $8,000 per month retainer) and against a junior hire (loaded cost north of $7,000 per month) is straightforward.
• 50 to 200 employees, regulated industry. AgileDocs Enterprise, or hire and pair them with a platform. Either works. Hiring takes longer; we are faster to value.
• 200 to 500 employees, multi-product organization. Hire a senior writer and pair them with a platform. We can complement that team for surge work or specialized verticals, but we are not a substitute for an in-house function at that scale.
• 500+ employees. Build the in-house team. You have the volume to justify it.

Why we are not really competing with platforms

Mintlify, Document360, GitBook, and the rest are good products. We are not trying to replace them. They solve hosting and authoring UX. We solve editorial discipline and AI-readability.

Many AgileDocs customers also use a platform. We deliver the structured, edited content; the platform hosts the public-facing UI. The two complement each other when the buyer wants both polished hosting and ongoing editorial work.

What we are competing with, honestly, is the status quo: docs that nobody owns, that go stale, and that AI tools confidently cite anyway.