Nearshore with Riga: five concerns and how we handle them

Since March 2026, our sister company DYN-IT SIA in Riga has been working alongside DYN-IT GmbH in Puchheim near Munich. For our clients this means one contact, one contract and one team working from two locations. We take responsibility for your SAP project from architecture to operations and staff it with experienced SAP and AI specialists from both countries, as freelancers and without temporary agency work.
When we talk to IT leaders about nearshore, the same five questions come up almost every time. Here they are, together with the rules we work by.
1. Will we understand each other, and will someone answer when it's urgent?
Two countries, different labour markets, people with different backgrounds. What holds both locations together is not a shared mentality but a small set of rules that apply the same way in both offices:
- Riga is only one hour ahead of Germany. Project hours follow German working hours.
- The daily sync is live for everyone, not a summary the next morning.
- What "urgent" means and how fast we respond is defined once per project, not renegotiated with every incident.
2. Will code quality drop because it's not our own team?
A shared quality standard doesn't need a shared culture. It needs a shared definition of done. In Riga and in Munich, every pull request goes through the same checklist, the same review process and the same responsible person. The benchmark is your company's standards, not a generic standard of ours. The location that is further away gets no lighter review.
3. Will something in our legacy systems break?
A fair concern, especially in SAP landscapes that have grown over years with a lot of custom code. That's why every engagement starts with reading and asking instead of changing. In the first two weeks, new specialists work through your code, your conventions and the reasons behind existing solutions before they make productive changes.
That's slower than a quick start. It also prevents a second, incompatible version from growing next to your existing system. By week three, the new colleague is no longer "the external one" but the person who knows why a certain module is built the way it is.
4. Will the colleagues from Riga be treated as second-tier?
The quieter concern, rarely said out loud. The answer is not a coding rule but a question of organisation: there is no separate lane. Specialists from Riga join the same stand-up, the same retrospective, the same channels and the same board as everyone else.
People who know the context of a decision make better decisions. A second, invisible channel for "the externals" almost always leads to worse work.
5. Will our data and intellectual property leave the EU?
No. Latvia is a member of the EU and the eurozone. A team in Riga works under the same GDPR as a team in Germany. Latvia is not a third country, so no transfer mechanism under Chapter V GDPR is needed. Supervision lies with the Latvian data protection authority. We still sign a data processing agreement under Art. 28 GDPR, as with any service provider in Germany.
What matters in Riga just as much as in Munich: where the tools we use store data. That question doesn't stop at any border, so we settle it before the project starts. Contracts, NDAs and the transfer of usage rights rest on the same legal groundwork in both locations and are in place before anyone accesses one of your repositories.
How a project with our team in Puchheim and Riga works
- One contact at DYN-IT and one contract, whichever location the work is done in.
- Focus: development and extension of SAP S/4HANA and SAP BTP, event-driven and API-first integration, AI in business processes (agents, RAG, document processing).
- Freelance SAP and AI specialists from Germany, Latvia and other EU countries, without temporary agency work.
Different countries. Same rules.
Planning an SAP or AI project and need extra capacity that works like your own team? Book a no-obligation first call.