Skip to main content
Contact

What a good project estimate contains

A good project estimate shows its working. It says what the team understood, how the hours divide between the parts, which questions are still open, and what it needs from you. A single number with none of that is a guess you cannot check.

Our 2020 guide for anyone on the team asked to estimate puts it plainly: an estimate is a usable approximation built from incomplete data. The data is always incomplete. The working shows you which parts.

What the estimate should contain

PartWhat it tells you
What we understoodWhether the team read the brief the way you meant it
Hours by part of the workThe header, each page or screen, and anything special, such as animation
Totals by disciplineDesign, front end, back end and content entry, each on its own line
Questions for youWhat the team could not decide from the files
What we need from youFonts, images, logins, content, decisions
What you should knowRisks, assumptions and anything left out

The questions are the most useful part. Our guide asks for questions written to the client, not to the colleague who assigned the estimate, so they can be sent without editing. If there are no questions, ask which assumptions the estimate relies on.

One estimate, worked through

In 2017 a partner asked us to estimate the design of a travel deals website for its client. We sent questions before we sent hours:

  • Do you want wireframes first, or straight to visual design?
  • Is there a logo and a brand guide? Are fonts and colours fixed?
  • Can users post and comment?
  • How does search work?
  • Is there a plugin for flight routes, and what does it show?
  • Do all deals share one structure?
  • How do alerts work?

The estimate then sized the parts before the pages. The header, footer, search results, sign in, the user's dashboard, a deal, an article, a route, alerts, forms, messages and a style guide came to 98 hours. Putting those parts together into 43 pages came to 50 hours. Making it work on every screen size came to 20.

The total was 168 hours. The original estimate described that as about three and a half weeks; your delivery schedule depends on team capacity and review time. Sized this way, a forty-fourth page adds little, because its parts already exist. A page that needs a new part shows up as a new line, not as a surprise.

What to send to get a good estimate

Every brief arrives differently: notes in a prototype tool, design source files, a font, a folder of images, a list of sites the client likes. Our guide's first step is to read every file and check that the fonts and linked images are actually there. A missing font found during the build becomes a delay and a change request.

So send, at the start:

  1. The brief, however rough, with what is already decided.
  2. Every file you have: designs, fonts, logos, images, content.
  3. Two or three sites you like, and what you like about each.
  4. What must connect to what: payments, a booking system, a customer database.
  5. Your date, and why it is that date.

Five questions to ask behind any estimate

  1. What did you understand the project to be? Read it against your brief.
  2. How do the hours divide? By part and by discipline, not one total.
  3. What is assumed? Each assumption is a place the number can move.
  4. How many rounds of feedback are included? That is where hours grow.
  5. What would change the number most? A team that knows its estimate can answer at once.

Two estimates with the same total can describe two different projects. The working is how you tell.

Need an estimate you can compare?

Send us the brief and whatever files you have. We will send back what we understood, the hours by part, and the questions we still have.

Ask for an estimate