🚀 Integration Possible - What Really Worked

Last weeks lingo systems | Tech Talk was a deep dive into a game-changing integration between Plunet and translate5 and it delivered on transparency, real-world insights, and step-by-step technical brilliance.

💬 What the Audience Told Us

We kicked off with a live survey and the results were loud and clear:

• 96% of participants said custom integrations between TMS and CAT tools are either “Very Important” or “Important”.

• 73% believe it plays a central or supporting role to influence or extend their TMS/editing system - especially in light of AI’s growing role.

• Over 80% are already using or planning tailored IT to optimize their processes.

📊 The takeaway? Translation businesses want control. They need flexibility. And they’re ready to move beyond off-the-shelf systems toward tailored, scalable, and automation-ready solutions.

🔍 The Integration in Focus

Plunet (presented by Sufian Reiter) enables 60,000 users daily across 450+ companies. With open APIs and JavaScript-powered UI customization, it offers a playground for teams to streamline their own processes – without waiting for vendor-side changes.

translate5 - Visual translation & terminology management (led by Marc Mittag) stands out as a professional, open-source alternative to closed CAT systems. It combines transparency, freedom, and commercial support - with innovative extensions like prompt-based AI assistance and real-time visualization.

The demo by Sylvia Schumacher and Marcel Moch showcased exactly what’s possible when custom-built tools meet business logic:

• Seamless quote-to-delivery workflows

• JavaScript UI plugins that integrate deeply with Plunet

• SOAP API communication, callback handling, job mapping, and automatic file exchange

In short: a made-to-fit solution, purpose-built for speed, clarity, and reliability.

🔧 What lingo systems Brings to the Table

lingo systems specializes in the last 20% of your tech stack - the part where standard tools stop and your actual needs begin.

Examples:

• 🔁 Custom connectors for systems like Plunet and translate5

• ⚙️ Middleware that aligns tools with your business logic

• 🧩 UI extensions that make existing systems more usable

• 🤖 AI-ready interfaces that plug into modern workflows without disruption

All of it is backed by a team with deep domain expertise (not just in code, but in translation workflows, project management, and language tech strategy).

"Because your system should work for you. Not the other way around." Quote from a wise man from the lingo systems marketing department.

🎙️ Behind the Scenes - Continuing the Conversation

After the official session ended, something interesting happened. While attendees logged off, our speakers André, Marc, Sufian, and Marcel kept going in the virtual "green room."

The demo had sparked so much interest (and a queue full of unanswered questions), we decided not to let that insight go to waste.

So we hit record.

What followed was a candid conversation on the real trade-offs between No-Code, Low-Code, and custom development, full of memorable metaphors, practical advice, and strong opinions.

🔽 Scroll down for the full transcript - or jump to some highlights:

🔹 Why they chose custom development over No-Code

“No-Code is more like ‘less code’ in reality. If you need full control over workflows and UI, custom development just makes more sense - especially long-term.” Marc Mittag

🔹 Shoe metaphors and the truth about integration

“It’s like buying shoes. Flip-flops work for short distances. But if you’re climbing a mountain, you want hiking boots. Same with integrations.” Sufian Reiter

🔹 API-first mindsets, plug-in frameworks & co-development

“translate5 was built for integration from day one. You can even develop your own UI components as plug-ins.” Marc Mittag

🔹 The myth of ‘set it and forget it’

“There’s no such thing in integration work. Even Low-Code platforms need constant maintenance as systems evolve.” Marcel Moch

The full conversation is transcribed below - unfiltered, unscripted, and 100% real-world.

📖 Read the Full Transcript here 👇

André: Marc, I was interested when you talked about the No-Code options you looked at. What made you choose custom development in the end? Was it just the technical needs or also the costs?

Marc: It was both, actually. The level of integration we needed made custom development necessary. Even with a Low-Code platform, we would have needed a lot of custom work beyond what these platforms offer out-of-the-box.

The cost structure is quite interesting. These platforms have high base costs that make sense when you use many connectors. For just one integration like ours, the custom way becomes cheaper, especially over time.

Sufian: I like to think of it as three main doors you can walk through: Door #1 - No-Code/Low-Code solutions, Door #2 - integration through the TBMS manufacturer, or Door #3 - custom development. Oh, and I guess there's also Door #4 - the "I give up" door!

Marc: Yes. Since 2018, we've seen that yearly maintenance costs for custom Plunet integrations are just a small fraction of what you'd pay every year for a No-Code platform. Of course, if you need ten different integrations, the math changes.

