About
voix is a documentation studio in Chișinău, Moldova. We migrate help centers to docs-as-code, structure documentation for AI assistants and localize it, with senior work at EU rates.
A documentation studio for SaaS teams: migrations, support content, AI-ready docs, localization and docs engineering.
Chișinău, Moldova. We work remotely with SaaS teams, in writing first.
Written scopes, fixed USD quotes, review gates and a reply within 1 business day.
The studio
voix is a documentation studio in Chișinău, Moldova. We work with software teams on the layer between writing and engineering: where documentation lives, how it ships, and how people and machines read it.
Most of our work sits in the gap between two jobs. A technical writer knows how to explain the product; a platform engineer knows how to build and ship a site. Nobody owns the layer in between: what counts as a page, where it lives, who reviews it, how it reaches production, and what a support bot or a translator does with it afterwards. That layer is what software teams hire us for.
The positions on this site are ours. Documentation belongs in the same repository as the product it describes. Reviewing a docs change should look like reviewing a code change. A platform you cannot leave is a platform you do not own. And content written for people is now also read by machines, so structure is no longer a nice-to-have.
There is no client list here and no logo strip. We do not publish a client’s name or work without written consent, as the confidentiality policy says, so the proof on offer is the method, written down in enough detail to argue with. The services page says what each line delivers, the pricing page says what it costs, the process page shows how a migration runs, the case studies are labeled composites, and the guides show our reasoning before you pay for any of it.
Service lines
We offer seven kinds of work. They share one idea: documentation is a product asset that should be structured, versioned and owned by the team that ships the product. Each card opens the service page with the scope and the price.
We move product docs off Zendesk Guide, Confluence, Word or Google Docs into Markdown in Git, published with Docusaurus, MkDocs/Zensical or GitBook, and we redirect every old URL so bookmarks and search traffic survive the move.
We read your resolved Zendesk or Zoho Desk tickets, group them by the question the customer was really asking, and write the knowledge base and FAQ articles that answer it before the next ticket is opened.
We restructure docs so a support bot or AI assistant retrieves one clear, current answer: consistent chunks, useful metadata, duplicates merged and stale pages retired, so it stops guessing.
We localize docs and UI in any language pair and run LQA on the result. Romanian and Russian are handled in-house; other languages go to vetted partner linguists while we keep the glossary and the review.
We build and fix docs sites: React and Docusaurus components, search, versioning and CI, plus accessibility remediation against WCAG 2.2 AA for teams that need to meet ADA expectations.
We keep docs in step with your releases: changelogs, release notes, versioned docs and refreshed screenshots and GIFs, shipped every release through a review gate.
We rate, evaluate and red-team AI model output in any language, with the same attention to meaning and tone that translation review needs.
Every line has a published USD price on the pricing page, so you know the order of magnitude before you write to us. The flagship is the migration, and the others often follow from it: once docs are in Git, mining tickets for missing articles, structuring content for an AI assistant, translating it and shipping it every release all become ordinary pull requests.
Principles
Six rules decide how a project runs. Each one costs us something, which is the only reason to believe they are real.
Every project starts with a written scope and a fixed USD quote: what we deliver, what we need from you, and what is out of scope. If something new comes up, we write it down with its price, and nothing changes until you approve it.
Most of the work is written and reviewed in pull requests, issues and email, so being in another time zone costs you nothing. We reply within 1 business day, and we book live calls for kickoff, reviews and handoff in your morning.
Each phase ends in something you can open and check: an inventory, a structure, a converted batch, a translated set. The next phase starts only when you approve it, so you see the work while it is still cheap to change.
For 30 days after delivery, anything we delivered that does not work as scoped gets fixed at no charge. If you want ongoing help after that, the release-ops retainer covers it. If you do not, you owe nothing further.
Your docs live in your Git organization from the first commit, in open formats (Markdown, frontmatter, a sidebar file) built by open-source tools. You can change hosts, tools or studios without asking us.
If a request would make your docs harder to maintain, or belongs in a tool you already pay for, we tell you that instead of quoting for it. The cheapest page is often the one nobody has to write.
These are principles, not the agreement. The terms of service set out payment, defects, ownership and liability in full, the confidentiality policy covers how your material is handled during and after the work, and the privacy notice covers personal data.
If you want the same principles as steps rather than positions, the process page puts a migration in order and says what we need from you at each review gate, and the FAQ answers the questions that usually come before a first email.
Languages and tools
English is our working language. Romanian and Russian are in-house, and partner linguists cover other pairs. The tools below are the ones we actually work in, not a wall of logos.
Location and contact
In Chișinău, Moldova. We work remotely: in writing most of the time, on a call when a call is faster.
Moldova runs on Eastern European Time, so our afternoon overlaps the US East Coast morning. That is enough for a kickoff, a review or a handoff call. Everything else moves in pull requests and email, which read the same whether the reviewer is next door or an ocean away.
Senior work at EU rates is not a promise to cut corners. It is what working from Chișinău makes possible: the same review gates, the same written scope and the same care, at a price published in USD and fixed before the work starts.
The first step is an email. Tell us where your docs live, roughly how many pages there are, and what forced the question. You get a reply within 1 business day, and either a scoping call or a straight answer about why we are not the right fit. The contact page lists what to include.
Send your docs URL and what you want to change, and you get a reply within 1 business day.