Deployed Works Guide
For organisationsHow To Judge Price, Scope And Risk In A Provider Proposal
Read price beside scope, assumptions and risk so a cheap proposal does not become an expensive surprise.
How To Judge Price, Scope And Risk In A Provider Proposal guide trailer
A short walkthrough for this guide will appear here.
Audience
For organisations
Organisations reviewing provider proposals
Time
2 minute read
Outcome
Read price beside scope, assumptions and risk so a cheap proposal does not become an expensive surprise.
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
- Buyers comparing proposals after a first provider call.
The problem
Start with the outcome before choosing a capability route.
The cheapest proposal is not always the least risky, and the most expensive proposal is not automatically better. Buyers need to inspect what price includes, how scope is bounded, which assumptions carry risk and whether proof supports confidence.
Step by step
Build the brief around the work.
Treat price as one signal
Price only makes sense beside scope, assumptions, proof, timeline and handover.
Check scope clarity
Look for named deliverables, boundaries, out-of-scope items, access needs, review points and what would trigger a change.
Inspect risk ownership
Ask which risks sit with the buyer, which sit with the provider and which are shared.
Compare proof and confidence
Use proof to judge whether the provider has handled similar work.
Read delivery assumptions
Find the assumptions about availability, buyer feedback, system access, meetings, content, data, tools, decision speed and dependencies.
Complete the review worksheet
Summarise price, scope, proof, assumptions, missing information, key risk and recommended next step.
Example
Use this on Deployed Works
Two providers propose the same automation work. One quotes a low fixed fee but excludes data cleanup, documentation and support.
Template
Proposal review worksheet
Provider: Proposal date: Capability brief: Price: What price includes: What price excludes: Scope clarity: Deliverables: Acceptance criteria: Handover:
Common mistakes
Avoid these traps
- Choosing the lowest quote without reading exclusions.
- Comparing proposals with different scopes as if they are identical.
- Ignoring buyer-owned risks like access and decision delays.
Checklist
Ready to publish when
- Price is compared with scope and assumptions.
- Risk ownership is visible.
- Proof and proof gaps are noted.
- Missing information has been requested.
FAQ
Questions this guide usually raises
Is a higher price always safer?
No. A higher price can still hide weak scope.
When should we ask for a diagnostic?
Ask for one when the provider cannot responsibly price or scope the work without inspecting systems, workflow, data or stakeholder constraints.
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 the work into a capability brief.
Read price beside scope, assumptions and risk so a cheap proposal does not become an expensive surprise.
