Infosys - Business Standardbsmedia.business-standard.com/_media/bs/data/... · Infosys Design...
Transcript of Infosys - Business Standardbsmedia.business-standard.com/_media/bs/data/... · Infosys Design...
Infosys
Design Thinking, Agile & SMAC: Translating clients’ need
December 30, 2014
Prabhudas Lilladher Pvt. Ltd. and/or its associates (the 'Firm') does and/or seeks to do business with companies covered in its research reports. As a result investors should be aware that the Firm may have a conflict of interest that could affect the objectivity of the report. Investors should consider this report as only a single factor in making their investment decision.
Please refer to important disclosures and disclaimers at the end of the report
Compan
y Update Shashi Bhusan
[email protected] +91‐22‐66322300
Hussain Kagzi [email protected] +91‐22‐66322242
Rating BUY
Price Rs1,958
Target Price Rs2,550
Implied Upside 30.2%
Sensex 27,396
Nifty 8,246
(Prices as on December 29, 2014)
Trading data
Market Cap. (Rs bn) 2,239.7
Shares o/s (m) 1,144.0
3M Avg. Daily value (Rs m) 14747.2
Major shareholders
Promoters 15.92%
Foreign 42.67%
Domestic Inst. 14.48%
Public & Other 26.93%
Stock Performance
(%) 1M 6M 12M
Absolute (10.2) 21.5 9.9
Relative (5.7) 12.3 (19.3)
How we differ from Consensus
EPS (Rs) PL Cons. % Diff.
2016 121.1 120.3 0.6
2017 138.2 136.8 1.0
Price Performance (RIC: INFY.BO, BB: INFO IN)
Source: Bloomberg
0
500
1,000
1,500
2,000
2,500
Dec‐13
Feb‐14
Apr‐14
Jun‐14
Aug‐14
Oct‐14
(Rs)
We take a deep dive into the benefits of “Design Thinking” (DT) that could be useful for current paradigm like Agile, which are critical for addressing new technologies adoption. Clients are clear about the business outcome they want, but unclear about ways to achieve it. We believe Infosys’ push toward DT could help them understand the clients’ need and business requirements by posing questions to clients.
Design Thinking – Asking the right questions to clients: DT can be regarded as problem solving methods. In DT, a large part of the problem solving activity comprises of defining and shaping the problem. The effort is to ask questions like "What? How? Why?" to lead to creative solutions of the problem. The problem solver is cognizant of technical feasibility while contemplating the business problem. Design Thinking’s interrogative approach helps formulating the clients’ problem with deep understanding of the clients’ business need.
Agile – Building a story around clients’ need: Tech companies are using new paradigm like Agile, to provide solutions to enterprise as the paradigm evolves through collaboration cross‐functional team, adaptive planning, evolutionary development, early delivery, continuous improvement, and encourages rapid and flexible response that are needed these days to understand the clients' need. The understanding evolves with the multiple iterations with clients.
Disruptive Technologies – Time to market, clarity of thought, and use of new paradigms: Emerging technologies are now a disruptor and it is becoming source of competitive advantage. But, the challenge for enterprise is to balance between investments in unproven strategy or wait for proven concepts. The opportunity to grab the first mover advantage poses the challenge of no clear definition of “What customer wants?” Hence, problem solving methodology of DT and quick iterative process of Agile proved to be critical.
Valuation & Recommendation – BUY & TP Rs 2,550: Dr. SIkka is talking about moving away from “same mess for less” to “doing more with less for more” that require change in culture. Infosys’ focal‐points are on being mindful, curious, speak‐up and understand clients’ needs that are integral to Design Thinking.
Key financials (Y/e March) 2014 2015E 2016E 2017E
Revenues (Rs m) 501,330 539,957 611,160 697,061
Growth (%) 24.2 7.7 13.2 14.1
EBITDA (Rs m) 134,150 150,113 168,106 189,411
PAT (Rs m) 106,480 122,329 138,520 158,115
EPS (Rs) 93.1 106.9 121.1 138.2
Growth (%) 13.0 14.9 13.2 14.1
Net DPS (Rs) 27.5 64.9 69.9 77.9
Profitability & Valuation 2014 2015E 2016E 2017E
EBITDA margin (%) 26.8 27.8 27.5 27.2
RoE (%) 24.4 24.5 25.1 25.6
RoCE (%) 24.3 24.3 24.9 25.5
EV / sales (x) 3.9 3.6 3.1 2.7
EV / EBITDA (x) 14.8 13.0 11.4 9.9
PE (x) 21.0 18.3 16.2 14.2
P / BV (x) 4.7 4.3 3.8 3.4
Net dividend yield (%) 1.4 3.3 3.6 4.0
Source: Company Data; PL Research
December 30, 2014 2
Infosys
Infosys: The core of the effort is to understand “What clients want?”
Dr. Sikka’s pursuance for “Design Thinking” is about getting people to think openly
about why a certain thing is not there. Today, customers are unclear about their
requirement but clear about the business outcome they want. They approach Indian
IT vendors for piece of advice on what they want to achieve. They want an
evolutionary process to achieve the goal and how they can do it better. The key
question for Infosys would be how they can evolve their processes that can help
them achieve their goal.
In one of the recent interview to “Horses for Sources” Dr. Sikka said, “The challenge
is that clients are not aware of their business problems and don’t know what their
problems are. It’s our job to be innovative and more open to helping our customers
find and identify problems, and to become more confident while we don’t know
what great problem or opportunity is going to be there tomorrow, we will help our
customers find it. And then, of course, once we find it, our education, our knowledge,
and our background gives us the tools to solve it. We’ll go after it and solve it
together. Design thinking really is about that. In the 1950’s, when Polya wrote his
book on problem solving, problem solving was the big deal in education. Now, I think
it’s problem finding.”
Vertical silos – Is it the best fit to solve the business problem?: Infosys’ endeavour
over the last five years to break‐away from the continuum of outsourcing has met
with little success. There are multiple headwinds in a tech driven innovation for
Infosys due to difficulty to foster collaboration, best practices with a vertical driven
silo businesses. We believe using the new paradigm Infosys is seeing a period of
great change, a discontinuity maybe and the potential to find new problems in
verticals and use the learning organization engine to help solve these.
Is there any change in stance of Infosys?: Both Mr. Shibulal and Dr. SIkka see the big
potential to build IP driven and software driven service models with ‘ReUse’ at the
core. Both recognize that core cultural elements are foundational to any
change/strategy as eventually it is the people that will be transformed in enabling
the organizational change. And Indian IT cannot do that by going down the vicious
cycle of cost cutting forever.
Right balance between New and Renew, Cutting Edge and Legacy: Infosys needs to
have one foot in the present to protect its traditional (and legacy) business and make
the right investments to grow its 5 year+ horizon businesses. We see a very level
playing field across the providers right now – the next phases of development are
crucial – acquiring and developing the technology‐enablement consultative talent,
building out the platforms, creating the right partnerships.
Exhibit 1: A compulsion of storytelling
Source: PL Research
Exhibit 2: DT, Agile, SMAC: Relationship
Source: PL Research
Adopting SMAC
Develop change agility
Be proactive, not reactive ‐ Look for and experiment with new
disruptive technologies (like SMAC)
Being proactive mean innovation and no prior definition of problem
December 30, 2014 3
Infosys
Design Thinking: A paradigm to formulate the clients’ need
Basically, Design Thinking is a design methodology. Design Thinking can be regarded
as a problem solving method or, by some definitions, a process for the resolution of
problems (but see below for the differences between methods and process).
As a solution‐based approach to solving problems, Design Thinking is particularly
useful for addressing problems that are ill‐defined or tricky. For ill‐defined problems,
both the problem and the solution are unknown at the outset of the problem‐solving
process (as opposed to "tame" or "well‐defined" problems, where the problem is
evident and the solution is possible with some technical knowledge.) Even when the
general direction of the problem may be clear, considerable time and effort is spent
on clarifying the requirements. Thus, in Design Thinking, a large part of the
problem‐solving activity is comprised of defining and shaping the problem.
Exhibit 3: Design Thinking – Basic Framework
Source: d‐School, PL Research
Exhibit 4: Iterative learning in Design Thinking about the clients’ need
Source: d‐School, PL Research
In Design Thinking, designers do not make any early judgments about the quality of
ideas. As a result, this minimizes the fear of failure and maximizes input and
participation in the ideation (brainstorming) and prototype phases. "Outside the box
thinking" is encouraged in the earlier process stages, since this style of thinking is
believed to lead to creative solutions that would not have emerged otherwise.
Exhibit 5: Change in culture
Source: PL Research
December 30, 2014 4
Infosys
We tried to understand the basics of Design Thinking through some of the
discussions available on YouTube.
1) Stanford Design Thinking Virtual Crash Course
(http://www.google.co.in/url?sa=t&rct=j&q=&esrc=s&source=web&cd=3&cad=rja&
uact=8&ved=0CCQQtwIwAg&url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3F
v%3D‐
FzFk3E5nxM&ei=9hWdVIaaKdKwuASQg4LQBA&usg=AFQjCNFQOaXDvwQvkKn8tMZJ
GUHxFZKqLA&sig2=I8cscHq9XiL37MAYBUfHHQ
2) Lean Start‐up Meets Design Thinking
http://www.google.co.in/url?sa=t&rct=j&q=&esrc=s&source=web&cd=4&cad=rja&u
act=8&ved=0CCoQtwIwAw&url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv
%3DbvFnHzU4_W8&ei=9hWdVIaaKdKwuASQg4LQBA&usg=AFQjCNFCV2yiI5Gutx_E0
7ece3NruFiZRg&sig2=WcKcE8KLhoKWwfN61fF3tw
A User‐Centred approach that brings Design into the business World
Design Thinking is often used to explore and define business problems and to define
products and services. In other words, Design Thinking brings the design approach
into the business world.
In this vein, Design Thinking has been characterized as a discipline in which the
designer's sensibility and methods match people's needs, by applying what is
technically feasible and by contemplating what a viable business strategy can
convert into customer value and market opportunity.
As a methodology or style of thinking, it combines empathy for the context of a
problem, creativity in the generation of insights and solutions, and rationality and
feedback to analyze and fit solutions to the context – All this helps derive a solution
that meets user needs and at the same time generates revenue, that is, drives
business success.
Exhibit 6: Thinking process: Iterative to understand clients’ need
Source: SAPGuild.org, PL Research
December 30, 2014 5
Infosys
Despite some differences, there seems to be a broad agreement between all the
protagonists about the stages and what they entail. This allows me to describe the
"prototypical" stages of the Design Thinking process as follows:
Understand the problem: Get an initial understanding of the problem
Observe users: Observe users, visit them in their (work) environment, observe
physical spaces and places
Interpret the results: Interpret the empirical findings
Generate ideas (Ideate): Engage in brainstorming sessions to generate as many
ideas as possible (expand the solution space)
Prototype, experiment: Build prototypes and share them with other people
(narrow down the solution space again, experimental phase)
Test, implement, improve: Test, implement, and refine the design (narrow
down the solution space again; solution‐driven phase)
Exhibit 7: Overview of Selected Methods That Can Be Employed in the Course of the Design Thinking Process
Stage (Mode) Methods
Observe users (Empathy)
Assume a beginners mindset
What? How? Why?
Define problem statement
Observe users (may include think aloud protocols)
Conduct site visits (contextual inquiry) (users doing their tasks at their work places)
Interview users, send questionnaires
Point‐of‐view (Synthesis, Interpret the results)
Contextual inquiry models (including affinity diagrams, etc.)
Why‐how ladder
Personas, roles
Use cases, scenarios, user stories, day‐in‐a‐life scenarios, etc.
Ideate (Generate ideas)
Brainstorming
User days, focus groups
Impose constraints
Prototype (Experiment)
Prototyping o Low fidelity: Wireframes, paper prototypes, simple HTML prototypes o High fidelity: More or less functional prototypes o Prototype for empathy o Prototype for test
Test (Improve)
User tests in the lab (may include think aloud protocols)
Remote user tests
User tests in the field
Feedback capture grid
User‐driven prototyping
Informal user tests (e.g. with colleagues, friends, etc.)
KPI studies
Other Storytelling
Card sorting
Source: PL Research
December 30, 2014 6
Infosys
The Art of Story Telling: Agile Development
Agile software development is a group of software development methods in which
requirements and solutions evolve through collaboration between self‐organizing,
cross‐functional teams. It promotes adaptive planning, evolutionary development,
early delivery, continuous improvement and encourages rapid and flexible response
to change.
In software development and product management, a user story is one or more
sentences in the everyday or business language of the end user or user of a system
that captures what a user does or needs to do as part of his or her job function. User
stories are used with agile software development methodologies as the basis for
defining the functions a business system must provide, and to facilitate
requirements management. It captures the 'who', 'what' and 'why' of a
requirement in a simple, concise way, often limited in detail by what can be hand‐
written on a small paper note‐card.
The Agile Manifesto is based on 12 principles: (Source: Wikipedia)
1) Customer satisfaction by rapid delivery of useful software
2) Welcome changing requirements, even late in development
3) Working software is delivered frequently (weeks rather than months)
4) Close, daily cooperation between business people and developers
5) Projects are built around motivated individuals, who should be trusted
6) Face‐to‐face conversation is the best form of communication (co‐location)
7) Working software is the principal measure of progress
8) Sustainable development, able to maintain a constant pace
9) Continuous attention to technical excellence and good design
10) Simplicity—the art of maximizing the amount of work not done—is essential
11) Self‐organizing teams
12) Regular adaptation to changing circumstances
Exhibit 8: Well‐known agile software development methods and/or process frameworks
Adaptive Software Development (ASD) Agile Modeling Agile Unified Process (AUP)
Crystal Clear Methods (Crystal Clear) Disciplined Agile Delivery Feature Driven Development (FDD)
Dynamic Systems Development Method (DSDM) Extreme Programming (XP) Lean software development
Kanban (development) Scrum Scrum‐ban
Source: Wikipedia, PL Research
December 30, 2014 7
Infosys
Why do we use story points instead of man days when estimating user stories?
In agile methodologies (e.g. SCRUM), the complexity/effort needed for user stories
are measured in Story points. Story points are used to calculate how many user
stories a team can take in iteration. In this framework for incremental product
development using one or more cross‐functional, self‐organizing teams are used. It
provides a structure of roles, meetings, rules, and artifacts. Teams are responsible
for creating and adapting their processes within this framework. It uses fixed‐length
iterations, called Sprints, which are typically 1‐2 weeks long (never more than 30
days). Teams attempt to build a potentially shippable (properly tested) product
increment every iteration.
Exhibit 9: Processes for different Agile Software Development
Source: Wikipedia, PL Research
Agile, Lean, and DevOps – Intervened together
Things like Lean, Scrum, Kanban, and DevOps seem to be important but it’s hard to
sort them out. Lean principles are the basis of entire product development flow. As
the path of improvement starts, there should be optimization for whole part of the
product and not just one part of the business.
Lean is the basis of Agile
Lean paradigm is used to optimize the end‐to‐end process which creates value for
the customer – from the initial idea to delivering final product. Lean principles focus
on flow more than anything else: bottlenecks in the process must be removed and
wasteful activities need to be identified and avoided.
December 30, 2014 8
Infosys
Exhibit 10: Blends all development activities into each iteration after fixed intervals
Source: PL Research
Build product development flow on top of Lean
Creating value for customers is all about finding and verifying product ideas,
implementing these ideas, and running them to benefit your users. There are several
excellent schools of thought can be used for structuring processes: Lean Startup and
Running Lean to hash out product ideas, Scrum, Kanban, and XP for building features
in an adaptable way, and DevOps to create a culture of focusing on delivering value
for the customer instead of only caring for technical issues.
The three aspects of product development flow
Lean Startup or Running Lean: Create a learning cycle during feature discovery.
From validating ideas to testing possible solutions, attack problems and keep
focus on solutions.
Scrum, Kanban, and XP: The typical agile processes to setup adaptive software
development for fast feedback cycles through early customer involvement.
DevOps: The cultural aspect of concentrating on business results rather than
technical details. DevOps incorporates a lot of lean principles, focusing on
improving the collaboration between developers and operations folks
December 30, 2014 9
Infosys
Exhibit 11: How are Lean, Agile, and DevOps related to each other?
Source: PL Research
Why Agile Is needed to address disruptive technologies adoption?
SMAC challenges enterprises to take advantage of the positive disruptions it
portends, while they operate at the rapid pace of innovation and change that SMAC
demands. The world is at the confluence of four technologies: social networking,
mobile computing, analytics, and cloud computing. Together, the technologies are
commonly abbreviated as SMAC.
Exhibit 12: Abide by guiding principles to drive a common mindset
Stakeholder Principles Mindsets
1. Partner with customers Focus on business value
2. Work towards a shared vision Advocate for constituency
3. Deliver incremental value Take pride in workmanship
4. Invest in quality Deliver on commitments
5. Empower team members Keep a solution perspective
6. Set clear accountability Foster a team of peers
7. Learn from experiences Practice good citizenship
8. Foster open communications Improve continually
9. Stay agile (expect & adapt to change) Understand qualities of service
Source: Capgemini, PL Research
Companies worldwide are finding value in embracing the disruption brought by
SMAC and the need to adopt the means to meet the challenges. The luxury of long
technology evaluation cycles, introspective analysis of systems, and long
deployment timeframes are giving way to rapid deployments and systems
designed for accuracy and speed. That means companies should adopt
methodologies that enable them to innovate at a faster pace and meet the fast
changing needs of customers. Agile is precisely the methodology for responding to
quickly morphing realities.
December 30, 2014 10
Infosys
Exhibit 13: The values SMAC elements really offer are
Source: PL Research
Emerging technologies are now a disruptor and should become a competitive
advantage. There are so many opportunities – each with its own costs, risks and
complications ‐ that it is difficult to cut through the noise and find the best way
forward. Because of these challenges, clients find themselves with two options:
Invest in an unproven strategy which could result in a significant loss in time,
money and opening new security threats.
Wait for proven concepts in the market and potentially lose market shares to
innovative competitors.
According to Zinnov, the impact of disruptive concepts such as mobility, cloud, big
data, and analytics, lead to an urgent need for the companies to challenge traditional
business models and embrace agile and flexible workplace environments. It has
therefore, become imperative for companies to re‐define their turnaround time,
design innovative solutions and adopt collaborative business models.
Develop change agility: As stated previously, the speed at which SMAC is
developing requires an exceptional agile methodology in order to react quickly to changes in market trends and behaviours. Because the SMAC playing field has
an evident first‐mover advantage, the agile capability is crucial to successful SMAC adoption. Invest in organisational or structural changes that allow quick decisions and frequent iterations.
Be proactive, not reactive ‐ Look for and experiment with new disruptive technologies (like: SMAC): The first‐move advantage is clear with SMAC
technology, so as the market moves towards more agile methodology, organisations should be proactive in experimenting and trialling new SMAC technology models. As stated previously, SMAC is still relatively nascent, leaving
the majority of opportunities as unrealised potential.
Being proactive mean innovation and no prior definition of problem: The
opportunity to grab the first mover advantage poses the challenge of no clear definition of “What customer wants?” Further, beyond the analytical research done on the consumers’ and employees’ interaction touch points, businesses
should also focus on listening to what customers and employees have to say. As consumers expect more power, knowledge, and interaction while walking through a purchasing decision, they become more accustomed to vocalising
their sentiment.
•Ecosystem Collaboration and Listening CapabilitySocial
•Reach and AppealMobile
•Insights and Rapid Action EmpowermentAnalytics
•Fast‐track GTM, Scale, and New Service ModelsCloud
December 30, 2014 11
Infosys
Exhibit 14: A compulsion of storytelling
Source: PL Research
Design Thinking – Key to develop disruptive technologies using Agile
Emerging technologies (ETs) are transforming and will transform the way clients do
business almost at the speed of light. When referring to ETs we are looking at Social,
Mobile, Analytics and Cloud, but also the Internet of Things (IoT), the New Way Of
Working (NWOW), wearable, drones, advanced analytics, etc.
These ETs are not just IT challenges but they are also business imperatives. ETs
innovation is coming from all angles ‐ it’s easy to become overloaded with the rapid
pace of technological change. In short, effective emerging technologies are now a
disruptor and should become a competitive advantage. There are so many
opportunities – each with its own costs, risks and complications ‐ that it is difficult to
cut through the noise and find the best way forward. The strong first foot forward is
source of competitive advantage for clients. Hence, paradigm like Agile is seeing
wide‐spread acceptance among IT vendors.
However, the key to success is in articulating the business problem and
understanding the clients’ need. We see the process of Design Thinking gives a
proven framework to do so.
Exhibit 15: A driving relationship between Design Thinking, Agile Development, & SMAC
Source: PL Research
Adopting SMACDevelop change
agility
Be proactive, not reactive ‐ Look for
and experiment with new disruptive technologies
Being proactive mean innovation and no prior definition of
problem
Design Thinking
Agile, Devops, Lean
SMAC Adoption
December 30, 2014 12
Infosys
Income Statement (Rs m)
Y/e March 2014 2015E 2016E 2017E
Net Revenue 501,330 539,957 611,160 697,061
Raw Material Expenses 307,670 324,429 369,317 423,882
Gross Profit 193,660 215,528 241,843 273,179
Employee Cost — — — —
Other Expenses 59,510 65,415 73,737 83,768
EBITDA 134,150 150,113 168,106 189,411
Depr. & Amortization 13,740 11,407 13,599 14,693
Net Interest — — — —
Other Income 26,690 32,383 35,246 38,951
Profit before Tax 147,100 171,089 189,753 213,669
Total Tax 40,620 48,760 51,233 55,554
Profit after Tax 106,480 122,329 138,520 158,115
Ex‐Od items / Min. Int. — — — —
Adj. PAT 106,480 122,329 138,520 158,115
Avg. Shares O/S (m) 1,144.0 1,144.0 1,144.0 1,144.0
EPS (Rs.) 93.1 106.9 121.1 138.2
Cash Flow Abstract (Rs m)
Y/e March 2014 2015E 2016E 2017E
C/F from Operations 121,870 119,687 139,926 158,099
C/F from Investing (50,030) (22,138) (25,058) (28,580)
C/F from Financing (30,660) (74,253) (79,965) (89,104)
Inc. / Dec. in Cash 41,180 23,295 34,903 40,415
Opening Cash 218,320 259,500 282,795 317,699
Closing Cash 259,500 282,795 317,699 358,114
FCFF 100,820 97,549 114,868 129,519
FCFE 100,820 97,549 114,868 129,519
Key Financial Metrics
Y/e March 2014 2015E 2016E 2017E
Growth
Revenue (%) 24.2 7.7 13.2 14.1
EBITDA (%) 16.1 11.9 12.0 12.7
PAT (%) 13.0 14.9 13.2 14.1
EPS (%) 13.0 14.9 13.2 14.1
Profitability
EBITDA Margin (%) 26.8 27.8 27.5 27.2
PAT Margin (%) 21.2 22.7 22.7 22.7
RoCE (%) 24.3 24.3 24.9 25.5
RoE (%) 24.4 24.5 25.1 25.6
Balance Sheet
Net Debt : Equity (0.5) (0.5) (0.5) (0.6)
Net Wrkng Cap. (days) — — — —
Valuation
PER (x) 21.0 18.3 16.2 14.2
P / B (x) 4.7 4.3 3.8 3.4
EV / EBITDA (x) 14.8 13.0 11.4 9.9
EV / Sales (x) 3.9 3.6 3.1 2.7
Earnings Quality
Eff. Tax Rate 27.6 28.5 27.0 26.0
Other Inc / PBT 18.1 18.9 18.6 18.2
Eff. Depr. Rate (%) 10.2 7.3 7.5 7.0
FCFE / PAT 94.7 79.7 82.9 81.9
Source: Company Data, PL Research.
Balance Sheet Abstract (Rs m)
Y/e March 2014 2015E 2016E 2017E
Shareholder's Funds 475,300 523,375 581,930 650,941
Total Debt — — — —
Other Liabilities 3,870 3,870 3,870 3,870
Total Liabilities 479,170 527,245 585,800 654,811
Net Fixed Assets 78,870 89,601 101,060 114,947
Goodwill 24,990 24,990 24,990 24,990
Investments 32,710 32,710 32,710 32,710
Net Current Assets 306,100 343,444 390,539 445,664
Cash & Equivalents 259,500 282,795 317,699 358,114
Other Current Assets 137,980 150,892 170,790 194,795
Current Liabilities 91,380 90,244 97,949 107,245
Other Assets 36,500 36,500 36,500 36,500
Total Assets 479,170 527,245 585,800 654,811
Quarterly Financials (Rs m)
Y/e March Q3FY14 Q4FY14 Q1FY15 Q2FY15
Net Revenue 130,260 128,750 127,700 133,420
EBITDA 36,200 36,410 34,410 37,730
% of revenue 27.8 28.3 26.9 28.3
Depr. & Amortization 3,610 3,600 2,300 2,900
Net Interest — — — —
Other Income 7,310 8,510 8,290 8,770
Profit before Tax 39,900 41,320 40,400 43,600
Total Tax 11,150 11,400 11,540 12,640
Profit after Tax 28,750 29,920 28,860 30,960
Adj. PAT 28,750 29,920 28,860 30,960
Key Operating Metrics
Y/e March 2014 2015E 2016E 2017E
Volume (persons month) 1,367,759 1,429,308 1,615,118 1,849,310
Pricing (US$ / Hr) 34 35 36 36
Currency (USDINR) 60.8 60.5 60.0 59.0
SW Devp. Cost (% of sales) 61.4 60.1 60.4 60.8
SG&A (% of sales) 11.9 12.1 12.1 12.0
Revenue (US$ m) 8,249 8,925 10,186 11,815
EBITDA Margin Expansion/(Erosion) (bps) (188.4) 104.2 (29.5) (33.3)
Tax Rate (%) 27.6 28.5 27.0 26.0
Source: Company Data, PL Research.
December 30, 2014 13
Infosys
Prabhudas Lilladher Pvt. Ltd.
3rd Floor, Sadhana House, 570, P. B. Marg, Worli, Mumbai‐400 018, India
Tel: (91 22) 6632 2222 Fax: (91 22) 6632 2209
Rating Distribution of Research Coverage PL’s Recommendation Nomenclature
37.4%
43.9%
17.8%
0.9%
0%
10%
20%
30%
40%
50%
BUY Accumulate Reduce Sell
% of Total Coverage
BUY : Over 15% Outperformance to Sensex over 12‐months
Accumulate : Outperformance to Sensex over 12‐months
Reduce : Underperformance to Sensex over 12‐months
Sell : Over 15% underperformance to Sensex over 12‐months
Trading Buy : Over 10% absolute upside in 1‐month
Trading Sell : Over 10% absolute decline in 1‐month
Not Rated (NR) : No specific call on the stock
Under Review (UR) : Rating likely to change shortly
DISCLAIMER/DISCLOSURES
ANALYST CERTIFICATION
We/I, Mr. Shashi Bhusan (BTech (IIT), MBA (IIM)), Mr. Hussain Kagzi (BMS), Research Analysts, authors and the names subscribed to this report, hereby certify that all of the views expressed in this research report accurately reflect our views about the subject issuer(s) or securities. We also certify that no part of our compensation was, is, or will be directly or indirectly related to the specific recommendation(s) or view(s) in this report.
Terms & conditions and other disclosures:
Prabhudas Lilladher Pvt. Ltd, Mumbai, India (hereinafter referred to as “PL”) is engaged in the business of Stock Broking, Portfolio Manager, Depository Participant and distribution for third party financial products. PL is a subsidiary of Prabhudas Lilladher Advisory Services Pvt Ltd. which has its various subsidiaries engaged in business of commodity broking, investment banking, financial services (margin funding) and distribution of third party financial/other products, details in respect of which are available at www.plindia.com
This document has been prepared by the Research Division of PL and is meant for use by the recipient only as information and is not for circulation. This document is not to be reported or copied or made available to others without prior permission of PL. It should not be considered or taken as an offer to sell or a solicitation to buy or sell any security.
The information contained in this report has been obtained from sources that are considered to be reliable. However, PL has not independently verified the accuracy or completeness of the same. Neither PL nor any of its affiliates, its directors or its employees accepts any responsibility of whatsoever nature for the information, statements and opinion given, made available or expressed herein or for any omission therein.
Recipients of this report should be aware that past performance is not necessarily a guide to future performance and value of investments can go down as well. The suitability or otherwise of any investments will depend upon the recipient's particular circumstances and, in case of doubt, advice should be sought from an independent expert/advisor.
Either PL or its affiliates or its directors or its employees or its representatives or its clients or their relatives may have position(s), make market, act as principal or engage in transactions of securities of companies referred to in this report and they may have used the research material prior to publication.
PL may from time to time solicit or perform investment banking or other services for any company mentioned in this document.
PL is in the process of applying for certificate of registration as Research Analyst under Securities and Exchange Board of India (Research Analysts) Regulations, 2014
PL submits that no material disciplinary action has been taken on us by any Regulatory Authority impacting Equity Research Analysis activities.
PL or its research analysts or its associates or his relatives do not have any financial interest in the subject company.
PL or its research analysts or its associates or his relatives do not have actual/beneficial ownership of one per cent or more securities of the subject company at the end of the month immediately preceding the date of publication of the research report.
PL or its research analysts or its associates or his relatives do not have any material conflict of interest at the time of publication of the research report.
PL or its associates might have received compensation from the subject company in the past twelve months.
PL or its associates might have managed or co‐managed public offering of securities for the subject company in the past twelve months or mandated by the subject company for any other assignment in the past twelve months.
PL or its associates might have received any compensation for investment banking or merchant banking or brokerage services from the subject company in the past twelve months.
PL or its associates might have received any compensation for products or services other than investment banking or merchant banking or brokerage services from the subject company in the past twelve months
PL or its associates might have received any compensation or other benefits from the subject company or third party in connection with the research report.
PL encourages independence in research report preparation and strives to minimize conflict in preparation of research report. PL or its analysts did not receive any compensation or other benefits from the subject Company or third party in connection with the preparation of the research report. PL or its Research Analysts do not have any material conflict of interest at the time of publication of this report.
It is confirmed that Mr. Shashi Bhusan (BTech (IIT), MBA (IIM)), Mr. Hussain Kagzi (BMS), Research Analysts of this report have not received any compensation from the companies mentioned in the report in the preceding twelve months
Compensation of our Research Analysts is not based on any specific merchant banking, investment banking or brokerage service transactions.
The Research analysts for this report certifies that all of the views expressed in this report accurately reflect his or her personal views about the subject company or companies and its or their securities, and no part of his or her compensation was, is or will be, directly or indirectly related to specific recommendations or views expressed in this report.
The research analysts for this report has not served as an officer, director or employee of the subject company PL or its research analysts have not engaged in market making activity for the subject company
Our sales people, traders, and other professionals or affiliates may provide oral or written market commentary or trading strategies to our clients that reflect opinions that are contrary to the opinions expressed herein, and our proprietary trading and investing businesses may make investment decisions that are inconsistent with the recommendations expressed herein. In reviewing these materials, you should be aware that any or all o the foregoing, among other things, may give rise to real or potential conflicts of interest.
PL and its associates, their directors and employees may (a) from time to time, have a long or short position in, and buy or sell the securities of the subject company or (b) be engaged in any other transaction involving such securities and earn brokerage or other compensation or act as a market maker in the financial instruments of the subject company or act as an advisor or lender/borrower to the subject company or may have any other potential conflict of interests with respect to any recommendation and other related information and opinions.