“For a small company like ours, Plunet is a big investment. But it’s totally worth it!”
Plunet published that quote. They’re proud of it — and to be fair, the company in question went ahead and implemented it anyway. But buried inside that sentence is the entire reason you might be reading this page.
This post is for translation agency owners who are somewhere in the middle of evaluating Plunet — who’ve sat through a demo, liked what they saw, submitted a contact form to get pricing, and are now waiting. Or who got the pricing and are trying to figure out what’s actually included. Or who’ve already signed and are three months into an implementation that was supposed to take three.
We’ll be direct about what Plunet is, who it’s genuinely right for, and where it falls short for the UK agency market. If Plunet is the better fit, we’ll say so.
What Plunet actually is
Plunet has been building translation management software since 2003. That’s more than two decades of institutional knowledge, and it shows in some ways that matter: a genuinely comprehensive feature set, deep bidirectional CAT integrations with Trados, memoQ, Phrase TMS, and XTM, a vendor management system capable of handling hundreds of resources, flexible hosting options including self-hosted and cloud deployments on AWS or Azure, and a support reputation that most users describe as responsive.
For large language service providers managing complex, high-volume workflows across multiple departments and geographies, Plunet has earned its position. It has well over 500 customers and a dominant share of mid-market and enterprise LSP deployments. That did not happen by accident. But Plunet is also a product built for 2003’s enterprise sales model, running on 2003’s API protocol (SOAP, not REST), and priced and deployed accordingly. Whether that’s right for your agency depends entirely on the specifics of your situation — and getting to those specifics is harder than it should be.
“Contact Sales” is not a price
There is no pricing page on the Plunet website. There is a contact form. This is not unusual for enterprise software, but Plunet is not always sold to enterprises. Agencies with three project managers inquire. Solo translators scaling up inquire. Translation departments at mid-size firms inquire. All of them submit the same contact form and wait.
Third-party aggregators estimate the floor somewhere around $220 per month. Actual costs, once you account for the number of users, the add-on modules you’ll need to run a real workflow, and the implementation services, run considerably higher. One commonly cited pattern: the quoted figure before the sales process looks very different from the invoice you’re signing.
What makes this harder to disentangle is that Plunet’s product is genuinely modular. The base system does a lot. But the things that transform it from a database into an automated workflow platform are not all in the base system.
The AutomationManager trap
Here is how the Plunet evaluation process often goes for a growing agency: you watch the demo, you see automated job dispatching, automated quote generation, automated vendor notifications. Your immediate reaction is that this is exactly what you need. You’ve been doing all of this manually. You sign up.
Then you find out that AutomationManager — the module that actually delivers most of that automation — is a separate paid add-on. It is not in the base package.
This is not a hidden clause in a terms document. Plunet is transparent enough that you can discover this if you ask the right questions during the sales process. The problem is that “ask the right questions” is doing a lot of work in that sentence. Most agencies evaluate TMS software on the strength of a demo. The demo shows what the platform can do. It does not always prominently flag which features require additional purchase.
The automation layer in a translation management system is not a premium extra. It is the point. If you are evaluating Plunet and automation is central to your use case — which it almost certainly is — establish in writing, before signing, exactly which modules are included in the package being quoted.
“If your TMS implementation manual is longer than your employee handbook, something has gone wrong.”
What 17 weeks actually costs
Plunet’s own documentation describes a three-phase implementation: system setup and administrator training, followed by user training at one to two sessions per week, followed by go-live. Their own documentation states: “The entire training phase with system setup, learning about the system and testing it usually takes around three months — with a good buffer.” The stated range is 3 to 6 months.
Plunet implementation timeline
Discovery calls. Documenting existing workflows for data model mapping.
System configuration — service types, workflow templates, vendor rate cards, price lists. Every client has different pricing; each must translate into Plunet's internal structure.
Admin training + user training (1–2 sessions/week). Plunet's own materials note: "project managers typically don't practice what they learned, and after training finishes, few resources remember how to accomplish even the simplest tasks."
Testing, parallel running, troubleshooting, go-live.
During all of this, your team is still running your business. Project managers are still managing projects, except now they’re also attending training sessions, answering configuration questionnaires, and learning a new system while completing their actual jobs. That opportunity cost does not appear on the Plunet invoice, but it is real.
“We have redesigned our price lists several times”
One user review that appears across multiple aggregator sites captures something specific:
“Managing many different price lists is very time-consuming, especially if one uses several CAT tools. Price lists really should be well thought out in the implementation phase, but unfortunately, in that phase, one often still lacks the necessary knowledge. We have redesigned our price lists several times.”
Translation agencies have genuinely complex pricing. Rates vary by language pair, by CAT match band, by client, by service type. Getting it wrong in the initial setup means going back and rebuilding it — and the period in between, when quoting is either manual, inconsistent, or both, is operationally expensive. VectorLingo’s CAT analysis pipeline runs natively through the Phrase TMS integration. When a file is analysed, the match breakdown maps directly to your rate card without a middleware layer or a manual import step. If rates change, you change them once.
DATEV, QuickBooks, Sage, ADDISON. Notice anything missing?
Plunet offers accounting integrations with DATEV (the dominant German accounting platform), QuickBooks, Sage, and ADDISON. For UK agencies, the options narrow to QuickBooks and Sage.
FreeAgent is not on that list. Neither is Xero. FreeAgent is the accounting platform of choice for a significant portion of UK small businesses and freelancers, partly because of its HMRC Making Tax Digital compatibility and partly because it is purpose-built for the UK market. An agency running FreeAgent for finances and Plunet for project management is running two systems that do not speak to each other.
Invoices generated in Plunet have to be manually recreated or exported and imported into FreeAgent. VectorLingo was built for the UK market from the start. FreeAgent sync is a first-class feature, connected via OAuth. When an invoice is raised, it moves to FreeAgent. The contact, the line items, the amounts — no retyping.
The communication gap
“Aside from one comments box when marking delivery, there doesn’t seem to be any other areas for comment threads or communication — thus that would need to happen outside of Plunet.”
Plunet does not have in-app messaging or comment threading. In practice, the communication layer for a project — translator questions, client feedback, revision requests — lives somewhere else. Usually email. Sometimes a team chat platform. When a project manager leaves and someone else picks up the file, the history they need is not in one place.
Plunet is the right tool if…
You are running a medium-to-large LSP — fifteen or more staff — with established, complex workflows that you need to configure precisely rather than adopt from a default template. You have a dedicated operations person who can own the implementation and ongoing administration. You need self-hosted deployment for data residency reasons, or you are already deeply integrated with Trados Studio at the enterprise tier. You primarily use DATEV, QuickBooks, or Sage for accounting. You have the budget and runway for a six-month implementation. In those circumstances, Plunet’s maturity and depth are genuine advantages.
VectorLingo is the right tool if…
You are running a UK translation agency with one to ten people and you are spending too much of your week on work that should be automated. You use Phrase TMS as your CAT platform. You run your finances through FreeAgent. You want to see your pricing clearly before you sign up. You need to be operational quickly.
VectorLingo starts at £15/month for freelancers and £49/user/month for agencies. There is a 30-day free trial. No credit card required at signup. The FreeAgent integration is included. The Phrase TMS integration is included. The per-language workflow tracking across nine step types is included.
There is no AutomationManager — because the automation is not an add-on.