SaaS & API docs that cut onboarding tickets by up to 30%.

Native English and French docs for teams selling into France and Europe, written by senior people, right the first time.

Docs that ship with the release.

ScribeOps is a technical-writing agency delivering end-to-end documentation for SaaS products, APIs and compliance packs, in English and French, as a dedicated doc team or an integrated extension of your developers. Software documentation rots between releases, so we build docs-as-code workflows where documentation is reviewed like code and published with it, then keep writing inside them.

How we work

  1. Map the product From Jira, interviews and your material, we map what users do and what they need to know. You validate the map.
  2. Draft Every page is drafted against the map, then reviewed and rewritten by a senior writer.
  3. Organise Pages are arranged the way your users search: by task, by product area, by audience.
  4. Publish Docs-as-code in your repository, or on your docs platform, with search and navigation.
  5. Maintain Every release updates the docs: changelog, revised pages, outdated pages removed, the dashboard.

Everything you need to onboard users

Documentation audit

We perform a gap analysis of your existing docs, flag missing topics, and highlight inaccuracies. Deliverable: Prioritized audit report, content map, and remediation roadmap. Tools: Content inventory scripts, analytics, stakeholder interviews. Outcome: Clear path to ROI‑driven documentation improvements. Credited in full against any project ordered within 60 days. The audit comes with a map of your product and the coverage of your pages.

Documentation maintenance

A quality pass over an existing documentation set: every page checked against the current product, aligned with your writing style guide, broken links and stale screenshots fixed, outdated pages retired, delivered as reviewed changes, not a rewrite.

SaaS documentation

A complete user documentation set for a SaaS product, getting started, feature guides, concepts, admin and reference, mapped to the customer journey, organised with documentation organisation methods, Diátaxis among them, and published docs-as-code. 50 pages, one month.

API reference docs

Complete, accurate API documentation that developers integrate against directly. Deliverables: a validated OpenAPI spec, a reference page per endpoint, error, pagination and versioning pages, a quickstart, working examples checked on your sandbox. Outcome: onboarding tickets drop up to 30%.

Documentation migration

We move legacy docs into a modern, version‑controlled system. Deliverable: Git repository with Markdown source, CI pipeline, and published site on GitHub Pages or Netlify. Tools: Git, MkDocs, Sphinx, custom migration scripts. Outcome: Single source of truth; updates ship without editorial bottlenecks.

SaaS launch pack

SaaS documentation (50 pages), API reference (up to 30 endpoints) and docs-as-code set-up, in one order with one brief and one repository. Less than the three services bought separately.

Our expertise, built into our tools

What we work in

FAQ

What does a monthly plan include?

A named senior person on call all month, with replies within one business day, and up to 6 working days of work a month as fair use. Days beyond that are billed at the plan's day rate. Plans run 6 or 12 months; for anything shorter, pick a fixed-scope service.

What if I need changes?

Every order includes free revision rounds (shown on each service page). Extra rounds are quoted up front, no surprises.

Who actually does the work?

A senior team. The people you brief are the people who write and manage your docs, no handoff to juniors, no anonymous subcontracting. When a project needs more hands, we bring in senior writers we have worked with, under the same standards and the same point of contact.

Can you work in our tools?

Yes, Git, MkDocs, Docusaurus, Confluence, your CI. We adapt to your stack, not the other way around.

What happens to the tool when the plan ends?

You keep it. The map of your product, the checks that run on every pull request, the style guide and the portal are files in your repository, not a subscription. When a plan ends they stay where they are and keep working. Hosting the portal and the docs assistant after the plan is an option we agree on together.

Do you sign NDAs?

Of course. Send us yours, or ask for ours.

Team

Memberships