Region
Enterprise software in Ankara
The work that comes from Ankara is mostly opened by public institutions, public bodies and foundations. What makes software harder on that side is not the technology but the obligation to keep a record.
Building a system for a public institution runs differently from building one for a company. Scope is fixed by a specification, acceptance happens on a signed record, data protection obligations have to sit inside the architecture from the start, and the system must one day be capable of being handed to someone else.
A feature added on a whim in a company is a change of scope in an institution. So we put the scope in writing at the outset and record each change separately, so that no argument about who asked for what arrives later.
A record of who did what and when cannot be a feature added afterwards either. An auditable trail belongs to the first architectural decision.
Most of the work on this side moves as documents: petitions, applications, supporting files, approvals, rejections and notifications. Without a system that flow scatters across folders and mailboxes, and nobody can say alone where an application stands.
In the flows we build, the stage of every document, whose desk it waits on and whether its clock has run out are visible — and the citizen or member who filed it can see their own status.
Rules change on the public side: forms change, deadlines change, signature authority changes. So we build the rules as managed definitions rather than burying them in code; updating a changed deadline does not wait for a release.
The institution being able to sustain the system with its own team is part of the goal for us. Documentation and a handover rehearsal are not a formality left to the end.
On the public sector side, web work is more than a brochure: citizen- or member-facing application screens, accessibility requirements and multi-language publishing belong to the same job. We build them inside the same system as the corporate site.
What sets the price? →Document Processing and Automation
The layer where invoices, forms and paperwork become structured records.
Integration and Middleware
A structure where separate systems talk through one connection layer.
ERP — Enterprise Resource Planning
The core system where finance, stock, purchasing, sales and production meet one data model.
- Do you have an Ankara office?
- No. Our base is Kayseri. We travel to Ankara for meetings, acceptance and training.
- Have you worked with public institutions?
- Yes. We have delivered systems to public institutions and bodies; the names we may publish are on the references page.
- Do you bid against a specification?
- We do. Where a specification is unclear we first state in writing which clauses need settling, and then we price it.
Let’s talk.
If you have a system to build, write to us — we come to the first meeting.