Professional judgment · The first reply
The Prospect Asks for a Quote Before There Is a Scope
A price can make a conversation feel settled while leaving the work almost entirely undefined. Here is how to give an early inquiry a useful answer.
Professional Services
“Can you send something over?”
The prospect sounds interested. They have seen your work, someone has recommended you, and they would like a proposal by Thursday. This is good news until you realize that Thursday is the most specific part of the assignment.
You know they want help with onboarding. Or positioning. Or a website. You do not yet know what is failing, who needs to use the result, what the business can contribute, or which decisions have already been made.
The natural urge is to be helpful. A quick number keeps the conversation moving. A polished proposal demonstrates enthusiasm. It also creates an anchor around assumptions the prospect may never have agreed to and the professional may not have examined.
I would rather make the next answer useful enough to support a real decision. Sometimes that answer is a bounded estimate. Sometimes it is a short scoping conversation. Sometimes the honest offer is a paid diagnostic with its own defined result.
The first task is to establish which conversation you are actually having.
Find out what the number is for
“We need a quote” can mean several things. A manager may be trying to reserve a budget. A founder may be deciding whether to do the work at all. Procurement may need comparable offers. Someone may simply want to know whether your fees belong in the same universe as their expectations.
Ask how the number will be used. That question is usually easier to answer than a request for a complete project brief. It also reveals how much precision is useful at this point.
For a fictional consulting inquiry, imagine a distributor asking for a price to “fix customer onboarding.” If the operations director is building next year’s budget, an initial range with explicit assumptions may help. If the company is choosing a supplier for an imminent implementation, the same range may leave the important work unresolved.
The purpose of the number determines the responsibility attached to it. A planning allowance should be labeled as such. A fixed offer needs sufficiently defined inclusions, dependencies, and limits. Neither becomes clearer because the cover page looks expensive.
Ask for the smallest useful brief
An early inquiry should not require the prospect to complete your entire discovery process for free. It should provide enough information to decide whether you can responsibly offer the next step.
For the fictional distributor, I would ask what happens today, where the difficulty appears, what the engagement should enable, and who will participate. A recent example is more useful than an adjective. “Three new accounts waited a week for their first delivery information” gives the conversation somewhere to begin. “We need world-class onboarding” mostly gives the proposal writer a font problem.
Ask what has already been decided. The business may have selected software, promised a launch date, or assigned internal staff. Those commitments can materially change the work even if the prospective consultant did not make them.
| Early question | What the answer helps establish |
|---|---|
| What prompted the request now? | The event or constraint behind the urgency |
| What should someone be able to do afterward? | The practical result the work needs to support |
| What exists already? | Whether the assignment starts from a blank page, a partial system, or an operating process |
| Who will contribute and approve? | Access, review, and decision dependencies |
| What is the price being used to decide? | Whether a planning estimate or a defined offer is appropriate |
These are scoping questions, not a disguised consulting engagement. If answering them requires interviews, document analysis, or substantial diagnosis, the conversation has reached a different kind of work.
Give the reply a clear next step
A useful response should acknowledge the request, explain the minimum missing information, and offer a manageable route forward. It should not punish the prospect for failing to arrive with professional procurement training.
Here is a fictional email for the distributor:
Thanks for the outline. I can help you determine what this would involve. Before I give you a project fee, I need to understand where onboarding currently stalls, what you want the engagement to deliver, and which parts your team expects to handle. Could you send one recent example and the materials a new customer receives? We can then have a short scoping conversation. If the underlying issue needs investigation before implementation can be priced, I’ll explain a separate discovery option and its cost before any paid work begins.
Illustrative wording
The reply leaves room for a simple assignment to remain simple. It also explains why a more complicated one may need an additional step.
The amount of information requested should fit the situation. Do not ask for confidential customer records when a redacted example will answer the early question. Do not invite uploads of sensitive materials into an ordinary inquiry form. Agree on an appropriate way to share what is actually needed.
Professional Services
Three honest responses to incomplete scope
Once the basic information arrives, the next move usually becomes clearer. A professional can offer a bounded estimate, propose a defined discovery assignment, or explain why the work is not a fit.
A bounded estimate is useful when the unknowns can be made explicit without making the number meaningless. State the assumed output, quantity, review allowance, client contribution, and circumstances that would change the estimate. The range should have a reason, not simply a wide enough spread to protect every possibility.
A discovery assignment is appropriate when investigation is itself valuable work. Give it an output the client can use: perhaps a documented problem statement, a current-process account, identified constraints, and options for the next decision. Explain whether the client can take that work to another provider. Do not make discovery a mysterious admission fee to a proposal.
A decline can also be useful. If the prospect requires a guaranteed implementation price while refusing access to information necessary to define the work, say what prevents a responsible offer. Keep the explanation factual. There is no need to diagnose the prospect’s character because their purchasing process does not fit yours.
A range needs boundaries readers can see
Suppose the distributor only needs a planning allowance for a later budget discussion. The consultant might describe two possible assignments rather than inventing one supposedly precise package.
The first could be a review of a limited set of onboarding materials with a written recommendation. The second could include process mapping and a supervised test of a revised handoff. Those are different commitments. An estimate should make the difference visible before anyone compares the numbers.
The important qualification belongs beside the figure. Do not hide it three pages later under “miscellaneous.” If interviews, implementation, software configuration, or ongoing support are excluded, say so where the reader encounters the price.
Dates need the same treatment. A four-week engagement that begins after records and participants are available is different from a promise to finish four weeks from today. Name the dependency and explain what happens if it is not met.
The reader should be able to repeat the offer back without accidentally enlarging it. That is a better early quality check than whether the proposal sounds confident.
Keep free scoping and paid thinking distinguishable
A professional needs enough conversation to assess fit. A client needs enough clarity to decide whether to engage. Neither benefits when the boundary between those activities and paid work remains implied.
Tell the prospect what the scoping conversation will accomplish. It might establish the requested result, obvious constraints, and the appropriate form of engagement. It will not necessarily solve the underlying operating problem or produce a detailed implementation plan.
If the discussion reveals the need for substantive investigation, pause and describe that work. Name its purpose, output, fee basis, and decision point. Let the client agree before the assignment changes.
There is no need to manufacture complexity. If the issue is clear and the work is bounded, price it. The value of disciplined scoping is that it can make a small job possible as well as identify a larger one.
For a deeper examination of how the underlying problem is established, my Discovery and Framing article develops that separate process. The job here is earlier: respond to the inquiry without making an unsupported commitment.
What happens if Thursday cannot move?
An immovable procurement date does not create missing facts. It does require a practical response.
Explain what you can provide by the deadline. That might be a statement of approach, an explicitly provisional budget, a fixed-price discovery offer, or a response identifying the information needed for a full proposal. Ask whether that format serves the buyer’s actual decision.
If the procurement process permits assumptions, record them clearly and consistently. If it requires a binding offer for undefined work, the professional may need to decline. The prospect is entitled to choose another route. You are responsible for understanding the promise you make.
Avoid submitting an artificially low opening fee on the assumption that every missing item will become a change order. That approach transfers uncertainty into the relationship after the buyer thinks the question has been settled. A more candid early conversation is usually a better foundation for useful work.
Professional Services
The proposal should arrive after the question improves
The ideal result of the first exchange is a more answerable request. “Fix onboarding” becomes “review these materials and identify the information gaps before the first delivery,” or “investigate the handoff and recommend a testable process.” Now the professional can describe a deliverable, the client can assess relevance, and the fee has something concrete to refer to.
Once comparable proposals exist, the buyer has another task. My article on comparing professional-service proposals when scopes do not match addresses that later decision. The present conversation should not try to do both jobs at once.
In professional-services consulting, the first useful contribution is often a question that makes the work describable. That can feel slower than typing a number into a document. It can also prevent weeks of disagreement about what the number was supposed to buy.
Give the prospect something they can act on. Make sure you know what it is.
Rob Urban
A few useful distinctions
Questions about
the story.
Can I give an early price range?
Yes, when it serves the buyer’s decision and the assumptions are meaningful. Label its purpose, inclusions, exclusions, dependencies, and the circumstances that would change it.
Should every uncertain inquiry become paid discovery?
No. A short scoping exchange may resolve the uncertainty. Paid discovery should have a useful, defined output that warrants the engagement in its own right.
What if the prospect only wants to know whether they can afford the work?
Answer that question as directly as the available information allows. Explain the fee basis or bounded options without presenting an initial budget indication as a complete implementation offer.
What is the most important distinction in the first reply?
Separate the next step you can responsibly offer from the eventual project the prospect hopes to buy. That keeps an introduction from turning into an accidental promise.