Write to usDiscuss a project
All articles

How we estimate a project

What goes into a price, why the first stage is fixed, and what changes the number later.

An estimate is a list of assumptions with a price attached. The more of those assumptions we can check before work starts, the closer the price is to the final bill.

What we need from you

  • Who will use the product and what they need to get done.
  • Screens or flows you already have: sketches, a spec, a competitor you like.
  • Systems the product has to talk to: payments, CRM, an existing backend.
  • A deadline, if there is one, and the reason behind it.

How the number is built

We break the product into screens and server tasks, then estimate each one in days. Design, testing and release work are separate lines, so you can see where the time goes.

Each line gets a range. A login screen has a narrow range. An integration with a system nobody has documented has a wide one. The total is the sum of the ranges.

Why the first stage is fixed

The first stage is usually discovery and a clickable prototype. Its scope is small and known, so we fix the price. After it, both sides know enough to estimate the build with narrow ranges.

What changes the price later

  • New features added after the estimate.
  • Third-party services that behave differently from their documentation.
  • Content or access that arrives late.

When one of these happens, we re-estimate the affected part and agree on it before continuing.