Skip to content

Services

Internationalization for existing SaaS products

Adding another language affects more than the interface strings. We help product teams make internationalization part of their code, translation workflow, and delivery, including the content their users create.

When this helps

  • Text is spread through an established codebase and language support is difficult to introduce safely.
  • Catalogs, terminology, reviews, and releases are disconnected from the team's development workflow.
  • Users need to work across languages with content they create themselves, not just translated interface labels.

How we work with your team

Separate the language problems

We inventory interface text and user-generated content as different concerns. With your team, we clarify languages, context, terminology, review responsibilities, and the systems that already hold or translate the content.

Build the workflow into the product

For the interface, we connect extraction, catalogs, review, and build or release integration. For user content, we examine the translation pipeline, processing, quality evaluation, and operational needs separately.

Introduce the changes incrementally

We work in the existing application and its delivery process. Pairing, code reviews, and documentation help the team understand the conventions and maintain language support after the initial work.

What you take away

  • An internationalization approach that distinguishes interface text from user content.
  • Agreed extraction, catalog, terminology, and review workflows connected to development.
  • Implementation and operational guidance for the language capabilities in scope.

Experience behind the work

At Regrello, Werner and Fastner worked on interface internationalization and translation of user-generated content. Their profiles explain their respective work; Chris Lewis's recommendation also describes the shared contribution.

Read the Regrello recommendation

Our open-source work on Palamedes grows from practical internationalization experience. It is relevant tooling experience, not a requirement that your team adopt Palamedes or buy a managed product.

Meet the consultants and their experience

Scope and fit

This work fits an established product whose team needs language support to become a maintainable capability. We work with the application's current architecture and the people responsible for its content and releases.

We do not promise perfect automated translations or a guaranteed market outcome. Quality criteria, human review, and the handling of sensitive content need to match the product and the material being translated.

Before we start

Do we need to change translation tools?

Not by default. We first examine the workflow and constraints. Keeping existing tools, improving their integration, or changing part of the setup are options to assess with your team.

Is translating user content the same as localizing the interface?

No. Interface text usually follows the development and release workflow. User content needs its own processing, evaluation, and operational decisions. We agree which problem the engagement needs to address.

How do we start?

Tell us which application and languages are involved, where the current process breaks down, and who develops, translates, and reviews the content. We can then discuss a useful first scope.

Start with the situation

Tell us what your team needs to decide or change. In an introductory conversation, we discuss whether and how we can help, before agreeing a scope.

Newsletter

Why build our own translation tools? When is it worth reworking an architecture? In our newsletter we share the decisions behind our software and what we learn when teams put it to use.

See what we build beyond consulting.

We build products, open-source projects and agent tools for everyday work.

Discover Sebastian/Software

A drawn desk calendar with one marked appointment beside a potted plant.