FAQ
Straight answers about what each service costs, how a migration protects your search traffic, what happens to your support data, which languages we cover and how we work with remote teams. Every answer here is the one you would get on a call.
Published in USD for all 7 service lines, with EUR equivalents.
Within 1 business day, in writing.
A 30-day fix window on everything we deliver.
Pricing
Every service line has a published USD price. EUR equivalents are shown for teams that budget in euros.
A docs-as-code migration starts at $4,500 for up to 150 pages and $9,500 for up to 500 pages; larger sets are scoped individually. That covers the audit, conversion, redirects, the site build, author training and handoff described on the process page. In euros, the two tiers are about €4,150 and €8,750. The pricing page lists every tier and what it includes.
Support-ticket mining starts at $1,800 per 500 tickets. An AI-readiness audit is $2,500, and implementation starts at $6,000. Localization is $0.05 per word and LQA $45 an hour, in any language pair. Docs-site engineering is $75 an hour or $560 a day, and a WCAG 2.2 AA audit starts at $1,900. Release ops runs on a retainer from $900 a month. Multilingual AI data work is $35 an hour. The full price list shows the EUR equivalents.
Project work is fixed. Every project starts with a written scope and a fixed USD quote that names the deliverables, what we need from you and what is out of scope. If something new comes up midway, we write it down with its price, and nothing changes until you approve it in writing. Hourly lines such as engineering, LQA and AI data work are billed by the hour against a scope we agree in writing first.
Every delivery comes with a 30-day fix window: anything we delivered that does not work as scoped is fixed at no charge. After that, fixes and changes are billed at the engineering rate or covered by the release-ops retainer, whichever you prefer. The full commitments are in the terms of service.
Migrations and SEO
Platforms, redirects, ownership and timing: the questions that decide whether a migration is worth starting.
We move documentation out of Zendesk Guide, Confluence, Word files and Google Docs into Markdown in Git, published with Docusaurus, MkDocs (with Zensical) or GitBook. Other sources, such as a legacy wiki or an HTML export, are scoped after we see a sample. The dedicated pages cover Confluence to Docusaurus and Zendesk to Docusaurus, and this comparison helps you pick a target.
Redirects are what protect it. Every old URL is mapped to its new page, or to the closest useful parent, and shipped as a permanent redirect; internal links are rewritten so the build can check them; titles and descriptions move with the content. Redirect mapping and link checks are part of every migration, not an add-on. The Zendesk migration guide and the redirect mapping chapter explain the method.
You do, from the first commit. The docs live in your Git organization, in plain Markdown, built by open-source tools, so you can change hosts, themes or vendors later without asking us. On full payment you own the final deliverables; voix keeps rights only to its own pre-existing scripts, templates and know-how.
It depends on the page count, how messy the source export is and how quickly your reviewers clear each review gate. The timeline is written into the fixed quote before work starts, and it runs from the day we have access to the source content. The migration checklist lists what to prepare so review never stalls.
Support content and AI
Turning support history into articles, and structuring docs so AI tools answer from them correctly.
We work from an export of resolved tickets from Zendesk or Zoho Desk, cluster them by the question the customer was really asking, rank the clusters by volume, and write deflection articles titled in the customer's own words, including the exact error messages they paste. Pricing starts at $1,800 per 500 tickets. How ticket mining works and the method in detail.
Tickets are read to find the questions, and personal details of your customers are never copied into the articles. Where your helpdesk allows it, the export is filtered before it is shared. Working copies are deleted when the project ends. The confidentiality policy and the privacy notice cover the details.
Usually because the documentation it retrieves from is ambiguous: long pages that mix versions, the same procedure written several ways, missing metadata, and answers locked in screenshots the retriever cannot read. The model fills the gap with a confident guess. AI-ready structuring fixes the source: consistent chunks, clear titles, product and version metadata, duplicates resolved. The audit is $2,500; implementation starts at $6,000. AI-ready documentation and why your support bot hallucinates go deeper.
Human rating, evaluation and red-teaming of AI model output in any language: judging whether answers are correct, fluent and safe, writing adversarial prompts, and documenting failure patterns so they can be fixed. Romanian and Russian are handled in-house, and partner linguists cover other languages. It is billed at $35 an hour. Multilingual AI evaluation.
Languages, engineering, releases
The work that keeps a docs site readable in every language, usable by everyone and current with every release.
Any language pair. Romanian and Russian are translated in-house; other languages go to vetted partner linguists, and we run the project, the glossary and the LQA, so you have one contact. Translation is $0.05 per word and LQA $45 an hour. Localization and LQA.
We also build. React and Docusaurus components, theming, search, versioning and CI for docs sites that already exist are billed at $75 an hour or $560 a day. Docusaurus development describes the scope.
Yes. A WCAG 2.2 AA audit, from $1,900, tests the site with a keyboard, a screen reader and automated checks, and returns a prioritized fix list your developers can act on, which helps teams working toward ADA expectations. We can also make the fixes at the engineering rate. The accessibility audit and the common Docusaurus issues.
Changelogs and release notes written from your tickets and pull requests, versioned docs cut at each release, and screenshots and GIFs refreshed when the UI changes, all through a review gate before anything publishes. It starts at $900 a month. Release notes and the template we use.
Working together
Who does the work, how it runs across time zones, and how your material is protected.
A senior documentation lead owns each engagement end to end, from the first scoping call to the handoff, working from Chișinău, Moldova. Partner linguists join for language pairs beyond Romanian and Russian, and only after signing a written confidentiality agreement. More about voix.
Asynchronously and in writing. Scopes, questions and deliverables live in pull requests, issues and email, and we reply within 1 business day. Our afternoon overlaps the US East Coast morning, so live calls for kickoff, reviews and handoff are easy to schedule. Each phase ends at a review gate you approve before the next one starts.
Your docs URL or a sample export, the rough page count, where the docs live now and where you want them, the languages involved and any deadline. You get a reply within 1 business day, then a short scoping call and a fixed USD quote. Contact details.
Your material is used only to deliver the quoted work, never in marketing, and your name is never published without written permission. A separate written NDA can be signed on request. The commitments are in the terms of service, the confidentiality policy and the privacy notice.
Nothing on this page is a hidden term. The commercial answers come from the terms of service, the confidentiality policy and the privacy notice; the delivery answers come from the process, the services and the price list. If the question you need answered is missing, send it and it gets added here.
Send your docs URL, the rough page count and what you want to change. You get a reply within 1 business day.