Deployed Works Guide
For providersHow To Write A Short Proposal After The First Call
Write a brief proposal that confirms the problem, first phase, outputs, price and boundaries.
How To Write A Short Proposal After The First Call guide trailer
A short walkthrough for this guide will appear here.
Audience
For providers
Providers writing proposals after a first call
Time
2 minute read
Outcome
Write a brief proposal that confirms the problem, first phase, outputs, price and boundaries.
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 following up after a first discovery call.
The problem
Clear capability language makes deployment easier to assess.
Providers often overbuild proposals because they want to look professional. Buyers usually need something clearer: restated problem, first phase, outputs, boundaries, price, assumptions, risks and the next decision.
Step by step
Build the profile around capability.
Keep it short
Aim for one to three pages.
Restate the problem
Start with the buyer's situation in their language.
Define the first phase
Name whether the next step is a paid diagnostic, scoped delivery, audit, implementation, advisory phase or handover-focused work.
Describe outputs and boundaries
List what the buyer receives, what is out of scope, what access you need and what assumptions affect delivery.
State price and assumptions
Give a price, range or commercial model that matches the scope.
Use the proposal template
Close with the decision required: approve, clarify, run a diagnostic, change scope or pause.
Example
Use this on Deployed Works
After a first call, a provider sends a two-page proposal for a five-day diagnostic. It restates the workflow problem, lists outputs, includes the fixed fee, names access needs and says a build proposal will only follow if the diagnostic shows automation is sensible.
Template
Short provider proposal template
Proposal for: Buyer: Provider: Date: 1. Problem as understood 2. Recommended first phase - Diagnostic / scoped delivery / advisory / handover: - Why this is the right first step: 3. Outputs
Common mistakes
Avoid these traps
- Writing a long proposal before the buyer has agreed the first phase.
- Hiding assumptions that change price or scope.
- Skipping exclusions because they feel negative.
Checklist
Ready to publish when
- The proposal is short.
- The buyer problem is restated.
- The first phase is clear.
- Outputs, boundaries and exclusions are visible.
FAQ
Questions this guide usually raises
Should I send a deck?
Only if it helps the buyer decide. A concise written proposal is usually better for a first deployment because it makes scope and assumptions easier to inspect.
Can I propose a diagnostic instead of delivery?
Yes. If the work is not clear enough to price responsibly, propose a paid diagnostic and explain what it will produce.
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.
Write a brief proposal that confirms the problem, first phase, outputs, price and boundaries.
