Planning, commissioning and running custom software
When your own software pays off, what drives cost and duration, how a project starts small and who owns the source code.
Custom software
How much does custom software cost?
The price depends mainly on four things: the number and depth of features, integrations with other systems, security and data protection requirements, and running the software after launch. A serious figure only exists once the scope is described. At Ouhud you then receive a fixed-price offer.
When does custom software pay off, and when not?
Custom software pays off when your processes set you apart, standard software only fits with many workarounds, data is moved between programs by hand, or spreadsheets reach their limits. It does not pay off for tasks that work the same everywhere, such as payroll or financial accounting.
How long does a software project take?
The duration depends on scope, integrations and how quickly decisions are made. The fastest route to usable software is a small first version that fully solves one task, then extending it step by step. You plan the timeline together with the team.
Fixed price or time and materials: which is better?
A fixed price gives you planning certainty but requires a clearly described scope. Time and materials is more flexible when requirements are still changing a lot, but shifts the cost risk to you. A proven approach is a fixed price for a clearly described first phase, followed by further phases.
What is an MVP, and why start with one?
An MVP (minimum viable product) is the smallest version of software that fully solves one real task and is used day to day. You start with it because real use shows what is needed faster than any concept. That lowers cost and risk, because only what proves itself gets built.
Who owns the source code, and how do you avoid vendor lock-in?
Vendor lock-in happens when you can only keep running your software with one particular provider. You avoid it when you own the source code, widely used technology is chosen, the software is documented and you can export all your data at any time. At Ouhud, what we build for you belongs to you.
Can a new team take over and develop existing software?
Yes, if the source code, access and data are available. It starts with an assessment: how is the software built, how secure is it, how well is it documented and tested? Then you decide whether to improve it step by step, replace it part by part, or rebuild it.
The first step is a conversation
You describe what you have in mind. If we are a good fit, you receive a fixed-price offer for a clearly described scope. The call is free.