Deployed Works Guide
For providersHow To Run The First Discovery Call
Use the first call to test fit, understand the work and decide whether there should be a next step.
How To Run The First Discovery Call guide trailer
A short walkthrough for this guide will appear here.
Audience
For providers
Providers running first buyer discovery calls
Time
2 minute read
Outcome
Use the first call to test fit, understand the work and decide whether there should be a next step.
Share this guide
PDF guide
Share this guide with your team.
Download the PDF for meetings or offline use. The web guide has the latest version.
Related guides
Before / after transformation
Turn a provider-shaped request into an outcome brief.
Use this sequence when a need starts as a provider label but the real requirement is a business result.
Start
Outcome
What needs to be different for the business, customer, team or workflow?
Diagnose
Current blocker
What is manual, blocked, risky, slow, expensive or unclear today?
Shape
Useful context
Success signals, non-negotiable constraints, evidence, timeline and budget signal.
Routes
Deployment routes
Derive viable approaches before asking the buyer to choose a person, tool, vendor or service.
Guide summary
What this guide helps you do
Who it is for
Best fit readers
- Providers preparing for a first call from Deployed Works.
The problem
Clear capability language makes deployment easier to assess.
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.
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.
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:
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.
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.
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.
Take it with you
Share this guide with your team.
Download the PDF for meetings or offline use. The web guide has the latest 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.
Use the first call to test fit, understand the work and decide whether there should be a next step.
