Blog · Scoping and estimates
Why “how much will this cost” rarely has a one number answer, and what a useful estimate actually looks like.
Every software conversation eventually gets to the same question, and the honest answer is almost never a single number, at least not this early.
A fixed number implies a level of certainty that does not exist before the work has started. Anyone who gives you a confident single number for an open ended project is either wildly experienced with something nearly identical, or guessing and hoping nobody asks how they got there.
It breaks the work into small pieces. Scope creep is easy to catch inside a two week increment. It is nearly invisible spread across a three month block with no checkpoints.
It gives a range, not a point, and explains what would move a project toward the low end versus the high end. A range with reasoning behind it is more useful than a false-precision number with none.
It separates what is fixed from what is exploratory. A login screen is predictable. A reporting feature that depends on how messy the underlying data turns out to be is not, and pretending otherwise just moves the uncertainty later instead of removing it.
Picture a client asking for a customer portal. The login and account pages are well understood territory, and an experienced team can estimate those closely. The reporting dashboard depends on data nobody has fully audited yet. That piece gets a wider range, or gets scoped as a short discovery phase before a real number is possible at all.
Scope changes get flagged the moment they are noticed, not absorbed quietly and not used to pad the next invoice without a conversation first. An estimate is a living document, not a number you get once and never revisit.
Curious what our own process for this looks like in more detail? See how we build
Tell us what you are trying to build or fix. We will give you a straight read on what it takes, and if we are not the right team, we will tell you that too.
