What This Service Covers
You get your site working properly in every language you sell in, and a translation bill that stops growing every time you add a page. Elevio Solutions is a software development company in Belgrade, Serbia, and we build the language layer as part of the site rather than bolting it on afterwards. The engine underneath is ours, which is the reason this costs less than the usual arrangement and why your translations sit on our own platform rather than in a plugin vendor’s cloud you have no relationship with.
This page covers the whole of it: setting up a site to work in several languages, moving one that already does, keeping translations in step as the content changes, and the day-to-day of publishing when your team writes in one language and sells in four. If the site itself still needs building, that is websites and e-commerce.
Who This Is For
- You are opening a second or third market and the site is the last thing standing between you and selling there.
- Your translation bill grows every month and you cannot see why, because you are charged per word for sentences the site has already paid to translate.
- Your translations live somewhere you do not control: a plugin vendor’s cloud, a subscription that goes up, and no clean way to take your own words with you if you leave.
- The languages have drifted apart. The English page was updated in March, the German one still says something you no longer offer, and nobody noticed for six months.
- You tried machine translation and it embarrassed you in front of a customer, so now everything waits on a human and nothing ships.
What You Actually Get
You Pay for a Sentence Once
Most translation arrangements charge you per word, every time, including for text the site has already translated. That is why the bill grows with the site instead of settling down. Your setup keeps every approved translation and reuses it wherever the same text appears again, so a phrase in your footer, your checkout or your product template is paid for once and then free for the rest of the site’s life. The savings compound: the more you publish, the larger the share of each new page that is already translated before anyone looks at it.
A Human Stays in Charge of What Ships
Machine translation gets a draft in front of you in seconds, and that is genuinely useful. What it must not do is publish itself. Translations are graded, so you can see at a glance what a machine produced, what a person checked, and what has been approved as the wording you stand behind. You choose where the line sits: some sites publish machine drafts for blog posts and require approval for anything on a product or checkout page, and that is a sensible default rather than a compromise.
Your Translations Sit on a Platform We Answer For
Your approved translations live in a Translation Memory we build and operate, not in a plugin vendor’s cloud whose pricing and terms you do not control. When something needs to change, you are asking the people who wrote it rather than filing a request with a supplier. Ask us on the call exactly what leaving would involve for your setup, and you will get a straight answer rather than a brochure one.
You Can See What Has Been Checked and What Has Not
Every machine translation enters the memory as a candidate. Review and approval move it up through trust tiers, from candidate to verified to gold, and the tier travels with the segment. So the question “has a person actually looked at this sentence?” has an answer you can query rather than guess at, which is the difference between a translation you can stand behind and one you hope is fine.
One Team for the Site and the Language Layer
Because we build both, there is one team to call when something needs to change and no argument about whose side the problem is on. The platform is ours, so a change you need is something we can make rather than a feature request filed with a supplier.
The Engine Is Ours, and That Is Why This Costs Less
Most agencies resell someone else’s translation service, add a margin, and pass the per-word pricing on to you. We built and operate Polyglot Translate Cloud, a translation platform live in production, and the WordPress plugin that talks to it is ours too. The Polyglot Translate Connector is published on WordPress.org.
You do not have to care about any of that. It matters for exactly three reasons: the pricing is not a per-word margin on top of a vendor’s bill, the reuse that makes repeat text free is something we built rather than something we hope our supplier offers, and when you need a change we can make it instead of filing a feature request with someone else. It also means we run this in production every day, which is a different thing from having read the documentation.
What We Do Not Claim
The automation page on this site names two capabilities and says plainly which ones it does not have, and this page follows it. We have not built a migration path that lifts translations out of another vendor’s plugin, and we do not promise one: if you are moving from an existing setup, what carries over is a question for the call, and the honest answer may be that some of it does not. We do not employ translators. And we will not tell you a language layer improves your search rankings by itself, because the thing that decides that is whether each market gets content worth ranking.
What is proven is the part above: the memory, the trust tiers, the three engines, and a platform that has been running in production with its own subscribers rather than a slide about one.
What It Looks Like Six Months After Launch
| What you need to do | What that takes on your site |
|---|---|
| Publish a new page in four languages | The repeated parts are already translated and free; only genuinely new text costs anything |
| Check what a machine wrote before it goes live | Every segment carries its trust tier, so approval is a review rather than an audit |
| Ask for a change to how translation works | It reaches the people who build the platform, not a vendor’s support queue |
Process and Pricing
- Discovery call. Which markets, which languages, how much content, and who on your team approves wording. If a plugin off the shelf genuinely fits your case, you hear that on this call.
- Fixed scope. A written proposal with a fixed price and a date, before a line of code exists.
- Setup. Languages configured and the translation layer wired into your site.
- Handover. Your team is walked through publishing and approving in their own editor, on your own site.
- Support. A direct line to the people who built both the site and the platform under it.
A language layer is quoted with the work it sits on: custom websites start at EUR 2,500 and platform builds at EUR 5,000, and maintenance partnerships start at EUR 350 per month. What moves the number is how much content you have and how much of it needs a person to approve the wording. Tell us which markets you are opening and you have a reply within 24 hours: start here.
Frequently Asked Questions
How much does a multi-language website cost?
It is quoted with the work it sits on rather than as a separate product: custom websites start at EUR 2,500 and platform builds at EUR 5,000. What moves the number is how much content you have and how much of it needs a person to approve the wording. You get a fixed written proposal before any code, so the price you accept is the price you pay.
Do you use machine translation, or human translators?
Both, deliberately. A machine produces the draft in seconds, which is what makes publishing in four languages affordable at all. A person approves anything you would be embarrassed to get wrong, and the system tracks which is which so you can see the difference at a glance. You decide where the line sits, typically machine drafts for blog content and approval required on product and checkout pages. We do not employ translators ourselves; where you need a professional linguist we work alongside yours.
Why is this cheaper than paying per word?
Two reasons. Every approved translation is stored and reused, so text that repeats across your site is paid for once rather than every time it appears, and that share grows as you publish more. And the platform doing the work is ours rather than resold, so you are not paying a margin on top of another vendor’s per-word rate.
Which languages do you support?
The platform treats Serbian, Croatian, Bulgarian and Slovenian as first-class languages rather than an afterthought behind the large Western European pairs, which is one of the reasons we built it instead of reselling someone else’s. The major European languages are covered too. Tell us which markets you are opening and we will confirm on the call rather than promise a number here.
Are you a translation agency?
No. We are a software development company, and we build the platform and the site it runs on. We do not employ translators. Machine translation produces the draft and your team, or a linguist you already work with, approves what ships. If what you need is a human translation service rather than a language layer built into your site, we are the wrong call and will say so.