Skip to content
← All articlesOutsourcing

Software Project Estimation: How to Judge Vendor Quotes

Learn how software project estimation really works, what a credible vendor estimate contains, and how to compare offshore quotes without being misled.

Every outsourcing project starts with a number, and that number is almost always wrong in one direction or another. Software estimation is not a sign of dishonesty when it misses; it is a prediction made with incomplete information. But some estimates are far more trustworthy than others, and a CTO, founder or product manager can learn to tell the difference before signing anything.

This guide explains what estimates actually are, what a credible one contains, and how to compare quotes from different vendors fairly.

Why estimates are usually wrong

Three forces push estimates off target:

  • Unknowns. Early in a project, nobody knows how hard the integration with your payment provider or legacy ERP will be until someone tries it.
  • Scope drift. Requirements grow as stakeholders see working software. The estimate was for the original scope, not the one that emerged.
  • Optimism. Teams tend to estimate the happy path. Reviews, bug fixing, deployment, and waiting for feedback are underestimated or forgotten.

The practical lesson: treat an estimate as a range with a confidence level, not as a promise.

Estimate, quote and commitment are different things

Buyers often mix these up, and vendors sometimes let them.

Term What it means When it is reliable
Rough order of magnitude A broad range from a short conversation Only for deciding whether to continue talking
Estimate A reasoned range based on a defined scope After requirements and designs are reviewed
Fixed quote A price the vendor commits to for agreed scope When scope is stable and well documented
Budget cap A ceiling you set, with scope flexing to fit When priorities are clear and ranked

If a vendor gives you a single precise figure after one call, treat it as a rough order of magnitude, however it is labelled.

What a credible estimate contains

Ask for a written estimate and check that it includes the following.

  1. A scope breakdown. Features split into small pieces, not a handful of large lines like “backend: 400 hours”.
  2. Ranges or three-point figures. Best case, likely case and worst case per item show where the uncertainty sits.
  3. Stated assumptions. Third-party APIs available, designs supplied, content ready, number of supported devices and browsers.
  4. Explicit exclusions. Hosting, licences, app store fees, data migration, post-launch support.
  5. Non-coding work. Project management, QA, design review, DevOps setup and documentation should appear as lines, not be hidden.
  6. A risk list. The two or three things most likely to move the number, and what you can do about each.
  7. Change handling. How new requests are assessed, priced and approved.

An estimate with no assumptions or exclusions is not more confident; it is less honest.

Red flags in vendor quotes

  • The lowest quote is much lower than the rest, with no explanation. Either scope was misunderstood or corners will be cut later.
  • QA and testing are missing or described as “included” with no detail. See our guide to regression testing for what should be planned.
  • The vendor did not ask questions. Good teams ask many before pricing.
  • Nobody named who will actually do the work, or their seniority mix.
  • Pressure to sign quickly because “the price expires”.

How to compare quotes fairly

Normalise before you compare. Put each vendor’s figures into the same template:

  • Same scope list, with each vendor marking what is in, out or assumed.
  • Same phases: discovery, design, build, testing, deployment, warranty or stabilisation.
  • Same team assumptions: roles, seniority and expected availability.
  • Same currency, tax treatment and payment milestones.

Then ask each vendor to walk you through their biggest line item. How they explain it tells you more than the total does.

Reduce uncertainty before you commit

The cheapest way to improve an estimate is to spend a little to learn more first.

  • Run a short discovery phase. A paid discovery workshop produces better requirements and a firmer estimate. Our product discovery workshop guide outlines what to expect.
  • Build a thin slice. Delivering one end-to-end feature early shows real velocity and exposes integration problems.
  • Prototype the riskiest part. If one component could break the plan, test it first.
  • Rank your requirements. Clear must-have, should-have and nice-to-have lists let scope flex without surprises.

Choose a commercial model that fits the uncertainty

When scope is well understood, fixed price can work. When it is not, forcing a fixed price just moves the argument to change requests. A dedicated team with a monthly rate and a visible backlog gives you flexibility and transparency, while a fixed-scope phase can cover the parts you do understand. Our comparison of fixed price vs dedicated team goes through the trade-offs in detail.

Keep estimates honest during delivery

Estimation does not stop at signing. Good practice includes:

  • Re-estimating the remaining backlog every sprint or two, using actual progress rather than the original numbers.
  • Reviewing a burn-up chart that shows scope added as well as work completed.
  • Sharing bad news early. A vendor who flags a risk in week three is worth more than one who hides it until week twelve.
  • Recording what was estimated against what happened, so the next estimate improves.

A short checklist before you accept an estimate

  • Is the scope written down and broken into small items?
  • Are ranges, assumptions and exclusions stated?
  • Is testing, project management and deployment included?
  • Do you know who will do the work?
  • Is there a defined process for changes?
  • Have the biggest risks been named and discussed?

If you can answer yes to all six, you have an estimate you can plan around.

Talk to a team that shows its working

If you are weighing vendors and want an estimate that explains its assumptions rather than hiding them, our dedicated development teams service starts with a clear scoping conversation. Contact us with your requirements and we will respond with questions first and numbers second.

Let’s build what’s next.

Tell us about your platform, your product idea or the systems you want to modernise. Someone from our Chennai engineering team will get back to you personally.