When Paid Discovery Makes More Sense Than Repricing a Proposal

Understand the situation before responding

Identify which unknowns materially change cost or feasibility: data condition, stakeholder requirements, integration constraints or delivery responsibilities. Separate information you should already understand through normal qualification from work that genuinely requires investigation. If the project can be scoped from available facts, do not invent a discovery requirement. Explain why a reliable implementation proposal depends on the missing evidence.

An example message to adapt

The unresolved issue is [specific unknown], which could materially change the implementation. Rather than pretending the full scope is fixed, we can consider a defined discovery stage producing [outputs]. You would then have a separate decision about implementation. Shall we review whether those outputs would be useful before discussing the discovery fee?

Illustrative teaching example. Replace the prompts with buyer-confirmed facts; this is not a client conversation, claimed result or message to send automatically.

Prepare a useful next action

Specify activities, deliverables, access needs, client time, exclusions and investment. Explain what the buyer can use the output for even if they do not buy further work from you. State whether any fee credit exists only if you actually offer it. Avoid implying discovery guarantees an implementation price or technical outcome. Make any dependency on specialist access or third-party cooperation explicit.

Record the decision and its limits

Keep the discovery agreement distinct from the future project decision. Agree who reviews the findings and what would make the next phase feasible. If discovery reveals the project is unsuitable, report that plainly. If the buyer cannot justify the discovery output itself, pause instead of using a low-priced first stage to create an unclear obligation to buy more.