Stop Giving Away Free Consulting: Define Discovery and Paid Scope

• Tell the prospect what the first call covers and what work requires a separate engagement.
• Ask whether they want general context or a specific plan, then explain the information needed for that plan.
• Use a transparent handoff in advisory, coaching and software conversations.

Fictional example: a financial professional is asked for a second opinion. They begin analyzing specific holdings and suggesting tax and investment actions before establishing the purpose or limits of the conversation. This article is not a guide to investment recommendations.

The example illustrates the need to make scope clear, not that a prospect has improperly taken work or owes the advisor a fee.

The advisor gave specific guidance before establishing whether the call was meant to include that work.

In different fields, a discovery conversation may drift into detailed work. The professional can explain what is included in the meeting, what would require a separate engagement, and what they can responsibly discuss now.

Clarify the purpose and limits of the call

Discovery, general education and client-specific recommendations are different kinds of work. Professionals should follow their firm’s process and role boundaries when a question moves into regulated or technical advice.

At the beginning, explain what the conversation will cover. If the prospect asks for detailed analysis, say what information would be required, whether that is within the scope of the call, and what a separate engagement would involve.

Separate context from scoped work

Ask about the situation and what the prospect wants to understand. You can share general context that is appropriate to the conversation, then be clear if a specific plan requires additional information or paid work.

For example: “I can explain the general factors we would consider. A recommendation for your situation would require reviewing additional details through a separate process. Would you like to discuss what that process includes?”

This is transparent scope-setting. It should not create anxiety or imply that the prospect cannot make progress without hiring you.

Questions that clarify the request

Useful questions help establish the scope of the conversation, not make a prospect uncomfortable or force a realization.

• “What would you like to understand by the end of this call?”
• “What have you already reviewed?”
• “Which question is most important to address today?”
• “Would general information help, or are you looking for a recommendation for your particular situation?”

Then explain what you can answer, what you would need to verify, and what would fall outside the current conversation.

When the prospect asks for a recommendation

“What do you think I should do?” is a request to clarify scope, not automatic permission to prescribe. Explain what you can answer now, what information a tailored answer would require, and whether that work belongs in a separate engagement or formal process. Then let the prospect choose whether to explore it.

Examples of transparent boundaries

Financial professional: “I can explain what these terms generally mean. To comment on your specific holdings or tax situation, I would need to follow our review process. I can describe that process if you’d like.”

Coach: “We can use this call to see whether the goals you described fit the program. A full coaching session is part of the paid engagement.”

Software seller: “I can show the workflow you asked about. A detailed implementation plan would require confirming the systems and requirements with your team.”

Be useful and clear

Clear scope does not mean being stingy. Answer the question you agreed to discuss, be honest about what you do not know, and explain what further work includes before asking someone to purchase it.

A prospect may decide that the paid work is useful, may choose another provider, or may handle the issue themselves. Do not present these outcomes as a failure or use uncertainty to push them toward a contract.

Three ways to handle “what would you do?”

Advisory setting. A prospect asks for a recommendation about specific holdings. The professional says: “I can explain the general factors we would review. A recommendation about your situation needs the full information and our required process. Would you like me to outline that process?” The prospect has a clear answer about scope, with no implication that they must hire this advisor.

Coaching setting. A prospect asks for a personalized plan halfway through a discovery call. The coach says: “We can use this call to check whether the program fits the change you want. Building and adjusting a personal plan is part of the coaching engagement. I can explain how that work is done and what it costs.”

Software setting. A buyer asks for a detailed migration design. The seller says: “I can show how the product handles the workflow you described. A migration design needs your system map, data owners and technical review. We can scope that work with your team if it is useful.” The seller can still answer a bounded product question now.

These responses do not depend on waiting for a magic phrase that means the buyer is ready. They separate diagnosis, general education and scoped delivery. Rehearse a follow-up question for each: “What would you need to see to decide whether the next engagement is worth considering?” Then state the deliverable, inputs, fee if relevant, and the next choice. The boundary should make the relationship easier to evaluate, not generate discomfort.

Define the deliverable before the meeting

A useful invitation states the topic and the boundary: “We can spend twenty minutes understanding your question and explaining how our review works. We will not be building a custom plan during that call.” The exact time may vary; the important part is the deliverable. If you offer a free review, be specific about what is included. If the buyer wants a paid diagnostic, describe its output, inputs, price and who owns the work.

During discovery, a Direct question can clarify the request: “Are you looking for an explanation of how the product works, or a design for your environment?” A Clarifying question follows: “When you say ‘second opinion,’ which part do you want checked?” Those questions prevent both extremes—giving a generic pitch when the buyer has a precise issue, or producing a tailored plan when the call was meant to determine scope.

Make the handoff concrete

At the end, recap the question, what you answered, what remains open and what a further engagement would produce. For a software team, the next step might be a paid implementation assessment with a system inventory and a written integration plan. For a coach, it might be enrollment in a defined program. For a regulated professional, it may require a formal review before any individualized advice. The boundary changes by field, but the communication skill is the same: no surprise work and no surprise ask.

Common questions

How do I keep discovery from becoming free consulting?

Set the call’s purpose at the start, answer questions within that scope and explain what inputs, process and agreement a tailored deliverable would require.

Should I wait until the prospect asks for a prescription?

No. Explain your service when relevant and answer the question they actually ask. A request for specific advice does not erase professional obligations or make a paid engagement automatic.

Can I still be generous with useful information?

Yes. General context and clear examples can help the prospect. Make the boundary explicit when they request a tailored plan, regulated advice or implementation work.

Put it into practice

Choose a conversation to practise.

Explore the framework and put this idea to work on your next call.

Explore VIVID Layer 3: Diagnostic Engine →