Sufian: It's like buying shoes, right? For a quick walk to the store, flip-flops will do the job. But if you're climbing a mountain, you'd better invest in some serious hiking boots! Same with integrations - simple needs, simple tools. Complex needs, custom solutions.

Marc: That's... actually a good comparison. Our custom integrations handle those edge cases much better too. And our shared development approach has worked well. We bring together multiple clients for these projects, which makes it much cheaper for everyone.

Marcel: I've noticed that maintenance is needed no matter which approach you take. There's no "set it and forget it" in any integration work.

Sufian: Exactly. At Plunet, we maintain many integrations: accounting systems, production tools and we have a whole team just handling compatibility and adding new features.

We expect more tools will need integration in the future. The hot tool today might be replaced by something new tomorrow. We know we can't build every possible integration ourselves, so we focus on giving customers flexible connection options and making the process easier.

Marcel: And then you are hoping for companies like lingo systems to do the leg work?

Sufian: Absolutely. Companies like yours help us to be able to focus on our core product!

—------------

Sufian: That's the dream, isn't it? A completely hands-off workflow from start to finish.

Marc: Exactly. It works with systems like WordPress, COTI, and various other platforms. The big advantage is that all the business data for orders and billing is already in both systems.

Marcel: I'm curious about implementation. How adaptable would this be for other systems beyond what you've mentioned?

Marc: That's where our API-first approach is really powerful. We designed translate5 with integration in mind from the beginning. Almost everything is possible through our API.

What's particularly valuable is our plug-in system, which lets you connect to all translate5 processes through events. You can even develop your own powerful UI components - our Visual feature is actually built as a plug-in.

Marcel: So technically, customers could extend the system themselves?

Marc: Absolutely. That's the key point: any functionality you might want to add to your CAT tool can be added to translate5. This can be done by us, by the customers themselves, or by lingo systems, depending on technical capabilities and preferences.

Sufian: We can't just force everyone down one path. Different companies have different needs…and different technical resources. It’s the same for us. We are planning to open up Plunet even more specifically in the workflow area. We want to allow users to tie in any tool in an easy way. The world is rapidly changing and so are the tools.

Marcel: This openness from tech vendors creates interesting possibilities. We could build scenarios with translate5 and other tools, or Plunet and other tools. We already have quite an amount of in-house knowledge with various tech solutions in the market, so we are always happy to help!

André: And for companies interested in the Plunet-translate5 integration specifically?

Marc: They should just reach out to us. I'm always happy to jump on a call, talk through their specific needs, and show them how it works. The sooner we understand their workflow, the quicker we can figure out the right solution.

—--------------

André: One more thing I've been wondering: When someone says "No-Code," does that really mean no coding at all?

Sufian: Not exactly. "No-Code" is more like "less code" in reality. Before you even start with any solution, you need a clear problem statement and you have to map everything out first. You need to understand what you're trying to solve, which processes you want to automate, and how different systems should talk to each other.

Marc: I think this is a key point. We've seen many companies focus on the tool first rather than understanding their workflow needs. That approach almost always creates problems later.

Sufian: Absolutely. The tools make some things easier, but they can't replace the need to understand what you're trying to accomplish. It's similar to using translation technology - the technology is powerful, but you still need people who understand what good translation looks like.

Marc: But the setup for those 'No-Code' tools can get really complex, right? You're basically trying to force your workflow into the box they give you. Which is not necessarily a bad thing, it really depends on your use case.

Marcel: And these solutions require maintenance too, right?

Marc: Yes, especially when the integrated systems update. This is often overlooked in the initial cost calculations. We've found that long-term ownership costs sometimes end up being higher than expected because every platform change requires reconfiguration.

Sufian: The promise of not needing any technical knowledge usually doesn't fully work out in complex integration scenarios. Someone still has to understand how the pieces fit together.

Marc: Right. And with custom dev, you're just building exactly what you need to solve your problem. There are no extra constraints. For complex stuff, it just ends up being a more sustainable fix that actually fits how you work.

André: This has been incredible. Any final thoughts before we call it a day? 

Marcel: Just that this stuff is never "done." The moment we get this right, a new tool will pop up, or a client will have a wild new idea. That used to be a headache. Now, it's just the interesting part of the job. 🙂

If you would like to find out more - Let’s Talk! 💡

lingo systems | Tech Talk