Sunday, March 20, 2016

WhatsApp for Business


Over the past four years, I have grown really fond of WhatsApp. It is a wonderful application that offers a simple interface, is ad-free and is extremely easy to install, so much that I could really teach my mother and grandparents to use WhatsApp in 5 minutes. At the same time the notifications are very subtle unlike some of the other apps such as, Groupme. WhatsApp has also been making critical updates such as receipt updates with two blue ticks and voice calls over internet that gained widespread acceptance, thereby increasing its monthly active user base to 1 billion accounting for 42 billion messages per day by Feb 2016. In contrast, Twitter has only 300M monthly active users, Facebook messenger has 700M active users and Facebook has only recently crossed 1B daily active users. Further, applications such WhatsApp are driven by network externalities, where the application become more useful by having more users.
Source: Statista
Despite its stellar success in increasing its user base, WhatsApp has had limited success in developing a viable business model. It began charging a meek subscription fee of $1 per year and yes, I was one of those ardent fans to pay the amount (thought I want my dollar back now). But even with this moderate fee, not every user is willing to pay and the company generated only $20M in revenues in 2015, i.e. 2% of its user base paid the subscription fee. The revenues were barely able to cover the costs of developing and sustaining WhatsApp. It is clear that this is an unstainable model let alone being a model for growth.
If WhatsApp wants to continue growing its user base and yet generate a sustainable business model then it has to rightly shun its subscription fee model and begin catering to business segment, which has the spending power. In fact, forecast by Gartner suggests that enterprise spend on application software is expected to grow to $201B by 2020 from $140B in 2015 and WhatsApp can make more money, nearly $140M, by capturing 0.1% of the overall market than it would otherwise.

Source: Gartner
WhatsApp should consider catering to both B2C and B2B businesses and has various service options to offer for the business segment.
  1. Ordering
  2. Customer feedback
  3. Customer assistance
  4. Real time support
  5. Team communication and coordination
Companies such as WeChat have already started capturing this market in Asia and WhatsApp still has a long way to go. So, if WhatsApp wants to get a piece of the pie, it better start rolling out these services quickly.



Saturday, March 5, 2016

Sales in Technology Companies

Sales by definition is a way of bringing products or services to market so that they can be purchased by consumers. In any business, sales is the activity that generates revenues and is undeniably the most important activity. Robust manufacturing processes, or lean the cost structure or progressive management team cannot keep a business alive for long without the financial horse power. Unless an investor is pumping cash into the business, sales is probably the only path for a company to generate revenues to be in a self-sustaining business model is of utmost importance.
There are broadly two main ways of selling goods and services:
1.    Direct
2.    Indirect
Direct sales, as you may already know, is the process of selling goods and services directly to consumers without the involvement of an outsider or a third party. Direct sales, also known as B2C - Business to Consumer sales, includes anything from selling directly on a company website to employing sales folks to reach out to customers to sell products and services. Direct selling has some key benefits associated with it, namely:
1.    High level of influence over the consumer
2.    Ability to get direct feedback about products and services from the customer
3.    Complete ownership of the profits
Direct sales process typically tends to have a shorter sales cycle and lower price points. Also as direct sales team reaches the consumers directly, so they face with lesser number decision makers in the process. While these benefits make direct selling to be the best strategy but on further consideration this may not be the case always. Direct sales come with some hidden (and no to hidden) costs – salaries, and overheads. Also, it may be difficult to reach all types of consumers in different countries through a direct sales force. Imagine how it would sound if Apple or Microsoft have to reach each consumer directly to sell their products all the time.
So companies resort to indirect strategies of selling goods and services. Indirect sales is the process of selling goods and services through 3rd party websites, market places and channels. Indirect sales is also known as B2B, Business to Business sales, or channel sales. There are many different types of channels for a company to choose from depending on the nature of their products and services, and their business model. Some of more common ones for a technology company are namely:
1.    Retail
2.    Value Added Resellers (VARs)
3.    Service Providers
4.    Distributors
5.    System integrators
6.    Managed service providers
7.    Independent software vendors
8.    Original Equipment manufacturers

