How much does it cost to digitalise a company
The real ranges of the projects we run, what drives the price, and the cases where we say no. Published so you can rule us out without writing an email.
udae projects start at €2,000. Automating a single process usually lands between €2,000 and €6,000. Connecting two systems that do not talk to each other, between €4,000 and €12,000. A full custom build, between €8,000 and €40,000. Ongoing support starts at €500 per month. Always fixed scope against milestones, never a bucket of hours.
Ranges by project type
- Automating one process
- €2,000 to €6,000
- 3 to 5 weeks
- Systems integration
- €4,000 to €12,000
- 4 to 8 weeks
- Dashboards and reporting
- €3,500 to €9,000
- 3 to 6 weeks
- Custom software
- €8,000 to €40,000
- 2 to 5 months
- Web or e-commerce
- €3,000 to €12,000
- 4 to 10 weeks
- Monthly support
- From €500 per month
- Ongoing
Indicative ranges based on projects already delivered, VAT excluded. The final proposal arrives with scope, milestones and deliverables fixed in writing, and does not move unless the scope moves.
Why does the floor sit at €2,000?
Below that figure there is no time to understand the business, and without understanding it what gets delivered is a patch you have to redo in six months. A €2,000 project includes analysis, build, documentation and handover. If your problem can be solved for less, we will tell you and point you in the right direction.
What drives the price up?
The quality of the APIs of the tools you already run weighs more than any other factor, because integrating against a closed system costs several times what it costs against a documented one. Then come the process exceptions, which are almost always more numerous than the company believes. And finally the state of the source data, which is rarely as clean as assumed.
Do you charge by the hour or by project?
By project, with fixed scope and payments tied to milestones. Typically half on kick-off and the rest on delivery. We do not work with buckets of hours because they push the risk of our own bad estimate onto the client.
Is integrating cheaper than building?
Almost always, which is why we look at it first. If the tools you already pay for cover the substance of the problem, connecting them costs a fraction of replacing them and spares the team a retraining cycle. We only propose custom software when the existing tools genuinely cannot go further.
What happens if the project overruns?
If the overrun comes from our estimate, we absorb it. If it comes from a scope change requested by the client, it is quoted separately before anything is touched. That distinction is signed at the start, not argued at the end.
When do you say no?
When the problem is organisational rather than technical, because automating a process nobody has decided properly only speeds up the mistake. When there is nobody inside with authority to decide. And when the expected saving does not justify the investment, even if the project is perfectly feasible.