The proposal that gets funded is the one that proves you understand the client better than anyone else: and that you can deliver what they need. Learn the frameworks, structure, and persuasion tactics that win contracts.
A business proposal is a formal written offer to solve a client's problem or deliver a service. It combines research, persuasion, and evidence into a document that aims to convince a decision-maker to hire you, fund your initiative, or approve your budget request. Unlike a pitch (spoken, real-time, improvisational), a proposal is permanent, credible, and fully developed.
There are two fundamental types of proposals: solicited (in response to a client's request or RFP. Request for Proposal) and unsolicited (you initiate, identifying a need the client may not have explicitly stated). Solicited proposals have higher win rates but more competition. Unsolicited proposals have lower response rates but less competition when they work. The frameworks in this chapter apply to both.
Research shows that companies submitting RFP responses within 24 hours of the RFP release have 35% higher win rates than those submitting in the final week. This is not because early submissions are better-written: it is because early submission signals that the client matters enough for you to move quickly. It demonstrates prioritization and urgency. Conversely, submissions that arrive in the last hours before the deadline signal that responding to this RFP was not a priority.
A three-person design agency competed to redesign Samsung's mobile experience platform. Their competition: two global consulting firms with 300+ employees, $1B+ annual revenue, and extensive Samsung history. The global firms submitted what they always submitted: generic enterprise methodology, org charts, case studies from other Fortune 500 companies, and prices that ran into the millions. The three-person agency did something different. They spent two weeks understanding Samsung's internal design challenges from interviews with the product team. Their proposal showed specific mockups of how the new platform would work, annotated with Samsung-specific context ("This solves the localization bottleneck your team mentioned"). They included a detailed payment plan that aligned costs with milestones, reducing Samsung's risk. They did not compete on scale or credentials: they competed on understanding.
Result: The three-person agency won the engagement. The winning element was not their size or reputation: it was the proposal's evidence that they understood Samsung's specific problem better than the 300-person competition. This is the principle that governs all proposal success: specific understanding beats generic credentials every time.
The sequence and structure of a winning proposal are not arbitrary. Each element builds credibility, establishes shared understanding, and moves the decision-maker closer to yes.
Executive Summary (1 to 2 pages): The entire proposal compressed into its essential argument. This is written last but positioned first. A decision-maker who reads nothing else should understand: the problem you have identified, your recommended solution, key benefits, and the investment required. Pro tip: Decision-makers often read only this section. Make it complete and comprehensible as a standalone document. This is where the yes or no is often decided.
Problem Statement or Needs Analysis (1 to 2 pages): Demonstrates that you understand the client's situation with specificity and nuance. The stronger your problem statement, the stronger the implicit claim that your solution will work. Use client's own language and data when possible. Quote from interviews or their publicly stated priorities. Pro tip: Generic problem statements that could apply to any client signal lazy research. Specificity signals credibility.
Proposed Solution (3 to 5 pages): What you are recommending and why it specifically solves the problem you described. This is the core of the proposal. It must be concrete, not theoretical. "We will implement a cloud migration strategy" is vague. "We will migrate your three primary systems (ERP, CRM, and reporting database) to AWS using a phased approach: first the reporting database (low-risk, high-visible impact), then CRM (moderate risk, revenue-impacting), then ERP (highest risk, planned for month 12)" is concrete. Pro tip: Detail removes doubt. Vagueness triggers skepticism.
Methodology and Implementation Plan (2 to 3 pages): How you will execute, phase by phase. Include timeline, milestones, dependencies, and resource allocation. Clients fund approaches, not just outcomes. A detailed methodology reduces the client's uncertainty about the process and your competence. Pro tip: Visual timelines (Gantt charts, phase diagrams) often communicate more effectively than text.
Timeline and Milestones (1 page or visual): Specific dates and deliverables. "Launch in Q2" is vague. "Phase 1 deliverable (requirements) by March 15; Phase 2 (design review) by April 20; Phase 3 (launch) by May 30" is clear. Pro tip: Realistic timelines signal maturity. Over-promising timelines signal inexperience or worse, dishonesty.
Team Qualifications and About Us (1 to 2 pages): Why you are the right choice. Lead with the most relevant experience, not your company history. Instead of "Founded in 1995 with offices in 12 countries," write "Our team has executed 23 similar cloud migrations, with average project costs 15% under budget and timelines delivered on schedule. Key team member Jane Chen led the ERP migration for Hyundai Motor in 2022." Pro tip: Evidence beats biography. Specificity beats puffery. Include bios of key team members, not everyone.
Terms, Conditions, and Budget (1 to 2 pages): What is included in scope, what is not, what triggers a change order, and payment terms. Many proposals fail not on strategy but on clarity here. "We estimate ₩50M for this engagement" is less powerful than "Investment: ₩50M, structured as: ₩15M at project kickoff, ₩20M upon Phase 2 completion, ₩15M at launch. This covers X, Y, Z. Out of scope: A, B, C." Pro tip: Ambiguity in budget is the source of almost every client-vendor dispute later.
Call to Action and Next Steps (1 paragraph): What the client should do now. Not "We look forward to your feedback" (passive and easy to ignore). Instead: "To move forward, please sign the attached agreement and return it to me by [date]. Upon receipt, we will schedule a kickoff meeting for [date], and work begins [date]." Pro tip: Clarity and specificity remove friction from the decision.
Different contexts require different proposal approaches. Understanding which type you are writing shapes structure, tone, evidence, and audience expectations.
Requesting approval for a new initiative, budget allocation, process change, or hire within your own organization. These are often underestimated in importance but critical for career advancement. Audience: Your manager, department head, CFO. Structure: Lead with business impact (revenue increase, cost savings, risk reduction). Back with data. Include resource requirements clearly. Pro tip: Internal proposals succeed when they make the approver's job easier: show that you have thought through implementation and risks.
Offering consulting services, software implementation, design, training, or products to external clients in response to an RFP or an inbound inquiry. This is the most common proposal type. Audience: procurement, decision-makers, budget-holders. Structure: Problem + solution + proof + investment. Pro tip: Differentiation is critical when competitive. Show not just competence, but specific fit for their situation.
Requesting funding from government agencies, foundations, or nonprofits for research, educational programs, or community initiatives. Audience: grant officers, review panels with limited time and high volume. Structure: Strict adherence to funder guidelines. Clear problem statement addressing the funder's priorities. Evidence of organizational capability. Realistic budget. Pro tip: Funders read proposals to find reasons to reject. Make rejection difficult by following guidelines precisely.
Proposing a collaborative relationship, joint venture, or strategic partnership with another organization. Audience: executives, boards, legal teams. Structure: Vision for partnership. Complementary strengths. How value is created for both parties. Governance and risk mitigation. Pro tip: These proposals must address "what does the other side get out of this?" clearly and convincingly.
Requesting venture funding, angel investment, or bank financing for a startup or growth initiative. Audience: VCs, angels, bankers who review hundreds of pitches. Structure: Problem your company solves. Market size and opportunity. Team and traction. Use of funds. Exit strategy. Pro tip: Investors fund teams and markets, not products. Make the team's qualifications and the market opportunity absolutely clear.
Responding to formal government Requests for Proposals. Audience: government procurement specialists following strict evaluation criteria. Structure: Follows RFP format precisely. Addresses every evaluation criterion explicitly. Compliant with all technical specifications. Pro tip: Government proposals are often won on compliance, not creativity. Follow the format exactly. Use the government's language in your response.
Strong proposal writing requires specific techniques that convert research into compelling argument and features into benefits.
For every statement in your proposal, ask "So what?" and answer it. "We have 20 years of experience": so what? "Your team benefits from a partner who has solved this problem 23 times before." "Our solution integrates with your existing systems": so what? "Your team eliminates the 6-hour weekly manual data sync that costs ₩4M monthly." The stronger your "so what?" answer, the more persuasive your writing.
Passive: "The platform will be implemented by our team." Active: "We will implement the platform in three phases." Action language is stronger and clearer. Replace "will be determined" with "we will determine." Replace "can be improved" with "we will improve." Passive voice in proposals signals uncertainty or deflection.
Use the client's own terms, priorities, and values in your proposal. If their RFP emphasizes "agility," use that word. If they value "sustainability," demonstrate how your solution aligns with that. If interviews revealed they worry about "team disruption," address that concern specifically. Mirroring signals deep listening and fit.
When comparing options or showing results, choose the format that emphasizes your story. A table shows data neutrally. A chart emphasizes the narrative you want to tell. "Cost per unit" as a line chart shows trend better than as a table. "Percentage improvement" as a bar chart is more memorable than percentages in text. Use charts to guide the eye toward your solution's advantage.
Write your proposal in full, then distill the executive summary. This ensures your summary is accurate and contains all essential elements. Many writers draft the executive summary first, then realize it does not align with the actual proposal. Reverse engineering ensures coherence.
| Mistake | Why It Fails | How to Fix It |
|---|---|---|
| Vague scope definition | Client is uncertain what they are funding. Leads to scope creep, disputes, and misalignment. | Define in-scope deliverables explicitly. List what is out of scope. Be specific: "includes" not "may include." |
| No metrics or quantification | Claims without evidence are forgettable. "Significant improvement" loses to "28% improvement within 90 days." | Find numbers for every major claim. If you cannot quantify it, question whether it belongs in the proposal. |
| Talking about yourself instead of the client | Proposals are about the client's problem, not your capabilities. "We are experts in X" is less persuasive than "We will solve your X problem using approaches that have worked at similar companies." | Start every section with the client's need or benefit. Then explain how you address it. Client first, always. |
| Generic templates | Clients can spot recycled language immediately. "Leverage best practices" and "synergize" appear in every proposal. Generic language signals lazy customization. | Customize heavily. Use client's name, specific situation, and unique challenges throughout. Make the template invisible. |
| Weak or missing problem statement | If the client thinks you misunderstood their situation, they will not trust your solution. A weak problem statement is the foundation of a failed proposal. | Spend 30% of your writing effort on the problem statement. Make it specific, insightful, and slightly better than how the client describes their own situation. |
| Overly long proposals | Most proposals are twice as long as necessary. Busy decision-makers skim. Length signals lack of judgment about what matters. | Write the first draft, then cut it by 40%. Kill paragraphs that do not advance your case. Brevity signals confidence. |
| Unclear budget framing | Clients resist accepting the price if you position it as a cost instead of an investment. "Our fee is ₩30M" feels expensive. "Your ROI is 3:1 within 18 months, representing ₩30M investment" feels different. | Always frame budget as investment + expected return. Lead with value before stating the number. |
The quality of a proposal's visual design affects perception of quality and likelihood of being read. A poorly formatted proposal suggests poor execution. A clean, professional proposal signals that you care about details.
Use consistent fonts throughout. This course's brand uses Nunito for headings and Plus Jakarta Sans for body text. Maintain consistent margins (1 inch or 24mm on all sides). Use consistent heading hierarchy. Make sure sections are visually distinct. Number pages. Include a table of contents for proposals longer than 10 pages. Pro tip: Formatting that is invisible when done right becomes glaringly visible when done wrong.
Dense text paragraphs are hard to read. Break up long paragraphs into shorter ones. Use bullet points for lists. Add white space between sections. Readers should be able to skim the proposal in 3 minutes and understand the core argument. Design for skimmers, not deep readers. Pro tip: If every section is a wall of text, the proposal will not be read thoroughly.
If you have brand guidelines, apply them throughout the proposal. Color palette, logo, typography. If you do not have guidelines, create temporary ones for the proposal. Consistency is a signal of professionalism. Using three different fonts or five different colors suggests carelessness.
The cover page is disproportionately important. A clean, well-designed cover page suggests that what follows will be equally polished. Avoid cluttered covers. Include: client name (personalization), proposal title, your company name, date, and contact information. A single well-chosen image or graphic can elevate perceived professionalism.
Bad layout: Full-width paragraphs, 12-point Times New Roman, justified alignment, no section breaks, no white space. Heading hierarchy unclear. Images inserted without captions. Tables crammed with data. This requires sustained concentration to read. Most decision-makers will not finish.
Good layout: Consistent margins and margins. Clear hierarchy: section headings (22px, bold, navy), subheadings (18px, bold, navy), body text (15px, regular). Ample white space between sections. Lists instead of dense paragraphs. Captions for all images. Tables with clear headers and alternating row colors for readability. Side margins for callout boxes with key insights. This proposal invites reading.
This course uses Nunito (font-family: 'Nunito', sans-serif) for all headings and structural elements, and Plus Jakarta Sans for body text. Consistent use of these fonts signals alignment with the course brand and demonstrates attention to detail. If you apply these same fonts to your proposal, it visually ties the proposal to the course content and signals professionalism aligned with the teaching.
The following four case studies show how different proposal types deploy persuasion principles and structural best practices to achieve their goals.
A Kickstarter campaign is a proposal to a distributed audience. The most funded campaigns on Kickstarter share proposal elements: compelling problem statement (why does this product need to exist?), solution (detailed video showing the product and how it works), credibility (founder track record, team bios), social proof (early backer testimonials, press coverage), and a clear call to action (back this project). Campaigns that raise the most funds often have professional video (similar to a pitch), clear writing, honest budget breakdowns, and evidence of prototyping. The Pebble smartwatch campaign succeeded in 2012 by showing a working product, transparent budget, and honest timeline. It raised $10M.
McKinsey's consulting proposals are models of clarity and structure. They lead with a brief summary of the engagement objective and expected impact. They include a clear problem statement (framed from McKinsey's diagnostic work). They propose a solution structured as a series of work streams and a detailed timeline spanning 12-20 weeks. They include bios of the engagement team (highly credible: top consultants). They include case studies of similar engagements at comparable companies with quantified outcomes. Budget is transparent, structured by phase. The entire proposal signals confidence, expertise, and clarity. McKinsey proposals often succeed simply because the structure and confidence level are so high that clients feel assured of results before the work begins.
Y Combinator's application is a proposal to investors. Founders answer specific questions: What is your startup trying to do? What problem does it solve? How many people want your product? What makes you the right team? How much money do you need and what will you use it for? The most successful applications answer these questions with precision and evidence. Y Combinator favors teams that show: clear problem definition, evidence of customer demand (early users, revenue, pre-orders), founder credibility (previous startup success, domain expertise), and realistic budgets. The application format is intentionally constrained: founders cannot hide behind longer prose. Clarity and specificity are forced by constraint.
The Korean government's R&D grants (Ministry of SMEs and Startups, National Institute of Advanced Industrial Science and Technology) require highly structured proposals. They demand: clear research objectives aligned with government priorities, detailed methodology, realistic budget with cost-per-outcome calculations, team qualifications with relevant publications, and impact projection (commercialization potential, job creation). Winning proposals are those that prove alignment with government priorities and provide rigorous evidence of feasibility. Generic proposals fail. Proposals showing deep understanding of the funder's priorities and realistic execution timelines succeed. A startup that won ₩500M in government R&D funding framed their proposal not as technical innovation, but as solving a specific government priority: "reducing carbon footprint in manufacturing."
The following resources will help you develop mastery in proposal writing. They span video, audio, books, and templates.
Comprehensive video covering proposal structure, best practices, and common mistakes. 12 minutes. Focus particularly on the section on executive summary construction and the importance of problem statement clarity.
Investors share what they look for in startup proposals and pitch decks. Applicable to any proposal to a skeptical audience. Emphasis on clarity, founder credibility, and market opportunity. 20 minutes.
While focused on negotiation, Voss's frameworks on labeling emotions and getting to the other side's real concerns apply directly to proposal research and positioning. 8 minutes. Key insight: Proposals should address the unstated concerns before stated ones.
Deep dives into pricing, proposals, and value communication. Episodes like "How Much Should I Charge?" and "The Art of the Pitch" are directly applicable to proposal writing and positioning. 30 to 50 minutes per episode.
Short podcast focused on business development and proposal strategy for agencies. Each episode covers one aspect of proposals: research, structure, pricing, follow-up. 15 to 25 minutes.
The definitive textbook on business proposal writing. Covers psychology of proposal reading, structure, persuasion principles, and common mistakes. Case studies of winning vs. losing proposals. This is the book to read if you write proposals regularly.
Practical guide with templates and examples. Covers proposal types, research methodology, structure, and formatting. More tactical than Sant's book. Good for quick reference while writing.
Focused specifically on responding to Requests for Proposals. Covers how to parse RFP requirements, map to your capabilities, and structure responses that win. Essential if you write competitive RFP responses.
Covers the basics of business writing, including clarity, tone, and structure. Lighter than Sant or Baugh, but useful for fundamentals. Particularly good on grammar and clarity principles applicable to all business writing.
Academic textbook on business communication covering proposals, emails, reports, and presentations. Evidence-based approach to what makes communication persuasive. More research-oriented than practical guides.
The Benchmarks page of this course includes proposal templates for common scenarios: client service proposals, internal budget requests, and partnership proposals. These templates follow the structural principles outlined in this chapter and provide starting points for your own proposals. Use them as guides, not as templates to fill in and submit unchanged. Every proposal must be deeply customized to your specific situation.
I have read the RFP at least twice and highlighted every evaluation criterion
I can name the three most important decision-makers and their individual success criteria
I understand the implicit (not just explicit) selection criteria based on client history and strategy
I have researched the likely competition and can articulate my differentiation
I have conducted a pre-proposal meeting or validation conversation with the client
My executive summary is 1 to 2 pages, written last, and completely comprehensible as a standalone document
My problem statement uses specific client language and demonstrates understanding better than the RFP description
My proposed solution is concrete and specific: not generic or theoretical
My methodology and timeline are detailed enough to reduce client uncertainty about execution
My team qualifications section leads with most relevant experience, not company history
My budget is framed as an investment with expected return, not a cost
My call to action is specific and actionable: client knows exactly what to do next
Every major claim in my proposal has supporting evidence or data
I use active voice throughout ("we will" not "will be")
I mirror the client's language and priorities throughout the proposal
Every section connects explicitly back to the problem statement I identified
I have cut my first draft by at least 25% for brevity and clarity
I have quantified every major benefit claim (%, months, dollars, or metrics)
My proposal uses consistent fonts (Nunito for headings, Plus Jakarta Sans for body)
White space is ample: no dense walls of text
All images and charts have captions and are referenced in text
Pages are numbered and the proposal includes a table of contents
My cover page is clean, professional, and includes the client name
My proposal demonstrates ethos (credibility), pathos (emotional connection), and logos (data)
I have included social proof (case studies, testimonials, third-party validation)
My problem statement creates enough perceived urgency that the client feels change is necessary
I can articulate what makes my proposal different from competitors (without directly criticizing them)
I have proofread for grammar, spelling, and punctuation: no errors
All references to client name, products, initiatives are spelled correctly
All hyperlinks and cross-references work correctly
I am submitting within 24 hours of the RFP release (if solicited)
I have a plan to follow up within 48 hours of submission
Course materials are for enrolled students only.
Contact clementmj@hanyang.ac.kr for access.