Off the shelf translation or a custom workflow
Compare an existing translation tool with a custom workflow. Check staff effort, review, data handling, integration and maintenance before you choose.
Use an existing translation tool when it meets your task with acceptable effort and control. Consider a custom workflow when a specific gap causes repeated work, errors or delays. Compare both against the same business task before you commit.
Commercial disclosure: Vavus sells custom software. This guide explains when that work may be useful and when an existing tool may be sufficient. It does not rank translation providers or report a performance test.
Define what you are comparing
An off-the-shelf tool is a product you can use through its existing interface and settings. It may already include file handling, terminology options or team controls. Check the current product and plan rather than assuming those features are absent.
A custom workflow is software built or adapted around your process. It can connect a source system, translation, review and a destination. It may use an existing translation service underneath. Custom development does not necessarily mean building a new translation model.
A third option is to configure a connector or an automation in software you already use. Include this option in the review before you commission new development.
Choose an existing tool for a contained task
Start with a standard tool if one person translates occasional text and can check the result before use. It can also fit a repeatable document task when its supported formats and review process meet your needs.
Test the full job. Can the employee find the source, translate it, review it and return the result to the right record? Check whether the output keeps the required structure and whether staff can apply the correct terms.
Existing services can offer more control than basic copy and paste. For example, Google Cloud Translation documents a glossary feature for domain-specific terminology. [1] That is an API capability, not a promise that every consumer interface or subscription includes it.
If the available tool meets your requirements, avoid adding a custom system without a clear reason.
Consider custom work for a defined process gap
A custom workflow may be worth exploring when employees repeatedly move text between systems or struggle to track approval. Describe the gap in observable terms. For example, staff may need to copy an approved translation back into the correct support record.
The proposed software could keep the source and result together, route text to a reviewer and save the approved version to its destination. These are possible project requirements. They are not claims about a current Vavus integration.
Check the source application's supported interfaces first. A desired connection may be limited by access permissions, available APIs or the contract for that system. Include those limits in the estimate.
Ask who will maintain the connection when either system changes. Custom work creates an ongoing responsibility as well as an initial build.
Compare translation quality separately
A better interface can improve the review process, but it does not prove better translation. Test candidate approaches with the same representative content and language pairs. Ask a qualified reviewer to assess meaning, terminology and tone.
Check how each approach supplies useful context. DeepL's API, for example, has a context parameter and options for glossaries. [2] These controls need to be configured and tested for the task.
Keep the source text available during review. Define which mistakes block release and how corrections are saved. Measure the time to reach an approved result, not just the time to receive machine output.
Check control and total cost
For each option, ask where content is processed, who can access it and what is retained. Confirm these details for the exact service and configuration. Custom software that calls a cloud API still sends content to that service.
Compare costs over the same period. Include subscriptions or API usage, staff review, repeated data entry, setup, support and maintenance. For custom work, also include testing and changes to connected systems.
Do not assume automation always pays for itself. A low-volume task may not justify development. A frequent task with measurable handling errors may warrant a closer estimate. Use your own measurements instead of an unsupported savings percentage.
Run a small comparison before deciding
Write one task, a representative test set and the conditions for acceptance. Try the existing option first where practical. Record manual steps, review effort, defects and any control you cannot achieve.
If an important gap remains, ask for a focused custom proposal that addresses it. Keep optional features separate. Require a clear explanation of what the first release will do and how you will verify it.
Vavus offers written discovery for custom projects. [3] Describe your current process and the gap on the quote page. Compare the resulting scope with the existing-tool option before you choose.