Guide · 30 August 2026

How long does custom software actually take to build?

A business website is usually weeks. A system that runs part of how you work is usually months. A first version of a product you intend to sell is usually longer than anyone wants to hear. The more useful answer is what makes a project overrun, because it is almost never the building.

The honest shape of it

A website that has to explain a business and get people in touch is a short project. The design takes longer than the build, and the longest part is usually waiting for content that only you can write.

Software that replaces a process is a different order of thing, because the process has to be understood before it can be encoded, and most processes turn out to have exceptions nobody documented.

A first version of something you intend to sell sits somewhere between the two, and depends far more on how ruthlessly the first version is cut down than on how fast anyone works.

What actually makes projects late

Decisions, not development. A project stalls because a question needs answering by somebody who is busy, and it sits for a fortnight. Ten of those is five months, and none of them appear on a plan.

The fix is unglamorous: fewer people who can say yes, and a standing slot in the week where the open questions get answered rather than queued.

The second thing: scope that grows quietly

Nobody adds a month of work in one go. They add an afternoon, fifteen times, and each one is individually reasonable. Then the date moves and it is not clear why.

This is why a written scope matters more than an optimistic timeline. Not to refuse changes, but so that when one is made, both sides can see what it costs.

The third thing: content and data

The software is often finished while the thing it needs to run on is not. Photos, copy, product details, the export from the old system that turns out to be full of duplicates.

If you do one thing early, start on this. It is the part that only you can do, it always takes longer than expected, and it is the most common reason a finished build sits waiting.

The question that tells you most

Ask when you will first see it working. Not a design, not a demo video: the actual thing, in a browser, doing something.

If the answer is near the end, the timeline is a guess that will be tested only once, at the worst possible moment. If it is early and often, a slip shows up while there is still time to do something about it.

Think this is you?

Tell us what is getting in the way. If we are the wrong people for it, we will say so.

Start your project