What 24 years in IT taught me about estimates

By Tony John, engineer, e-commerce consultant and digital marketer with twenty-four years in IT. He writes about making technology less complicated for business, drawing on real projects in online stores, marketing and software. His articles are short, practical and written for people who run a business rather than a server room.

Published in Engineering on September 30, 2026

6 mins read

What 24 years in IT taught me about estimates
Table of contents+
  1. Estimate in ranges
  2. Shrink the unknowns first

Software estimates are not promises. Treating them like one is how good projects turn into bad relationships.

Every client wants a number. Every engineer knows the number is a guess. The gap between those two facts is where trust breaks.

Estimate in ranges

A range is honest. "Four to six weeks" tells the client there is uncertainty, and tells them how much.

Shrink the unknowns first

Spend the first week on the riskiest part of the work. Once that is understood, the estimate gets much tighter.

Clients forgive a late project. They do not forgive a surprise.

Have a project like this in mind?

Let's talk
Engineering
Tony John

About the author

Tony John

Engineer, e-commerce consultant and digital marketer with twenty-four years in IT. He writes about making technology less complicated for business, drawing on real projects in online stores, marketing and software. His articles are short, practical and written for people who run a business rather than a server room.

More about Tony

Latest articles