Skip to main content

Vendors Survival: Lessons from Zapthink's acquisition


Dovel Technologies is buying Zapthink. It is the first time I read about Dovel. 


Unlike Dovel, Zapthink is well known to me. As a SOA expert, I read Zapthink's analysis of SOA and other Architectural topics as well as short articles named ZapFlash


SOA is Zapthink's major field of expertise. The small company headed by Ronald Schmelzer and Jason Bloomberg provides SOA training and certification, SOA Consulting Services and SOA Research.


Schmelzer and Bloomberg's work reveals deep understanding and vast knowledge of SOA.


The challenges facing small Analysts and Consultants are incomparable to challenges facing a lot larger company. 
Like small software vendors many of the small Consulting and/or Market Analysis companies will not survive.


The circumstances are similar to the circumstances of smaller software vendors described in my post titled: 
Vendors Survival Guide: Supermarket Grocery and Kiosk  as well as in other Vendors Survival posts I wrote e.g. Software AG , SUN ,HP


Gartner, the largest IT Research company, aquired smaller companies like Meta Group, AMR Research and Dataquest and Forrester Research acquired Giga Information Web.


However, due to Zapthink's remarkable success it is interesting to analyze its acquisition and lessons we can learn from its acquisition.  


The acquisition
Dovel perspective of the acquisition emphasizes the strengthening of its SOA expertise to its USA based governmental clients. 


Jason Bloomberg's view is that the acquisition is part of Dovel's strategic plan to expand their scope, Capabilities and thought leadership in Service Oriented Architecture, Cloud Computing and related technologies as well as an opportunity to add new people to the Zapthink team three of them will be regular contributors to the ZapFlash newsletter.


Ronald Schmelzer will serve as Zapthink's consultant for few months and afterwards will be moving on. His perspective is the most interesting because he was a founder of Zapthink, because he is moving on and because he already sold ChannelWave, a Boston based software company.
  
According to citybizlist's Brian Wolak "Schmelzer is convinced that small businesses are going to dominate the landscape in the years to come, with a combination of former unemployed workers linking up with small businesses, a general backlash against big corporations, and the government's emphasis on kick-starting the economy through startups and innovation."







My Take



The success of a small consulting company highly depends upon key people.
 As far as Zapthink is concerned there are two key figures: Schmelzer and Bloomberg, so Schmelzer departure is a huge challenge. It is not easy to add or replace key figures in a small company. In case of too much success a company challenge is how to handle the large volume of tasks, while preserving the quality of deliverables. On 2007 David Linthicum joined Zapthink and was a contributor to the ZapFlash, but after a short period of time he was no longer a contributor to Zapthink efforts.

Evangelists or Thought Leaders are a must for new paradigm or a revolutionary technology not for a mature paradigm.
When the paradigm, architecture or technology is matured the number of experts who understand it or experienced it is growing and it is less a matter of Thought Leading and more a matter of actually deploying it. SOA is now Mainstream and mature. 


Dovel is a company which helps governmental agencies in USA to deploy SOA as well as other paradigms and not a Thought Leader. The new Zapthink's focus will probably be SOA implementations. 

A small company struggles to keep its position as a Thought Leader when newer paradigms or Technologies emerge.
If you are a Thought Leader in a new paradigm and a newer paradigm emerges, probably other experts will be better positioned for the newer paradigm. 
Examining the illustration following this paragraph could provide an explanation.  


New Technologies and Paradigms time overlap with older paradigms is the reason.  A Thought Leader in a relatively old paradigm is too busy in assignments related to this paradigm and therefore is lagging behind new fresh Thought Leaders of the new paradigm. 


This phenomenon is depicted in the simplified illustration beyond this line.  


The illustration depicts three related paradigms, which are not exactly comparable to each other. SOA is essentially an Enterprise Architecture. BPM is a Business Technology and Cloud Computing is more Operational approach. Cloud Computing is a general term including a variety of technologies and concepts, in different Maturity levels 


The point, which could be generalized to other paradigms and technologies, is that a small company based on one or two SOA Thought Leaders was not capable to allocate Thought Leading resources for thought leading BPM in the time BPM emerged. It was not able to allocate these resources for thought leading in Cloud Computing when it emerged.


There are many talented people, so other talented people explore the new technologies or paradigms before SOA became a mature technology and the SOA experts, saturated with many SOA related tasks, do not have the time to dive deeply into BPM or Cloud Computing.

Finally, the SOA Thought Leader have no other choice when the demand is for Cloud Computing thought leaderships, while the SOA demand is more for practical day to day skills: Architects, System Analysts and Developers etc.


But it may be too late for the SOA Thought Leader to replicate his  success: other people who started earlier in Cloud Computing are positioned better. 


Some of the SOA Thought Leaders will close the gap and become a Cloud Computing Thought Leaders, but it will take long time to do this. 


The challenge described in the last section face small companies such as Zapthink, as far as large consulting companies are concerned they can allocate enough resources: some potential Thought Leaders could  specialize in the new paradigm (e.g. Cloud Computing), while others take care of a previous buzz such as SOA.



  

Comments

Popular posts from this blog

The mainframe: still alive and kicking

Recently, I was interviewed by  Pcon   (unfortunately the link points to an Hebrew only site) as part of debriefing on Legacy Systems.  Pcon is an Israeli company investigating IT topics by quoting professional articles and interviewing experts. They publish the results of the investigations including practical recommendations. This post is mainly about topics raised by me during the interview, but not included in the debriefing, which will be published.    What are Legacy Systems? The term Legacy Systems refers to old application systems and/or veteran technologies still in use.  Usually, the term Legacy Systems is associated with: 1. Mainframe Hardware e.g. IBM System z and its Operating Systems or Proprietary Servers and Operating Systems such as HP Alpha and OpenVMS Operating System, IBM AS/400 and OS/400   Operating System. 2. Development and Production Environments, e.g. COBOL , Natural and DBMS systems such as Adabas  ...

Will Business and IT Aligned?

For decades we are talking about closing the gap between business and IT , but the gap is still as wide as it was. In the beginning of the ERP era, we focused on aligning Business Processes and Core Systems, but in most enterprises we failed. SOA was the next alignment promise: defining the SOA Services in Business boundaries instead of Technical boundaries, should narrow the gap. However, despite of SOA Business Value ( Agility and Reuse )  in most enterprises,  the large Business-IT Gap remained as large as it was.  The IT Community aimed at the next alignment attempt: SOA is technical and BPM is its Business related complement.  Will the current BPM based alignment attempt succeed? I do not know, but Nick Heath's article  titled: Stop doing what the vendors tell you, CIOs told , published in  Tech Republic , suggests that the root of the problem is not Technological .   Stop Doing What the vendors Tell You Nick Heath's article is based ...

Vendors Survival: Will Software AG Survive until 2019?

This post is another post in the Vendors Survival series following posts on Microsoft , Google , HP , Sun and EMC . On July 14 th Software AG and IDS Scheer announced that Software AG is going to take over IDS Scheer . The intended acquisition is an opportunity to add another post in my Vendors Survival posts series. A brief history of Software AG Mainframe products Software AG is larger than any German software company except SAP . It was established in the Mainframe age (in 1969). I worked with many customers, who used and some of them are still using, its two flagship products Adabas and Natural . Although these products support many platforms, their main platform is IBM Mainframe. Adabas is a database and Natural is a development environment. Like other pairs of Database and Development Environment in the mainframe environment (e.g. Ideal and Datacom , Mantis and Supra) build by the same vendor, they are tied together. As a result, although it is possible t...