When the work needs scoping before it needs a fixed fee

A buyer asks for a fixed fee to standardise onboarding across three teams. You do not yet know whether those teams should use the same process. A larger allowance in the quote would leave that decision unresolved while making you responsible for an assignment neither party has defined.

The question is whether you can name a useful piece of work to investigate first. A scoping assignment should leave the buyer with something they can use even if they stop there.

Identify the uncertainty that could change the assignment

Ordinary sales qualification helps both parties decide whether a conversation is worth continuing. You can discuss the buyer’s situation, explain the kind of work you do and check obvious constraints without selling a separate engagement.

A different situation arises when answering a question requires substantive investigation. You may need to compare conflicting workflows, inspect existing materials or talk to the people who will have to use the result. The answer could change the deliverables, the people involved or whether the proposed project makes sense at all.

Ask which unanswered question could change the assignment you would accept. A missing logo file is usually an input to request. Uncertainty about whether the business needs a new offer or merely a clearer explanation can change the work itself.

The GOV.UK guidance on discovery separates understanding a problem and its constraints from committing to build a service. It also allows a decision to stop. That public-service framework does not prescribe how a consultancy should charge. It supplies a useful question: what must you learn before making the next commitment?

Give the investigation a result of its own

Consider a fictional operations consultancy asked to standardise client onboarding across three teams. All circumstances, assignments and possible recommendations below are invented for illustration; they describe no client engagement or result.

The buyer assumes that a common workflow will solve inconsistent handovers. The consultancy does not yet know whether differences between the teams reflect avoidable confusion or genuinely different customer requirements.

A bounded starting assignment could examine one recent onboarding example from each team, compare who makes the key decisions and identify what can sensibly be shared. It would finish with a written recommendation and a discussion of the alternatives. Implementation, staff training and rewriting every onboarding document would be outside that assignment.

The recommendation might support a common set of handover information with different team procedures. It might identify a suitable shared workflow. It could also explain why the examples are insufficient to recommend either option and name the next uncertainty to investigate.

The client can use that recommendation to choose a next step, including doing less than originally planned. Make the output understandable without requiring another purchase from you. If the only thing the buyer receives is permission to hear your delivery price, reconsider whether you have described a useful service.

This distinction also helps you explain which process detail belongs in a proposal. Describe what the investigation resolves and what the buyer receives, rather than presenting a list of meetings as its value.

Put a boundary around what you can learn

A smaller assignment still needs a real scope. Explain which materials you will examine, who needs to participate and what the recommendation will cover. State what limited access could leave unresolved.

In the fictional example, examining one case per team would provide a narrow view. The consultancy should say that its recommendation rests on those examples and the participants’ accounts. It cannot quietly turn them into evidence about every customer or promise a complete operating model.

Agree how to handle a missing input before the work begins. You might pause until the necessary records are available or offer a different, explicitly narrower investigation. Keep the buyer able to assess the changed commitment before proceeding.

A discovery label does not make an open-ended assignment clear. The buyer needs to understand where the work finishes and what question they should be better equipped to answer.

Explain what an early estimate does and does not support

A buyer may still need a rough cost orientation before deciding whether the investigation is affordable or relevant. Explain what you can responsibly estimate now. A familiar project with visible assumptions may support a range; a substantially undefined assignment may not.

The Infrastructure and Projects Authority’s cost-estimating guidance connects estimates to the development of scope and the uncertainty in available information. It concerns capital estimates for UK infrastructure projects. The narrower lesson for a service business is to make the basis of an estimate visible rather than make an uncertain assignment look settled.

Explain which decision the range supports and which assumptions could change it. Distinguish the defined starting assignment from any provisional discussion of later implementation. Avoid a low headline number that depends on discovering the smallest possible project.

For the website presentation, use pricing information your actual offer can support. For a buyer comparing proposals, make the responsibility covered by each fee clear.

Decide the next commitment from the findings

At the end, distinguish what you found, what you recommend and what remains unresolved. A recommendation to investigate further needs a reason the buyer can examine; it should not follow automatically from finishing the first assignment.

If the evidence supports delivery, describe that assignment using the findings and remaining assumptions. If it supports a smaller change, explain the smaller change. A buyer who can use your work to decline a larger project has received a decision they paid to understand.

AI can help organise supplied information or identify contradictory assumptions in a draft scope. It cannot inspect records it has never received or establish that different teams work in the same way. Check every proposed assumption against the actual assignment before it enters a quote.

Use the offer worksheet to examine the starting assignment on its own. The promise should describe a useful decision and a boundary you can keep, with a clear explanation of what would make a later commitment possible.