Your guide to getting started with ZoomMate
Everything you need to start using ZoomMate: notes, search, workflows, and AI tools — all inside Zoom Workplace.
Select a language
A practical, step-by-step walkthrough for writing a proposal that wins clients, from research to final send.
10 min read
Published on September 10, 2026
You've had a great discovery call with a potential client, and now they've asked you to send over a proposal. That's the moment many freelancers freeze: what goes first, how long should it be, and how do you avoid sounding like any other pitch in their inbox? Learning how to write a proposal that's clear, specific, and easy to say yes to is a skill you can build with a repeatable process, not raw talent. This guide breaks that process into six concrete steps, from researching the client to pricing the work to sending a polished final document. For a broader look at proposal types and when to use each one, check out our complete guide to business proposals for small businesses.
Below, we'll walk through exactly what to research before you write a word, how to structure the proposal so a busy client keeps reading, and how to close with pricing and a call to action that moves the deal forward.
Create branded proposals clients can accept online
A strong proposal starts long before you open a blank document. If the client sent a request for proposal (RFP), a brief, or even a string of emails, reread them and pull out the key requirements, constraints, and deadlines. A freelance copywriter pitching a bakery chain, for example, should note that the client mentioned "low engagement on Instagram" twice. That's the real problem to solve, not just "we need content."
Next, figure out who actually approves the work and what budget signals they've given, even vague ones like "we're comparing a few options." Knowing the decision-maker and the real outcome they want lets you write a proposal that answers their specific situation instead of a generic pitch.
Proposals don't all follow the same blueprint, and picking the wrong structure can make a strong pitch feel off-target. A business proposal sells a product or service to a prospective client and usually leads with the problem you'll solve and the value you bring. A project proposal narrows in on scope, deliverables, and timeline for one specific piece of work, like a website redesign or a three-month content contract. Grant and research proposals work differently: they justify funding by laying out clear objectives, a methodology, and expected outcomes for a reviewer who's comparing many applicants. Sales and bid proposals respond to a specific ask or RFP, so pricing and terms usually move higher up in the document. If you're unsure how to lay out any of these formats, our proposal outline for structuring a winning proposal breaks down section order and content in more detail.
A solicited proposal answers a client's RFP or direct request, so it should mirror their language and requirements closely and address the points they raised. An unsolicited proposal is a cold pitch, meaning you need extra space upfront to establish the problem and your credibility before getting into scope and price.
A client deciding whether to keep reading usually decides quickly whether to keep reading, so the opening elements carry real weight. Start with a title page that lists the project name, the client's name and company, the date, and your contact information. This looks simple, but it signals professionalism before the client reads a single line of content, and it makes the document easy to find again once they've saved a dozen other pitches to compare.
Right after the title page comes the executive summary, a short section that restates the client's problem in their own words and previews how you'll solve it. Keep it to a few sentences, free of jargon, and specific to this client's situation rather than a generic paragraph you could paste into any pitch. If you're structuring this section for a cold outreach pitch instead of a formal document, our guide on how to write a proposal letter covers a lighter-weight version of this same opening.
Create branded proposals clients can accept online
The scope of work is the technical core of a proposal, and vague language here is where projects go sideways later. Instead of writing "redesign the website," list deliverables as specific, measurable outcomes: a five-page responsive site, three rounds of revisions, and a style guide handed off at close. A freelance web developer pitching a dentist's office might specify "one booking page integrated with the practice's existing scheduling software" rather than "add online booking."
Alongside deliverables, spell out what's explicitly out of scope, such as ongoing hosting or future content updates, so the client understands where this engagement ends. That one clause can help prevent the scope creep that quietly eats into freelancer margins on many projects.
For longer engagements, break the timeline into phases with target dates and checkpoints, like a discovery phase, a draft review, and a final delivery date. Shorter, well-defined projects can often work with a single deadline instead, as long as the client knows when to expect the finished work.
Once the scope is locked in, pricing should feel like a natural next step rather than a negotiation surprise. Present costs as a simple table or itemized list tied to the deliverables you already defined, whether you're charging a flat fee, an hourly rate, or a package price for a bundle of services. A freelance video editor might list "raw footage edit," "color correction," and "final export in three formats" as separate line items instead of one lump number, so the client sees exactly what they're paying for.
State the payment schedule clearly: a deposit before work begins, milestone payments tied to deliverables, or net-30 terms after final delivery. Note which payment methods you accept and any late-payment terms upfront, so there's no confusion once the invoice arrives. Tools like Bonsai invoicing can help turn an accepted proposal into a professional invoice without re-entering the pricing details.
A proposal without evidence is just a promise, so back up your pitch with a short case study, a client testimonial, or a relevant work sample before you close. A freelance social media manager might include a screenshot of a past client's follower growth alongside a one-line quote from that client. This proof matters most for readers who are comparing several proposals and need a reason to trust your specific claims over a competitor's.
End with one clear call to action instead of a vague sign-off. Ask the client to sign by a specific date, schedule a fifteen-minute call to confirm details, or reply with any final questions before you begin work. If you're sending the proposal as part of an email rather than a standalone document, our guide on how to write a business proposal email that gets results shows how to frame that message so the ask lands clearly.
Say a freelance copywriter has just finished the bakery chain proposal from the steps above. Instead of building the document from scratch in a word processor, she opens Bonsai proposals and starts from an industry-specific template, then swaps in the client's name, the Instagram engagement problem from her research, and the deliverables she scoped out. The template already has sections for the executive summary, scope of work, and pricing table in place, so she's filling in specifics instead of formatting from zero.
Once she sends it, Bonsai tracks when the client opens the proposal and notifies her, so she knows whether to follow up with a call instead of guessing at silence. If the bakery accepts, Bonsai generates the invoice directly from the proposal's line items, meaning the pricing she itemized in step five carries over without retyping a single number.
The client's information doesn't disappear once the proposal is sent, either. Proposals, notes, and conversations are stored on that client's record inside Bonsai CRM, organized by deal stage, so a freelancer juggling a dozen active pitches can see at a glance who's still reviewing and who's ready for a contract. Because Bonsai integrates with Zoom Meetings, meeting transcripts can sync to that same client record, so notes from a discovery or follow-up call sit next to the proposal itself instead of scattered across email threads and personal notes.
For a freelancer sending five or six proposals a month, that combination can mean less time rebuilding documents and more time on the research and writing that helps win the work.
A standard proposal format includes a title page, an executive summary, a scope of work with deliverables, a timeline, pricing and payment terms, and a clear call to action. Most proposals also include a section for terms and conditions or a signature line so the client can approve the work in the same document. This structure gives a reader a predictable path from problem to solution to next steps, which matters when they're comparing your pitch against others.
The exact order can shift depending on proposal type. A grant or research proposal often needs a methodology and evaluation section instead of a pricing table, while a sales or bid proposal responding to an RFP may need to mirror that RFP's numbering exactly.
Start by researching the client's stated problem, budget signals, and decision-maker before writing a single line. Reread any RFP, brief, or email thread and pull out the specific language the client used to describe what they need, since that language belongs in your executive summary. Skipping this step is the most common reason proposals read as generic.
Once you understand the real problem, outline the sections you'll need (title page, summary, scope, pricing, and call to action) before drafting full paragraphs. Writing from an outline keeps the proposal focused on the client's situation instead of restating your general capabilities.
Most proposals should include a title page, an executive summary that names the client's problem, a detailed scope of work, a timeline, pricing broken down by deliverable, and a specific call to action. Proof of past results, such as a testimonial or short case study, also strengthens the pitch by giving the client a reason to trust your claims.
Leaving out any of these pieces creates gaps a client has to fill in with questions, which slows down approval. A proposal that answers scope, cost, and timeline in one document gives the client the information they need to say yes without a follow-up email.
When there's no formal request for proposal, you're writing an unsolicited proposal, which means you need to spend more space upfront establishing the problem before you get into scope and pricing. Open by naming a specific pain point you've observed in the client's business, since a cold pitch has to earn attention that a solicited proposal already has.
After framing the problem, structure the rest of the document the same way you would a solicited proposal: scope of work, timeline, pricing, and a clear call to action. The main difference is tone and length in the opening section, not the overall format.
The three C's of proposal writing are clear, concise, and compelling. Clear means the client understands exactly what you're delivering and when, with no vague language around scope or deliverables. Concise means you cut anything that doesn't help the client make a decision, since long, padded proposals lose readers.
Compelling means the proposal makes a specific case for why you're the right fit for this client's problem, not a generic case for your services in general. A freelancer who applies these three tends to produce shorter, sharper proposals that are easier for a busy client to approve quickly.
Bonsai gives freelancers industry-specific proposal templates with sections for the executive summary, scope of work, and pricing already in place, so writing a proposal means filling in client-specific details instead of formatting from a blank page. Bonsai also tracks when a client opens a sent proposal and notifies the sender, which can help reduce the guesswork around whether to follow up.
When a client accepts, Bonsai generates an invoice directly from the proposal's line items, so pricing carries over without retyping numbers. Because proposals, notes, and communication history live on the client's record inside Bonsai, a freelancer managing several active pitches can see proposal status and client details inside Bonsai, while client calls continue to happen over Zoom.
Writing a strong proposal comes down to a repeatable process: research the client's real problem, choose the right structure, and spell out scope, pricing, and next steps clearly enough that saying yes feels easy. The freelancers who win more work aren't the ones with the flashiest design, they're the ones who make the client's decision simple. Once you've got the process down, tools like Bonsai proposals can help you move from template to sent document faster, so you spend more time on the research and writing that actually lands the client.
