How Long a Custom System Takes, and Why Estimates Come Later

This usually comes up in the first conversation, and the honest answer sounds unsatisfying: it depends. This piece sets out realistic ranges, and why a proper estimate can only follow the mapping stage.

Realistic ranges#

A branding site or company profile: weeks. The content is reasonably clear from the start, and what takes the time is visual design and writing — not anything technical.

A custom system: months. Not because there is a lot of code, but because the business rules behind it have to be understood, rewritten as explicit rules, then tested against cases nobody anticipated.

What surprises people: two systems with the same number of screens can differ twofold in duration, depending on how many exceptions must be handled.

Why the estimate follows mapping#

Before we have seen how you work, we can only guess. And guesses at that stage always miss in the same direction: too optimistic.

Not for lack of care, but because the rules that consume the most time are the ones nobody has ever written down. A rule like "if it is a long-standing customer and the order is above a certain size, the price differs" rarely surfaces in an early conversation. It surfaces in week two of mapping, when someone says "oh, except when...".

The stages and their weight#

Work usually divides like this:

1. Mapping — understanding how you work now, writing the rules down, agreeing scope
2. Design — interface and flow taken to where you can see and try them before any code
3. Build — done in stages, each part usable as it is finished
4. Deployment and adjustment — put on a server, used for real, then fixed from what real use reveals

The fourth stage is almost always underestimated. A system in genuine use always surfaces things testing did not.

What speeds it up#

• Fixing scope and holding it. Mid-build changes are the number one cause of delay.
• Providing one decision-maker. If every question waits for a meeting, the schedule waits too.
• Starting with one process. A system running next month beats a complete system running next year.
• Deferring integrations not needed at the start.

What slows it down while looking like it helps#

Adding people to the team mid-build. Newcomers need time to absorb business rules already mapped, and while they do they consume the time of whoever is building.