Paid Discovery for a New Service Business

A prospect asks for a fixed quote. You cannot responsibly give one without reviewing their process, interviewing the people involved, or inspecting sample work. Doing all that for free turns selling into unpaid delivery. Charging for a vague conversation, however, gives the buyer little reason to say yes.

Paid discovery is a small, separately scoped engagement that helps a customer make a decision before committing to implementation. For a new service business, it is worth testing only when the customer receives useful findings they can act on without buying the next project. It is not a toll on every sales conversation.

Decide whether the uncertainty deserves paid work

Use a free fit conversation to establish the problem, decision-maker, urgency, broad budget constraints, and whether you are qualified to help. Charge for a bounded investigation when a sound recommendation needs evidence you do not yet have.

For example, an operations specialist could investigate why customer onboarding stalls before proposing a redesign. The buyer is purchasing a documented diagnosis and options, not a promise that a particular system will fix everything. Schmidt Consulting’s firsthand agency guidance similarly distinguishes research-dependent proposals from routine work that can be scoped during a sales conversation.

• Good fit: competing explanations, uncertain dependencies, accessible evidence, and a buyer with a consequential decision.
• Free scoping instead: a repeatable service with known inputs, clear deliverables, and little investigation needed.
• Decline or defer: no decision owner, no permission to inspect necessary evidence, or a request outside your competence.

Do not use discovery to disguise a sales pitch. If the deliverable is merely a quote for your own implementation, explain why the investigation itself is worth purchasing. If you cannot, improve the offer before charging.

Design an offer the customer can keep

Start with one decision, not a list of workshops. A buyer should be able to describe what changes after discovery: “We will know which onboarding failure to fix first, what evidence supports that choice, and what remains untested.”

Current provider offers illustrate different boundaries. Creative Codes’ project discovery service separates a free fit discussion from an agreed investigation. Mytnic’s discovery process allows the result to be a recommendation against new software. These are examples of how services are offered, not proof that your customers will buy or that a standard market price exists.

Copy-ready discovery offer card

Replace the bracketed fields before sending this to a prospect. This is an operating brief, not a substitute for an appropriate services agreement.

A new implementation proposal is a separate decision. Discovery does not authorize a build, and a buyer’s disagreement with your recommendation is not automatically a failure to deliver. Define acceptance around the promised evidence and analysis rather than agreement with your preferred solution.

Price the investigation without hiding founder labor

Use the following as an illustrative planning model, not a market-rate benchmark or profit forecast. Suppose a founder offers a narrowly bounded onboarding diagnostic for $1,200:

• Delivery: eight hours at an internal planning cost of $60 per hour = $480.
• Factual corrections and administration: two hours at $60 = $120.
• Acquisition effort allocated to this sale, including unsuccessful conversations: three hours at $60 = $180.
• Incremental tools and transaction expenses assumed for this example: $60.

The modeled remainder is $1,200 − $480 − $120 − $180 − $60 = $360, or 30% of the fee. That is not net profit: it excludes any fixed overhead and taxes not already included in the planning costs. Do not count the same overhead twice. An unpaid founder still consumes capacity, so removing their labor does not make the offer healthier.

If evidence collection takes four extra hours, another $240 of modeled labor leaves only $120. That exposes the real commercial risk: an apparently small engagement can become an unbounded investigation.

Estimate the offer on its own. Do not justify a loss merely by assuming every discovery buyer will purchase implementation. If you offer a future credit, model its effect on the later project too; a credit does not erase work already performed. There is no universal credit rule—Eforah’s published discovery offer, for example, explicitly describes its own continuation terms rather than an industry requirement.

Run a bounded demand test before building a delivery team

Choose a buyer group you can actually reach and a problem you can credibly investigate. Start through relevant existing relationships, referral partners, or targeted outreach. Ask about a real upcoming decision rather than whether “paid discovery sounds useful.”

Here is an illustrative founder experiment. Its thresholds are chosen planning rules, not validated industry benchmarks:

Two engagements do not prove a market or repeatable acquisition. They give you an initial basis for another bounded test. Track acquisition hours, effective delivery effort, revisions, and the buyer’s actual next decision. Implementation conversion is informative, but not a substitute for discovery’s standalone value.

