Business Case

Template

INTERNAL
Business Case – Template
Project Identification

Project Name CPI Project Number

<Project Name>
Customer Name Customer Number
<Customer Name>
SAP Project Manager Customer Project Manager
<SAP Project Manager> <Customer Project Manager>

DOCUMENT IDENTIFICATION
Author Document Location (repository/path/name)
<Author> <Document location>
Version Status Date (YYYY-MM-DD) Document Classification
0.1 Final <Date> Internal

REVISION HISTORY
Version Date Description
December 6,
0.1 <Text here>
2017
0.2

2
TABLE OF CONTENTS
BUSINESS CASE 4
Executive Summary........................................................................................................................................ 4
Strategic Allignment....................................................................................................................................... 4
Benefits........................................................................................................................................................... 4
Investment Appraisal..................................................................................................................................... 5
Interface Dependencies................................................................................................................................. 5
Stakeholders..................................................................................................................................................... 5

3
BUSINESS CASE

The Business Case provides the economic justification for the proposed project. It documents how
and when the investment will be profitable for the customer.

Executive Summary

Objective
< State what business need the project is solving. Highlight the economic justification for the project >
Problem/Opportunity
< Leverage some of this information from the Project Charter. This section presents the “As Is” Situation.
The objective in producing an “As Is” description is to understand the underlying reasons for the existing
process. To create this information, use the following process, as needed: Break the problem into concise
distinct bullets and separate them into causes and effects. Then consolidate the bullet items into a
concise statement. >
Proposed Resolution
< Define what the project will deliver—how it will address the identified functional/operational need. This
section presents the “To-Be” situation. >
Industry Comparison
< If you know if other companies have invested in this type of technology initiative, describe similar
technology initiatives. >

Strategic Alignment

Business Strategy Business Strategy

< All projects should support and tie to the
organization’s strategic goals. Answer how the
objectives align with the business strategy. >
TECHNOLOGY STRATEGY
< All projects should support and tie to strategic
goals. Answer how the objectives align with the
technology strategy. >
< All projects should support and tie to the
organization’s strategic goals. Answer how the
objectives align with the business strategy. >
TECHNOLOGY STRATEGY
< All projects should support and tie to strategic
goals. Answer how the objectives align with the
technology strategy. >

Benefits

TANGIBLE BENEFITS
< Tangible Benefit>
< Tangible Benefit>
< Tangible Benefit>
< Tangible Benefit>

4
 INTANGIBLE BENEFITS
< Intangible Benefit>
< Intangible Benefit>
< Intangible Benefit>
< Intangible Benefit>

Investment Appraisal

Discount rate 8%

Year 0 1 2 3 4 5
Cash Outflow
Cash Inflow
NetCashFlow 0€ 0€ 0€ 0€ 0€ 0€

Discount Factor 1.000 0.926 0.857 0.794 0.735 0.681

Net Cashflow Discounted 0€ 0€ 0€ 0€ 0€ 0€

Net Present Value 0€

Break even (Payback) 0€z #VALUE! #VALUE! #VALUE! #VALUE!

ROI Statical #DIV/0!

IRR (Approximation) #NUM!

Interface Dependencies

DEPENDENCIES
<<Identify the projects, people and/or organizations along with the associated locations that will be
affected or impacted by the proposed need/solution.>

AFFECTED SYSTEMS
< Identify the systems, along with the associated locations that will be affected or impacted by the
proposed need/solution.

Stakeholders

INDIVIDUALS AND ORGANIZATIONS WHO HAVE INTEREST IN THE PROJECT

<Identify name and title of the stakeholders that will be involved in the project. Stakeholders are
individuals or organizations who are involved in the project and whose interests may positively or
negatively impact the completion of the project, i.e., John Doe – Purchasing Manager. Note: Identification
is necessary to manage and influence those expectations for success. Indicate other organizations and
individuals who will have crucial responsibilities for the project or will be affected by project outcomes.
Also, include any non-IT organizations, such as external consultants or vendors. This list is further refined
in the Initiating and Planning Processes>
< Stakeholder/Stakeholder Area>
< Stakeholder/Stakeholder Area>
< Stakeholder/Stakeholder Area>

5
www.sap.com/contactsap

© 2017 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.

The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.
National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable
for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality
mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are
all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation
to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are
cautioned not to place undue reliance on these forward-looking statements, and they should not be relied upon in making purchasing decisions.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other
countries. All other product and service names mentioned are the trademarks of their respective companies. See http://www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark
information and notices.