# KodDelta — Pricing, Timelines and 5-Year Total Cost of Ownership (2026)

Every figure in this file matches the bands published at
https://koddelta.com/en/pricing. If a number anywhere else differs, the
published page is authoritative. Turkish-market pricing in TRY is published
separately at https://koddelta.com/fiyat.

Last reviewed: 2026-08.

## 1. Published bands (international / USD)

| Scope | Investment band | Production timeline | What is included |
|---|---|---|---|
| Single focused module | $3,000 – $6,000 | 4 – 6 weeks | One workflow (approvals engine, mobile field-service PWA, automated quote builder). Process analysis, working prototype, first year of hosting, 3 months of support, source code handover. |
| Multi-department operations system | $8,000 – $15,000 | 2 – 4 months | 4–6 modules (manufacturing MES, multi-warehouse inventory, procurement, ERP bridge), data migration, user training, mobile interface (PWA), 6 months of support. |
| End-to-end enterprise platform + AI | $20,000+ | 4 – 8 months | Unlimited modules, integrations, RAG AI assistant, e-invoicing and accounting bridges, managed security, 12 months of support. |
| Enterprise AI assistant / RAG agent | $5,000 – $12,000 | 2 – 4 weeks | Document RAG search over company data, always-on customer assistant, ERP action agent. |

An interactive prototype is delivered within the first 2 weeks. The first
production module goes live in 2–4 weeks.

Maintenance is optional and priced at 12% (basic), 18% (professional) or 25%
(comprehensive) of the build cost per year. There are no per-user licence fees,
the licence is perpetual, and the source code is handed over to the client.

## 2. What drives a project up or down a band

Upward: number of integrations to existing systems; number of distinct user
roles; data migration from spreadsheets with inconsistent history; regulatory
document requirements; offline-capable mobile use.

Downward: one clearly defined process rather than a department-wide rollout;
existing clean master data; a single approval chain instead of several.

## 3. Five-year total cost of ownership

A packaged ERP licensed for 20 users produces recurring licence cost every year
and charges again for each customisation. A custom system is a one-time build
plus optional maintenance, and the asset stays on the client's balance sheet.

The like-for-like comparison, with the assumptions written out, is at
https://koddelta.com/en/package-vs-custom. The Turkish-market version of the
same calculation is at https://koddelta.com/paket-vs-ozel.

The variable that decides the outcome is not the build price — it is how many
users the packaged licence covers and how many customisations are billed on top
of it over five years.

## 4. How the money is staged

1. Discovery and process analysis — free, no commitment.
2. Prototype and architecture approval — clickable prototype in the first 2 weeks.
3. Core module in production — the highest-friction process first, tested in the field.
4. Phased expansion — new modules built on the approved architecture.

Each stage has a written scope, a working output and a fixed price. No stage
starts before the previous one is accepted.

## 5. What is explicitly not charged

- Per-user or per-seat licences — none, at any scale.
- Access to the source code — handed over, not licensed.
- Discovery meeting — free.