#1206 2003 · PeopleSoft · Enterprise software
PeopleSoft made a successful Oracle takeover trigger refunds Oracle itself would owe
the problem
Oracle's hostile bid scared buyers away from signing PeopleSoft contracts that might get killed after acquisition
background
In June 2003 Oracle launched a hostile bid to acquire rival PeopleSoft. The announcement alone spooked enterprise customers, who hesitated to sign multi-year software contracts for a product line that Oracle might discontinue after buying it, threatening to strangle PeopleSoft's sales pipeline long before the takeover fight was even decided.
PeopleSoft could reassure customers with verbal promises, but a hostile acquirer's promises mean nothing once it owns the company, and litigation to block the bid outright could take years while sales quietly bled out in the meantime. PeopleSoft needed customer confidence to survive even if Oracle actually won.
what everyone would do
Publicly reassure customers that support would continue, or race to court seeking an injunction against the bid - neither made the underlying risk to customers go away, and both left Oracle free to simply wait PeopleSoft's sales pipeline out.
what they saw
A bidder's future ownership is itself an asset a target can attach a liability to. By binding the guarantee to whoever controlled the company, PeopleSoft made Oracle's own victory the event costing Oracle the most.
the move
PeopleSoft launched a Customer Assurance Program guaranteeing that if an acquisition led the new owner to stop developing or supporting a customer's product within a set window, PeopleSoft - or whoever bought it, Oracle included - would pay that customer two to five times what they'd spent on the software.
why it works
The guarantee runs with the company regardless of who owns it, so it can't be waived away by a change of control; it reassures customers with a number, not a promise; and it forces the acquirer to either raise its price to cover the contingent liability or watch sales keep flowing under the guarantee.
the payoff
Over half of new license revenue tied to the guarantee; potential liability hit nearly $800 million - a bill Oracle would owe if it won.
where it breaks
It needs a credible balance sheet to make the guarantee believable and a customer base that values contractual protection over price. A determined, well-capitalized acquirer can simply absorb the liability into its bid and proceed anyway, as Oracle ultimately did.
what came after
Oracle called the program a 'poison pill' that made the deal financially unworkable and fought it in court and in its bid price; PeopleSoft let the program lapse in 2004 once a friendlier price was negotiated, but it had preserved sales for nearly a year and forced Oracle to substantially raise its offer before finally completing the $10.3 billion deal in 2005.
references
- [1]PeopleSoft renews refund offer to counter Oracle takeover attemptComputerworld, 2003computerworld.com
- [2]Oracle slams PeopleSoft refund offerNBC News, 2003nbcnews.com