The price question comes quickly, but it is often badly framed. Custom business software should not be evaluated like an isolated purchase line. It should be evaluated against the daily cost of the workflow it is meant to bring back under control.
For an SME, the right calculation must look at lost time, duplicate entry, errors, fragile reporting, dependence on a few people, and the difficulty of handling more volume without more noise.
The wrong question and the right one
The wrong question is to ask how much "the software" costs in the abstract. The right question is to ask how much the badly tooled workflow costs today, then how much it will cost tomorrow once stabilized.
That is when trade-offs become readable. A custom budget can feel substantial. But it may be more rational than the long-term stacking of SaaS tools, exports, workarounds, and wasted human time.
What changes the budget
Two "custom" projects can have neither the same price nor the same effort. It all depends on the expected level of structure and the constraints of the target workflow.
- The number of roles, permissions, and approvals to manage.
- The complexity of the workflow data and statuses.
- The need for integrations with CRM, ERP, business tools, or third-party services.
- Data migration or temporary coexistence with the old workflow.
- The level of demand around interface quality, security, traceability, and go-live.
How to build a serious estimate
1. Isolate the priority workflow.
A usable estimate starts from a precise workflow, not from a broad wish list. The clearer the scope, the more defensible the budget.
2. Identify the real constraints.
Permissions, integrations, history, reporting, data migration, and production setup are often what separates a small tool from a solid system.
3. Compare it with the cost of inertia.
A budget only makes sense when compared with the time, errors, and margin already consumed by the current workflow.
What should be inside the budget
Scoping, development, testing, go-live, first field feedback, and initial maintenance should be framed from the start. Otherwise the project is almost always underestimated.
The right budget is not the lowest one. It is the one that puts a critical workflow back under control without recreating an even more expensive debt tomorrow.
For an SME, custom software becomes a good decision when it turns a fuzzy and expensive workflow into a readable, delegable, and governable system.
Sources
France Num - TPE/PME : pourquoi informatiser la gestion financiere de votre entreprise ?
France Num highlights time savings, better financial visibility, and more professional management as direct effects of digitization.
France Num - Pourquoi utiliser des outils no-code pour gerer sa TPE PME, et lesquels ?
The guide shows that custom or semi-custom tooling makes sense when the need fits poorly with standard solutions.
Frequently asked questions
Why are price gaps so large?
expand_more
Because custom software can range from one simple workflow with few roles to a critical system with integrations, data migration, fine-grained permissions, and production demands.
Can you start small?
expand_more
Yes, and it is often the right approach. You simply need to choose a first workflow that justifies the investment and build a healthy base for future expansion.