How long custom software takes and where time gets lost

Where time gets lost

In projects that run late, the problem is rarely the developer. Four causes come up again and again:

• Half-defined requirements. Development starts with a general idea of what is needed. When the case nobody foresaw appears, part of the work has to be redone.
• Unknown integrations. Connecting to an ERP or a shop looks simple until you find out how it is configured, which fields are mandatory or where data is duplicated.
• Dirty data. Products without a code, repeated customers or prices kept in three different spreadsheets. Cleaning that data is not programming, and it is usually underestimated.
• Slow approvals. A demo left unreviewed for weeks delays the next round of changes more than any development task.

How we plan so it does not drag on

We split the project into phases that can be reviewed separately. First comes a shared diagnosis, where the workflows are reviewed and we decide what is automated and what is not. Then the solution is designed, with its scope and what is left out. Only then do we build, in short cycles with demonstrations.

This split has a practical effect: the first delivery is already useful. If the first module solves the most expensive problem, the rest can wait while the team uses it and asks for adjustments with judgement.

A date without a written scope is not a date. Ask the proposal to say what is included, what is not, and what the client has to decide, and when.

What the client can do to shorten the timeline

1. Choose the process that takes the most time and leave the rest for later.
2. Name one person who decides. If decisions go through three people, the project moves at the pace of the slowest.
3. Review demos on time, with concrete comments instead of "we will see".
4. Gather the data and access needed for integrations before they are required.

What to ask before signing

Before accepting a timeline, ask three things: what is included in the first delivery, what is reviewed in each demo, and what happens if a new requirement appears halfway through. The answer to the last question says a lot about the supplier: if nobody can answer it, the timeline they give you has little basis.

If you want to assess your own case, start with our custom software service or write to us and we will tell you which part of the project weighs most on the timeline.