Nythrex

Guide · Estimates

Why every software estimate is wrong — and how to read one anyway.

An estimate isn’t a promise; it’s a forecast made with incomplete information. The useful question isn’t “is it right?” but “what does it assume, how uncertain is it, and how will it get better?” Here’s how to read estimates like an engineering manager.

By Nythrex EngineeringUpdated 1 min read

  1. Idea

    Very wide range

  2. After discovery

    Narrower: scope & risks known

  3. After design

    Narrower still

  4. Mid-build

    Forecast from real velocity

  5. Near release

    Mostly known

The “cone of uncertainty”: estimates get better as the project reveals what it really is.

Why estimates miss

  • Unknown unknowns: integrations behave differently than documented; data is messier than expected.
  • Scope drift: small additions accumulate — see how change requests double budgets.
  • Optimism: estimates describe the happy path; reality includes reviews, bugs, meetings and waiting.
  • Different assumptions: two vendors estimate different things under the same title.

How to read an estimate

0/6

Comparing quotes fairly

Put quotes side by side by scope item and assumption, not by total. The cheapest quote often simply excludes things the others included. Our brief generator helps you give every vendor the same starting point.

Frequently asked questions

Want a second opinion on your project?

Tell us what you’re building and where you’re stuck. We’ll reply within one business day with the most practical next step — even if that step isn’t us.

Start a project