What a business proposal is
A business proposal is a persuasive document that recommends a specific course of action and asks a named reader to approve it. It sits between a report and a sales pitch: it must be evidence-based like a report, but it ends with a clear request like a pitch.
It is not the same as a business plan. A business plan describes a whole venture and how it will operate. A proposal argues for one decision.
| Document | Purpose | Reader's question |
|---|---|---|
| Business proposal | Win approval for a specific project or offer | Should we say yes to this? |
| Business plan | Describe a whole business and its strategy | Is this venture viable? |
| Business report | Analyse a situation and present findings | What is happening and why? |
| Business case | Justify an investment internally, often with detailed financials | Is the return worth the cost? |
Types of proposal
Your assignment will usually specify one of these. If it does not, say which you are writing in your introduction.
- Internal proposal: to managers in your own organisation, for example proposing a new scheduling system or a training program.
- External proposal: to a client or partner, offering a product or service.
- Solicited proposal: a response to a request for proposal (RFP) that sets out what the client wants. Follow its structure exactly.
- Unsolicited proposal: you identify the opportunity yourself, so you must work harder to establish that the problem exists.
The standard sections
Most proposals follow this order. Adjust headings to your assignment brief or RFP.
| Section | What it does | Approx. share |
|---|---|---|
| Title page | Title, prepared for, prepared by, date | – |
| Executive summary | The whole proposal in one page: problem, solution, cost, benefit, request | 5 to 10% |
| Problem or opportunity | What is wrong or possible, with evidence | 15% |
| Proposed solution | What you recommend and how it works | 25% |
| Alternatives considered | Other options and why yours is better | 10% |
| Costs and benefits | Budget, savings, revenue, ROI or payback | 15 to 20% |
| Implementation and timeline | Steps, owners, milestones | 10 to 15% |
| Risks | What could go wrong and how you will manage it | 5 to 10% |
| Conclusion and call to action | Restate the value and the specific decision needed | 5% |
| References and appendices | Sources, detailed calculations, supporting data | – |
Write the executive summary last. Many readers will read nothing else, so it must stand alone. Our guide on how to write an executive summary covers it in detail.
Defining the problem
A proposal is only as strong as the problem it solves. If the reader does not believe the problem is real and costly, no solution will interest them.
- State the problem in one sentence. "Customer complaints about delivery delays rose 40% in the last year."
- Quantify its cost: lost revenue, wasted hours, staff turnover, compliance risk.
- Show the cause, using data, a root-cause analysis or a framework such as SWOT.
- Explain the cost of doing nothing. This creates urgency.
Use real or clearly labelled data
Cite industry statistics and company data where you have them. If the assignment uses a hypothetical company, label assumptions clearly ("assuming 200 orders per day") rather than presenting invented figures as fact.
The proposed solution
Describe exactly what you recommend: what it is, how it works, who it involves and why it solves the cause you identified. Link each feature of the solution back to a part of the problem.
| Problem cause | Solution element | Expected result |
|---|---|---|
| Manual route planning | Route optimisation software | Shorter delivery times |
| No delivery updates for customers | Automated text notifications | Fewer "where is my order" calls |
| Drivers untrained on new system | Two-day training program | Fast adoption |
Then address alternatives. Showing that you considered and rejected other options, with reasons, makes your recommendation far more credible.
Costs, benefits and ROI
Decision-makers want to know what it costs and what they get back. Present the numbers clearly in a table, and put detailed calculations in an appendix.
| Item | Year 1 (hypothetical) |
|---|---|
| Software licence | $18,000 |
| Training | $6,000 |
| Total cost | $24,000 |
| Fuel savings | $15,000 |
| Reduced customer service hours | $12,000 |
| Total benefit | $27,000 |
| Net benefit / ROI | $3,000 / 12.5% |
ROI = (benefit − cost) ÷ cost × 100. For multi-year projects, consider payback period or net present value; see our guide to NPV, IRR and payback. Include non-financial benefits too, such as customer satisfaction or staff retention, but do not let them replace the numbers.
Timeline and implementation
Show that the plan is realistic. A simple table or Gantt chart works well.
| Phase | Activities | Owner | Weeks |
|---|---|---|---|
| 1. Approval and procurement | Sign-off, vendor contract | Operations manager | 1 to 2 |
| 2. Setup | Install software, import routes | IT | 3 to 4 |
| 3. Training | Driver and dispatcher training | HR / vendor | 5 |
| 4. Pilot | One region, measure results | Logistics lead | 6 to 9 |
| 5. Rollout and review | All regions, KPI review | Operations manager | 10 to 12 |
Name the measures you will use to judge success, such as average delivery time and complaint volume, so the reader can see how results will be tracked.
A worked outline
Assignment: propose a solution to high staff turnover at a regional restaurant chain.
- Executive summary: turnover is costing the chain an estimated amount each year in hiring and training; a structured onboarding and mentoring program is proposed at a stated cost with a payback within the first year.
- Problem: turnover rate versus industry benchmark; exit interview themes; cost per hire.
- Solution: 30-day onboarding plan, peer mentors, scheduling flexibility.
- Alternatives: wage increase across the board (higher cost), doing nothing (rising costs).
- Costs and benefits: mentor stipends and training time against reduced hiring costs.
- Implementation: pilot at two locations, then roll out.
- Risks: manager buy-in, mentor burnout; mitigation for each.
- Call to action: approve the pilot budget by a specific date.
Making it persuasive
A proposal succeeds when the reader feels their own priorities are being served. Frame benefits in the reader's terms, anticipate their objections in the risk and alternatives sections, and support every claim with evidence. Ending with a single, specific request ("approve a $24,000 pilot budget by 1 March") makes saying yes easy.
Writing style and formatting
- Write for a busy decision-maker: short paragraphs, informative headings, bullet points where content is a list.
- Use the reader's language and priorities. Finance cares about ROI; operations cares about workload.
- Be confident but not exaggerated. Avoid "revolutionary" and "guaranteed".
- Use visuals for numbers: tables, simple charts.
- Follow the referencing style your course requires; our Harvard and APA guide covers both.
Mistakes to avoid
- Starting with the solution Establish the problem first, or the reader has no reason to care.
- No numbers A proposal without costs and benefits rarely gets approved, in class or at work.
- Ignoring alternatives Show why your option beats the others, including doing nothing.
- A vague request End with the specific decision, budget and date you need.
- An executive summary that only introduces It must state the recommendation, cost and benefit.
- Unrealistic timelines Build in time for approval, training and a pilot.
Checklist before you submit
- Is the reader and the decision you want clearly identified?
- Is the problem quantified and its cause explained?
- Does each part of the solution link back to the problem?
- Have you compared at least one alternative?
- Are costs, benefits and ROI presented clearly, with assumptions stated?
- Is there a realistic timeline with owners and measures?
- Are risks identified with mitigation?
- Does the executive summary stand alone?
If you are working to a deadline and want expert help, you can order business proposal or report help.