Who we build for
Five situations, not five industries
Companies rarely arrive describing a technology. They arrive describing a situation, and the situation predicts the build far better than the sector does — a plant exporting to Rotterdam and a plant selling only at home need different systems, while two exporters in unrelated industries usually need the same one.
KodDelta builds custom operational software, process automation and AI systems for five recurring situations: exporting manufacturers, European and Gulf buyers of nearshore engineering, SMEs outgrowing packaged SaaS, companies with ERP or CRM data to move, and teams automating internal work with AI. Each has its own page below.
Which one are you?
The middle column is the situation. The right-hand column is the signal that tells you it is yours — if you recognise it, the linked page is written for you.
| Page | Situation | The signal |
|---|---|---|
| Export manufacturers based in Türkiye | You manufacture here and sell into Europe, the UK or the Gulf. Production is tracked one way and the export desk works another, in spreadsheets and email. | Quotations take an afternoon, delivery dates come from experience, and the document pack is assembled by retyping. |
| European and Gulf companies buying nearshore engineering | You are outside Türkiye and looking for a team that overlaps your working day, contracts in English and hands over the source code. | The questions that decide it are the engagement model, IP ownership, where the data sits and what a stage actually delivers. |
| SMEs that have outgrown packaged software | The subscription still renews, but the real process has moved into spreadsheets beside it and seats are bought so people can read. | Four or more workarounds sitting permanently next to the software you pay for. |
| Companies with ERP or CRM data to move or connect | The new system is the easy half. Years of customers, items, orders and documents in an old schema are the project. | Nobody can yet answer how much history moves, how duplicates are resolved, or how the move will be proved correct. |
| Companies automating internal work with AI | A team is buried in repetitive work and someone has been asked to look into AI. Half of it is a rules problem, half of it is genuinely language. | Documents arriving in varied layouts, free-text requests to route, and answers buried in procedures nobody can find. |
What is the same in all five
The situations differ; the way the work runs does not.
- Published prices. A single focused module is $3,000–6,000, a multi-department system $8,000–15,000, an enterprise platform $20,000+, and a retrieval-based AI assistant $5,000–12,000. The bands and what falls into each are on pricing.
- Staged delivery. A clickable prototype in about 2 weeks, a first module live in 2–4 weeks, and every stage after that ending in something running that you can open yourself.
- Your accounting package stays. Statutory accounting and e-invoicing are bridged rather than replaced — see integrations.
- You own the output. Source code, database schema and intellectual property transfer on delivery, with no per-user licences. The reasoning is on source code ownership.
- We say no to bad fits. Work built on judgement, negotiation or more exceptions than rules is declined rather than sold, which is set out on about.
If none of the five is you
These are the situations we see most often, not the limit of what gets built. Companies also come to us for field service and mobile maintenance, described on field service; for project and progress billing in construction and engineering, on project tracking; and for B2B dealer ordering, on dealer portal. Systems already delivered and running are listed on cases, and the whole English library is indexed on the sitemap.
If you are still deciding whether a custom system is the right answer at all, start with packaged vs custom, which works through the five-year comparison, or custom software, which describes what a built system actually contains.
Describe the process that costs you the most hours.
Whichever of the five you are, the first answer is the same: a written scope, a fixed price against the published bands, and a date for the prototype.