What this covers
You can publish or submit with confidence, because the translation reads naturally, says the same thing as the source, and comes back in files that still work.
We’ll run translation and localisation from your source files, keep your formatting intact, and give you a checked delivery package you can publish or submit. You’ll know who is translating, what we’re following for terminology and style, and what changed between source and target. Once we’re done, you’ll have language versions that fit the UI, match your house style, and pass review without last-minute rewrites. Send the files you want priced and we’ll come back with a quote and a delivery plan.
We quote from the files you’ll actually ship, set up the project in a CAT tool so repeated text stays consistent, and align on glossary and style before we translate. Every job goes through bilingual review and QA checks for meaning, numbers, names, links, and tags, then we return a delivery package you can drop into your build or layout.
About us
We’re a small Cardiff-based team that does translation and localisation all day, and we stay close to the files, not just the words. We started in document-heavy work where a small mistranslation can cause real damage, then pulled the same habits into web and software, where a broken tag or a too-long string can break a release.
Clients come to us when they need language they can defend and files they can use. We keep one accountable team on your work, we confirm terminology before we translate, and we run QA on what you will publish, not on a copy-pasted version. If something is unclear in the source, we flag it and offer options instead of guessing.
Who you will work with
You’ll deal with the same few people from quote to handover, and you’ll always know who to message when something changes.
Team
Carys Morgan, Project manager. Carys runs your schedule and files, confirms what we’re working from, and keeps a single list of open questions so nothing gets lost in email.
Owain Griffiths, Lead translator. Owain leads translation decisions, builds or refines the glossary, and keeps tone and terminology consistent across every file in the set.
Eleri Thomas, Software localisation lead. Eleri handles software and app localisation, checks tags and variables, and makes sure strings fit screens, buttons, and store listing limits.
Rhiannon Price, Reviewer and QA editor”】【{. Rhiannon reviews and QA-edits every target file, checking meaning, numbers, names, punctuation, and layout-sensitive breaks before delivery.
Selected work
A few recent translation and localisation jobs that show the mix of file types and the level of checking we build into every delivery.
Portfolio
App update localisation. We localised UI strings, onboarding, and release notes from source files, then ran checks for variables and character limits so the build could ship without rework.
Tender pack translation. We translated a multi-document tender pack and kept headings, numbering, and tables aligned so the submission matched the source structure page by page.
InDesign brochure translation. We translated an InDesign brochure and returned an IDML package with styles preserved, overset text flagged, and all amended pages ready for final export.
“The translations read naturally, and the files dropped straight back into our build.”
Product manager, a software team shipping regular releases
How we work
We keep the work auditable. You’ll see what we received, what we changed, what we queried, and what we’re returning, with the same file structure you sent.
1. Quote and plan Day 1 You send the source files and target languages. We confirm file types, count words from the source, and flag anything that affects time or risk, like scanned PDFs, tracked changes, or missing screenshots. You get a quote, a delivery date, and a list of what we need from you to hit it. 2. Glossary alignment Days 2-3 We collect your house style, existing translations, term lists, and any product vocabulary you already use. If you have nothing written down, we draft a starter glossary from your source and ask you to approve key terms and tone choices before translation begins. 3. Translation and review Days 3-10 We set the job up in a CAT tool so repeated text stays consistent, then translate and review in the same environment. You’ll see queries as we go, especially around ambiguous source phrasing, regulated terms, and brand voice, so decisions are made once and applied everywhere. 4. QA and handover Days 10-12 We run bilingual QA checks for meaning shifts, numbers, units, names, punctuation, and missing text, then do format checks for tags, links, and layout-sensitive line breaks. We deliver the finished files plus a short handover note listing any decisions, open questions, and items to watch in final publish.
Translated target files
Your content returned in the same file types you sent, ready to publish, submit, or import, with formatting preserved where the format allows it.
PROJECT GLOSSARY
A bilingual term list for key product, brand, legal, or technical terms, so the same term is used the same way across every file and future update.
STYLE AND TONE NOTES
A short set of choices we followed for voice, formality, punctuation, and Welsh or regional preferences, written so your reviewers can audit decisions quickly.
QA report
A checklist-style report of what we checked, plus any issues we found and fixed, such as missing numbers, mismatched names, or tag problems.
QUERY LOG AND RESOLUTIONS
A single list of questions raised during translation, your answers, and the final wording we used, so nothing relies on memory in a later release.
FINAL DELIVERY PACKAGE
A zipped handover with organised folders, clear file names, and a brief note on what changed, what to review, and where to paste or import each file.
Pricing
Pick the tier that matches how much file-handling and QA your release needs. Final pricing is confirmed after we review your source files and wordcount.
Priced items
Getting started
If you want to lock in the slot for translation and localisation, we can start as soon as you sign and send the source files.
1. Sign this proposal to confirm scope and timing. 2. Pay the 30% booking invoice so we can schedule the linguists and QA. 3. Send the final source files and any glossary or style notes, and we’ll begin.
Signature
Fee summary
Payment
We take 30% to book the work when you sign, then 70% when we hand over the finished work. Invoices are payable within 14 days of the invoice date.
What we need. Before we start, we need the source files, target languages, and your deadline. If you have a glossary, style guide, or previous translations, send them on Day 1 so we can align terminology.
Source files and formats. We quote from the files you supply and we deliver in the same format where possible. If we only receive a PDF or flattened artwork, we’ll confirm any limits on editability before you approve the quote.
Queries and approvals. We’ll keep a query log for anything that needs a decision, such as product names, UI limits, or legal wording. Turnaround on queries affects the schedule, because we don’t guess where meaning can shift.
Changes to scope. If the source text changes after Day 1, we’ll re-run the analysis and confirm the impact on cost and timing before we apply the change. Translation and localisation stays auditable when versions stay controlled.
Consistency of linguist
Owain Griffiths leads the translation work and keeps the glossary and style and tone notes consistent across files. If we need additional linguists for volume or languages, we’ll tell you before we assign the work.
Quality checks. Our bilingual QA checks terminology, numbers, names, and obvious omissions against the source. For software and app localisation, we also check tags and placeholders where they exist in the source files you provide.
Confidentiality. We treat your files as confidential and only share them with the translators and reviewers working on your project. If you need an NDA, send it with the source files and we’ll sign before setup begins.
Ownership and reuse. Once the final 70% is paid, you own the translated target files we deliver. We may retain the project glossary, style and tone notes, and QA report so follow-on updates use the same terms and choices.
