Service
Custom software development and integration
For processes no off-the-shelf product covers. Most projects start with the same sentence: “we track this in Excel, but it no longer works.”
When is custom software the right call?
Custom software is expensive and needs continuous maintenance. So our first question is never “what shall we build” but “is an existing product really insufficient?”
If a ready product fits, we say so — even when it isn’t ours. Custom software genuinely pays off when:
- The process is specific to you and is your advantage. Bending it to fit generic software means losing that advantage.
- Systems don’t talk to each other. If the same data is typed into three places, errors and lost time exceed the development cost.
- Manual workload is measurable. A figure like “40 hours a month” makes the return calculable.
- Per-user licence costs explode with headcount. Past a certain scale, owning the software is cheaper.
What we build most often
Internal admin panels
Order, account, stock, production and service tracking with role-based permissions and reporting.
Integrations
Data exchange with accounting/ERP, e-invoicing, shipping, banks, marketplaces and supplier systems.
Automation
Automating repetitive work: report generation, email flows, file processing.
Reporting and dashboards
Scattered data brought onto one screen, with scheduled daily and monthly reports.
Customer and dealer portals
Order entry, order tracking, document sharing and account visibility.
Legacy modernisation
Gradual renewal of software that still works but has become hard to maintain. Never a big-bang switch.
How custom projects run
In large projects the risk sits in scope, not code. That is why we deliver in small pieces.
Process analysis
We watch how the work is done today. The question is not “what do you want” but “what do you do”.
Scope and priority
Not every request is equal. The piece that saves the most time is built first; the first release stays narrow.
Incremental development
You see a working version at each delivery. A misunderstanding surfaces within two weeks, not after six months.
Rollout
Old and new run in parallel for a while. The old system is not switched off before migration and training are complete.
Maintenance and evolution
Software is alive. Changing business rules and new needs are planned as continuous development.
Clauses to insist on in the contract
Ask for these even if you don’t work with us.
- Unlimited data export, at any time. You must be able to take your data out in a standard format (CSV/SQL) whenever you ask. This is the single most important clause: if the data is yours, you are never locked in.
- Data export. You must be able to extract your data in a standard format.
- Technical documentation. Another team must be able to take over.
- Server and account ownership. Domain, servers and service accounts in your company’s name.
- Acceptance criteria. Define what “done” means in writing.
Market
Custom software costs — 2026 ranges
Scope determines cost. That is why we recommend keeping the first release as narrow as possible.
| Scope | Common range | Example |
|---|---|---|
| Small panel / single process | from ₺30,000 | Quotation prep, service tracking, simple stock |
| Simple web application | ₺80,000 – 250,000 | Logins, data entry, basic reporting |
| Mid-size business software | ₺100,000 and above | Multi-module panel with a few integrations |
| Medium–high complexity | ₺250,000 – 600,000 | CRM, stock + order management, multi-role flows |
| Integration (per system) | ₺5,000 – 30,000 | E-invoicing, shipping, ERP, payments, marketplaces |
Source: agency price pages published in Türkiye, August 2026. These are not our prices — they are market ranges and do not constitute a quotation. Published Turkish agency prices usually exclude VAT; ask when comparing quotes. Ask for integrations as separate line items: “integrations included” does not say which systems.
Integration
The integrations we build most often
Most of the value of custom software comes from connecting systems. Typing the same data into two places is the source of both errors and lost time.
Accounting and ERP
Transferring orders, invoices and account movements. Live where an API exists, file-based where it does not.
E-invoicing
Automating invoice issuance through an integrator, including the reconciliation flow.
Shipping carriers
Creating shipments, generating labels and writing delivery status back into the system.
Banking and payments
Payment gateways, payment notifications and automatic reconciliation; takes collection tracking off manual work.
Marketplaces
Product, price and stock synchronisation plus order retrieval. The critical part is single-source stock.
SMS and email
Order, appointment and reminder notifications, with reporting so delivery rates can be monitored.
Transition
How to move from an old system to a new one
Replacing a working system overnight is the highest-risk approach. Operations stop, data goes missing and the team loses trust in the new system.
Our method is phased transition: the new system goes live for one process first, the old one runs in parallel for a while, and results are compared. If the numbers match, the next process follows.
Data migration follows the same principle: a small sample migration first, verified, then the full transfer. In projects that skip the sample, the error always surfaces in the largest table.
- Parallel running period — compare against the old system before switching it off.
- Sample migration — verify with a small set before the full transfer.
- Rollback plan — what happens if something goes wrong must be written down.
- Training and a short guide — if the team does not use it, the system does not exist.
Frequently asked
What does custom software cost?
It depends on scope, and the honest answer is that it can’t be quoted unseen. As a rule of thumb: a narrow panel digitising a single process costs roughly a tenth of a multi-module enterprise system. That is why we recommend keeping the first release as narrow as possible.
Can it talk to our accounting software?
Usually yes, if the software offers an API or a data exchange format. That is the first thing we check in discovery; for closed systems we evaluate intermediate approaches such as file-based transfer.
Do we host it ourselves?
The software runs on servers we operate and continuously patch. The reason is security: an application’s security is not just its code — OS patches, TLS certificates, firewall rules, verified backups and daily monitoring are links in the same chain. Holding that chain in one place is far safer than splitting responsibility across vendors. For enterprises with a regulatory requirement to host on their own infrastructure, we discuss a separate deployment and handover model. Either way, your data can be exported at any time.
What if we stop the project midway?
Everything completed up to that point is handed over in working condition and all of your data is exported in standard formats. Because we work in stages, you do not pay for unfinished stages. Your domain, accounts and content are already in your name. This is precisely why large projects are split up front — every stage leaves a result that stands on its own.
Do you build AI features?
Yes — where they genuinely help. Document summarisation, classification, text generation and first-line triage of customer questions create real value. Adding AI to every screen only adds cost and complexity; we work out together where it pays.
What does custom software cost?
A narrow panel digitising one process starts around ₺30,000 in the market; multi-module enterprise systems reach ₺250,000–600,000 (table above). Almost all of that difference is scope. That is why discovery asks not “what shall we build” but “which single problem saves you the most time”.
How do I calculate the return?
A simple method: measure how many hours per month the work takes today, multiply by loaded hourly cost, multiply by twelve. If the annual saving approaches the software cost, the project makes sense. If you cannot measure it, measure for one month first — that alone is the best decision tool.
Can it integrate with our ERP or accounting software?
Yes, if the software exposes an API or a data exchange format. The market prices integrations at ₺5,000–30,000 each, so the total grows quickly with count. This is the first thing we check, because a closed system changes the whole plan.
Why build custom when off-the-shelf exists?
Usually you should not, and we say so. Custom pays off in four cases: the process is specific to you and is your advantage; the same data is retyped into several systems; manual workload is measurably large; or per-user licence costs explode at your scale.
Tell us about your process
Describe what slows you down. Sometimes the answer isn’t custom software but configuring what you already have — and we’ll say so.