The team that writes your software is the team that stands behind it after delivery
The real risk in enterprise software projects is not that the code can't be written; it is that nobody is left standing once it has been delivered. Hatson Tech is an Ankara software company that does not subcontract the work, so a single team carries the project from analysis to maintenance.
We build custom business applications, enterprise portals, mobile apps and systems integrations. We also write and run our own products; we are a team that has to live with the code we write for years, so writing maintainable software is not a preference for us but a necessity.
Before we start, we put in writing how long it will take, what is included and what is not. If the scope changes, we put the price and the timeline back in writing.
We work face to face in Ankara and run projects remotely with organisations across Türkiye.
The services we offer as an Ankara software company
We run six service lines. If you need a single item, we work on that item alone; if you are building a system from scratch, everything comes from one team.
Custom software development
We build business applications, management dashboards and reporting systems that fit your organisation's own processes. Instead of bending the process to the software, we build the software around the process. See our custom software development service for details.
A process run on Excel and manual tracking comes together in one system.
Enterprise web applications and portals
Dealer, supplier, staff and citizen portals, with multi-role permissions, audit logging and reporting. We have delivered a government-scale portal built for high numbers of concurrent users.
Phone and email traffic moves to a self-service screen.
Mobile app development (iOS / Android)
We do end-to-end iOS and Android development for field teams, customer apps and internal apps. Details are on our mobile app development page.
Field data enters the system where it happens, without a trip back to the office.
Systems integration and API development
We set up the data flow between your ERP, CRM, accounting, e-invoicing and authentication systems. Where needed, intelligent features built by our AI development team can be added to the same infrastructure.
No more entering the same data into two systems separately.
Legacy system modernisation
We renew systems that have slowed down, can no longer be updated or carry security risks, step by step. Instead of replacing everything overnight, we migrate piece by piece while keeping the working system running.
You get out of technical debt without stopping the business.
Maintenance, support and inherited projects
We take over projects written by another company, left unfinished or no longer supported. Most companies won't; we first review the code and write a status report, then tell you whether to continue or rewrite.
An unfinished investment is evaluated before it goes to waste.
When do organisations work with us?
The decision to work with an Ankara software company is usually made in one of these four situations. Whichever looks like yours is what we should talk about in the first meeting.
Off-the-shelf packages don't fit your business
Your process doesn't fit the package, and the team keeps spreadsheets to work around the software. We build a system that runs your process as it is.
Your current software is slow or insecure
The system slows down as it grows, it can't be updated and there is a risk of security holes. We measure first, then draw up a phased modernisation plan.
Your systems don't talk to each other
ERP, accounting and the field app run separately and data is moved by hand. We build the integration layer between them and automate the flow.
You parted ways with your previous vendor
The project is half done, documentation is missing and nobody knows the code. We take it over, report its state in writing and rescue what can be rescued.
Whichever of these sounds like your situation, let's start with an analysis meeting.
Get a project proposalHow we work, and what we guarantee at delivery
We define up front how the project will run, when you will see what, and what you will have in hand when the work is done.
Process
- Analysis and scoping1–2 weeks
We map your processes and system inventory. This meeting is free.
- Technical design and proposal1 week
The architecture, screen list, integration items and price are given in writing.
- Sprint-based development6–16 weeks
Work proceeds in two-week cycles; at the end of each cycle you see a working version.
- Testing and acceptance1–3 weeks
Because the acceptance criteria were written up front, testing is based on a list, not a negotiation.
- Go-live and user training1–2 weeks
Installation, permissions, training and handover of the documentation.
Transparency
We demo at the end of every sprint, and on a shared project board you can see at any moment which task is at which stage. We don't hide developers behind a project manager; it is normal for your technical team to talk directly with ours.
Commercial model
We work on a fixed-price project basis when the scope is clear, on a time-and-materials basis when the scope will be shaped by research, and under a monthly maintenance agreement after go-live. We tell you which fits at the end of the analysis; tying uncertain work to a fixed price hurts both sides.
Scope changes
When a new request comes in, we give you the effort and the impact on the timeline in writing; nothing is started or invoiced until you approve it. Each sprint keeps some capacity for small fixes, and those are not charged separately.
After delivery
A warranty period starts at go-live, during which defects within the delivered scope are fixed free of charge. After that we continue with about two years of maintenance support: incident response, security updates and version upgrades. Response times are defined level by level in the maintenance agreement.
The source code and intellectual property are yours. We hand over all of the code written for you, the database schema, and the installation and architecture documentation. If you want to hand the project to another company tomorrow, you can; we leave no hidden dependency, closed component or key that stays with us.
Our technology and architecture approach
| Layer | What we work with |
|---|---|
| Backend and API | Service-based and microservice architectures, REST and event-driven APIs, enterprise authentication and authorisation |
| Frontend | Modern component-based web applications, enterprise admin dashboards, multi-role portal interfaces |
| Mobile | iOS and Android; field, customer and internal apps |
| Data | Relational databases, vector databases, data pipelines and reporting infrastructure |
| Infrastructure and DevOps | Containerisation, CI/CD pipelines, cloud-native and on-premise deployment, monitoring and logging |
Our architectural choices rest on three principles. First, write code that the team coming after us can read: consistent structure, meaningful naming and documentation that is actually kept up to date. Second, protect critical business rules with automated tests, so a change made six months later doesn't silently break something elsewhere. Third, design the system for the load three years from now, not today's, and separate the part that will need to scale from the start.
Sector experience and reference projects
| Sector | Work delivered |
|---|---|
| Public institutions | A national-scale data and knowledge-sharing platform for a ministry (SYDhub) |
| Industry and field operations | Live location, operator and job tracking for a crane fleet (VinçTakip) |
A national-scale platform for a public institution
- Problem
- Data, resources and stakeholder information on industry's green transition were scattered across institutions; academia, industry and government could not look at a shared picture.
- Solution
- For the Turkish Ministry of Environment, Urbanisation and Climate Change, we brought environmental data, resources and the sharing ecosystem together on one platform, and delivered it against the technical specification and acceptance criteria.
- Result
- The platform is live on the institution's own domain: sydhub.csb.gov.tr. Usage figures belong to the institution and are not shared.
A fleet tracking system for a field operations company
- Problem
- Where each crane was, who was using it and which job it was on were tracked by phone, and dispatch decisions were made on outdated information.
- Solution
- We built an operations dashboard that brings each vehicle's live location, assigned operator, current job and loaded/idle/available status onto a single screen.
- Result
- Dispatch questions are answered by looking at one screen instead of a round of phone calls, and which vehicle is available is visible in real time.
Why work with a local software company in Ankara?
Software can be built remotely, but some steps really are easier when you are in the same city:
- Analysis happens at the desk. The most productive form of process analysis is sitting next to the person who does the work and watching their screen. From our office in Çankaya we can reach organisations in Ankara the same day.
- Acceptance and training happen on site. When acceptance testing and user training are done face to face, they finish faster and the real objections come to the surface.
- We know public-sector processes. Delivering to a ministry, we worked with technical specifications, acceptance criteria and internal approval cycles; we are not learning these with you.
- There is a clear counterpart. For contracts, invoices and legal matters there is a legal entity in the same city that you can reach.
- The maintenance relationship lasts. In the years after delivery, the same team stays reachable during the same working hours.
We also work with organisations outside Ankara; on remote projects we plan site visits only for the steps that have to happen on site.
Let's talk about your project and put a proposal in writing
The first step in working with an Ankara software company is not a contract but understanding your process properly. The first analysis meeting is free and carries no commitment; if you prefer, we sign a non-disclosure agreement beforehand. We listen to your process, then prepare a written proposal showing the scope, timeline and price line by line. If an off-the-shelf package would do the job more cheaply, we will tell you that too.