Done for you describes a platform where AI agents perform the setup and recurring production work. Your team supplies product context, direction, and approval. The agents turn that context into a complete documentation site and keep the site useful as the product changes.
The SaturnDocs process begins with whatever material already exists. That may be a repository, a product specification, old documentation, or a walkthrough with someone who knows the product well. The agents can begin before that material is organized into a perfect handoff. Finding the structure inside it is part of their job.
From there, your role becomes review. You check that the drafts reflect the product, point out details that need correction, and approve the result. SaturnDocs handles the documentation work around those decisions.
You send the context you already have
Every product leaves a trail of useful facts. The repository shows how the software behaves. A specification explains why a feature exists. Old docs reveal the questions readers have asked before. A walkthrough adds the judgment that has never been written down.
We can start with any combination of those sources:
- access to the relevant repository
- product specifications and release notes
- existing documentation, support answers, or internal notes
- a recorded or live walkthrough of the important workflows
SaturnDocs agents read the material, identify the likely readers, and plan the documentation around the tasks those readers need to complete. They draft the pages in plain files, organize the navigation, and build the first complete site.
Send the product context in its current form. If two sources disagree or an important detail remains unclear, the agents bring you a specific question. Your team supplies the product judgment. The agents turn that judgment into a clear page.
AI agents run the complete documentation site
Writing is one part of the job. A useful documentation site also needs dependable hosting, search, an API reference, and a way for readers to ask the docs a direct question. SaturnDocs runs those parts together on one platform.
The site is published on your domain. Search helps readers move from a term to the right page. When you have an OpenAPI specification, the interactive API reference comes from that source. The docs assistant answers from the published documentation and cites the pages it used.
All of this comes together on one platform under the Standard or Enterprise plan that fits the documentation program. The plain source files remain available to you, while SaturnDocs manages the working site around them.
The intended division of work is simple: your team reviews the docs because it knows the product, while SaturnDocs builds and runs the documentation system.
That is the working relationship we aim for. Your review carries the knowledge only your team can provide. The recurring production and operation work stays with the AI agents.
The documentation keeps following the product
A launch captures the product at one moment. The working relationship matters most after that moment, when a setting changes, an endpoint gains a field, or a new workflow reaches customers.
SaturnDocs agents keep the documentation current as the product changes. They revise existing pages, add missing explanations, and answer documentation requests from your team. Questions that the published docs cannot answer become useful signals about what to write next.
Review remains the main job on your side. A product owner can confirm the intended behavior. An engineer can catch a technical detail. A support lead can recognize a question customers will ask. Each person contributes a focused decision without taking on the whole documentation system.
That smaller role makes documentation easier to sustain. The people closest to the product stay involved where their knowledge matters. SaturnDocs carries the work that turns their knowledge into a maintained public resource.
Done for you means your team provides context and judgment, then receives documentation it can trust. The agents draft it, publish it, run it, and keep it current. You review the work, and your readers keep getting clear answers.