Blog
How long custom software takes: from audit to the first usable version
6 min read

Short answer
The first part that actually runs is usually live within six weeks of the start, and a full system takes three to nine months depending on scope, but it is deployed piece by piece rather than all at the end. Before that comes an audit, which takes a few days. The figures below are typical, not a guarantee, and what affects them most is not the programming but how quickly the client answers.
01The stages of a project
The order is similar; the length varies with scope.
- 01Audit: a few days. We look at how the work runs today, and the output is a document with the scope and a rough price. It is yours even if you do not continue.
- 02Design of the first part: screens and rules that can be shown and corrected before any programming. Correcting on paper is cheaper than in code.
- 03Building the first usable part: within roughly six weeks of the start. Not the whole system, but one thing that can really be used.
- 04Pilot: a few weeks with real people and real data, alongside the old way of working. This is where things nobody saw on paper come to light.
- 05Further parts one at a time: each goes live as soon as it is ready. The whole takes three to nine months to assemble, but use begins with the first.
02What makes it take longer
- 01Slow answers. If a question waits a week, a week is lost. It is the most common cause of delay and nobody puts it in the schedule.
- 02A change of scope along the way. Every new requirement is fine, but it is not free, including in time.
- 03Integrations with systems that lack a good API. A CSV export instead of an interface means longer and more fragile work.
- 04Dirty data. Importing customers from five spreadsheets with different names for the same person takes more than expected.
- 05Decisions by several people. If a committee decides on layout and rules, it takes longer than one person with authority.
03What shortens it
One person on your side who understands the work, has time and can decide. When there is such a person, the project is faster than any schedule would make it.
And a smaller first step. The question “what is the smallest thing that would already help?” shortens the time to use more than any speed-up in programming.
04When it can be faster, and when slower
A simple internal tool, such as a register or an approval with a few fields, can be done in less than six weeks. A system with several roles, invoicing and integrations is slower, and there is no point promising otherwise.
For any quote, ask not for the completion date of the whole, but for the date when someone in your company can first use the first part. If the supplier cannot name one, the project has not been divided up.
Frequently asked
- How long does custom software take to build?
- The first part that genuinely runs is usually live within six weeks; a full system takes three to nine months depending on scope. It is deployed piece by piece, and an audit of a few days comes first.
- What delays a project the most?
- Slow answers from the client, changes of scope during the work, integrations with systems lacking a good API and dirty data at import.
- What should I ask a supplier about the deadline?
- When someone in the company can first use the first part. A completion date for the whole is an estimate; a first-use date is a commitment.