<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<!--Web 2.0 Content Powered by MyST Blogsite® (http://blogsite.com)-->
<!--A service of MyST Technology Partners, Inc. (http://myst-technology.com)-->
<?xml-stylesheet href="http://blog.updataadvisors.com/public/styles/etc/object.xsl" type="text/xsl"?>

<?myst-baseUrl http://blog.updataadvisors.com/public/?>

<MySmartChannels Public="true" UserID="205196" dT="89" t0="1228187078301">
     <GetChannelItem_Result>
      <Item>
       <Resource>
        <ObjectID>193270</ObjectID>
        <ObjectClass>Resource</ObjectClass>
        <OwnerID ObjectClass="Domain" Title="[Weblog] Tech M&amp;A Talk">125361</OwnerID>
        <CreatedByID ObjectClass="User" Title="mparent">126226</CreatedByID>
        <ModifiedByID ObjectClass="User" Title="fbartolomey">200444</ModifiedByID>
        <CreateTime Title="2007-12-26 20:26:03 EST">1198718763443</CreateTime>
        <ModifyTime Title="2008-06-26 16:06:09 EDT">1214510769516</ModifyTime>
        <SecurityModel>Controlled</SecurityModel>
        <Name>Wipro + Capgemini: Why Mess With Success?</Name>
        <Summary>IT Services M&amp;A Requires Strong Mutual Interest in Addition to Complementary Business Models</Summary>
        <Description>&lt;p&gt;Over the holiday weekend, &lt;a title="Wipro Likely to Place Capgemini Bid" href="http://www.hindustantimes.com/StoryPage/StoryPage.aspx?id=3f61a133-aa6f-41d2-9695-b37793bc57de" target="_blank"&gt;The Hindustan Times of India reported&lt;/a&gt; that Wipro was &amp;quot;likely&amp;quot; to place a bid for the Paris-based global consulting firm Capgemini.&amp;nbsp; I stand ready to be corrected if this deal comes to fruition or if a bid is actually made.&amp;nbsp; But in reading the coverage from India and France, I felt like I had watched this play before: back in December 2001 the Times of India announced that Wipro had &amp;quot;decided to acquire&amp;quot; the US-based telecom consulting firm, The Management Network Group (NasdaqGM: TMNG).&amp;nbsp; At that time, other than the Indian press, no one seemed to know anything about this deal, and the silence which followed the &amp;quot;announcement,&amp;quot; was affirming -- there was no real deal here.&amp;nbsp; TMNG remains publicly-traded and independent today.&lt;/p&gt;&lt;p&gt;We are a long way from 2001, and the ability of offshore IT services firms to execute on cross-border M&amp;amp;A transactions is assured.&amp;nbsp; One need only look at Wipro's $600 million acquisition of Infocrossing, Caritor's combination with Keane&amp;nbsp;, and Patni's acquisition of Taratec for proof, if any is needed.&amp;nbsp; But I have serious doubts about the viability and reality of a Wipro/Capgemini deal.&amp;nbsp; To begin with, Wipro is going to need to muster considerable cash for this transaction.&amp;nbsp; As of September 30, 2007, Wipro had $1.1 billion in cash and ST Investments, well short of what would likely be demanded by Capgemini shareholders in a transaction for a company with a market cap of about $9 billion last week -- even after taking in to account Cap&amp;rsquo;s $660 million in net cash.&amp;nbsp; There is no arguing that Wipro's market cap is almost double that of Cap and that a stock swap is theoretically possible.&amp;nbsp; But this gets to the crux of my thesis on why this deal is nonsensical.&amp;nbsp; The offshore IT services vendors, including Wipro, have achieved incredible stock market valuations through a rare combination of high growth, high profitability, and recurring revenue models with great forward cash flow visibility.&amp;nbsp; A combination with a player the size of Cap would completely change Wipro's business model, and move it away from its traditional peers.&amp;nbsp; These are possible reasons why the&amp;nbsp;&lt;a title="Forbes.com: Infosys Rumored to Eye Bid for Capgemini" href="http://www.forbes.com/2007/06/29/infosys-capgemini-rumors-market-equity-cx_rd_0629markets3.html" target="_blank"&gt;Infosys bid for Capgemini rumored earlier this year&lt;/a&gt; never materialized.&lt;/p&gt;&lt;p&gt;Cap is a very large fish for Wipro to swallow.&amp;nbsp; While it would move Wipro up the value chain into higher-end business consulting and move Wipro physically closer to its clients, it would also drive down Wipro's margins, slow its growth rate, pose cross-cultural personnel turnover risks, and ultimately undermine its stock market valuations.&amp;nbsp; It would face daunting French regulatory scrutiny, not to mention potential government intervention if French public reaction is loud.&amp;nbsp; It certainly could not be executed in a hostile environment, a point underscored by Philippe Grangeon, a member of Capgemini's executive committee, in his &lt;a title="Bloomberg.com, Europe: Cap Gemini Gains..." href="http://www.bloomberg.com/apps/news?pid=20601085&amp;sid=avC4vVNV872E&amp;refer=europe" target="_blank"&gt;quote&lt;/a&gt; last Monday: &amp;quot;...we affirm our conviction that any hostile takeover in this sector is doomed to fail.&amp;quot;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Setting aside growth rates, margins, and business models, Grangeon's comment is true for almost all IT services M&amp;amp;A transactions.&amp;nbsp; It is hard to imagine a hostile acquisition of a business in which employee talent and time are the primary operating assets.&amp;nbsp; Even in the friendliest IT services M&amp;amp;A transactions, there is usually hand-wringing and negotiating about the retention of staff at all levels, which could never be the case in an unwelcome transaction.&amp;nbsp; As a multinational organization, Cap understands this.&amp;nbsp; It has executed on many successful international transactions which otherwise would have failed in a hostile setting.&amp;nbsp; In 2007, Cap made a $1.25 billion bet that it could favorably navigate multi-shore waters again through its friendly acquisition of Kanbay International.&amp;nbsp; A similarly friendly approach is underway between Keane and Caritor, which are forging a transformative combination that would have looked very unlikely just a few years ago.&amp;nbsp;&lt;/p&gt;&lt;p&gt;If Capgemini and Wipro had the strongest mutual desire to effect such a combination of their businesses, it would still be a very complex undertaking.&amp;nbsp; That mutual desire seems not to be the case based on Capgemini's initial negative reactions to the rumors, but the Indian press loves this sort of speculation.&amp;nbsp; If I were standing in Wipro's shoes, I would take a serious pause to contemplate why I would want to radically jettison my business model and leave my peer group, to join the ranks of the slow growth IT consulting behemoths.&amp;nbsp; I don't see the value creation in that.&amp;nbsp; But I stand ready to be corrected...&lt;/p&gt;</Description>
        <ResourceTypeID ObjectClass="ResourceType" Title="Item:Link">9</ResourceTypeID>
        <ContentType>application/xml</ContentType>
        <ContentDocument>
         <ItemProperties>
               <CommonProperties>
                <Hidden>false</Hidden>

                <Keywords>
                 <Keyword>Capgemini</Keyword>

                 <Keyword>Caritor</Keyword>

                 <Keyword>cross-border M&amp;A</Keyword>

                 <Keyword>Indian IT M&amp;A</Keyword>

                 <Keyword>Infosys</Keyword>

                 <Keyword>IT services</Keyword>

                 <Keyword>Keane</Keyword>

                 <Keyword>Wipro</Keyword>

       </Keywords>

                <Links>
                 <Link>
                  <Title>Updata Advisors IT Services M&amp;A Transactions</Title>

                  <Synopsis>Recent IT Services mergers and acquisitions deals completed by Updata Advisors</Synopsis>

                  <URL>http://updataadvisors.com/transactions.asp?sector=13&amp;level2id=54&amp;level2name=IT%20Services&amp;sectorname=ALL%20SECTORS</URL>

        </Link>

       </Links>

      </CommonProperties>

               <ns3:Details xmlns="urn:MyST-Technology.Structured.Details" xmlns:ns3="urn:MyST-Technology.Structured.Details">
                <ns3:Collection name="Right Justified Image (*)" type="urn:MyST-Technology.Structured.Collection.Captyx.Right_Justified_Image">
                 <ns3:Attribute name="Image" type="url:image" value="http://www.updataadvisors.com/data/team_images/Parent.jpg"/>

                 <ns3:Attribute name="Image Link" type="url" value="http://updataadvisors.com/team.asp?module=press&amp;newsid=30"/>

                 <ns3:Attribute name="Image Tooltip" type="text" value="Michael Parent"/>

                 <ns3:Attribute name="Height" type="number" value="106"/>

                 <ns3:Attribute name="Width" type="number" value="80"/>

                 <ns3:Attribute name="Caption" type="text" value="Michael Parent, Updata Advisors"/>

                 <ns3:Attribute name="Caption Link" type="url" value="http://updataadvisors.com/team.asp?module=press&amp;newsid=30"/>

                 <ns3:Attribute name="Caption Tooltip" type="text"/>

       </ns3:Collection>

      </ns3:Details>

               <RemoteInfo>
                <UserAgent>Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322; .NET CLR 2.0.50727; InfoPath.1)</UserAgent>

                <RemoteHost>127.0.0.1</RemoteHost>

                <RemoteAddr>127.0.0.1</RemoteAddr>

                <RemoteUser>fbartolomey</RemoteUser>

                <ForwardedFor>208.82.213.22</ForwardedFor>

      </RemoteInfo>

     </ItemProperties>
        </ContentDocument>
       </Resource>
       <Shares/>
       <Subjects/>
       <UserPermissions>
        <CanDelete>false</CanDelete>
        <CanDiscover>true</CanDiscover>
        <CanEdit>false</CanEdit>
        <CanEditPermissions>false</CanEditPermissions>
        <CanRead>true</CanRead>
       </UserPermissions>
       <CommentInfo>
        <CommentChannelRef>
         <ChannelID/>
        </CommentChannelRef>
        <Comments/>
       </CommentInfo>
       <Views>
        <SourceID ObjectClass="Channel" Title="[Weblog] Tech M&amp;A Talk">125361</SourceID>

               <View>
                <Name>blog</Name>

                <Model>blogsite/UpdataAdvisors/web</Model>

                <Style/>

                <Scheme/>

       </View>

               <View>
                <Name>edit-item</Name>

                <Model>blogsite/UpdataAdvisors/web</Model>

                <Style/>

                <Scheme/>

       </View>

               <View>
                <Name>left</Name>

                <Model>blogsite/UpdataAdvisors/left-content</Model>

                <Style/>

                <Scheme/>

       </View>

               <View>
                <Name>right</Name>

                <Model>blogsite/UpdataAdvisors/right-content</Model>

                <Style/>

                <Scheme/>

       </View>

               <View>
                <Name>wide</Name>

                <Model>blogsite/UpdataAdvisors/wide-content</Model>

                <Style/>

                <Scheme/>

       </View>

      </Views>
        <Views>
         <SourceID ObjectClass="Channel" Shared="true" Title="[Public] The Updata Circuit -- What's New">205219</SourceID>

                <View>
                 <Name>blog</Name>

                 <Model>blogsite/UpdataAdvisors/whatsnew</Model>

                 <Style/>

                 <Scheme/>

       </View>

                <View>
                 <Name>edit-item</Name>

                 <Model>blogsite/UpdataAdvisors/web</Model>

                 <Style/>

                 <Scheme/>

       </View>

                <View>
                 <Name>left</Name>

                 <Model>blogsite/UpdataAdvisors/left-content</Model>

                 <Style/>

                 <Scheme/>

       </View>

                <View>
                 <Name>right</Name>

                 <Model>blogsite/UpdataAdvisors/right-content</Model>

                 <Style/>

                 <Scheme/>

       </View>

                <View>
                 <Name>wide</Name>

                 <Model>blogsite/UpdataAdvisors/wide-content</Model>

                 <Style/>

                 <Scheme/>

       </View>

      </Views>
        </Item>
       </GetChannelItem_Result>
      </MySmartChannels>
