Write a project proposal or business case that gets approved
How to write a project proposal or business case that gets approved: the sections to include, how to compare options (including doing nothing), how to show costs, benefits and risks, and a checklist before you submit.

You have an idea that would save time, win clients or fix a recurring problem, but it needs money, hours or a decision from someone else. It might be a new system, a new hire, a new service line or a big internal project. A good idea explained badly is usually turned down, or worse, quietly approved and then forgotten. A short, well-built project proposal or business case is how you turn the idea into a decision.
This guide covers how to write a project proposal or business case that a busy owner, partner or lender can read in ten minutes and act on. It is for internal and partner decisions, not for selling to a client; if that is your need, see how to write a business proposal that gets signed. The advice scales from a one-page memo for a small purchase to a fuller document for a large investment.
Proposal or business case: what is the difference?
The words overlap, and people use them loosely. A practical way to separate them:
- A project proposal says what you want to do, how, by when and with whom. It focuses on the plan.
- A business case says why it is worth doing, compared with the alternatives, including doing nothing. It focuses on the justification: costs, benefits and risks.
For a small business, one document usually does both jobs. Open with the case for the change, then give the plan. If the decision is small, a single page is enough. As the money, risk or number of people affected grows, add detail.
The building blocks of a business case
Project-management guidance from Atlassian lists the same core sections for a business case: an executive summary, a problem statement, an analysis of options, a recommended solution, an implementation plan, a financial analysis, a risk assessment and stakeholder analysis, then a conclusion with a clear request for approval. Here is how to apply each in plain terms.
1. Executive summary (write it last)
Three to five sentences: the problem, your recommendation, the cost and the expected benefit, and the decision you need. Decision-makers often read only this, so it must stand alone.
2. The problem or opportunity
Describe what is happening now, with evidence: hours lost, errors, complaints, missed revenue, customer feedback. Numbers beat adjectives. "We spend about six hours a week re-keying orders" is stronger than "our process is inefficient."
3. Options, including doing nothing
This is the section that earns trust. Compare at least three realistic choices. The UK National Health Service's guide to the Treasury's five-case model explains that a shortlist of three or four options should always include a "do nothing" or "do minimum" baseline, so the preferred option is measured against what happens if nothing changes. You do not need public-sector formality, but the habit is excellent: reviewers believe a recommendation more when they can see what you rejected and why.
| Option | Upfront cost | Ongoing cost | Main benefit | Main risk | |---|---|---|---|---| | Do nothing | $0 | Lost time, errors continue | No disruption | Problem grows | | Minimal fix | Low | Low | Quick relief | Partial result | | Recommended solution | Medium | Medium | Solves root cause | Needs training time | | Larger rebuild | High | Medium | Most capable | Slow, costly |
4. Your recommendation
Name the option and say why in two or three sentences, tying it back to the problem and to the business goals.
5. Costs and benefits
Show the numbers plainly, and show your workings. Include one-off costs (purchase, setup, training, your own time) and ongoing costs (subscriptions, maintenance). Estimate benefits as hours saved, revenue gained or costs avoided, and state the assumptions behind each. The five-case guidance cautions that an economic case should never rest on a single number and should include risk and sensitivity results, so test what happens if benefits come in 30 percent lower. For a simple framework, read a cost-benefit check before you hire, buy or expand, and for estimating effort, estimating project time and cost without guessing.
6. Plan, timeline and owner
A short list of milestones with dates and one named owner for each. Atlassian describes this as a high-level roadmap with timeline, milestones, resources and deliverables. Keep it high level; detailed task lists come after approval (see how to write a project plan a small team will follow).
7. Risks and how you will manage them
List the three to five biggest risks, such as cost overruns, low adoption, supplier delay or key-person dependency, with one mitigation for each. Hiding risks does not make them smaller; it makes you look unprepared when one appears.
8. Who is affected
Name the people and groups the change touches, such as staff, customers, suppliers and advisers, and note what each needs from you. Projects often fail on adoption rather than technology.
9. The ask
End with a specific request: "Approve $6,500 and four hours a week of Priya's time from January, with a review point in March." A clear ask makes a yes easy and a no informative.
Write it so it is read
Use a one-page version
Even for a large project, produce a one-page summary: the problem, the recommendation, the cost, the benefit, the risks and the decision needed. Attach details as appendices.
Keep the language plain
Avoid jargon and unexplained acronyms. If a partner or lender has to ask what a term means, you have lost momentum. Short sentences, specific numbers and descriptive headings help skimmers.
Show your sources
Where a number comes from a quote, a report, a customer survey or your own records, say so. Reviewers trust figures they can trace.
A pre-submission checklist
- Is the problem stated with evidence, not opinion?
- Are there at least three options, including doing nothing?
- Are costs complete, including your own time and training?
- Are benefits realistic, with assumptions written down?
- Did you test a worse-case outcome?
- Are the top risks named with a response?
- Is there one owner and a date for each milestone?
- Does the first page stand alone?
- Is the decision you need stated in plain words?
Numbers in your case are estimates and not financial, tax or legal advice. For major spending, loans or contracts, check the figures with your accountant or adviser.
Common mistakes
- Starting with the solution. If you open with the product, readers ask why, and you have no answer yet.
- Skipping "do nothing". It is the most important comparison and the one most often missing.
- Counting only the purchase price. Setup, training, migration and lost time in the first month are real costs.
- Optimistic single-number forecasts. Show a low, expected and high case.
- No owner. A project everyone supports and nobody owns will not finish.
- Length without clarity. Twenty pages are not more convincing than two clear ones.
- No review point. Offer to check results after 60 or 90 days and stop or change course if they miss the target.
Where WorkBOS fits
A business case is easier to write when your numbers are already in one place. In WorkBOS, project budgets and actuals, invoicing and basic accounting, task and workload data, and CRM pipeline figures sit side by side, so evidence such as hours spent or revenue from a client is a lookup instead of a hunt. Once a proposal is approved, you can turn it into a project with tasks and owners, collect sign-off with document signing and track results against the budget. See the pricing page (a free plan covers up to five users) and the docs. WorkBOS will not write the case for you, but it makes the evidence easier to find.
Frequently asked questions
Q: How long should a business case be? A: As long as the decision needs and no longer. A small purchase can be one page. A large investment may need five to ten pages with appendices, but should always start with a one-page summary that stands alone.
Q: What is the difference between a project proposal and a business case? A: A proposal describes what you will do and how. A business case justifies why, by comparing costs, benefits, risks and alternatives. In a small business, one document often covers both.
Q: Why include a "do nothing" option? A: It is the baseline that every other option is measured against. It shows the cost of inaction and proves that your recommendation is better than leaving things alone.
Q: How do I estimate benefits I cannot measure yet? A: Use conservative assumptions, write them down and test a lower case. Use your own records or quotes where possible, and propose a review after 60 to 90 days to compare reality with the forecast.
Q: Who should review my business case before I submit it? A: Someone who will challenge it: a partner, a trusted manager or your accountant. A fresh reader quickly finds missing costs, unclear language and weak assumptions.
Sources are linked in the text above: Atlassian and England's National Health Service (NHS England).
Run it all from one place
Projects, clients, finance, people and AI employees in one system. Start free, no card needed.
Start free →