A Proposal Is a Sales Document, Not a Price List
The proposal that loses looks like this: a logo, a line item, a number, payment terms. The buyer compares your number to two other numbers and picks the lowest. You have handed them a spreadsheet exercise and removed every reason to choose you.
The proposal that wins does something different. It proves you understood the problem, it frames the number against the cost of not solving it, and it gives the person reading it something they can forward to their boss without having to explain it. In B2B, the individual reading your proposal usually cannot approve it alone. Write for the person who has to defend the choice internally.
Before You Write: Confirm You Understood the Need
Do not write a proposal from an RFQ email. Get a discovery conversation first, and come out of it with five things written down in the customer's own words:
- The operational problem. Not "we need 5,000 brackets" but "our line stops twice a shift because the current bracket fatigues."
- What it costs them today. Downtime hours, scrap rate, warranty claims, labor. This number is what your price gets compared against.
- The decision process. Who signs, what the approval threshold is, whether procurement or engineering owns the choice, and what the timeline is.
- The real constraints. Budget already allocated, a fiscal year deadline, an incumbent supplier with a contract that ends in April, a plant qualification requirement.
- Who else is bidding. Ask directly. Most buyers will tell you.
This is the part of the B2B sales process most vendors skip, and it is the difference between a proposal that reads as bespoke and one that reads as a template with the name changed.
The Structure of a Proposal That Wins
1. Restate the problem, in their language. One paragraph, opening the document, using the numbers they gave you. "Your assembly line loses about 90 minutes per shift to bracket replacement, at an estimated $2,400 per incident." A buyer who reads their own operation described accurately stops comparing you on price.
2. The proposed solution. What you will deliver, in specifics: quantities, materials, tolerances, finish, packaging. Include a rendering or a photo. Ambiguity here is what turns into a dispute later.
3. Scope boundaries. Explicitly list what is not included: tooling, freight, installation, qualification testing, spares. An excluded item stated up front is a professional boundary; the same item discovered after the PO is a fight.
4. Schedule with milestones. Not "8 to 10 weeks" but dated stages: drawing approval, tooling, first article, pilot lot, production. Tie payment to those milestones. Include what you need from them and by when, because the most common cause of a late delivery is a customer approval that sat for three weeks.
5. Price, structured. Not one number.
6. Evidence. Two or three sentences of relevant proof: a comparable job, a certification, a test result, a named reference willing to take a call. Keep it to half a page.
7. Terms and next step. Validity period, payment terms, warranty, and one clear action: sign here, or a call on a stated date.
Pricing That Does Work
Never present a single naked number. Three structures work, and they can be combined.
Break out the line items. Tooling, per-unit price, setup, freight, and testing shown separately. A buyer who can see the components can defend them internally and can negotiate one line instead of rejecting the total.
Give tiers. Price at three volumes, and show the per-unit price falling. This does two things: it anchors the buyer on the larger order, and it makes the economics of committing visible. Structuring those bands is its own exercise, covered in volume pricing tiers.
Offer three options, not one. A reduced-scope version, the recommended version, and a premium version with extra service or faster delivery. The question shifts from "should we buy this" to "which one," and roughly two-thirds of buyers choose the middle option. Price the options so the middle one is where you want the deal.
Set the floor before you write, not during negotiation. Know your true landed cost and the margin you need, using the math in how to price a product. Discounting under pressure without knowing the floor is how vendors win orders they lose money on.
Mistakes That Lose Proposals
- Leading with your company history. Three paragraphs about your founding before the buyer's problem appears. Move it to the end or cut it.
- Undefined scope. "Engineering support as required" is an invitation to unlimited demands or an argument.
- Optimistic dates. Quoting six weeks to look competitive when you know it is nine buys the first order and loses the second.
- No validity date. Material prices move. Put a 30-day validity on the price and a note that it is subject to raw material indexing on long-lead items.
- Ignoring procurement's paperwork. W-9, certificate of insurance, supplier registration, quality certifications. Missing documents park a signed decision for a month. If you are bidding public work, the requirements are heavier still; see selling to the government.
- Leaving revenue on the table. No spares, no service plan, no consumables line. Attaching an extended service plan at proposal time is far easier than selling it afterward.
Speed and Form Signal Competence
Turnaround is a proxy for how you will perform on the job. Aim for 48 to 72 hours on a standard quote, and if it will take longer, send a short acknowledgment with the date you will deliver. Two pages plus an appendix beats twelve pages. Send a clean PDF, named with the customer's name and a revision number, not "Quote_final_v3.pdf." Address it to a person.
After You Send It
Agree the follow-up date in the proposal itself, then hold it. If the answer is no, ask what the winning bid looked like and on what dimension you lost; buyers answer that question surprisingly often, and the answer is worth more than the order. If the answer is a smaller trial, take it and run it well, because a first order at low volume is how most long relationships start, as described in closing your first pilot.
Need a Second Set of Eyes on a Bid
Projects House supports clients quoting technical work: verifying the cost model, defining scope tightly enough to survive procurement, and putting the engineering evidence behind the number. Send us the RFQ and your draft through our contact form.