01
Restate the problem before the solution
A useful proposal starts with what you have understood: the context, difficulties and desired outcome. Separate confirmed facts from assumptions still to be checked. The client should be able to correct this diagnosis before approving a solution.
Connect each objective to a concrete use. “Modernise the website” remains vague; making an offer easier to understand or tracking enquiries more reliably gives people a basis for discussing the work.
02
Describe what will be delivered
Present deliverables with their content, format and purpose: pages, journeys, integrations, documentation or training. For each, state how you will check that it matches the request.
Do not substitute a list of tools for a scope of work. A client should understand what they will be able to use at the end, not just the technologies used to build it.
03
Make boundaries explicit
State what is included, what is excluded and what information the client must provide. Specify who supplies content, approves stages and grants access. An unstated dependency can make the schedule difficult to meet.
Describe how an additional request will be assessed before work begins. The aim is to discuss its effect on budget and timing when it arises, rather than discovering the gap at the end of the project.
04
Explain the schedule and budget
Organise the schedule around understandable stages and approvals. Identify timing that depends on your work and timing linked to client feedback or an external service. If a date is only an estimate, present it as one.
Separate initial delivery from recurring costs, options and support after handover. The client should be able to compare offers over a consistent scope and period.
05
Support claims with evidence
Show a relevant reference if you have permission to use it. State what was actually delivered and what was measured. Work completed in another context does not guarantee the same result for a new client.
Avoid claims about conversion or margin gains without a baseline and conditions. You can commit to a method, deliverables and checks; commercial outcomes also depend on factors outside the project's control.
06
Make the next decision easy
End with a concrete decision: approve the scope, confirm assumptions or arrange a clarification meeting. A good proposal lets the client understand what they are accepting, what they must provide and what starts next.
- A restated problem and concrete objectives.
- Explicit deliverables and boundaries.
- Clear dependencies, schedule and budget.
- Real evidence and a next decision.