ScribeOps Start a project
Bilingual EN / FR · Remote-first · Mauritius

Docs your users
actually read.

ScribeOps is a technical writing agency. Senior writers who are technical themselves shape documentation around how your users actually work, and pair every engagement with our own tooling, so even the most complex product becomes clear.

Work with the team Meet the writers
Docs-as-code
Git-versioned, automated
2
Languages · EN / FR
20 yrs
IT & writing experience
GMT+4
Overlap with EU & APAC

Trusted approach for SaaS, developer platforms and API-first products

SaaS platformsDeveloper toolsAPI-first productsFintech & complianceOpen-source projects
The team

Two senior operators, on every engagement.

ScribeOps is deliberately small. Your project is run end to end by the two people you see here, both of whom have shipped real systems and real documentation. You always know exactly who is writing your docs.

DJ
Didier Joomun

Didier Joomun

Founder · Documentation Manager
20 years in IT

Owns the technical side: architecture, docs-as-code, automation and agentic workflows.

Twenty years across Linux, DevOps and cybersecurity give Didier a rare vantage point. He documents systems he could just as easily build and operate. He leads the docs-as-code pipeline, designs the automation and agentic workflows behind every engagement, and writes the technical documentation for software and SaaS products himself.

BasedMauritius · GMT+4
LangsEnglish · French
LinuxDevOpsCybersecurityDocs-as-codeAutomationAgentic workflowsSoftware & SaaS tech writing
IJ
Inella Joomun

Inella Joomun

Technical Writer
Technical writer · software & SaaS

Writes clear technical documentation for software and SaaS products.

Inella is a technical writer for software and SaaS. An earlier career in HR and managed services gave her a sharp read on the real workflows behind a product, so her documentation reflects how people actually work, not just how the software is built. She pairs that operational instinct with genuinely readable prose.

BasedMauritius · GMT+4
LangsEnglish · French
Software & SaaS tech writingUser guides & help centresProcess documentationOnboarding docsHR & operations domainEN / FR bilingual
Why the team

A documentation team, for less than one hire.

Most companies solve documentation by hiring one technical writer, then discover that one person cannot be a writer, an editor, a docs engineer and a toolchain owner at the same time. Working with ScribeOps gives you all of those, from day one.

One in-house writer

Hiring in-house

  • Months of recruiting, onboarding and ramp-up before the first page ships
  • One person, one skill set: writing or tooling, rarely both
  • Salary, benefits and management overhead, whether the backlog is full or empty
  • Docs stall the moment they take leave or move on
  • You still have to buy, wire up and maintain the docs toolchain
  • Knowledge lives in one head, and leaves with it
The ScribeOps team

Working with us

  • Writing starts in days, not quarters, on a scope you approve first
  • A writer and a docs engineer on every engagement, together
  • You pay for the work, and scale it up or down as the roadmap moves
  • Two people cover for each other, so delivery never depends on one calendar
  • The toolchain comes with us, already built and already running
  • Everything lives in your repo, in your format. You own all of it
Already have writers?

We complement your team, we don't replace it.

Plenty of our best work sits alongside an in-house writer. They keep the product voice and the institutional knowledge. We take the load, the tooling and the surge capacity off their plate.

Extra capacity, on demand

Launch weeks, migrations and backlogs get an extra pair of senior hands, without a permanent headcount.

The docs engineering half

We build and run the docs-as-code pipeline, CI checks, style linting and publishing, so your writer writes instead of maintaining infrastructure.

Specialist coverage

API reference, CLI docs, security and compliance pages, and EN / FR bilingual work when your team doesn't cover it.

A second pair of eyes

Independent audits, gap analysis and structural reviews that are hard to run on documentation you wrote yourself.

And our own tooling

We arrive with our own technical writing tools.

ScribeOps is also the software we build: AI documentation agents, DocScan audits, screenshot capture, a docs-as-code pipeline and an executive KPI dashboard. Every engagement runs on it, at no extra licence cost, and your in-house team gets to use it too.

See the toolkit
  • AI documentation agents that draft against your style guide
  • DocScan audits that turn a messy doc set into a prioritised backlog
  • Screenshots and terminal recordings that never drift from the product
  • Time-to-doc, coverage and effort-saved, reported per product
Use cases

