A good proposal starts before the price

A proposal should help someone make a decision. When it begins and ends with a list of services and a total, your client has to imagine what they will receive, how the work will unfold and what they need to contribute.

You can remove some of that uncertainty with a document that connects the problem, the work and the investment. This guide offers an adaptable structure for design, development, film production and other project services. You do not need every section for every engagement.

Begin with what you understood

The opening should show that you understand the project. Describe the current situation, the change the client wants and the constraints that shape the work. If you have a completed brief, use that context without copying every answer into the proposal.

Consider a studio preparing a website for a company with several services. This is an illustrative example. Visitors may struggle to find the right service and end up asking by email. That situation is a more useful starting point than a generic introduction about the importance of an online presence.

Summarise what is agreed and identify what still needs confirmation. If the client has not decided who will supply the content, do not write the scope as though that question is settled. A proposal can also make outstanding decisions visible.

Turn the objective into a specific scope

Scope describes what you will do and where that work ends. An objective such as “make the services easier to understand” needs to become recognisable work: reviewing the structure, designing service pages and preparing navigation, for example.

Separate the intended result from the things you will deliver. The result is a clearer offer; the deliverables might be a content structure, a defined set of designs and an implemented website. Mixing those levels makes it harder to determine whether the engagement is complete.

Include exclusions when they prevent a reasonable but incorrect interpretation. You do not need an endless defensive list. Clarify the areas that commonly create uncertainty, such as translations, purchased assets, ongoing maintenance or photography.

Explain services as understandable work

Each service should explain its contribution to the project. Your internal catalogue names may help your team, but the client needs to know what a line item includes. “Creative direction” may need explanation; “reviewing references, defining an approach and presenting a direction” describes concrete actions.

For hourly work, distinguish estimated time from the hourly rate. For a fixed fee, identify the scope it covers. In either case, explain what would need revisiting if the engagement changes.

If you offer alternatives, compare actual differences in scope. A more complete option might add deliverables or support. Changing only the package name does not make the choice clearer. A recommendation should also have a reason that relates to the client's objective.

Connect services to the work plan

A roadmap turns the offer into a visible journey. Phases become useful when the client can see the work happening within each one and the outcome that allows the project to continue.

Part of the plan	What the client needs to understand
Phase	What you are resolving at that point
Services	The work it includes
Deliverables	What they can review or receive
Duration	Your estimate for that part of the work
Participation	What you need from their team

A relative duration can be more honest than a fixed date when the start has not been agreed. If the plan depends on reviews or client-supplied material, explain how those affect the journey. Do not present an estimate as a confirmed calendar.

Give the investment context

The price is easier to understand after the scope and the plan. Present the currency, line items and total consistently. If there are options, make it obvious which amount belongs to each one. Identify extras and distinguish them from work that is already included.

Read the document as someone who was not part of your internal conversations. Can they identify the difference between two alternatives? Do they understand what a smaller option leaves out? Can they connect the investment to what they will receive?

Clarity does not mean adding every available detail. A short, specific description can do more than a page of internal terminology. Keep the detail that changes a decision or prevents a mistaken expectation, and remove explanations that do neither.

Choose case studies with a purpose

A case study adds context when it relates to the client's challenge. Select work because of its connection to the problem, the deliverable or the way you collaborated. Explain your role and what you actually produced.

You do not need to promise the same outcome for another project. If you did not measure a commercial impact, describe the work delivered and the decisions that made it relevant. A strong image shows quality, but it still needs enough context to be understood.

End with one clear next step

The closing should answer a simple question: what happens after reading this? The next step could be reviewing an alternative, confirming an outstanding detail or discussing the scope. Provide a contact route and avoid giving several actions equal importance.

Before sharing, open the proposal as your client would. Check the mobile layout, names, total, plan and links. Also check what stays private: your commercial notes and the full brief answers do not necessarily belong in the shared document.

A considered proposal connects all its parts. Context explains the scope, scope supports the services, the roadmap shows the journey, the investment makes the decision possible, and the closing gives the conversation somewhere to go.