Pro free for 30 days.No card.Start free →

Business proposal that gets signed: how to write one

Turn interest into a signature. This guide covers when you need a full proposal, the structure that works, how to price with options, how to make signing simple, and the mistakes that leave proposals unanswered.

By WorkBOS Content Desk6 min read
Agreement document with a pen ready for signing on a desk (Photo by jarmoluk on Pixabay)
Photo: jarmoluk / Pixabay

A proposal is where interest turns into a decision. Yet many small businesses treat it as paperwork: a template with a price on the bottom, emailed with a hopeful line and then forgotten. The result is a pile of "we'll think about it" replies.

A good proposal does something different. It shows the client you understood their problem, lays out a clear way to solve it, makes the price easy to judge and tells them exactly how to say yes. This guide covers the structure, the writing and the sending, so your next proposal is easier to sign.

Decide whether you need a proposal at all

Xero's guide to writing a business proposal suggests a full proposal fits complex projects, formal requests for proposals, competitive bids, or situations where the client needs internal approval. A simple quote may be enough for well-defined work with an established client, and when the scope is unclear you should talk first.

That last point is worth repeating. If you cannot describe the client's problem in two sentences, you are not ready to write. Another call is cheaper than a long document that misses.

The structure that works

Xero boils a proposal down to three Ps: the problem, your proposed solution and the pricing. Salesforce's small business proposal guide breaks it into similar parts. Combined, they give you a reliable outline.

| Section | What it does | |---|---| | Cover page | Business name, contact details, date and purpose. | | Executive summary | The problem, your solution and the benefit, in a few lines. | | Problem statement | The client's pain points, in their words and with their numbers. | | Solution and plan | What you will do, with milestones, timeline and deliverables. | | Pricing | An itemized breakdown, ideally with options. | | Proof | Case studies, testimonials or relevant experience. | | Terms and acceptance | Scope, payment schedule, deadlines and a place to sign. | | Next step | One clear action and a response date. |

Lead with the client, not yourself

Xero lists focusing on yourself as a common mistake: lead with the client's problem rather than your company history. Open with a short summary that restates what they told you. Clients read that first, and it shows you listened.

Make the solution concrete

Describe what happens, in what order and by when. Include milestones, who is responsible for what, and anything you need from the client. Salesforce points to timelines, milestones and deliverables as the core of the solution section.

Quantify the value where you can

Xero recommends using real data, such as performance figures, quantified savings and realistic milestones. If you do not have numbers, use the client's own: "You told us you lose about five hours a week to manual booking. This removes most of that."

Pricing that is easy to say yes to

Hiding or blurring the price creates distrust and slows decisions, according to Xero's list of mistakes. Be clear instead.

  • Itemize. Show what each part costs so the client can see what they are paying for.
  • Offer options. Xero suggests tiered pricing with high, mid and low options in a table. A choice between yes and yes, rather than yes and no, often leads to a faster decision.
  • State what is not included. This prevents scope disputes later.
  • Show payment terms. Say when deposits and invoices are due.
  • Set an expiry date. Prices that are valid for 30 days give the client a gentle reason to decide.

If you are unsure whether a price covers your costs, our cost-benefit check can help you test it before you send.

Writing tips that make a difference

  • Use plain language. Xero recommends short sentences, roughly 15 to 20 words, and matching the length to the complexity of the project.
  • Use visuals on purpose. A timeline, comparison table or simple flowchart helps, as long as it adds meaning.
  • Add proof, with permission. Case studies and testimonials build trust, but get permission before sharing client information.
  • Be accurate. Check names, numbers and prices. Salesforce suggests having a colleague or mentor review it before sending.
  • Make it readable on a phone. Salesforce recommends a responsive layout and readable text size for mobile readers.

Make signing easy

A proposal that is hard to sign gets postponed. Cornell Law School's overview of contracts explains that a binding agreement rests on an offer and an acceptance, along with an exchange of value, capacity and a lawful purpose. In practice, your proposal is the offer, and your job is to make acceptance simple and unambiguous.

Include acceptance terms

Salesforce's guide includes terms and acceptance, such as payment schedules, deadlines, scope and a signature space. Spell out what the client is agreeing to, what happens next, and what you will do on signing. This is general information, not legal advice. Ask a lawyer to review your standard terms.

Offer an electronic signature

Let the client sign on a phone in a minute. Every extra step, such as printing and scanning, gives them a reason to delay. Track who has opened and signed it so you know when to follow up.

Send it at the right time

Salesforce suggests sending the proposal within 24 hours while the lead is warm, and setting a specific follow-up date and time. Tell the client in the covering note when you will check in. Our guide to follow-up that wins deals without nagging gives a simple schedule.

Proposal checklist

  1. I can state the client's problem in two sentences.
  2. The summary restates their goals in their words.
  3. The plan has milestones, dates and owners.
  4. Pricing is itemized, with options if possible.
  5. Exclusions and assumptions are stated.
  6. Terms, payment schedule and an expiry date are included.
  7. Someone else has proofread it.
  8. There is a signing step that takes under two minutes.
  9. A follow-up date is in my calendar.
  10. The proposal is stored with the deal.

Common mistakes

  • Being generic. Xero warns against sending a template unchanged. Customize each one.
  • Leaving out a call to action. If the next step is not explicit, nothing happens.
  • Overloading the document. Include enough to persuade without burying the key points.
  • Hiding the price. Vague costs slow decisions.
  • Skipping proofreading. Errors weaken credibility.
  • Sending late. Momentum fades after the first day or two.
  • Going silent afterward. Plan your follow-up before you send.

Proposals and signing in WorkBOS

In WorkBOS, a proposal can live with its deal in the CRM, so notes, contacts and history stay in one place. Document signing lets clients sign electronically, the branded client portal gives them a single page for their documents, and a signed deal can lead into a project and an invoice. Automations can remind you to follow up, and AI agents can help draft text, with a person approving every action. Explore the features page, the docs, the pricing page or the Academy. To see how the sales stages fit together, read defining sales pipeline stages, and for what happens after the yes, see client onboarding.

Frequently asked questions

Q: How long should a proposal be? A: As long as the project needs and no longer. Xero advises matching length to complexity: a few pages for a simple job, more for a complicated one.

Q: Should I include my price in the first proposal? A: Yes. Clear pricing builds trust, and Xero lists hiding it as a mistake. Offer options if you can.

Q: What is the difference between a quote and a proposal? A: A quote states a price for defined work. A proposal also explains the problem, your approach and why you are the right choice, which suits complex or competitive situations.

Q: How soon should I send a proposal after a meeting? A: Salesforce suggests within 24 hours, while the lead is warm. If you need longer, tell the client when to expect it.

Q: Is an e-signature enough to make a proposal binding? A: Often yes, but the rules depend on the contract and your state. Cornell's overview notes some contracts must be in writing. Check with a lawyer for important agreements.

Sources are linked in the text above: Xero, Salesforce, Cornell Law School.

Run it all from one place

Projects, clients, finance, people and AI employees in one system. Start free, no card needed.

Start free →