How do I price a project when I can’t predict the effort?

When you can’t predict the effort, don’t price the whole project as a single fixed number. Price it as a range built from the effort each phase is likely to take, with a review point at the moment the big unknowns resolve. Quote the first phase tightly because you can size it, give an honest effort range for the rest, and agree to firm up the number once the early work shows you what the job really involves. The price stays tied to real hours instead of a hopeful guess, which protects your team’s capacity and keeps you from underselling work you cannot yet see.

Why fixed quotes fail on unpredictable work

A fixed quote is only as reliable as the scope behind it. When the work is familiar, the inputs are clear, and the approval path is known, a fixed figure can be useful. When those conditions are missing, the quote creates an appearance of certainty that the project itself does not support.

The usual failure is not that the team works slowly. It is that the early quote assumed answers that nobody had yet. The old system needs more cleanup than expected. The client has three decision-makers instead of one. The content arrives in five formats. A technical dependency behaves differently in production. Each discovery adds real effort, but the original quote has nowhere for that effort to go.

This is why a firm can deliver strong work and still lose control of its capacity. The estimate was treated as a promise before the work was understood.

Size what you know, range what you don’t

Separate the project into three buckets: known work, comparable work, and unresolved work. Known work can receive a tight estimate because you understand the steps. Comparable work can receive a range based on similar projects. Unresolved work needs a time-boxed first phase that produces the information required for a better estimate.

For example, a redesign may include a well-understood discovery workshop, a reasonably familiar design phase, and an uncertain migration. Quote the workshop closely. Give design a range based on the number of page types and review rounds. Treat migration as a separate phase whose estimate becomes firm after the audit.

This is not evasive pricing. It is a clearer description of what you know today. If every piece still feels too large to size, use the process in How do I break a big project into estimatable pieces? before building the quote.

Build the quote from effort, not a round number

Start with the people and roles required for each phase. Estimate the hours for strategy, design, development, project management, testing, and any other work the job genuinely needs. Then apply the appropriate rate structure to those hours.

This bottom-up approach exposes weak assumptions. If the design phase contains only design hours, ask who is handling review notes, client calls, file preparation, and handoff. If development has no testing effort, the quote is incomplete. If project management appears as a token line, check whether the meetings and coordination have been counted.

A round figure chosen because it feels acceptable may still land near the right answer, but you will not know why. An effort-built quote gives you something you can revise intelligently. When one phase changes, you adjust that phase rather than inventing a new total.

Add review points where the unknowns resolve

A review point is a planned moment when the estimate gets sharper. Put it after discovery, an audit, a prototype, technical validation, or any other step designed to remove uncertainty.

Define what the checkpoint will answer. It might confirm the number of templates, the condition of the data, the integration approach, or the approval path. State what the client receives at that point and what happens next. The next phase can move forward within the original range, receive a firm figure, or be reshaped if the findings change the job.

The checkpoint should appear in the proposal and the delivery plan. It is not a private reminder for your team. When both sides know a decision is coming, new information feels like part of the process instead of a surprise request to revisit the quote.

Explain the range to the client without losing the deal

Clients rarely object to a range simply because it is a range. They object when it feels unsupported. Show the work behind the low and high ends. Explain which assumptions keep the project near the low end and which conditions move it higher.

Use plain language: “We can size discovery closely. The implementation range depends on what the audit finds. After the audit, we will confirm the implementation effort before you authorize that phase.” That sounds controlled because it is controlled.

You can also set a decision boundary. The team does not proceed past the review point without the client’s approval of the refined scope. That gives the client more control than a fixed quote that later produces change requests. For a fuller comparison of where each pricing structure fits, see Fixed fee or hourly: which pricing model fits your firm?.

Refine the estimate as the work reveals scope

An estimate should become more precise as uncertainty falls. After each phase, compare planned hours with actual hours, record what changed, and update the remaining range. Do not wait until the end of the project to discover that the early assumptions were wrong.

Keep the revision visible to the team. If discovery used more effort but reduced implementation uncertainty, the project may still be healthy. If every phase is landing near the high end, check whether the remaining capacity and timeline still hold. Workflow management software can keep the estimate, actual effort, ownership, and timing connected as the plan changes.

The goal is not to predict unfamiliar work perfectly on day one. The goal is to make uncertainty explicit, learn early, and keep the commitment tied to what the team can actually deliver.

FAQ

Should I just pad my estimate to be safe?

Padding hides the real effort and often makes your quote uncompetitive or leaves you overcommitted when the buffer gets used. It is clearer to quote a range with a stated review point, so the client sees the uncertainty and you are not silently absorbing it.

How do I explain an effort range to a client without sounding unsure?

Frame it as a professional read on the work: you know the first phase precisely and you will confirm the rest once discovery removes the guesswork. Clients trust a range backed by a plan far more than a single number that quietly balloons later.

What if the client wants one fixed price no matter what?

Then price the part you can define and scope the rest as a separate phase with its own quote once the work is understood. Committing to a fixed number on effort you cannot yet see is how jobs drift past capacity and get undersold.