
A business case can be designed in many ways. From an unofficial oral presentation, to a formal letter with paragraphs and larger calculations. Here you can see a version that lies somewhere in between.
Your business case must tell the story of your project. It tells the reader about the problem, changes or opportunities associated with the project you are working on. The business case must then describe how the problem is solved or the opportunity in the project is exploited.


The most obvious reason is to use it to justify the resources and investments needed to ensure that the change project was successful. However, this may indicate that a business case just is a financial document, which is a misconception Although a business case should include financial considerations, this should not be the sole purpose of the document.
In contrast, your business case is the only place where all relevant facts are documented and linked into a coherent narrative. The story tells what, when, where, how and why.
A project's cycle typically provides some natural points at which a business case should be finished.

The model shows the project's five milestones. Every milestone in the project team's work should result in a contribution to the business case. At the end of the project planning phase, all the project's key information, e.g. be documented in your business case.
If one of your primary goals in the project planning phase is to obtain funding, your chances of success are greater if you are also aware of the following goals:
A well-written and well-documented business case is also a great help for the entire project team, which i.a. achieve these benefits:
The conclusion should be the first paragraph of your business case, but is the last paragraph to be written. It is a short summary (1–3 pages) of the entire business case. Imagine you have two minutes to tell someone about the project and justify your request for resources and grants.
Each paragraph in the conclusion should accurately convey all the information that is vital to the project and involve the reader in the entire narrative of the project. The information in the conclusion is extracted from the detailed parts of the business case that you have just completed.
The situation description deals with the details behind the problems and opportunities that the organization is facing. It is a statement about what is happening in the organization right now. Most projects are started because something is wrong or because a significant opportunity is not being exploited. Every project has one or two central themes that relate to challenges or opportunities.
In this section, you present the reader with the details of the project. This section must convince your stakeholders that your team, in an efficient and professional way, will find the best processes, systems and organizational elements that can help your company solve the challenges that you have presented above. The project description consists of two main areas:
Here you describe the solution your team recommends to cope with the challenges and opportunities you have previously presented in the situation description. The solution description is written in this order:
Here you describe what the price is to reach the future state you have described above. A good business case is not complete without a thorough analysis of the costs and benefits associated with implementing the proposed solution. But remember that costs and benefits can be difficult to accurately determine.
How to do a Cost Benefit analysis >
Now that the management understands the solution and the financial benefit that is achieved by implementing the solution, it wants confirmation that the solution can actually be implemented.
This section must assure the management that your team has considered all the most significant challenges in relation to the implementation.
A number of elements are important for a successful implementation. The implementation section should address each area:
Most business improvement projects are based on assumptions and assumptions in order to develop a solution. It is absolutely essential that the business case documents these assumptions.
Before putting your assumptions into the business case, you should test them with the project's stakeholders.
The description of the assumptions should be followed by an unbiased discussion of the strengths, weaknesses, opportunities and threats (SWOT) you see in relation to the recommended solution. Finally, it is also important that the business case discusses the risks associated both with implementing the solution and, not least, with does not to implement it.
Here you can download the SWOT template
Here you finish your business case. Reiterate the central themes that drive the project. Repeat the solution on a higher level. The section also identifies the return on investment and the overall benefits of the solution. You should reiterate the risk of doing nothing and emphasize the seriousness of the situation. Finally, the section must describe the conclusions that the reader should draw based on the business case as well as your recommendations for what the next step should be.
Fill out the form to book a 30-60 minute session.
We will respond within 24 hours
Contact us today and hear about your options