Professional Documents
Culture Documents
Cover Page
Approvals:
Introduction: [Brief overview of the purpose of this case and the desired outcome
or decision required]
Description: [Describe the project and the reason for this investment and the
major issues that will be addressed]
Industry, market, and customer attributes: [What are the major customer
or market needs that are addressed through this case? State the market size, revenue
potential, targeted segments, etc.]
Assumptions and Risks: [What are the major assumptions, including financial,
operational, technological that are discussed in detail and which could
impact the probability of success?]
Part 2: [Each Business Case should contain a funding request. This should be
a carefully crafted statement that clearly articulates exactly how much money
is being requested initially, and in the future.]
Each FSP should describe the number of resources, skill sets, timing,
budgets, and any other characterization required to indicate what will be
done, by whom, and when. A table may be used to summarize this with
detailed FSPs as an attachment or appendix to the Business Case.
Launch Support
Since all product projects need to be launched, it might prove helpful to
include a high-level Launch Plan in this Business Case. It should spell
out the dates, resources needed, and any other pertinent information to
assure that the product hits the market at the right time with the right
amount of executive support.
SECTION 7—ASSUMPTIONS, FORECASTS, AND FINANCIALS
Every Business Case contains a set of assumptions that guide the forecasts
of unit volumes, pricing, revenue, and cash flow. Scenarios can
be used to provide the right context for a variety of outcomes under
varying assumptions. In this section, identify each scenario and the
assumptions for that scenario. Provide back-up data in the Appendix
as needed.
Scenario 1:
Scenario 2:
Financial Analysis
In this section you’ll be preparing estimates and forecasts based on the
scenarios built earlier, and the described assumptions. The assumptions
should be clearly stated and include rationale for choosing a specific
forecast. Make sure to include best case, worst case, and most
likely case. There are two financial templates that you can use to capture
your ‘base case’ and subsequent scenarios. Use as many as you
need to portray the scenarios you created. The following major categories
should be included in your financial analysis and forecasts:
1. Profit and Loss (P&L) estimates
a. Unit prices and volumes (sales mix)
b. Cost of goods
c. Expenses by function
2. Cash Flow
a. Timing of inflows and outflows
b. Capital expenditures needed (amount and timing)
c. Discounted cash flow (and NPV)
4. Cost of capital (the discount rate) for discounting cash flows (check with Finance Dept)
7. Study period (number of months or years covered by this case) —when does the investment have
to start and when does it end? Also, make sure to identify whether the case covers calendar years
or company specific fiscal years
11. Cost/benefit analysis for specific projects (including goals of cost savings, avoidance, or
increased revenue)
Base Case Financials—Business as Usual (or Base Case)
Use this financial profile to show how the business might perform if no
investment is made.
Business Case Financials—Scenario 1
Use this financial profile to show how the business might perform if no investment is made.
This section addresses the practical realities of the Business Case. Essentially,
it describes what is to be done if the investment is approved, when,
and how. This section can include any information regarding production,
facilities, timing, people, systems, supply chain, logistics, and anything
required to support a new product or an enhancement to an existing
product. Action-oriented Functional Support Plans can serve as a useful
way to think about operationalizing the business of the product and in
supporting the product after it’s in the market.
Use the following table as a way to describe what happens across the
product development, launch, and post-launch phases:
Referring to the table used in Section 8, two rows have been added to
identify and address possible risks.
Clarify any additional risks or any important contingency plans here:
SECTION 10—RECOMMENDATION
One of the last activities for the Business Case is to communicate to management
your opinion about the project. To achieve this, you will need
to draw appropriate conclusions and include your recommendation for
go or no-go. It is important to remember that the positive outcome you
might envision as you begin to assemble this case may indeed be different
from what the facts, data, and assumptions reveal. Remember, just
because your team invested a considerable time in developing the Case
does not mean it should be a go. That would obviate the need for the
Case; therefore, if the Case just does not make good business sense or
doesn’t fit with the profile of investments expected by management,
then incorporate good business judgment and do not recommend.
SECTION 11—APPENDICES