Deliver through evidence gates, not founder memory

Initially, the founder may sell, investigate, and review the work. Before involving another specialist, define which analysis they can perform, the evidence they need, confidentiality boundaries, availability, and the review standard. Where work requires regulated or specialist expertise, establish the applicable qualifications before accepting it; a diagnostic label does not expand your competence.

Use this sequence: Fit reviewed → Scope agreed → Inputs ready → Investigation → Findings review → Buyer factual review → Delivered → Next decision recorded. Keep “Awaiting inputs,” “Change requested,” and “Stopped” as explicit exceptions rather than silently extending the original promise.

Example: the missing evidence exception

In a constructed scenario, the founder agrees to examine twelve recent onboarding records. The buyer supplies only three, all selected by the same manager. The founder should not call that a representative diagnosis. Record the limitation and ask the decision owner to choose: provide the agreed evidence, accept a narrower question and revised deliverable, or pause under the agreed terms.

If a second department is added, estimate the scope and timing change before doing its interviews. The existing guide to agency scope-change approvals addresses that later change-control problem. It does not replace the initial discovery offer.

Build This Business in Workhint

Once the offer has repeated successfully, its coordination rules can become a workflow. Workhint’s Workflow Engine describes requests, assignments, role-based approvals, and required details or files before work advances. Those capabilities fit the boundary between “scope sold” and “inputs ready.”

The workflow automation software solution also describes configurable forms, process stages, routing, and permissions. For this service, use those building blocks to organize evidence collection and human decisions—not to claim that software performs the diagnosis or guarantees its accuracy.

Adapt this configuration brief, then verify the configured behavior with a sample engagement:

Build a paid-discovery operating workflow for a founder-led onboarding diagnostic service. Give customer, founder, assigned analyst, and administrator roles appropriate visibility. Capture the decision question, buyer approver, process owner, evidence sample, exclusions, delivery date, agreed fee, revision allowance, and required inputs. Onboard an analyst only after capability, confidentiality, availability, and assignment scope are reviewed. Match assignments manually by competence and availability.

Use Fit reviewed, Scope agreed, Inputs ready, Investigation, Findings review, Buyer factual review, Delivered, and Next decision recorded stages. Require scope approval and required inputs before investigation. Collect each finding’s source, limitation, recommendation, and unresolved question. Route missing inputs to the process owner, scope changes to the buyer approver, and disputed findings to founder review. Do not treat a delivery approval as permission to implement. Keep payment collection outside this initial configuration; have the administrator record confirmation from the agreed invoicing process. Let customers supply inputs and review findings, analysts access only assigned work, and administrators manage exceptions. Record delivery effort, input delays, revision count, acceptance, and the next decision for manual review. The outcome is an evidence-backed recommendation, not an automatically approved build.

FAQ

Is paid discovery the same as a consultation?

Not necessarily. A conversation can be part of it, but the offer should specify what evidence will be examined and what useful output the buyer retains. A routine fit conversation usually does not need a separate diagnostic engagement.

Must the discovery fee be credited toward implementation?

No single commercial rule fits every offer. State your policy before purchase, and check that both engagements remain viable if a credit is offered. Avoid implying that the customer must buy implementation to receive the promised findings.

What if discovery shows the project should stop?

That can be a useful outcome when the agreed service was to investigate and recommend. Deliver the evidence, explain limitations, and record why proceeding is not justified. Do not invent a build simply to protect the next sale.

When should a founder add delivery specialists?

After the scope, evidence standard, review method, and economics recur across completed engagements. Add a specialist for a defined capability gap or capacity need, not merely to make the business look larger. The broader operations consulting launch guide covers the surrounding firm model.

Verdict: conditional, with a clear stop rule

Paid discovery is a Conditional offer for a new service business. It is strongest when uncertainty matters, evidence is accessible, the founder has relevant judgment, and the customer keeps a decision-ready asset. It is weak when routine scoping is dressed up as research, the work depends on unavailable records, or the fee cannot cover investigation and acquisition effort.

Validate the diagnostic as a real service first. Keep the boundary small, make the evidence portable, measure the hidden labor, and allow “do not proceed” to be an honest result.