Service scope
Four connected layers: interface strings, product descriptions, marketing copy, and the terminology and QA work that keeps them aligned. Every engagement opens with a string inventory, so the estimate reflects real word counts and the number of plural, gender, and case variants.
Outside the scope by default: legal certification, print production, and live A/B testing. We name these during scoping rather than absorbing them quietly.
Send a string sample for scoping| String | Requested | Draft scope | Confirmed |
|---|---|---|---|
| UI-014 | Save button, 14 char limit | Shorten label, keep verb first | Verb-first label, limit checked in build |
| PRD-207 | Feature table with units | Convert units, keep number format | Metric first, separator convention noted |
| MKT-031 | Launch email subject | Rewrite for tone, keep the claim | Claim intact, no added superlatives |
| QA-005 | Plural and case variants | Count categories, agree gender | Four categories, glossary locked |
Character limitPlural rulesCase agreementGlossary locked
Note 03: a draft scope never ships without a confirmed row and a named reviewer.
Service lines
Interface strings, product content, marketing copy, terminology and QA run through a single workflow: source in English, draft, reviewed Ukrainian, notes kept on the same row.
Buttons, form errors, empty states and inline hints rebuilt to the character limits your layout already enforces.
QA Plural forms verified for one, few, many and other.
Specs, sizes, materials and feature names adapted so the Ukrainian listing matches the source catalogue, line by line.
Note Model numbers and dimensions copied verbatim.
Landing pages, campaigns and lifecycle emails written for a Ukrainian reader, keeping claims and tone consistent with the source.
Note No promise added in Ukrainian that the source did not make.
One approved term per concept, agreed before production starts and applied across product, help centre and campaigns.
Approved Green rule marks terms locked in the glossary.
Second-pass review against the source file and a screenshot diff of the built screen, with findings written beside each string.
QA Files ship only after the review pass is closed.
Send your source files and you get a scoped estimate with open questions listed. Request a scope review
Process ledger
Start with a single batch and scale into a release cycle. Timelines count working days from the moment source files and terminology are approved.
300 to 500 strings from one screen or one product page. You get a reviewed Ukrainian file, a starter terminology list, and QA notes on character limits and plural categories.
Pilot scopeGlossary seedWorking days for the full batch. One revision round sits inside the quote; further rounds are priced separately.
One release window: interface strings plus product descriptions for every screen in scope. Returned as reviewed files per string group, a redline log, and glossary updates.
Release windowPer sprint, provided the drop arrives complete. Redlines sit in the source file, not in a separate email thread.
Continuous review tied to your cadence. Each drop gets a regression pass over approved terms, a drift check against the glossary, and notes on tone, gender, and case agreement.
OngoingWorking days to open review after each drop. Findings land in the same ticket as the string.
A standing glossary and style guide kept under version control: approved terms, plural rules, reject lists, and a dated changelog you can hand to any vendor.
Style guideWorking days to stand the glossary up, then a monthly review so approved terms do not drift.
Include the screen, the string count, and any glossary you already maintain.
Scope notes / Q&A
Scope, formats, AI disclosure and how an estimate is built, stated plainly. If your question is missing, write to contact@aeathevr.com.
Related: the process ledger and the scope form.
Interface strings, product descriptions, marketing and lifecycle content, terminology bases and QA. UI work covers character limits, placeholders and variable order, so a button that fits in English still fits in Ukrainian.
JSON, YAML, .strings, XLIFF, PO, CSV and spreadsheet exports for product catalogs. Marketing copy arrives as Word, Google Docs or InDesign packages. Send one sample file and we confirm the import rules before quoting.
Machine translation or an LLM may be used as a drafting aid, and the estimate says so. Human review and QA are part of the agreed scope: every delivered string is edited and terminologically approved. No project is described as fully human unless the scope states it.
From string count, content volume, review rounds and terminology work. We do not promise rankings, sales figures or a fixed turnaround before the files are read. You receive a written scope with every assumption listed.
Ukrainian uses one, few and many plural categories, and UI labels must agree in gender and case with the noun they describe. Each plural or gender-sensitive string is flagged, tested with real counts and signed off in the terminology sheet.
Two rounds plus a final QA pass by default: linguistic review, then a consistency check against the approved glossary. Additional rounds are quoted separately, and corrections return as a redline file you can merge.