Retail: These are outlets such as Walmart etc that directly stock vendors’ products and sell them directly to consumers. Retails stores offer consumers the experience of physically touching and browsing before they can buy a product, something that big companies cannot offer on a large scale to consumers.   
Value Added Resellers: These are companies that resells products / services and provides value beyond order fulfillment. Traditionally, a VAR put together products from a single or multiple vendors along with its customer applications and sell as a turnkey solution. These days, many VARs have turned to services as their key value-add.
Service Providers: These are VARs that provide consulting, design, implementation and training services around the products it resells. The main focus of these VARs is services rather than developing custom applications to develop solutions for the products they resell.
Sometimes, smaller VARs or SPs are serviced through a distributors if the vendors have an active distribution network built out.
Distributors: These are intermediaries between a producer of a product and another entity in the distribution channel or supply chain, such as a retailer, a value-added reseller (VAR) or a system integrator (SI). The distributor performs some of the same functions that a wholesaler does but generally takes a more active role. At a minimum, distributors handle payment and procurement like wholesalers but also frequently take a more proactive approach in educating resellers about new products, through activities such as presales training, road shows, and demos on behalf of vendors. Although the specific entities and orders involved can vary, the supply chain or distribution channel involving a distributor is generally:
Vendor à distributor à reseller or SI à End customer
System Integrators: A systems integrator (SI) is an individual or business that builds new systems for clients by combining products from multiple vendors. Using a systems integrator, a company can align cheaper, pre-configured components and off-the-shelf products to meet key business goals, as opposed to more expensive, customized implementations that may require original programming or manufacture of unique components. Some systems integrators working in specialized areas, like SAP installations or upgrades, may offer more customization for specific applications.
Managed service providers: These are typically IT providers that provider a defined set of services to its clients. MSPs usually operate with a flat monthly fee based subscription model. MSPs often provide their offerings under a service-level agreement, a contractual arrangement between the MSP and its customer that spells out the performance and quality metrics that will govern the relationship. MSPs are different from other channel partners in a way they model their services on subscription model and depend on recurring revenues rather than one off services.
Independent software vendors: These make and sell products for particular business application to run on different operating system platforms. The companies that make the platforms like Microsoft, IBM, Hewlett-Packard, Apple etc encourage ISVs, often with special "business partner" programs. In general, the more applications that run on a platform, the more value it offers to customers.
Original Equipment manufacturers: OEM (original equipment manufacturer) is a broad term whose meaning has evolved over time. In the past, OEM referred to the company that originally built a given product, which was then sold to other companies to rebrand and resell. Over time, however, the term is more frequently used to describe those companies in the business of rebranding a manufacturer's products and selling them to end customers. An OEM might acquire a hardware product from a vendor, rebrand and sell them without modification. Alternatively, an OEM may incorporate and bundle the vendor’s products with its own technology for resale. Even big companies, such as Dell, EMC etc, get products from smaller vendors, rebrand and sell them under their own brand.
On the whole, gone are the days when companies could survive with just one sales channel, primarily the direct one. However, to defend their turf, expand market coverage, and control costs, companies have to employ a hybrid sales strategy, using a combination of direct and indirect sales methods, to reach different customer segments and under different circumstances. Some of the modern day examples are companies such as Apple, Dell etc. Apple computers started out with a clear and simple channel strategy of distributing its products through an independent dealer network. But as the products began to get more sophisticated systems, it hired a set of 70 national account managers as part of a direct sales strategy. On the other hand, Dell famously started with direct sales strategy and heavy customization. It stuck to its guns for a very long time. However as the market dynamics began changing with personal computers becoming increasingly commoditized, Dell had to evolve its market strategy and adopt indirect sales strategy along with direct sales. In fact, today it uses multiple indirect sales channels, such as distributors, VARs, SPs etc.

Friday, March 4, 2016

Enterprise Application Integration

