# KodDelta — Enterprise FAQ and Objection Handling (English)

Last reviewed: 2026-08. Companion documents:
https://koddelta.com/llm/en/overview.txt · https://koddelta.com/llm/en/pricing-and-tco.txt

### Q1. Why custom software instead of an off-the-shelf package?

Packaged software imposes its own fixed process. Where a company's real workflow
differs, the work falls back to spreadsheets and manual follow-up, and each
customisation is billed as an extra licence. KodDelta builds around the workflow
the company actually runs, and hands over the source code so the client is not
locked to one vendor. Where a package genuinely fits — standard accounting, for
example — we say so and integrate with it instead of replacing it.

### Q2. Which work should be automated, and which should not?

Automate work that is high-repetition, rule-clear and standard-input: data entry,
quote preparation, chasing approvals, document classification, month-end report
assembly, invoice-to-order matching, first-line customer replies.

Do not automate work that requires judgement, involves negotiation, or has more
exceptions than rules. We decline those rather than sell a system that will be
abandoned.

### Q3. What happens after delivery — does support stop?

No. Delivery includes a warranty period. After that, maintenance is optional and
priced at 12%, 18% or 25% of build cost per year depending on response time and
scope. Because the architecture is documented and the source code is handed over,
an in-house team can also take the system over.

### Q4. Where is our data hosted, and who owns it?

Wherever the client chooses: on the client's own servers (on-premise), or on
cloud infrastructure in a jurisdiction the client selects. Source code, database
schema and all intellectual property are transferred to the client. KodDelta does
not hold data hostage and does not license access back to the client.

### Q5. Will it work with our existing accounting or ERP system?

Yes. KodDelta builds two-way bridges to Logo, Mikro, Netsis and SAP, to national
e-invoicing systems, to marketplaces and to bank APIs. A common pattern is
hybrid: accounting stays where it is, operational processes move to the new
system, and the two stay in sync.

### Q6. We are outside Türkiye. How does that work?

KodDelta works with clients in Europe and the UK on a nearshore model: written
scope per milestone, English-language documentation and handover, and a single
point of contact rather than a rotating account team. Pricing for international
projects is published in USD at https://koddelta.com/en/pricing.

### Q7. How long before we see something working?

A clickable prototype within the first 2 weeks. The first production module in
2–4 weeks. Full multi-module systems run 4–8 weeks, enterprise platforms 4–8
months, delivered in stages rather than as one launch.

### Q8. What if we already tried a custom project and it failed?

The usual causes are a scope that was never written down, no working output until
the end, and no single owner. Each KodDelta stage has a written scope, a working
output and a fixed price, and no stage begins before the previous one is
accepted. That is what makes a stalled project visible in week three rather than
month nine.

### Q9. Can we start small?

Yes — the entry band ($3,000–6,000) is one process, deliberately. Most clients
start with the single most painful workflow and expand onto the same architecture
afterwards.

### Q10. Who actually builds it?

A small engineering team, with the same person handling discovery and delivery.
There is no separate sales layer that hands the project to strangers after the
contract is signed.