Our clients
We work with organisations of every size, from manufacturing to education, retail to the public sector. Each a different process, the same approach.
References
We have worked with every organisation on the list below on at least one of our lines: software development, consulting or information security.
We publish this list as evidence of our range rather than as a showcase. If the same team can build both the business application of an organisation with hundreds of users and the order flow of a single office, it is because we read the work by its process rather than by its size. Scale changes the architecture; it does not change how we work.
Most projects begin on one of three lines: enterprise software development, digital transformation consultinginformation security consulting. Work that starts on one line usually touches another: a process simplification exercise ends in a new application, and the application ends in the access model being rebuilt. Rather than splitting these into separate contracts, we treat them as layers of the same project.
Sectors
Our sector list was formed by the real distribution of the organisations we work with, not by a marketing preference.
Hilton, Doğadan, Axis AVM, Quasar İstanbul, Geyve Otel
Multi-site businesses share the same problem: every branch keeps its own spreadsheet and head office merges them by hand. The systems we build here first define a single source of record, then set a permission model on top of it that still lets branches work at their own pace.
Dicle Üniversitesi, Artuklu Üniversitesi, KAMOSB, Sakarya Barosu
In public bodies and universities the work has to stay inside the boundary regulation draws. Most design decisions here are not technical; they are answers to who may see what, who holds which approval, and how long a record is kept. We do not start development before those answers are written down during analysis.
Drc BYD, Oto Bravo, Gelecek Otomotiv, Baş Pehlivan Otogaz
In dealer networks, sales, service and stock sit with three separate teams. The flows we build bring those three onto the same record; customer contact history and vehicle or parts history become readable from one place.
Danış Asfalt, Emiryol Asfalt, Ond İnşaat, Bakırtaş İnşaat, Gökçen PVC, Zeki Metal Plastik
In field work, data is not always born in the office. In these sectors offline resilience, later synchronisation and photo or document attachment flows are a necessity rather than a luxury. That need is where our asset and maintenance tracking products started.
Akademik Kasko, Diji Kasko, Serbesler Döviz, Sitec, Alo Hizmet Merkezi
Where quotes, policies and customer records move together, the most expensive mistake is duplicated data. In the systems we build here, deduplication rules, an audit trail and access logging are part of the architecture from the beginning.
Fizyo Zone, VD Academy, Rasna Dijital, Tibet Mentaş, Jegand Company
Small and mid-sized organisations where appointments, content and customer communication are intertwined. The real gain here is that the content and operations team no longer waits on a developer for every change; we design the admin panel to that measure.
Yolo Cosmetic, Hobi Kozmetik, Ashley Joy, Mattie Pro, Ustam Kapıda, Hemen Gelse, Genç Ticaret Köprüsü
Businesses where orders, stock and delivery all move at once. What matters is that the state of a single order means the same thing to every team; we define the state machine together with the client.
The working relationship
A reference list is a list of sustained relationships, not of one-off deliveries. Four things make the difference.
One party is responsible from analysis through to go-live. We do not split the pieces across suppliers and leave the organisation to cover the gaps.
We deliver working releases in short cycles. Progress is measured in working software, not in presentations.
Code, documentation and infrastructure are left in a state the organisation can take over. Dependency is a risk, not a business model.
Maintenance, monitoring and development against new requirements are a natural part of the relationship. Most of our engagements continue past the first release.
The most frequent request is turning a process an off-the-shelf package does not cover into software: approval flows, field records, custody and maintenance history, multi-role admin panels. Second comes taking over an existing system — understanding an application written by another team with incomplete documentation, then making it sustainable. Third are reviews on the infrastructure and security side: reworking the access model, the backup plan and the data classification.
Over time we turned the needs that kept recurring into products; you can look at our ready-built solutions on the products page. If you want to read step by step how we work, the our approach page describes all five stages; for information about the company itself see the company page, and for our commitments the corporate responsibility page.
You are welcome to ask for a reference call. We pick the engagement closest to your sector and, with that organisation’s consent, put you in touch directly.
Let’s discuss your project