How to write a formal proposal that wins clients

A vague, casual pitch rarely wins over a corporate client who needs to justify the spend to a finance committee. That's where a formal proposal comes in: a structured, professional document that lays out the problem, your solution, pricing, and terms in a way that builds trust before a signature ever happens. Freelancers and small agencies often lose deals not because their work is weaker, but because their proposal looks like an afterthought next to a more polished competitor. This guide breaks down exactly how to write a formal proposal that reads as credible and client-ready, from the research phase through final delivery. For a broader look at proposal types and when to use each one, check out this complete guide to business proposals.

Below, we'll walk through six concrete steps: researching the client, structuring the document, writing a strong executive summary, detailing scope and pricing, nailing down terms and timelines, and formatting the final draft for signature.

Create branded proposals clients can accept online

Get started

What is a formal proposal?

A formal proposal is a structured, written document that presents your solution, pricing, and terms in a set format designed for scrutiny, not just a quick read. Unlike a casual pitch or a two-line email, a formal proposal is longer, more detailed, and built to stand on its own when it lands in front of people who weren't part of the original conversation. If you're unsure what a business proposal looks like once it's fully assembled, this breakdown of what a business proposal looks like is a useful reference point.

Formality tends to matter most when multiple decision-makers, procurement processes, or larger contract values are involved. Several sub-types share the same backbone: solicited proposals written in response to a direct request, unsolicited proposals sent proactively, formal responses to a request for proposal (RFP), and renewal proposals for existing clients. Each one still needs the same structured, professional treatment.

Step 1: research the client and define the problem

Before drafting a single line, read every piece of information the client has already given you. Go back through the RFP, the intake brief, or your notes from the discovery call and pull out stated goals, budget signals, and any constraints on timeline or scope. Skimming this material leads to a generic proposal; rereading it closely is what lets you speak directly to the client's actual situation.

Next, name the specific problem the client wants solved, not just the broad service category they're shopping for. A bakery asking for "marketing help" might really need foot traffic on slow weekdays, which is a different proposal than one built around general brand awareness. It also helps to identify who will actually read the document. A founder might care most about speed and expertise, while a procurement team on a finance committee will scrutinize cost and risk first. Matching the proposal's tone and formality to the client's industry, whether that's a buttoned-up RFP process or a more relaxed small-business relationship, signals that you understand how they work before you've done any of the work itself.

Step 2: choose a clear formal proposal structure

A formal proposal needs a consistent structure so reviewers can find what they're looking for without hunting through paragraphs. At minimum, plan for a cover page, an executive summary, a problem statement, your proposed solution, an itemized scope of work, pricing, a timeline, terms and conditions, and a signature block. For a closer look at how these pieces fit together section by section, this proposal outline guide walks through the full structure.

That consistency matters most when a proposal passes through multiple hands. A finance committee member skimming for cost, a department head checking scope, and a procurement officer confirming terms should each be able to jump straight to their section. But the structure isn't just organizational, it's persuasive: each section should build logically toward the same conclusion, which is that signing is the obvious next step.

While the backbone stays consistent, tone and framing shift depending on how the proposal originated.

Step 3: write an executive summary that hooks the reader

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 earn attention in two to three sentences. State the client's problem in their own terms, name your proposed solution, and summarize the core value of working together, without repeating the whole proposal in miniature. For a deeper walkthrough of this section, see this guide to writing an executive summary proposal that holds up on its own.

Write this section last, even though it appears first. Only after drafting the scope, pricing, and terms will you know exactly what to summarize. Keep the tone formal but specific: reference the bakery's slow Tuesday afternoons or the client's Q3 launch deadline, not generic industry language. Describe what the engagement will do, not outcomes you can't guarantee.

Create branded proposals clients can accept online

Get started

Step 4: detail scope, deliverables, and pricing

A vague list of services invites questions and, eventually, scope disputes. Break the work into specific deliverables with dates or milestones attached, so the client can see exactly what they're paying for and when they'll receive it. A freelance consultant scoping a $6,000, three-month engagement might split the work into a discovery phase, a strategy phase, and an implementation phase, each with its own line item and price rather than a single lump sum labeled "consulting services."

Itemized pricing builds trust because it shows your math instead of asking the client to take a number on faith. If your pricing approach leans closer to a fixed-cost estimate than a full proposal, this guide to writing a formal quote covers the format in more detail. Whichever structure you use, state plainly what's included and what's explicitly out of scope. That one paragraph prevents most disputes before they start.

Step 5: add terms, timeline, and next steps

Once scope and pricing are locked in, the proposal needs a timeline that lets the client visualize how the engagement actually unfolds. Break the work into phases with target dates, so a three-month project reads as discovery in week one, strategy by week three, and delivery by week twelve, rather than one vague end date.

Payment terms belong in this section too: state the deposit amount, the invoicing cadence, and exactly when payments are due. A formal proposal that gets accepted often becomes the basis for a signed agreement, and this guide to writing a contract proposal covers how that transition typically works. Close with a specific next step, such as signing by a stated date or scheduling a kickoff call, so the client knows exactly how to move forward.

Step 6: format, proofread, and send for signature

Before sending, apply consistent branding throughout the document: the same logo, fonts, and color palette across each page. A proposal that looks assembled from mismatched templates undercuts the professionalism the rest of the document worked to establish.

