Let's Not Call It Bonding Together
One of the press releases claimed that the development groups from the two companies were coming together, "bonding", to create "synergy" and the greatest ever talent technology team.
This may be what will happen, but acquisitions rarely result in bonding. Instead, the event takes on the closing that it really is, with disruption and unpleasantness for all parties involved. I received my education in bonding together in third grade when my elementary school ‘merged' with another, and I ended up walking an extra mile to get to school each day.
The acquirer might state that they are preparing a sound upgrade path for their affected clients, but software platforms do not mesh easily. Soon the cozy pillow talk of mutual benefits subsides, and the nasty task of porting a client from one environment to another begins. This is a very tough task since even the best IT people tend to have trouble handling two distinct platforms at the same time.
These incompatibilities do not always surface at the beginning of the merger. In fact, things may begin with a honeymoon period during which top management declares that the acquired company will continue to run as a separate business entity. After three months or so, the rumbling begins to get loud, and after six months, a complete management change and exodus of staff takes place.
This may not happen here, but if it does fast moving competitors will move in to serve their neglected customers.
Gregg Dourgarian
CEO, Tempworks Software