A practical, step-by-step guide to writing a proposal to provide a good or service that clients actually say yes to.
11 min read
Published on November 13, 2026
A promising client call ends with "send me something in writing," and suddenly you're staring at a blank document wondering where to start. Writing a proposal to provide a good or service is the step that turns a good conversation into a signed deal, but only if it clearly spells out what you're offering, when you'll deliver it, and what it costs. Too many freelancers and small business owners either over-explain their process or jump straight to a price tag, leaving the client without enough context to say yes. This guide breaks the process into seven concrete steps, from researching the client's needs to following up after you hit send, so you build a proposal that reads as clear and professional rather than rushed. For a broader look at proposal strategy across industries, see our complete guide to business proposals for small businesses.
Below, you'll find the exact structure, language, and sequencing that helps a proposal move from "we'll think about it" to a signature, along with a real example of how the pieces fit together.
Create branded proposals clients can accept online
A proposal to provide a good or service is a formal document that outlines what you'll deliver, how you'll deliver it, and what it will cost. It answers the client's core question, "why should I hire you," by laying out your understanding of their problem, your proposed solution, a timeline, and pricing in a single, structured document. If you're unsure whether your draft covers the right ground, it helps to see what a business proposal looks like before you start writing.
Not every proposal looks the same, and matching the format to the situation makes a difference in how professional it reads.
A solicited proposal is written in response to a client's direct request, such as an RFP (request for proposal) or a simple "send me a quote" after a call. An unsolicited proposal is one you initiate yourself, usually to pitch a prospect who hasn't asked for one yet. Formality varies too: a formal proposal tends to follow a strict, multi-section structure, while an informal proposal might be a shorter, conversational document or email for a smaller job.
| Type | Trigger | Formality | Typical use case |
|---|---|---|---|
| Solicited | Client requests it (RFP, verbal ask) | Usually formal | Competitive bids, larger contracts |
| Unsolicited | You initiate it | Often informal | Cold outreach, upselling existing clients |
Before you open a blank document, revisit everything the client has already told you. Reread the RFP, the discovery call notes, or the email where they described their problem, and pull out any stated requirements, deadlines, or budget signals so your proposal reflects their actual words back to them. A proposal that echoes the client's own language proves you listened, which matters more than polished formatting.
Next, define what's included and excluded before you start writing. A freelance web developer quoting a five-page site should decide upfront whether copywriting or stock photo licensing is part of the deal, since vague scope invites scope creep later. Finally, confirm who actually reads and approves the proposal. A proposal addressed to the marketing coordinator reads differently than one written for the founder who signs the check.
A proposal that jumps between ideas forces the client to hunt for the information they need, which slows down approval or gives them a reason to set it aside. The fix is a predictable skeleton: each section answers one question, in an order that builds from context to commitment. For a deeper breakdown of section-by-section formatting, see this guide on how to structure a winning proposal.
Order matters as much as content. Lead with the client's problem and your proposed value before you ever mention price, so the cost feels justified rather than arbitrary.
The executive summary is the first thing a client reads and often the only section a busy decision-maker reads in full, so it needs to preview your value in two to three sentences: who you are, what you're proposing, and the outcome the client can expect. Skip generic openers like "thank you for the opportunity to submit this proposal," which tell the client nothing and waste the section's best real estate. If you want a closer look at framing this section for maximum impact, this guide on how to write an executive summary that wins clients breaks down the format further.
Right after the summary, the problem statement should mirror the client's own language back to them almost verbatim. If a bakery owner told you "our online orders keep getting lost between three different apps," restate that exact frustration rather than rewriting it as "streamline your e-commerce operations." Clients often recognize their own words quickly, and that recognition can help build trust before you've proposed a single deliverable.
Create branded proposals clients can accept online
Once the client understands their problem and your proposed fix, they need to see exactly what they're getting. Vague language like "ongoing design support" leaves room for misread expectations, so spell out deliverables in specific, measurable terms: number of pages, revision rounds, file formats, or units delivered. A freelance web designer proposing a three-page site should state that the package includes a home page, an about page, a contact page, and two rounds of revisions, not an open-ended promise to "design a website."
Attach a realistic timeline to those deliverables so the client can see when each piece arrives, not just the final due date.
By the time a client reaches the pricing section, they should already understand the value on offer, which is why cost comes after deliverables and timeline, not before. Choose a format that matches the project: a flat fee works for a single, well-defined deliverable, while a package or itemized breakdown suits projects with multiple components, since it shows the client exactly what each line covers. If you're pricing a smaller, one-off job, this guide on how to send a quote walks through a simpler format.
Whatever format you choose, state payment terms without ambiguity: deposit amount, milestone payments, and due dates, so nothing is left for the client to guess or negotiate after signing.
A proposal without terms leaves too much open to interpretation once work begins. Add a short terms section covering how scope changes are handled, your cancellation policy, and how long the pricing stays valid, often 30 days, so clients know the quote isn't open-ended.
Make approval as easy as possible for the client. A proposal that requires an e-signature, rather than a reply email confirming agreement, removes friction and creates a clear record of acceptance; tools like Bonsai contracts support this kind of signing flow directly on the document. Send the finished proposal as a shareable link or through email instead of a static PDF attachment, since a link lets you track whether the client has opened it.
Sending the proposal isn't the finish line. If a client hasn't responded within two or three business days, a short, low-pressure check-in email keeps you top of mind without seeming pushy. Ask a simple question, like whether they have any questions about scope or pricing, rather than a generic "just following up."
Tracking whether the proposal was actually opened helps you gauge real interest versus silence caused by a busy inbox. If a client opened it twice but hasn't replied, that's a signal to follow up with specifics, not just a nudge. Have a plan ready for objections too: if they push back on price or ask for revisions, treat that as a negotiation step rather than a rejection. For more on turning these moments into signed work, see this guide on how to turn more leads into paying clients.
A freelance web designer quoting the three-page site from the example above doesn't need to rebuild a proposal template from scratch every time a new lead comes in. Bonsai proposals offers industry-specific templates that already follow the structure this guide walks through: problem statement, deliverables, timeline, and pricing in one document, so the designer can drop in the client's details and send a $3,200 proposal without having to format a new file from scratch.
Once that proposal is out the door, Bonsai's open and view tracking notifies the sender when the client opens it, which can help answer the question from step 7 by showing whether a follow-up may be worth sending. If a bakery owner opens the proposal twice in one afternoon but hasn't replied, that pattern is visible directly in Bonsai rather than left to assumption. And when the client does accept, Bonsai generates the invoice directly from the proposal's line items, so a consultant who quoted a $5,000 project in three milestones doesn't have to re-enter pricing into a separate Bonsai invoicing document; the numbers carry over automatically.
For proposals that came out of a discovery call, Zoom meeting transcripts can sync to the client's record in Bonsai, so the exact language a client used to describe their problem (like the bakery owner's comment about orders getting lost between apps) stays attached to that client's file for reference when drafting the problem statement. Between the proposal template, the acceptance-to-invoice handoff, and the synced meeting notes, the steps in this guide become fewer separate tasks and more of one continuous record tied to a single client.
Proposals generally fall into two categories: solicited and unsolicited. A solicited proposal responds to a direct request from the client, such as a formal RFP (request for proposal) or a simple "send me a quote" after a call, and it typically follows a more formal structure. An unsolicited proposal is one you initiate yourself to pitch a prospect who hasn't asked for one, and it's often shorter and more conversational.
The right type depends on where the relationship stands. A freelance copywriter responding to a company's published RFP would send a solicited, formally structured proposal, while the same copywriter reaching out cold to a local business owner would likely send a shorter, unsolicited pitch that reads more like a tailored offer than a formal bid.
Most proposals need seven core parts: a brief intro with the client's name and date, a problem statement that reflects the client's own words, a proposed solution, a clear list of deliverables, a timeline with milestones, transparent pricing, and terms covering payment and scope. Leaving out any one of these sections tends to create confusion or delay approval, since the client is left to guess at missing details like payment timing or what happens if the scope changes.
Order matters as much as content. Placing the problem statement and proposed solution before the pricing section gives the client context for the cost, so a $4,000 rebrand quote feels justified rather than arbitrary when it follows a clear explanation of what that fee covers.
A concrete example: a freelance web designer proposing a three-page website for a bakery would open with a short summary of the bakery's problem, such as online orders getting lost between multiple apps, then describe the solution as a single integrated site with a home page, an about page, and a contact page. The deliverables section would list two rounds of revisions, the timeline would show wireframes due in week one and a final launch-ready site by week three, and the pricing section would state a flat fee of $3,200 with a 50% deposit due upfront.
This structure works because each section answers one specific question for the client: what's wrong, what's being fixed, what they'll receive, when they'll receive it, and what it costs. A proposal missing any of these pieces, like a timeline without milestones or a price with no payment terms, leaves room for the client to hesitate rather than sign.
Bonsai provides industry-specific proposal templates that already follow a structure similar to the one covered in this guide, letting a freelancer or small agency fill in client-specific details rather than build a document from scratch for every new lead. Once a proposal is sent, open and view tracking notifies the sender when the client opens it, which can help reduce the guesswork around whether a follow-up is warranted.
When a client accepts, Bonsai generates the invoice directly from the proposal's line items, so pricing doesn't need to be re-entered into a separate document. Zoom meeting transcripts can also sync to the client's record in Bonsai, keeping the exact language a client used to describe their problem on file for reference when drafting future proposal sections.
Writing a proposal to provide a good or service comes down to sequencing: understand the client's problem, structure the document so it builds toward price rather than leading with it, and make approval as frictionless as possible once you hit send. Get those seven steps right and the proposal itself does the selling, whether it's a $3,200 website build or a multi-milestone consulting engagement. As you compare tools to speed up this process, Bonsai's proposal templates and tracking features are worth a look for keeping the proposal, invoice, and client record connected in Bonsai while meetings continue in Zoom.
11 min read
Learn how to make an invoice for graphic design work, with clear steps for project details, pricing, and payment terms freelancers use.
10 min read
Learn how to build a client welcome packet that sets clear expectations, saves time, and makes a strong first impression on new clients.
11 min read
Learn how to accept payments online with ease and security. Discover methods that save time and help grow your business, including options from Bonsai.
