How do we work with a company in Witten from Istanbul?
Witten is a city in the Ruhr area of North Rhine-Westphalia, Germany. Our client Tegoly is based there; our team is in Istanbul.
The advantage of a city-level engagement is that the counterpart and the decision chain are clear. We work with one product, one team and an explicit priority list. Meetings are held in English and can be online or in person. Decisions and open questions stay written on the project board, so a topic raised in one meeting does not get lost by the next sprint.
What did we do for Tegoly?
Tegoly runs a digital signature and business process platform aimed at the global market. When we took it on, the system already worked; the need was to strengthen the user experience, close some integration gaps and become more visible in search engines. So the job was not to build a product from scratch but to grow a live product without breaking it.
User screens and modules
New interfaces were designed around customer needs, and digital signature, document management and integration modules were developed. The front end runs on React and the server side on .NET Core, with data held in MSSQL and MongoDB.
Performance and security on Azure
The platform runs on Azure. Cache mechanisms and tuned server configurations improved page load times, and data protection was strengthened with the security layers of MSSQL and Azure.
Search visibility
Meta descriptions, content adjustments and technical SEO improvements increased the platform's visibility in search engines. For an international product, that means the right page can be found for the right search in more than one market.
What do we watch for when working on a live product?
Changing a system that users rely on every day, such as digital signatures, needs a more careful plan than building something new. On inherited projects like Tegoly we follow this order:
- First a technical analysis and a code quality review, with the risks shared in writing.
- The development plan is split into small steps that do not disrupt existing users.
- Every change is tested before release and planned so that it can be rolled back if needed.
- Performance changes rely on measurement, not guesswork: find the bottleneck first, then improve it.
What do time zones and data protection mean for a Ruhr-area company?
Istanbul is one hour ahead of Witten in summer and two hours ahead in winter. That gap is small enough for both teams to share most of the working day. On data protection, the GDPR framework applies to Tegoly's customers and users, and infrastructure and access decisions are made with it in mind. We cover the country-level details on our Germany page.
How does an engagement run week by week?
Development moves in two-week sprints. Priorities are set together at the start of each sprint, and a working demo is shown at the end. Work is visible on a Jira or Linear board, and a weekly status meeting and a sprint report keep both teams looking at the same picture. A direct channel stays open for urgent matters.
On a live product this rhythm has one more benefit: every change that goes out is recorded along with the sprint and the reason it was made. When the project ends or the team changes, those records and the technical documentation become a written handover package, so the product stays maintainable regardless of who built it.
How do we start if you have a similar platform?
The first meeting is free, and we reply within 24 hours. If you already have a product, the first step is to look at the codebase and the infrastructure together. After that we prepare a written proposal on either a fixed-price or a time and materials basis. On delivery, full ownership of the source code passes to you.