Identify the decisions that change the budget
Four languages do not automatically mean four times the design cost, but they do multiply editorial responsibility. Cost rises with page volume, specialist terminology, regulated claims, custom integrations and the number of reviewers. An existing translation memory or approved glossary can reduce repeated work; unclear source copy increases it.
Integrations also need language decisions. Form confirmations, booking tools, CRM fields, transactional emails and downloadable documents may sit outside the visible page. Include them in the inventory so customers do not move from a polished localized page into an untranslated process.
- Number and uniqueness of localized pages
- Subject expertise and review standard
- Forms, documents and third-party journeys
- Redirects, analytics and technical migration
Budget for ownership after launch
The cheapest launch can become expensive if nobody owns updates. Decide who monitors changes to the source version, commissions adaptations and checks that links, offers and legal wording remain current. Reserve time for periodic parity reviews, especially after service, team or policy changes.
A staged release can protect quality and cash flow. Launch the most valuable language and page set first, measure real enquiries and add the next version when a reviewer and update owner are available. Keep the underlying structure ready for expansion so staging does not create rework.
- Named content owner per language
- Planned review cadence
- Allowance for new pages and changed offers
- Technical maintenance and quality checks
Frequently asked questions
Frequently asked questions
Is adding another language mainly a translation cost?
No. Translation is one line. Budget also for adaptation, review, publishing, metadata, navigation, forms and testing. The exact mix depends on your platform and who supplies approved content.
Can we reduce cost by launching fewer pages?
Yes. A focused first release can cover the pages needed to understand the offer and enquire. Avoid publishing thin or incomplete versions merely to claim language coverage.
Can you quote without a final page list?
We can discuss a planning range, but a responsible proposal needs an agreed page and language inventory, content responsibilities, integrations and review standard before paid work begins.