Skip to content
dvnt.io

Resources · glossary

Project estimate

An estimate of a project’s effort and cost made before it starts, based on what is known about the scope at that moment. It is not a price promise — the less is known, the wider its range should be.

Also called
  • project estimation
  • software estimate
  • effort estimate
  • cost estimate
  1. 01

    How it differs from a quote

    An estimate says how long the work will probably take given what is known now. A quote is a commercial commitment: a specific price for a specific scope, valid for a set period. A supplier who gives a single number right after the first call is pricing their own risk, not the project.

  2. 02

    Why it comes as a range

    Because at the start nobody knows the answers to questions that only come up along the way: where the data comes from, who approves the content, how the integration works on the client’s side. A range is honest information about uncertainty — you narrow it through discovery, not through pressure.

  3. 03

    What spoils it

    Unclear scope, missing decisions on the client’s side and changes made after the design is approved. These are the three most common reasons a project ends up outside the estimate — and none of them is a calculation error.

  4. 04

    How to use it

    Treat it as a frame for the conversation, not as a price. Ask for a breakdown into stages and for the assumptions that affect the result most. Before you order an estimate, it is worth working out the order of magnitude yourself — cost calculators show how the budget changes with scope.

Related terms

  • Hourly rateThe price of one hour of a specialist's work, which most web project quotes are built from. On its own it tells you nothing; it only means something once multiplied by the number of hours.
  • Fixed price vs time and materialTwo ways of paying for a project: a fixed price for a scope agreed in advance, or payment for the time actually worked. The choice shifts risk between the client and the supplier.
  • MVP (minimum viable product)The smallest version of a product that genuinely solves a user's problem and lets you check whether anyone will use it. Not a prototype, and not a version stripped of quality.

← All terms

15 minutes. No sales pitch.

A term in a proposal sounds foreign? In 15 minutes we explain what it means for your project.