How much does custom software cost in Türkiye, and what decides the number?
Custom software from KodDelta starts at $3,000 for one focused operational module and passes $20,000 for a multi-department platform. Where you land inside that range is decided by how many modules you need, how many distinct user roles use them, how deep the integrations run, and how much old data must be migrated.
A number without a scope is meaningless. This page explains what a custom software price is made of, publishes the bands we quote from, and gives you a way to work out where your own project sits before you talk to anyone.
What you are buying is scope, not hours
When two suppliers quote wildly different numbers for what sounds like the same project, it is almost never because one is greedy and the other cheap. It is because they wrote down different systems. One heard "an order screen" and priced an order screen. The other asked who approves the order, what happens when the item is out of stock, whether the price comes from the accounting package, and who gets the email — then priced a system. The second quote is higher and usually closer to what you will end up needing.
The five things that move the price
- Number of modules. One workflow — purchase approvals, field service visits, dealer ordering — is a small project. Purchasing plus stock plus production plus reporting is four projects that also have to agree with each other, which is a fifth piece of work on its own.
- Number of user roles. Every role that needs a different screen is a separate design and permission problem. A system for two office staff is cheap. The same system used by an office clerk, a warehouse picker on a phone, a supervisor, a finance manager and an external dealer is five interfaces and five rounds of feedback.
- Integration depth. Reading data out of an existing system is straightforward. Writing back into it — posting invoices, reserving stock, updating a customer record — needs error handling, retry logic and a way to prove no record was written twice.
- Data migration volume and quality. Starting empty costs nothing. Bringing in fifteen years of product codes, customer records and open balances from spreadsheets with inconsistent spelling is a real engineering task, and the messier the source the longer it takes.
- How conditional your rules are. "Anything over $500 goes to the manager" is one rule. Add "unless it is a raw material, unless the branch is Izmir, unless the supplier is on the framework agreement" and it is a rules engine, discovered piece by piece during discovery rather than before it.
Published price bands
These are the bands KodDelta quotes from. They are the same numbers on our pricing page — we do not adjust them based on how large the company on the other side of the table looks.
| Project scope | Investment band | Delivery time |
|---|---|---|
| One focused operational module — approvals, field service app, quote builder | $3,000 – $6,000 | 2–4 weeks |
| Multi-department operations system — production, stock and purchasing together | $8,000 – $15,000 | 4–8 weeks |
| Full platform — several departments plus external portals and AI assistance | $20,000+ | 3–6 months |
| AI assistant over your own documents and records | $5,000 – $12,000 | 2–4 weeks |
| Additional module on an existing system | Quoted per module against the same drivers | 2–6 weeks |
Where inside the band do you land?
Bands are wide because projects are. Use the table below as a self-assessment: count how many rows on the right describe you.
| Driver | Bottom of the band | Top of the band |
|---|---|---|
| User roles | 1–2 roles, all on desktop | 4+ roles, mixed phone and desktop use |
| Integrations | None, or a nightly export | Live two-way sync with an ERP or accounting package |
| Existing data | Start empty or a few hundred rows | Tens of thousands of records from several inconsistent sources |
| Approval logic | One threshold, one approver | Conditional by branch, category, amount and supplier |
| Process maturity | The process is written down and stable | Everyone describes the process differently |
| Reporting | A handful of fixed lists | Dashboards, exports and figures that must reconcile with accounting |
Two or fewer rows on the right: expect the lower half of your band. Four or more: budget for the upper half and stage the work, so you are not paying for everything before anything is running.
What the build price does not cover
- Annual maintenance, quoted separately at 12%, 18% or 25% of the build cost. What each tier contains is a topic on its own.
- Hosting after the first year. The first year is included in the build; after that it is a small annual line, sized to the deployment.
- Your own people's time answering discovery questions, testing the prototype and training the team. Not billable to us, but real, and projects that skip it go badly.
- Work you invent later. New modules are quoted as new modules, which is why a written scope matters more than a low headline price.
The same request at three different prices
A distributor asks for "a dealer ordering system". Depending on scope, that is any of three projects:
- Around $4,000. Dealers log in, see a fixed price list, place orders. Orders land in a queue your office staff still processes. No stock check, no accounting link. Live in about five weeks.
- Around $12,000. The same portal, plus dealer-specific pricing, live stock availability, order status tracking and a nightly two-way sync with the accounting package. Three roles, and migration of the existing customer and product lists.
- $20,000 and up. All of the above, plus credit limits, multi-warehouse allocation, a field sales app and reporting the finance team trusts enough to close the month with.
All three are honest quotes for the same sentence. The difference is entirely in what was written down.
Write those five drivers down before you approach anyone, and send the identical list to every supplier. That single step is what makes competing quotes comparable; the rest of the evaluation is covered in how to choose a software vendor.
When custom software is the wrong purchase
If your process is genuinely standard — statutory accounting, payroll, basic invoicing — a packaged product beats a custom build on both price and time, and we will say so. Custom software earns its cost where your process is specific to your business and no package covers it, or where the same manual task repeats every day. The arithmetic is in the five-year comparison, and the decision itself in package versus custom.
When you have your module list, role list and record counts ready, put them through the quote form and you will get a band rather than a guess.
Frequently asked questions
How much does custom enterprise software cost in Türkiye?
One focused operational module costs $3,000 to $6,000 over 4 to 6 weeks. A multi-department operations system costs $8,000 to $15,000 over 2 to 4 months. A full platform with portals starts at $20,000. An AI assistant over your own documents is $5,000 to $12,000.
Why do two quotes for the same project differ so much?
Usually because the two suppliers scoped different things. One priced the screens you described, the other priced the screens plus the integration, the migration, the second user role and the reporting. Ask both to list modules, roles, integrations and record counts separately and the gap explains itself.
What makes a project land at the top of its price band instead of the bottom?
Four signals push a project upward: more than three user roles with different screens, a write-back integration into an existing ERP or accounting package, tens of thousands of historical records to migrate, and approval rules that vary by branch, product line or amount.
What is not included in the build price?
The build covers discovery, design, development, testing and go-live. Hosting is included for the first year. Maintenance is quoted separately at 12%, 18% or 25% of the build cost. Your own staff time for testing and training is yours to plan.
Can I start smaller than the band suggests?
Yes, and it is usually the better decision. KodDelta delivers a clickable prototype in the first two weeks and the first working module in weeks 4 to 6. You can stop there, run it for a quarter, and decide on the next module with real numbers.
Do I own the source code?
Yes. The source code is delivered to you, there is no per-user licence and the licence does not expire. You can hand the codebase to your own developer or another firm at any time without asking permission.
Let's talk about what you need.
The 30-minute discovery call is free and carries no commitment.