Read a sample: 1. The Proposal as a Working Agreement
A promising client conversation can end with a deceptively simple request: “Could you send me a proposal?”
You may already know what you want to recommend. The client needs help, your skills seem relevant, and the conversation felt productive. Yet when you sit down to write, the work becomes less obvious. What exactly are you offering? How much input will the client provide? What happens if feedback arrives late or the project grows? Which details must be settled before anyone can make a responsible decision?
A proposal gives those questions a place to land. It translates a conversation into a specific offer the prospective client can understand, evaluate, and respond to. It also gives you a chance to test whether the work you discussed can be delivered within the time, fee, and boundaries you intend.
That makes the proposal more than a polished sales document. It is a working agreement: a practical statement of the work you propose and the conditions under which you propose to do it. Depending on how the parties use it, a proposal may be part of a contract, accompany a separate contract, or remain an offer that has not yet been accepted. Calling it a working agreement describes its practical purpose; it does not settle its legal status.
The aim is not to cover every imaginable contingency. It is to make the important expectations visible while there is still time to discuss them.
During discovery, people naturally speak in shorthand. A client might say, “We need a better website,” while imagining a new design, new copy, photography, and help choosing a platform. You might hear the same sentence and imagine redesigning a handful of existing pages using copy the client supplies.
Neither interpretation is necessarily unreasonable. The trouble is that both can survive an enthusiastic meeting. If the proposal says only “website redesign,” the difference remains hidden.
A useful proposal replaces shorthand with choices. It might explain that the engagement covers the design of selected pages, identifies who supplies the copy and images, and states whether implementation is included. If the client expected something else, the document creates an opportunity to adjust the scope or price before work begins.
This is not merely a defensive exercise. Clear proposals help clients make decisions. A prospective client may need to compare approaches, explain the expense to a colleague, or determine whether the organization can supply the requested materials. A document that makes those decisions easier is often more persuasive than one filled with broad promises.
For the provider, clarity serves a related purpose. It reveals when a project has too many unknowns, when the requested outcome depends on work outside the proposed engagement, or when the timeline assumes a level of client availability that has not been discussed. You may still choose to take on an uncertain project, but you can describe that uncertainty rather than quietly absorbing it.
A good proposal therefore answers two sets of questions at once:
- For the client: What are you recommending, why does it address our need, what will we receive, and what will it require from us?
- For you: What have I agreed to provide, what assumptions support the offer, and where does this engagement end?
Those questions are connected. A boundary that protects your time can also help the client understand the cost of a new request. A clear client responsibility can prevent a deadline from becoming a surprise. A precise deliverable can help both sides recognize when a phase is ready for approval.
A proposal does not need to be long to be useful. It does need enough substance for the reader to make an informed decision. Most service proposals should make the following points clear.
The need and the desired outcome. Show that you understand the situation the client wants to improve. Use the client’s language where it is helpful, but avoid repeating a broad request without interpreting it. “You want a better onboarding process” says less than “New customers are receiving different setup instructions depending on who handles the account, and your team wants a consistent starting point.”
The recommended work. Explain what you will do and why that work is a reasonable response to the need. The client should be able to distinguish your recommendation from other possible projects.
The deliverables. Name what the client will receive in a form that can be recognized. A written assessment, a workshop, and an implementation plan are different deliverables, even if all support the same goal.
The timing and dependencies. Describe the expected sequence and make the client’s contributions visible. A timeline based on prompt access to documents and feedback is more useful when that condition appears on the page.
The price and payment approach. State the proposed fee or rate and explain how payment will be requested. The reader should not have to infer whether the figure covers the entire described scope.
The working boundaries. Identify relevant exclusions, feedback terms, responsibilities, and the process for handling a change. These details define the offer rather than diminish it.
The decision requested. Tell the client how to respond and what happens next. A proposal without a next step can leave an interested reader unsure whether to approve it, schedule another conversation, or wait for a separate agreement.
The relative emphasis will vary. A short coaching engagement may require less explanation of production milestones than a website project.…