- Technical decisions get debated but never written down
- The team is growing faster than its standards are forming
- An independent second opinion is needed on a specific question
Technology Consulting & Technical Leadership
The way to improve a system for good runs through raising the decision-making maturity of the team that builds it.
What we take on
Rather than imposing decisions from outside, we strengthen the hand of the team making them. We leave findings and reasoning in writing, so the team can keep working to the same framework after we step away. The aim is not a lasting dependency but a working order that can be handed over.
Workstreams
- An independent technical second opinion before a major investment decision
- Technology choices grounded in written criteria rather than preference
- Code quality tied to a process rather than to an individual
- Senior technical leadership without building a full-time role
- A team that becomes able to make its own calls
If these signs
look familiar.
Tech lead role across the KocDigital and Obilet teams: architectural decisions, engineering standards and mentoring.
Which platforms
have we applied this on?
Travel Distribution Platform
Multi-supplier inventory came together in one model, and the same volume is now served at 20% lower cloud cost.
Obilet’s bus, air and rail inventory was fed by suppliers that each had their own data model and their own failure behaviour, so every new integration put the search and booking flow at risk of regression. We normalised the inventory into a single internal model, solved station matching through geographic proximity and GIS, isolated supplier-side failures and reworked resource usage on AWS. The platform now runs independently of any one supplier, holds predictable performance through peak season, and serves the same workload at roughly 20% lower cloud cost.
Read the case study →
Industrial IoT & MES
The production line and its field devices were opened up to real-time monitoring.
On the Ford MES and Platform360 lines, production data stayed locked inside device protocols, and operations teams could only see deviations in end-of-shift reports. We integrated field devices over OPC UA and Open Protocol, and at KoçDigital brought live microservices that process more than 10,000 sensor records per second at low latency, together with alarm and telemetry dashboards. Production data now becomes visibility people can act on immediately, and deviations can be addressed without waiting for the shift to end.
Platform →Let’s look at a need you have around technology consulting.
Tell us where you are today and which constraints matter most; we will define a clear starting point together.