Proposal Writing · Proposal Presentation
Proposal & Presentation
What is proposal writing?
- A document that sets out the solution to a customer’s needs and the terms
- Structure it as problem → solution → evidence, not company boasting
- The final hurdle in winning B2B deals is the proposal presentation
Start writing a proposal and you see exactly what sales has been collecting all along. Without things like the client’s org chart, when budgets get released, the approval chain, and the name of the project that fell through last year, the first three pages can’t be filled. What stalls a proposal is not writing skill but gaps in information. That is why the proposal kickoff day is less the day writing begins than the day the information sales has gathered gets audited. With enough information, the outline takes half a day.
A proposal is different from a quotation or a company profile. A quotation states terms and a company profile talks about you, but a proposal is a document that gives the customer’s problem back to them in their own language. Public-sector and large-corporate bids usually split scoring roughly 80/20 between technical and price evaluation, so even a 10% price cut often can’t make up a 2–3 point gap in technical score. And if you miss any format, length, or submission document the RFP requires, you are disqualified on formal requirements right away, regardless of content, so it is safest to build a requirements compliance matrix the moment you start.
A proposal presentation is not a summary of the proposal. Five to seven evaluators score it on a 10–15 minute presentation and 5–10 minutes of Q&A, and the scoring sheet items often look different from our proposal’s table of contents. Rather than skimming 40 slides, you score better if you land 'why us' in one sentence within the first 3 minutes. Q&A often decides the outcome, so draft 20 likely questions and rehearse with an answerer assigned to each question in advance.
The most common misstep in practice is starting the proposal three days before the deadline. From that point, people open an old proposal and just swap the client name, and a previous client’s name left somewhere in the body can catch an evaluator’s eye. This really happens. The attitude that 'the proposal is the proposal team’s job' is also risky. If sales hands over a task without passing along information, the proposal turns generic, and generic proposals get dragged into price competition. Moving on after a loss without asking why you were eliminated is costly too. A single scoring sheet can change your scoring strategy for the next proposal.
John KimAuthor of B2B Marketing Design and CEO of Nanum Consulting
Jaehyuk ParkHands-on instructor in B2B technical sales and AI-driven sales strategyIt developed alongside competitive bidding systems in government and business, and proposal methodologies such as Shipley have become global standards.
Let’s walk through a hypothetical case. Company A, an auto parts manufacturer with 1,200 employees, issued a call for a “frontline leadership training” project. The budget was KRW 300 (≈ US$1) million, four vendors were competing, and proposals were due in 12 days. Company A had run similar training for three years, and the reaction on the floor was “this again?”
- Two days after the RFP was posted, the sales team lead met a manager on Company A’s talent development team and heard, "Satisfaction is 4.2, but nothing changes on the job." They redefined the problem as on-the-job application rate after training rather than satisfaction.
- At the proposal kickoff, the team agreed to keep just one condition that three competitors could not match, and locked in '8 weeks of on-the-job assignment coaching per team lead + a monthly coaching-log report' as the winning strategy.
- Of the 40 pages in the main body, they filled the first 3 with Company A’s line-stoppage counts and frontline leader turnover data, and moved the company introduction and track-record table to a 5-page appendix.
- The presentation ran 15 minutes, so the presenter changed from a salesperson to the consultant in charge, and the first 3 minutes opened with one real page from a coaching log. The team drafted 22 likely questions and rehearsed them, and 14 of those actually came up.
- With a technical score of 87.6, they beat the runner-up (81.2) by 6.4 points and won a KRW 320 million (≈ US$239,400) project. The following year, the client doubled the number of coaching participants, and the contract was renewed.