Application integration or sometimes also referred to as Enterprise Application Integration (EAI) is a category of approaches of sharing of processes/functions and data among different applications in an enterprise. The integration can be between of on-premise programs at a customer’s end or programs on cloud or programs on cloud and on-premise. The set of technologies and services used to accomplish this task form a part of the middleware.
Over the course of the year, enterprises have accumulated a bunch of systems in disparate technologies, and platforms, as a result of lack of a single solution or a vendor catering to all the diverse business needs. Sometimes companies may also accumulate such system from other companies through mergers and acquisitions. A few examples of such systems are supply chain management applications, ERP Systems, CRM applications, payroll and human resource systems etc. These systems and applications may be on different operating systems, use different database solutions or computer languages, or different date and time formats or be legacy systems that are no longer supported by the vendor who created them. At the same time there may be a need to make these systems and applications communicate with each other to share data or business rules. A lack of communication between critical applications leads to inefficiencies with identical data being stored at multiple locations, lower degree of automation, higher costs and more operational overhead.
Given these requirements, any application integration software has to satisfy three main criteria:
  • Interoperability: Allow different application systems to interact
  • Data integration: Seamless and consistent integration of data
  • Robustness, Stability, and Scalability: As these software stack are the glue that holds together modular infrastructure
Typical there are 4 main architectures for application integration, namely
  • File transfer
  • Shared database
  • Remote procedure invocation
  • Messaging
File transfer and Shared database help in exchanging data between applications while Remote procedure invocation and messaging integrate both data and functions
File transfer is where one application writes a file that the other application reads and visa-versa.
Shared database is use of a common database to share data among each other. In case, there are simultaneous data writes to the same area of the database then transaction management systems used with these shared databases help in managing the conflict.
Remote Procedure Calls (RPC) expose a business functionality via an interface definition and implementation of that interface using different technologies. This architecture applies the principle of encapsulation to integrating applications. If an application needs some information that is owned by another application, then it interacts with the application directly to get this information. Technologies such as CORBA, RMI etc implement RPC.
While encapsulation helps reduce the coupling of the applications by eliminating a large shared data structure, the applications are still fairly tightly coupled together. The remote calls that each system supports tend to tie the different systems into a growing knot.
Messaging helps integrate applications more loosely and allows data exchange in an asynchronous fashion.  This is basically exchange data and invoke functionalities via messages and allows for as much of decoupling as we get in File Transfer architecture. (eg:SOA)
Integration software have been around for a long time and have evolved with evolving business needs.
It began with Custom development, which as you can imagine is cumbersome, point to point, propriety and hard to reuse.
The next was Enterprise application integration that offered more seamless integration of applications and was initially designed based on hub-spoke model and later evolved into a bus architecture.
EAI Evolution
With the advance of web services, EAI gave rise to SOA/ESB, "Service Oriented Architecture" / "Enterprise service bus" has been coined to describe a system that maps standards-based interfaces to business functions. Some EAI vendors rebrand EAI solutions as ESB while some vendors built ESBs from scratch: WSO2, Mule. However, SOA is primarily for on premise applications. Leading companies offering ESB are Fujitsu, Hewlett Packard, IBM, Microsoft, Mulesoft, Oracle, Redhat, SAP, Software AG, and TIBCO Software.
As one can imagine, ESB suites have become very popular and the market is expected to grow at nearly 5% CAGR.
Gartner-ESB
Souce: Gartner
The increasing platforms, such as social, mobile and cloud platforms, are further creating a strong demand for more hybrid platforms that allow for a mix of on premise, cloud, B2B, social, and mobile integration scenarios. This is realized with a combination of SOA and integration platform as a service (iPaas). Some common examples of iPaas based SOA software are IFTTT, Zapier, WSO2 Integration Cloud.
iPaas appears to be the architecture for the future as it provides a combination of some of the features found traditionally in on-premises integration platform software, such as enterprise service buses (ESBs), data integration tools, B2B gateway software, application service governance platforms, and managed file transfer products along with integration with cloud services.
Industry reports indicate that the iPaaS market is poised to dramatically grow over the next few years at a rate nearly twice of that of ESB due to several factors, including:
  • The explosion of CSI, MAI, API and Internet of Things requirements.
  • The emergence of the agile integration approach and citizen integrators, for which traditional integration platforms are unsuitable.
  • Adoption by SMBs so far often unwilling to embrace integration middleware because of its high cost and complexity, but now interested in iPaaS offerings due to their low entry cost and ease of use
Markets&Markets-Overall
Source: MarketsandMarkets.com
Above and beyond, Gartner has kindly rated all the iPaas companies providing EAI services to rate them in their famous magic quadrant table
Gartner MQ