Charge for Discovery When the Work Produces a Deliverable

Free qualification has a limit

A prospect asks for help evaluating a contact center, network redesign, security program, or cloud migration. You take the first call. Then comes the environment review, stakeholder interviews, supplier coordination, invoice analysis, requirement mapping, and written recommendation.

Two weeks later, your firm has done real consulting. The prospect has not made a commercial commitment, and your team still calls the work "discovery."

That is where small advisory firms give away more than time. They blur sales work and client work. The buyer cannot tell what they are receiving. The advisor cannot control the scope. Nobody has agreed on the output, access, ownership, or decision date.

The answer is not to charge for every conversation. A normal qualification call should help both sides decide whether there is a credible problem and a reason to continue. Charge when the next phase requires analysis and produces something the client can use, even if the client does not buy the eventual solution through you.

The broader technology advisor discovery process explains what a good first call should capture. This playbook draws the commercial line after that call.

Separate the sales decision from the advisory decision

Free qualification answers a short set of questions. Is the company a fit? Is there a real problem? Is somebody willing to own the decision? Does the timing justify another step? Can your firm help?

You need enough information to answer those questions without asking the client to buy an assessment first. If you cannot establish basic fit in a normal conversation, paid discovery will not rescue a weak opportunity.

Paid discovery begins when the client wants you to determine what should be done, not merely whether another conversation makes sense. That may require examining source records, reconciling conflicting requirements, bringing several stakeholders into the process, testing assumptions with suppliers, or turning messy inputs into a decision document.

Keep that distinction visible in your pipeline. Qualification is a sales activity attached to a possible opportunity. Paid discovery is its own engagement with scope, value, an owner, dates, and acceptance. If you mix the records, your forecast will treat unapproved consulting labor like sales progress.

Use five signals to decide whether discovery should be paid

No single hour threshold works for every firm. A focused two-hour review by a senior advisor may create more value than ten hours of basic data collection. Look at the nature of the work.

Discovery probably belongs in a paid engagement when several of these signals are present:

• The answer depends on records, contracts, invoices, diagrams, usage data, or system access the advisor must review
• Several client stakeholders have different requirements, priorities, or approval roles
• The advisor must coordinate suppliers or specialists before defining a credible path
• The work will produce a written assessment, requirements package, roadmap, shortlist, business case, or other reusable deliverable
• The client could take the completed work and make a decision without buying the next phase from your firm

That last signal matters. If your work creates standalone value, call it client work. The fact that it may lead to a larger supplier transaction does not make the work free.

Paid discovery is usually unnecessary when the request is narrow, the current environment is already known, and the client only needs routine options or a simple renewal check. It may also add friction when a long-term client has already supplied the required context through ongoing account planning.

Sell an output, not access to your calendar

"Ten hours of discovery" is easy to question because the client does not know what ten hours buys. Define the decision the engagement will support and the evidence the client will receive.

A useful paid discovery scope should state:

• The client decision the work is meant to support
• The records, access, and people the client must provide
• The interviews, analysis, and supplier work your firm will perform
• The deliverables the client receives
• The questions and activities that remain outside scope
• The owner, working dates, review meeting, and acceptance method
• The fee, payment timing, expenses, and any approved credit toward later work

The deliverable does not need to be a giant report. It needs to make the next decision easier. For one client, that may be a verified requirements brief and supplier evaluation plan. For another, it may be a current-state inventory, risk register, and recommendation on whether to proceed.

Do not promise a final supplier recommendation before you know whether the available evidence supports one. The engagement can conclude that the client needs more data, should fix an internal issue first, or should not pursue the project. A paid answer still has value when the answer is "not yet."

Put boundaries around the client's part of the work

Discovery slips when the advisor is waiting for invoices, scheduling a fifth stakeholder, or chasing access that was supposed to arrive before analysis began.

Write the client dependencies into the scope. Name the documents, people, access, and due dates required. Decide what happens if those inputs are late or incomplete. You may extend the timeline, deliver findings with stated limitations, revise the scope, or pause the work. Pick the treatment before the delay occurs.

Also name the client owner who can resolve access questions and confirm priorities. A group of interested stakeholders is not an owner.

This protects the client too. They can see exactly what your firm needs and challenge requests that do not connect to the agreed decision. Paid discovery should not become permission to collect everything.

Decide whether the fee is credited before you start

Some firms keep the discovery fee separate. Others credit part or all of it toward a later advisory or implementation engagement. Either model can work. The problem starts when the advisor invents the credit during negotiation.

Base the treatment on the economics and purpose of the work. If discovery is a complete, useful engagement that consumes senior time, a full credit may turn the fee back into unpaid labor. If the work directly replaces effort already priced into the next phase, a defined credit can be reasonable.

Write down the amount or percentage, the qualifying next engagement, the approval condition, and the date when the credit expires. Do not say the fee "may be applied later" and leave both sides to remember what that meant.

Supplier compensation deserves the same clarity. If a supplier, distributor, or another party funds part of the assessment, disclose the relationship and keep the recommendation criteria tied to the client's decision. Do not present supplier-funded activity as proof that every required option was evaluated.

Do not send a vague discovery proposal

A paid phase should not move forward on a paragraph that says your firm will assess requirements and provide recommendations. That language hides every future disagreement.

Use the same discipline you would use for any other client engagement. Connect the decision, evidence, deliverables, exclusions, owners, dates, and commercial treatment in a clear decision brief and proposal. If the client cannot see what completion looks like, the scope is not ready.

Give the buyer a clean exit after discovery. They should know what they receive if they choose another supplier, delay the project, or decide not to proceed. Charging for work while making the output unusable without your firm will feel like a toll booth. That is not a strong advisory relationship.

Run paid discovery as a real project

Once approved, stop treating the engagement like extended pre-sales. Create the project, assign the work, track client dependencies, and hold the review date.

Before closing it, confirm that:

• The required analysis was completed or the limitations were documented
• The promised deliverables were provided
• The client reviewed the findings and recorded questions or exceptions
• Ownership of open items is clear
• The next decision is recorded without assuming the next sale

The project closeout process should apply even if the discovery leads nowhere else. Close the engagement based on delivered evidence, not on whether a larger deal moved to proposal.

Then review the economics. Compare the scoped work with what your team actually performed. Look at delays, extra interviews, supplier effort, revisions, and senior time. Use that evidence to tighten the next scope. Do not respond to one messy engagement by creating a pricing rule that makes every future buyer pay for the exception.

Draw the line before the next request arrives

Advisor OS CRM connects organizations, contacts, deals, proposals, activities, projects, tasks, contracts, suppliers, and reporting. That gives an advisory firm a place to separate sales qualification from approved discovery work while keeping the account context connected.

The software does not decide when your thinking should be free. Your firm needs a commercial rule.

Review the last five opportunities that required substantial pre-sale work. Identify what the team produced, who used it, how much client coordination it required, and whether the prospect made any commitment before the work began. If the output had standalone value, design a paid discovery offer around that decision.

You do not need to charge for coffee and questions. You do need to stop calling client work a sales call because you hope a supplier commission will show up later.

Use the free Advisor OS agency scorecard if discovery scope, proposals, projects, and follow-up still live in different places.