What Does Custom Software Development Cost? A Transparent Guide for SMEs

"What does software cost?" is an honest question with a dishonest standard answer. Any flat figure is either marketing or luck.

Software does not cost "X euros". It costs whatever its scope, its integrations, its permission model and its operation cause over time. This article names the real cost drivers so you can frame a request that a serious answer is even possible for.

Why there is no meaningful flat price

A quote without clear requirements is an estimate over an unknown quantity. Two projects behind the same sentence "we need a customer portal" can differ in effort by a factor of five — depending on how many roles, integrations, edge cases and compliance requirements sit underneath.

So the more important question is not "what does it cost" but "which decision or process should this improve — and how small can it be cut?"

The seven cost drivers

1. Scope and edge cases

It is not the standard feature that is expensive, it is the exception. "Create an invoice" is cheap. "Create an invoice, except for consolidated orders with partial deliveries and customer-specific tax rates" is a different project. Edge cases are the single most underestimated driver.

2. Integrations

A self-contained app is predictable. The moment ERP, webshop, accounting, DATEV or an industry tool is connected, effort rises — not because of the code, but because of authentication, data validation, failure cases and foreign systems you do not control.

3. Roles and permission model

An app for "one user type" is simple. Tenants, roles, approval workflows, "who may see and change what" — that is architecture, not a detail. A clean permission model is often 15–30 % of the effort, but it is also what later carries security and scaling.

4. Mobile and offline

A responsive web app is one thing. A native app with offline capability, synchronisation and conflict resolution for field staff or drivers is significantly more — because the hard part is not the app, it is what happens on an unstable connection.

5. AI components

AI features shift cost from "development" to "data preparation, permission control, human-in-the-loop and operation". An AI feature is rarely expensive in the prompt — it is expensive in everything that makes it reliable, auditable and GDPR-compliant.

6. Hosting and operation

EU hosting, backups, logging, monitoring, tenant isolation and recovery are not one-off line items. They are running costs that belong in the total — including for standard software, just hidden there inside the licence.

7. Maintenance and evolution

A launch is not a finish line. Security updates, bug fixes, small improvements and paying down technical debt are predictable, ongoing costs. DORA's 2024 Accelerate State of DevOps Report also shows that teams shipping in small, tested steps are more stable and faster — large, rare releases raise risk and therefore follow-on cost. Maintenance is cheaper when the system is built small and clean from the start.

What a fixed price hides

An attractive fixed price is often a narrow scope with expensive change requests. A day rate with no plan is open-ended risk. The defensible middle path for SMEs: a clearly cut first scope with a measurable goal, a fixed frame for that, and an honest statement of what is deliberately not included.

Serious is not whoever names the lowest number — it is whoever tells you which assumption that number rests on.

How to lower budget risk

Cut it small. One process, one measurable goal, a production first version in 8–12 weeks. That replaces a big estimate with a small, real result.
Buy what is solved. Accounting, payroll, office: buy. Build only what differentiates — see Custom vs Standard Software for SMEs.
Plan for data reality. If the Excel, email and legacy-system reality is not in the plan, the plan is too cheap — and gets expensive.
Count operation. Licence/hosting/maintenance over three years, not just the entry price.

Checklist before requesting a quote

Can we describe the need as one decision/process, not a tool name?
How many roles and approval steps are there really?
Which external systems must be connected?
Are there regulatory requirements (GDPR, retention, EU hosting)?
Do we need mobile/offline — or is responsive web enough?
Can we define a first scope that is in production within weeks?
Have we counted operating costs over 3 years?

Answer those seven and you get a defensible number instead of a marketing flat rate.

Frequently asked questions

Can't you just give a ballpark? A ballpark without scope is misleading. A serious ballpark only emerges once roles, integrations and the first scope are roughly clear — that takes a conversation, not a price table.

Fixed price or day rate? Both carry risk. Best: a fixed frame for a clearly cut first scope, then iterate. Risk stays bounded and value shows early.

Why is maintenance a separate item? Because software lives: security updates, dependencies, small improvements. Standard software also costs to operate — just less visibly.

How do we avoid cost blow-up? Start small, measurable goal, ship early, then extend. No big bang, no 200-page spec as the starting point.

Conclusion

Custom software has no list price because it is not a list product. But it has clear cost drivers: edge cases, integrations, permissions, mobile, AI, hosting, maintenance. Naming them and cutting the need small replaces a risky flat estimate with a predictable, honest number — and a first result in weeks, not years.

Next step

Want a defensible number instead of a marketing flat rate? Start with a short assessment of your requirements. Together we cut a first, measurable scope — before budget is committed.

Sources

DORA, Accelerate State of DevOps Report 2024 — dora.dev
Atlassian, Agile Project Management — atlassian.com
Thoughtworks, Technology Radar — thoughtworks.com