Custom software development for companies that have outgrown standard tools

There is no single figure worth giving before we know your case. Four things move the number most:

• How much the software has to do, and how many kinds of user it serves
• How many existing systems it has to talk to
• What you need in terms of security and audit trails
• Whether data from an older system has to come across

We budget one phase at a time, so you can stop or change direction after any of them. Worked examples and full price ranges are on our app development costs page.

Off-the-shelf software is a finished product built for many companies. You pay licence fees and adapt your processes to the product. Custom software is built for your case: it follows your processes, it belongs to you, and its future development follows your plan, not a vendor roadmap.

As long as your process matches the market standard, off-the-shelf is the cheaper and simpler choice. Once your workflow is a competitive advantage, or you are holding it together with workarounds and spreadsheets, you start running into its limits.

The timeline follows the scope: the number of user roles, the systems to be connected, and whether legacy data has to be migrated. We give you a reliable schedule at the end of the concept phase, once the project has been broken down. Before that, any date would be a guess.

Because we deliver in stages, you can try out a usable part of the system in daily work long before the whole project is finished. That does not shorten the overall timeline, but it moves the important insights forward, while changes are still cheap. Typical project durations by project size are listed on our app development costs page.

You do, outright. The code we write for you is yours, together with:

• the repositories and their full history
• the build and release pipelines
• the runbooks your operations people need

Nothing stops you taking the whole thing to another supplier or bringing it in house, and you do not need our permission to do it. Open-source libraries keep their own licences, which we list in the project. Mid-sized companies ask this early and they are right to, because plenty of suppliers leave the answer vague.

Most of the time we recommend modernising. A system that has run for a decade carries knowledge nobody ever wrote down, and starting from zero throws that away. Our approach is incremental: we map what the live system really does, then replace it piece by piece behind a stable boundary, with no downtime for the people using it.

A full rebuild makes sense in two situations: the platform underneath has stopped receiving security patches, or the way it models your business no longer matches how you work. Migrations from Xamarin to .NET MAUI are routine work for us.

Yes. This is ordinary work for us, not a project of its own. We connect ERP systems such as SAP and Microsoft Dynamics, and we work with Azure, with Entra ID for sign-in and permissions, and with Microsoft 365.

Where a system exposes nothing we can use, we build a Web API that joins it up and records every transfer. We also settle early which system owns which piece of data, so that nobody has to guess later whose number is the right one.

Go-live starts the longest phase in the life of custom software. We keep runtimes and libraries current, apply security updates, watch errors and load in production, and add new functions in planned releases.

For applications that cannot go down during business hours, we put response times and availability in writing. If you want to look after the software yourself later on, we hand it over to your team and support the handover. For the period after that, our Expert as a Service model stays open to you.