Custom software development for companies
Internal applications for the part of the business no product on the market contemplates, built only when the existing software genuinely cannot go further.
Custom software at udae lands between €8,000 and €40,000 and is delivered within two to five months. Before proposing it we check whether the problem can be solved by configuring what already exists, because in most of the work that reaches us that is the right answer and it costs far less.
What the work covers
Ruling out existing products first
We look at whether a market tool covers the substance of the problem. We only build when bending it costs more than writing it.
Fixed scope against milestones
What is in, what is deferred, and what ships at each milestone, in writing. No buckets of hours.
Full code ownership
Repository, credentials and deployment in the company's accounts from day one. No lock-in by design.
Maintenance plan
Keeping a custom build alive costs fifteen to twenty per cent of the build cost every year. That gets said before starting, not after.
When does it fit?
When what makes the business money is exactly what no tool on the market knows how to do, because that is what sets it apart. There, building makes sense. For the administration every company in the sector does identically, it does not.
When do we decline?
When the process is going to change a great deal over the next two years, because a platform gives more room to manoeuvre. And when there is no concrete answer to who will maintain it and on what annual budget.
What it costs
Between €8,000 and €40,000 depending on screens, flows and integrations. Each integration against a third-party system adds according to its API quality: against a documented one it takes days, against a closed one it can cost more than everything else combined.
Ranges for every service are published on the pricing page.
Isn't SaaS cheaper?
Almost always at the start, which is why we look there first. The honest comparison also adds licence costs as the team grows, the middleware in between, and the risk of the product changing direction.
Who owns the code?
The company, from day one and with full documentation. If a build stops working the day you change supplier, it was never yours.
Can we start small?
That is the norm and the recommendation. The proprietary layer is usually far smaller than feared: not a whole application, just a handful of processes and a database that governs the other tools.