An appetite for growth

www.cio.com |  Development Add a new comment

YOU MIGHT CALL Lloyd DeVaux the wizard of bank acquisitions. In 1998 alone, DeVaux, executive vice president and CIO at Union Planters, oversaw the technical side of 18 different bank acquisitions. In 1999, there were five more acquisitions. In fact, DeVaux has been involved in more than 50 bank acquisitions since he joined the $33 billion Memphis, Tenn.-based bank holding company in 1994. It's enough to make anyone's head spin.

But here's the kicker: These acquisitions didn't happen one at a time, in orderly fashion. Between 1989 and 1999, one of the growth strategies Union Planters pursued was continuous acquisition -- that is, it was in the process of acquiring various smaller banks all the time. Many acquisitions were underway at once, as were multiple systems conversions. And the banks being acquired were scattered across the country. The result? Lloyd DeVaux was one very, very busy man.

Continuous acquisition is a strategy that many companies -- particularly in the banking industry -- have chosen to pursue as a means of growth. "It's a lot easier to grow by acquisition than it is to grow organically by building new banks and trying to win new depositors," says Mark Feldman, partner and managing director of the global M&A consulting division of PricewaterhouseCoopers in San Francisco. But a continuous acquisition strategy is much less certain of success today than it was a few years ago, because the pace of acquisitions has driven up prices for smaller institutions, says Feldman, who is also coauthor of Five Frogs on a Log: A CEO's Field Guide to Accelerating the Transition in Mergers, Acquisitions, and Gut Wrenching Change (HarperCollins Publishers, 1999).

Indeed, Union Planters itself has not made any new acquisitions recently (DeVaux declines to speculate about the company's future plans), and it's not yet clear whether the strategy has paid off for the bank. The 18 acquisitions in 1998 alone increased UP's assets by 78 percent, from $18 billion to $32 billion. But in his letter to shareholders in the company's 1998 annual report, Chairman and CEO Benjamin W. Rawlins noted the company had achieved only half the $100 million savings in operating costs it had projected from those acquisitions. That's largely because in many cases UP had to keep redundant staffs in place for longer than it had anticipated. Expenses during the acquisition period were also higher than anticipated, Rawlins noted, though the company expected to recoup the projected savings in 1999. As a result, profitability did not grow as quickly as expected.

Yet even with the chaos that just a single acquisition can cause, UP has managed to preserve the good graces of its customers. Customer retention has been better than average for a company in the middle of continuous acquisition, says DeVaux.

In any case, the past few years have made Union Planters in general and DeVaux in particular an authority on continuous acquisition. The following are best practices the company has culled for simultaneously managing multiple acquisition projects.

Spot the Bad Deals

UP's continuous acquisition strategy was simple: Buy a smaller bank, install standard IT systems and operate the newly merged entity much more cheaply than it could be as a separate organization. In general, the banks acquired were small compared with UP, and they often outsourced their IT operations. So, for UP, eliminating the acquired bank's outsourcer and bringing IT back in-house promised to save a lot of money. Overall, the idea was to gain the target bank's assets (and customers) while losing much of its expenses. In addition, the acquisitions gave UP an instant customer base in areas of the country in which it had not previously operated.

In order to reap those benefits, though, Union Planters had to pay careful attention to making sure -- in advance -- that a deal was right. As CIO, DeVaux was often part of the UP executive team that went onsite to evaluate target banks in advance of any deal, and his input was considered in the decision whether or not to go through with the proposed acquisition. As such, it was his job to speak up -- before both sides signed on the dotted line -- about any potentially serious systems problems.

For example, for each proposed acquisition DeVaux estimated the value of buying out the target bank's outstanding service contracts, such as PC hardware leases or mainframe application maintenance. If there was a stiff penalty to void one of the target bank's contracts -- say, a $1.5 million price tag to walk away from a mainframe lease -- and the value of the deal as a whole was small -- say $500 million -- that would be a deal killer.

    Add a comment

    Post a comment using one of these accounts
    Or join now
    At least 6 characters

    Note: Comment will appear soon after you have activated your account.
    Obscene/spam comments will be removed and accounts suspended.
    The information you submit is subject to our Privacy Policy and Terms of Service.

    ITworld LIVE

    DevelopmentWhite Papers & Webcasts

    White Paper

    HP NonStop SQL Fundamentals whitepaper

    This whitepaper offers a detailed look into the fundamentals of HP NonStop SQL solutions. See how this system delivers unprecedented levels of application availability with fail-safe data integrity and meets the needs of enterprises with large-scale business critical applications.

    White Paper

    Nebraska Medical Center case study

    See how the Nebraska Medical Center implemented a SQL solution to make information more readily available to streamline operations, improve patient care and facilitate medical research with an enterprise solution running on HP NonStop servers.

    White Paper

    Concepts of NonStop SQL/MX

    For DBAs and developers who are familiar with Oracle solutions and want to learn about NonStop SQL/MX, this whitepaper provides an overview of the similarities and differences between the two products-with a specific focus on implementation.

    White Paper

    6 Things Your CIO Needs to Know About Requirements

    If your organization is not predictably successful on technology projects, there is likely an issue in requirements. CIOs must take action and own requirements maturity improvement. There are 6 main things a CIO must know about requirements.

    Webcast On Demand

    User Experience Monitoring

    In this webinar, you will learn hints & tips for improving end-user response times from Forrester Research analyst, Jean-Pierre Garbani.

    Sponsor: Nimsoft

    See more White Papers | Webcasts

    Ask a question

    Ask a Question