Proofread for more than typos. Check that each client name, date, and dollar figure is correct, and that the tone stays formal and consistent from the executive summary through the terms section. Small inconsistencies, like referencing the wrong company name from a previous proposal, are an easy way to lose credibility fast.

Send the final version as a PDF or a shareable link rather than an editable file, so formatting stays intact no matter what device the client opens it on. If possible, track whether the client has opened or viewed the proposal, so follow-up timing is based on activity rather than a guess.

How Bonsai helps with formal proposals

Writing a formal proposal from a blank page is where most freelancers lose momentum, and re-keying the same scope and pricing details into an invoice later is where they lose time. Bonsai proposals start from industry-specific templates, so a freelance consultant responding to an RFP can pull a structure that already includes a cover section, scope breakdown, and terms, then adjust it to the client's language instead of building the format from scratch.

Once the proposal is out, Bonsai tracks when the client opens it and notifies the sender, which turns follow-up timing into something based on activity instead of a guess about whether the finance committee has even seen the document yet. Line items support per-item tax rates and fixed or percentage discounts, so a $6,000 three-phase engagement can show discovery, strategy, and implementation as separate priced lines rather than one lump total the client has to take on faith.

The bigger time savings can show up after the client signs. When a proposal is accepted, Bonsai generates the invoice directly from the proposal's line items, so a design agency that itemized a $9,500 project doesn't have to retype scope and pricing into a separate Bonsai invoicing template. That invoice inherits the same branding and numbers the client already reviewed and approved.

Because Bonsai integrates with Zoom Meetings, transcripts from a discovery or kickoff call can sync to the client's record as notes, so the specifics a client mentioned about their timeline or budget stay attached to their file instead of buried in a call you half-remember when it's time to draft the executive summary. For a solo consultant juggling several active proposals at once, that record helps keep research notes, the sent proposal, and the resulting invoice connected to the same client, so details stay organized even as you work across Bonsai and Zoom.

FAQ

Q1: What is a formal proposal?

A formal proposal is a structured, written document that lays out a client's problem, your proposed solution, pricing, and terms in a set format built to withstand scrutiny from multiple readers. It differs from a casual pitch or a short email in both length and rigor, since it's designed to stand on its own even when it reaches people who weren't part of the original conversation, such as a procurement officer or finance committee.

Formality typically matters most when a deal involves multiple decision-makers, a procurement process, or a larger contract value. Common variations include solicited proposals written in response to a direct request, unsolicited proposals sent proactively, formal RFP responses, and renewal proposals for existing clients, but each of them shares the same structured, professional backbone.

Q2: What are the main types of formal proposals?

The four main types of formal proposals are solicited, unsolicited, RFP responses, and renewal proposals. A solicited proposal answers a direct request from a client, an unsolicited proposal is sent proactively to make a case the client hasn't asked for yet, an RFP response follows a formal request for proposal from a procurement process, and a renewal proposal extends an existing client relationship.

Each type calls for a different tone even though the structure stays consistent. A solicited proposal can be direct and responsive to stated requirements, an unsolicited one usually needs to educate the reader on the problem before pitching a fix, an RFP response has to be highly structured and compliance-focused, and a renewal proposal can be warmer and reference the history and results already delivered.

Q3: What format should a formal proposal follow?

A formal proposal should follow a consistent structure that includes a cover page, an executive summary, a problem statement, a proposed solution, an itemized scope of work, pricing, a timeline, terms and conditions, and a signature block. This order lets different readers, such as a department head checking scope or a finance committee member skimming for cost, find their section without hunting through unrelated paragraphs.

Consistent branding matters as much as section order: the same logo, fonts, and color palette should appear on every page so the document reads as one cohesive piece rather than a patchwork of templates. Sending the final version as a PDF or a shareable link, instead of an editable file, also helps keep that formatting intact regardless of the device the client opens it on.

Q4: How long should a formal proposal be?

There's no fixed page count for a formal proposal; length should scale with the complexity of the engagement and the amount of detail a client's decision-makers need to justify the spend. A straightforward, single-phase project might only need a few pages, while a multi-phase engagement with itemized deliverables, a detailed timeline, and formal terms can run considerably longer.

What matters more than length is that every section earns its place. A proposal padded with generic industry language or repeated points reads as filler, while one that stays specific about the client's problem, deliverables, and pricing tends to feel appropriately thorough without dragging on.

Q5: How does Bonsai help with formal proposals?

Bonsai helps with formal proposals by starting from industry-specific templates that already include a structured cover section, scope breakdown, and terms, so a freelancer or small agency isn't building the format from a blank page for each new client. Once sent, Bonsai tracks when a client opens the proposal and notifies the sender, which turns follow-up timing into something based on actual activity instead of a guess.

Bonsai also carries proposal details forward instead of requiring them to be re-entered. When a client accepts a proposal, Bonsai generates the invoice directly from the proposal's line items, and because Bonsai integrates with Zoom Meetings, transcripts from a discovery or kickoff call can sync to the client's record as notes, keeping budget and timeline details attached to that client's file for future proposals.

A formal proposal wins clients not because it sounds impressive, but because it makes the decision easy for each person who has to sign off on it, from the founder to the finance committee. Nail the research, structure the document consistently, and price the scope in a way that shows your math, and the proposal does most of the persuading before the call ever happens. Bonsai can carry that structure, tracking, and pricing detail forward from the first draft to the signed invoice, so the next formal proposal starts from a template instead of a blank page.