Scoping call
Email us the docs URL and what is going wrong. We reply within 1 business day and book a call at a time that overlaps your morning.
Senior work, EU rates
Docs-as-code migrations and AI-ready documentation
voix is a documentation studio in Chișinău, Moldova. We move help centers off Zendesk and Confluence into docs-as-code, turn support tickets into knowledge-base articles, and structure docs so AI assistants stop making things up. We also translate and review docs in any language pair, build and fix Docusaurus sites with accessibility included, keep release notes current, and rate multilingual AI output.
docs/guides/authentication.md
@@ Zendesk Guide export → docs/ in your repo @@
-<div class="article-body">
- <h2 style="font-size:18px;color:#333">Authentication</h2>
- <p><span style="font-family:Arial,sans-serif">Send your
- key in the </span><code style="background:#eee">
- Authorization</code><span> header.</span></p>
-</div>
+---
+title: Authentication
+description: Send your API key in the Authorization header.
+sidebar_position: 2
+---
+
+## Authentication
+
+Send your key in the `Authorization` header.
The problem
What usually brings a SaaS team to us#the-problem
Nobody hires a documentation studio because the docs are fine. These are the situations that start the conversation, and each one maps to a service line below.
- A help center trapped in a platform
- Your articles live in Zendesk Guide or Confluence. You cannot review a change as a pull request, version the docs with the product, or leave without an export that arrives as markup instead of content.
- Tickets answering the same questions
- Agents answer the same questions every week because the knowledge base never covered them. The answers already exist, scattered across resolved tickets nobody has time to read as a whole.
- A support bot that makes things up
- Your AI assistant retrieves duplicated, outdated or badly split pages and answers with confidence anyway. Most of the fix is in the content it reads, not in the model.
- Docs that fail accessibility checks
- A customer asks about WCAG 2.2 AA or ADA, and the docs site has contrast failures, keyboard traps, skipped headings and images with no alt text. Heavy pages make it slow on top of that.
- Release notes and translations lagging
- The product ships faster than the changelog. Screenshots show an older UI, versioned docs fall behind, and translated pages trail the English ones by several releases.
Services
7 service lines, all priced in public#services
Each card links to the page with the scope, the deliverables and the full price. Prices are in USD; EUR is available on request.
01
Docs-as-code migrations
We move help centers and wikis off Zendesk, Confluence, Word or Google Docs into Docusaurus, MkDocs/Zensical or GitBook, with every old URL redirected. From $4,500 (up to 150 pages), $9,500 (up to 500 pages), custom above.
02Support-ticket mining into knowledge base and FAQ
We read your resolved Zendesk or Zoho Desk tickets, find the questions customers keep asking, and write the KB and FAQ articles that answer them. From $1,800 per 500 tickets.
03AI-ready content structuring
We restructure docs so RAG assistants and support bots retrieve the right, current page: chunking, metadata, deduplication and cleanup. $2,500 audit; implementation from $6,000.
04Localization and LQA
Translation, MT post-editing and LQA for any language pair. Romanian and Russian are handled in-house; other languages go to vetted partner linguists. $0.05 per word; LQA $45/hour.
05Docs-site engineering and accessibility
React and Docusaurus components, search, versioning, and WCAG 2.2 AA and ADA remediation on the docs site itself. $75/hour or $560/day; accessibility audit from $1,900.
06Release ops
Changelogs, release notes, versioned docs and screenshot or GIF refreshes, shipped with every release through a review gate. Retainer from $900/month.
07Multilingual AI data work
Human rating, evaluation and red-teaming of AI model output, in any language, following your guidelines and your tooling. $35/hour.
08Not sure which one?
Describe the problem instead of picking a service. We reply within 1 business day and tell you which line fits, or that none of them does.
The difference
What you own after the handover#what-you-own
The end state is documentation your team can run without us and without a vendor: Markdown in your Git account, a build you can run locally, and a publishing pipeline your engineers can read and change.
- The repository
- Your docs ship as Markdown files with frontmatter in your own Git account, next to the config and build scripts that turn them into a site. We work in your repository from the first commit, so there is nothing to hand back at the end.
- The build
- The site builds with open-source tooling such as Docusaurus or MkDocs/Zensical, or on GitBook if you choose it. A README says how to run it locally and how it deploys, so any developer on your team can read it and change it.
- The content
- On full payment the deliverables are yours: every article, translation, template and redirect map. We keep only our own pre-existing tools and know-how, and we publish nothing about your project without written consent.
Platforms, languages and standards
- Docusaurus
- MkDocs and Zensical
- GitBook
- Exports from Zendesk, Confluence, Word and Google Docs
- Any language pair
- Romanian and Russian in-house
- Other languages via vetted partner linguists
- MT post-editing and LQA
- Docs-as-code review gates
- WCAG 2.2 AA
- Versioned docs
- AI-ready structure and metadata
Process
How a project runs#how-it-works
Four steps, in order. The quote fixes scope, price and delivery dates before the first file moves, and nothing ships without your review.
Fixed USD quote
You get a written scope with a fixed price in USD: what moves, what gets rewritten, what is out of scope, and when each slice ships. EUR on request.
Build in reviewed slices
We deliver a section or a batch of articles at a time, each one reviewed as a pull request, so problems surface early instead of at launch.
Handover
You get the repository, the redirect map and a README for running it. Anything we delivered that breaks during the 30-day fix window after delivery, we fix at no charge.
Questions
What SaaS teams ask first#common-questions
Short answers to the questions that usually come before a scoping call.
What does it cost?
Prices are public. A docs-as-code migration starts at $4,500 for up to 150 pages and $9,500 for up to 500. Ticket mining starts at $1,800 per 500 tickets, and an AI-readiness audit is $2,500. Every project gets a fixed USD quote after a scoping call.
Will our time zones overlap?
Yes, for part of your day. We work from Chișinău, which is UTC+2 in winter and UTC+3 in summer, so our afternoon overlaps the US morning. Most of the work happens asynchronously in pull requests, and we reply to email within 1 business day.
Who actually does the work?
A senior documentation lead owns each engagement end to end, from the scoping call to the handover, and stays your single point of contact. Romanian and Russian are handled in-house; other language pairs go to vetted partner linguists.
Will we lose search rankings when we migrate?
Not if the redirects are done properly. Every old URL gets a mapped redirect to its new page, and the map is checked before launch. The guide to moving from Zendesk to Docusaurus without losing SEO walks through how.
Tell us what is broken in your docs
Send the docs URL, roughly how many pages or tickets you have, and where you want to end up. We reply within 1 business day, and the scoping call ends with a fixed USD quote.