Deployed Works Guide
How To Run The First Discovery Call
Use this discovery-call structure to keep the first buyer conversation anchored to the work, not a rambling sales pitch.
How To Run The First Discovery Call guide trailer
A short walkthrough for this guide will appear here.
Audience
Providers running first buyer discovery calls
Time
9 minutes
Outcome
A practical discovery call worksheet
Share this guide
PDF guide
Download and share with your friends and colleagues.
Download this guide as a PDF and share it with your friends, colleagues or team. The web guide remains the canonical version.
Related guides
Before / after transformation
Turn a role-shaped advert into a capability brief.
Use this sequence when a need starts as a job title but the real requirement is deployed capability.
Start
Role label
Senior developer, automation consultant or product manager. Useful shorthand, but not enough to brief the work.
Diagnose
Current problem
What is manual, blocked, risky, slow or unclear today? Preserve concrete workflow details.
Shape
Deployment brief
Outcome, scope, must-haves, timeline, budget signal and what good looks like.
Review
Human-reviewed shortlist
Use fit indicators and human review to start fewer, better conversations.
Guide summary
What this guide helps you do
Who it is for
Best fit readers
- Providers preparing for a first call from Deployed Works.
- Consultants and specialist teams selling capability, not generic time.
- Providers moving from profile interest to a real buyer conversation.
- Anyone who wants a calmer discovery process.
The problem
CV language hides deployable value.
A first call should help both sides decide whether there is fit and what should happen next. Providers lose trust when they dominate the call, skip proof, avoid uncertainty or end without a concrete next step.
Step by step
Build the profile around capability.
Know what the first call is for
The call is for understanding the work, checking fit, testing assumptions and choosing a next step. It is not a guarantee of deployment and not a place to force a full proposal too early.
Use a simple opening structure
Set a 30-minute agenda: restate the problem, ask questions, share relevant proof, discuss first scope or diagnostic and agree the next decision.
Ask useful questions
Ask what happens today, what needs to change, why now, who owns the decision, what access exists, what has been tried and what would make the first phase useful.
Listen for fit signals
Listen for urgency, owner clarity, realistic expectations, available access, budget signal, internal constraints and whether your capability profile matches the buyer's actual problem.
Handle uncertainty directly
If scope is unclear, say what you need to inspect. Suggest a paid diagnostic where more discovery would reduce risk for both sides.
End with a next step
Close by naming the next action: send a short proposal, ask for more information, recommend a diagnostic, introduce a better-fit provider if appropriate, or agree that now is not a fit.
Complete the worksheet
After the call, write the buyer problem, likely first phase, assumptions, risks, proof shared, open questions and agreed next step.
Example
Use this on Deployed Works
A provider uses the first call to discover that the buyer's requested build is really a data-quality problem. Instead of quoting the build, they propose a three-day diagnostic to map the workflow and decide whether automation is sensible.
Template
Discovery call worksheet
Buyer: Brief/problem: Call date: Restated problem: Desired outcome: Current workflow: Decision owner: Timeline: Budget/commercial signal: Proof shared: Fit signals: Risks: Open questions: Recommended next step: - Short proposal - Paid diagnostic - More information needed - Not a fit Follow-up date:
Common mistakes
Avoid these traps
- Talking more than the buyer.
- Pitching proof that does not relate to the brief.
- Ignoring uncertainty because it feels commercially awkward.
- Ending without a next step.
- Promising a deployment before scope is clear.
Checklist
Ready to publish when
- The call opens with an agenda.
- The provider restates the buyer problem.
- Questions cover fit, scope, proof, risk and decision process.
- Uncertainty is named.
- The next step is agreed.
FAQ
Questions this guide usually raises
Should I record the call?
Only with permission and in line with the buyer's process. Whether recorded or not, write a short follow-up so assumptions are visible.
What if the buyer asks for price on the call?
Give a range or model if you can do so responsibly. If the work is unclear, explain what needs discovery before a reliable price is possible.
How much proof should I show?
Enough to support relevance. One or two focused examples usually beat a broad portfolio tour.
Take it with you
Download and share with your friends and colleagues.
Download this guide as a PDF and share it with your friends, colleagues or team. The web guide remains the canonical version.
Share this guide
Use the canonical page link. No social scripts or tracking widgets are loaded.
Use the guide
Turn your work into a capability profile.
A provider guide for running a first buyer call that clarifies fit, scope, proof, risk and the next step.