What teams actually hire us for.

Find the situation that sounds like yours. Each one opens a page with the pain points we hear, how we work through them, and what you get.

Launching a product with zero docs You're shipping software or SaaS and have nothing written yet. API & developer documentation Your product is API-first but the reference is thin or auto-generated noise. Docs-as-code, automated Your docs live in wikis that rot and nobody trusts. Agentic documentation workflows You want AI in the loop without losing editorial control. Security & compliance documentation You need runbooks, hardening guides and audit-ready docs. Managed documentation service You don't want to hire and manage an in-house docs team. Support team knowledge base Your helpdesk team needs an internal KB: SOPs, macros and escalation paths.
Portfolio

Documentation structures we build.

These are sample documentation sets, most for well-known open-source tools plus a common internal one, to show how we shape structure for different kinds of documentation. They are examples of our approach, not ScribeOps products. Open one and browse the actual articles.

Pure Diátaxis Mozilla's free, open-source email client. Diátaxis framework User-flow structure The DNS lookup utility from the BIND tools. Task / journey-based API and SDK reference The multiprotocol file-transfer C library behind curl. Library / SDK reference Custom structure A terminal multiplexer for sessions, windows and panes. Bespoke / hybrid Internal knowledge base An internal, agents-only knowledge base of SOPs. Internal KB / SOPs
Expertise

What a senior writing team brings.

Documentation is not one skill. It's a stack of them. Here's the depth the ScribeOps team pairs with your product.

Information architecture

We map every product, feature and path to reach it, then pick the doc structure that fits, before a single word is written.

Adapted documentation structure

No forced framework. We shape the right set for your product: API reference, tutorials, how-to guides, reference and concepts, in a task-based structure your users can follow.

API & developer docs

OpenAPI reference, SDK guides, quickstarts and code samples that are tested, not guessed. Written for people who read the source.

Documentation audits

Gap analysis, broken-link checks and a line-by-line audit of every article against your style guide, grammar and structure.

Standards & compliance

Generic, ISO/IEC/IEEE 15289 or ISO 9001. We match the documentation lifecycle to your product and your compliance needs.

Bilingual EN / FR

Native-quality English and French, remote-first, built for international SaaS teams. Inclusive language, free of idioms that don't travel.

Works with your stack

We work in the tools you already use.

No rip-and-replace. We plug into your existing workflow and documentation platforms, so docs live where your team writes and your users read.

Jira We read your tickets and turn shipped work into documentation.
Confluence We write and maintain docs directly in your team's wiki.
GitBook Docs-as-code publishing with a polished reading experience.
MkDocs Markdown docs with the Material theme, versioned in Git and built in CI.
Docusaurus React-based docs sites with versioning and localization.
And most other docs-as-code toolchains: SphinxAntoraHugoJekyllRead the DocsAstro StarlightNotionZendeskSharePoint

If it takes Markdown, reStructuredText or AsciiDoc and publishes from Git, we can work in it. Tell us your stack and we'll fit into it.

Packages

Work with us your way.

Whether you need one project delivered or an ongoing documentation function, there is a way to work with ScribeOps that fits how your team operates.

One-shot
A defined project, delivered.

A scoped piece of work with a clear start, end and deliverable.

  • Documentation audit and gap analysis
  • A complete doc set for a launch
  • A one-off migration to docs-as-code
  • Fixed scope and timeline
Scope a project
Most popular
Part-time
Ongoing docs, a few days a week.

A senior writer embedded in your team on a recurring retainer.

  • A set number of days per week or month
  • Continuous writing, review and maintenance
  • Present in your Slack and standups
  • Scale up or down as you need
Start a retainer
Full-time
A documentation function, without the hire.

A dedicated writer working as part of your team, full time.

  • One writer, fully embedded
  • Owns your entire documentation surface
  • Planning, writing, publishing and reporting
  • The output of a hire, none of the overhead
Talk to us
Start a project

Tell us what your users can't find.

Send us your product, your docs (or lack of them), and the gap you're feeling. We'll come back within two business days with a scope and a plan.

  • Documentation audits & gap analysis
  • Full docs sets: tutorials, how-tos, reference, explanation
  • Ongoing docs-as-code retainers
Get in touch

Or email us directly: didier@scribeops.com Mauritius · GMT+4