skip to main content

← All one-pagersSoftware with a large documentation site

Syncanix for documentation-heavy software

Security platforms, developer tools and work-management vendors all end up the same shape: a large public documentation site, a deep API, a support team working through a queue, and an assistant that reads paragraphs back and stops there. What is missing is one that can also do the thing, at a price you can predict, with a record of every action it took.

Who this is for

  • Your customers read the documentation before they write in, and your support queue is busy enough that you plan around it.
  • Your documentation is public (Mintlify, ReadMe, Docusaurus, GitBook or Notion) and your tickets live in Zendesk or Intercom.
  • Somebody owns how good the support is, and somebody else has to agree before anything touches a customer account.

What usually hurts

  • The assistant you have reads an answer back. It cannot run the scan, add the integration, or look up what happened on the account last week.
  • Keeping it current is somebody’s job. Every release your engineers ship breaks something the assistant thought it knew.
  • Per-seat pricing punishes a good month, and a busy week can double the invoice.
  • Anything that would change something still goes to a person, so the requests that cost the most to handle are the ones the assistant never touches.

How Syncanix solves it

  • Point it at your documentation and it reads all of it, whether that is Mintlify, GitBook, Docusaurus, ReadTheDocs, Notion, Confluence, or any site with a sitemap. It reads it again every time you publish.
  • It learns what your product can do from the product itself: the screens and forms people use, what your app does while they use it, and an optional one-off scan of your source code if you want it exact. It notices when something changes.
  • Public pages and the signed-in app get different rules. On the documentation it answers. Inside the account it acts as the person who is signed in, and only within what they are allowed to do.
  • Anything that changes something is shown and confirmed before it runs, and every one of them lands on a record of who asked, what changed, and when.
  • You pay for what the assistant does. Every interaction has a posted price of 3, 6, 9 or 12 usage credits, so hiring never moves the invoice.

Why it works here

  • Your documentation and your product stop being two separate answers. One conversation can explain the thing and then do it.
  • The price is posted before you buy, and it follows what the assistant did rather than how many people you hired.

What it costs

  • There is no free tier and no trial that starts by itself. A workspace runs on a paid plan, or on evaluation access we grant with an end date.
  • Most teams start on Growth ($999/mo, 110,000 usage credits): one live surface, the assistant reading your product, and full control over what it may change.
  • Scale ($2,999/mo, 360,000 usage credits) adds more surfaces and lets you bring your own AI keys and pay your provider directly.
  • Enterprise is a committed usage-credit contract: your own keys, a private connection for your customers’ AI tools, single sign-on and role controls, EU residency, and a named contact.