There Is Trouble Brewing In BPO Land....And The Cloud Is To Blame

Executives in charge of BPO operations know that their business is under siege. Growth rates have stalled and for some markets negative growth rates are firmly established.

There are of course a few reasons for it but perhaps the single biggest reason is the migration of services into the cloud. SaaS has become a job killer for some BPO services and there is little doubt that the trend will continue.



One of the challenges the BPO industry faces is to put a numeric value on the exodus of services into the cloud and come up with a good estimate.

Gardner has done the work for the industry now. They have compiled a report which attempts to give a forecast as to what what % of revenue will be either lost or transferred  to cloud services.

The report does a great job analyzing individual segments of the IT industry and providing estimates as to the $ amounts expected to be migrated.

The BPO industry is seen as the biggest loser. Out of the current 119 billion (market size in 2016) a whopping 43 % are expected to migrate into the cloud until 2020 -  (Cloud Shift Rate)...making the BPO industry by far the biggest loser.

Of course, all that cloud business still needs to have operators and administrators....so the 43 % shift in revenues does not necessarily equate to a 43 % reduction  in workload for the BPO providers.

However...given that any business which transfers into the crowd does ultimately so because they want to increase efficiencies (=save money)...there will be a noticeable impact on BPO providers.

Once the emergence of AI powered chat bots and NLP powered voice solutions are thrown into the mix...it becomes clear that the BPO industry should face some significant headwinds from here on out.

How To Close The Productivity Gap When Outsourcing Web Design Work ...A Real Life Example

It is well known that outsourcing does have some disadvantages. One of the biggest ones every user of outsourcing services has to battle with  is the issue of productivity gap vis a vis the onshore worker.

Experienced users of outsourcing services know that the productivity gap is real...and they have some specific strategies to make sure that it is as small as as possible in the beginning.

Over time and with proper integration of the outsourced worker the productivity gap will shrink...and often times the offshore worker might become more  productive than the onshore worker.

Below is the real life experience of one of my customers. The customer is a web development and design firm. When the company needed to increase headcount they decided  to hire 2 web developers overseas and integrate them into their team of onshore web developers.

With our help the company devised a specific, 6 Step plan to integrate the developers.


Step 1:
The company assigned each one of the developers to a designer in their US office. The offshore designer were deemed junior to the onshore designers.  In the event of vacation and/or sickness the onshore developers/designers would cover for each other and supervise the offshore designers. Importantly though...the offshore designers were not supposed to cover for each other.

Step 2:
Daily Skype Meetings. A schedule was set whereby each design team would meet up via skype once a day. In the beginning the meetings primarily served as a "get to know each other" opportunity. It was deemed important that a team spirit was created among the onshore and offshore designer and in order to foster it the Skype meets were deemed mandatory.

Step 3
It was decided that collaborative tools were to be used instead of emails. Specifically it was agreed that skype was going to be used for screensharing. Active Collab ( https://www.activecollab.com/) was to be used for the submission , feedback and related  questions regarding any project assigned to the offshore designers.

Step 4
In order to enable the President to verify that the offshore designers were in fact working and not just playing video games both offshore workers were put on Hivedesk (http://www.hivedesk.com/). By using Hivedesk any perception that the offshore workers might not dedicate the hours needed towards the client were eliminated. It was agreed that the offshore workers were on a 9 hour workday with a one hour flex break.

Step 5
In order to properly integrate the offshore workers the company decided on a set course of action as to what the offshore designers were supposed to do. It was agreed that the offshore designers were going to build only webpages after the initial design had been approved by the client. The senior designer/developer (onshore) was responsible for the home page design and built.  As such the offshore worker had only limited ability to bring their own design ideas into any project. The site tree and structure was already there and thus the offshore workers were to finish out the site after the approval of design and site structure.  

Step 6
All communication between the client and the company was to be handled by the onshore developer/designer. The client would not communicate with the offshore worker.


Results/Conclusion:
The steps described above might seem simple in itself. The end result though was that a well functioning team developed between the onshore and offshore developer.

Within a few weeks the offshore designer became attune to the thinking of the onshore team leader and started to adopt and instinctively follow the design ideas of the team leader without having to engage in extensive back and forth.  

The relationship stated to click, enabling the team leader to increase the level of responsibilities assigned to the offshore designer.

The company realized significant financial benefits and increased the size of the offshore team to 6 designers within one year.  




The Distributed Workforce Model Is Creating Problems For BPO Providers....

Traditional BPO providers have had a challenging business environment globally. EMEA has been down a solid double digits  last year (-18 %) and APAC was down a more moderate single digit number. (-6.3%).

The BPO industry has always been rather fragmented. One problem has always been how  to capture the correct data to come up with estimated revenue numbers for the industry as a whole. Market intelligence firms are usually looking at Annual Contract values above 5 Million (some firms will include lower ACV's of 3 Million US-$).

As such the decline in Annual Revenue numbers is rather "top heavy"...it is geared towards bigger contract values.

What is not captured in annual revenue numbers is the shift away from traditional BPO providers  to a more distributed workforce model.


A new breed of providers has emerged which cater specifically to organizations who have demand spikes for services followed by a significant decline.

In the past conventional BPO providers were tasked to absorb those demand surges and had to staff accordingly. Not any longer.

There are now specialized providers who offer "On Demand" (aka Access Contractors) employees to handle those demand spikes. The model is highly attractive to any  sales heavy  organization (etailers) which has to absorb strong seasonal changes in sales volume. (either promotional or seasonal driven)

The distributed workforce model has always been plagued by a rather high error rate. But that has been changing. Tasks have been further reduced into missions. A mission specific employee is tasked with such a small subset or responsibilities that training and subsequent error rate are both minimal.

Making an employee mission specific instead of a more general trained employee in a BPO environment has allowed the distributed workforce model to gain rapid speed.

There are companies in India which have created significant workforce's of on demand workers which can be marshaled into action  within a few minutes. (the biggest providers are in the 1000's of workers or "Access Contractors").

Access Contractors claim that there error rate is about even to the error rate of conventional BPO providers.

The lure of using an Access Contractor is in the associated savings. Savings can be as high as 70 % (!) vis a vis a conventional BPO provider.

Given the realized savings it is easy to foresee continued revenue drain for the established BPO providers. It is one more thing to worry about, besides the emergence of cloud services and AI.












  

Strange News - Phone Fraud puts Indian BPO providers on the defensive

Most people have been getting unsolicited calls from (mostly)  Indian call centers. Sometimes the calls are simply a solicitation for a  product...sometimes the reason for the call is much more sinister.

The Federal Trade Commission has received about 400,00 calls last year regarding what it deems "imposter scams" where the caller claims to be from law enforcement or even the IRS...with the motive  to extort money.


In almost every case the caller has an Indian accent (or an accent which is deemed Indian). The problem which has been arising for the BPO industry is that distrust is brewing between consumers and operators of BPO companies because of it.

The consumer who calls his bank, or even worse, gets called by his bank and hears an Indian accent goes immediately on the defensive. Call center operations are not easy as it it is anyhow....and immediate distrust only makes it worse.

I can attest to the fact that the problem described above is very much front and center for executives planning to set up or relocate call center operations. The Indian Call Center industry is being tarnished...and it is becoming a factor for executives in charge of call center operations.

It is certainly not the main reason...but it a significant contributing factor why the Philippines are now the call center capital of the world.





Should You Ever Visit Your Outsourcing Provider ?...Here Is What You Need To Consider

Big corporations with budgets of millions of dollars do it all the time..they visit their outsourcing provider...wherever they are located.   Often times, and if the budget warrants it,  they actually have a representative embedded with the outsourcing team..or at the very least have a local rep which looks after the relationship.

There are significant advantages to be realized...which is the reason why they do it.
The question I get asked sometimes if smaller scale projects are worth while to warrant a visit.

The short answer it "Sometimes"..and it depends. 
There are a few things which go into the evaluation of whether or not a visit can make a difference. 

That travel in almost every case leads to second or even third world countries and cities which require connecting flights. As such the decision to travel requires a more significant investment as it relates to time and money.

Below are some of the considerations a small business owner with a smaller project might want to consider to decide if the trip is worth his/her time.

Consideration 1
How long is the estimated time to completion of your project?
If the project is estimated to be completed within 6 weeks even a substantial overrun in time to completion might no be material to your business.  If on the other hand estimated time to completion is 8 months..then a visit might make it more likely that the project will be on time.

Consideration 2
How expensive is your project...and are you responsible for cost overruns ?
This might be the cardinal question...if your project is only 5k...even a 40 % cost overrun amounts to only a 2 k difference. From a financial cost/benefit analysis it might make no sense to visit. If on the other hand the project is spec'ed out at 100 k...a 40 % increase would add an additional 40 k in expenses. Avoiding the additional expense might make it worth your time to go.

Consideration 3
When should you go and visit?
Assuming you have a time to completion numbered in months and a budget which, if there  were a significant cost overrun, would  make it economically feasible to plan a visit...you need to decide when you should visit. As a general rule..the earlier in the process you visit ..the better it will be. Your outsourced software development team will not get a lot of client visits. If you visit them you will l leave a definite mark on their thinking and they will be much more attentive to your needs for the remainder of the project. 

Consideration 4
Will my visit make a difference as it relates to schedule and costs?
The short answer is unequivocally ...YES. It will. I can assure you that there is a pretty good chance that you might be the only client visiting the developers that year. If you buy them a meal, perhaps some drinks...you can be assured that there will be a lot of goodwill created. The Goodwill will translate into more diligence as to your project, saving you time and money.

Consideration 5
Do you have the time to go and spend at least a week with the team?
This consideration is something only you can decide. f you do have the time and like to travel to areas / cities which are usually not mainstream travel destinations...it might be a good idea.

Consideration 6
Does it make financial sense to travel?
I briefly touched on it in consideration 2. There is obviously little point in spending 5k on travel if the total project is 5k. As such there is a relationship between travel expenses and expected benefits. There is though another way of looking at it...and a lot of companies are utilizing that strategy. An alternative way to look at the projects costs is to include travel expenses upfront in your calculation. The combined project cost and travel expenses then make up the Total Project Costs. If the total Project Cost is sufficiently below what onshore development will cost you..then u have found the economic justification for travelling to your Outsourcing Provider.

At the end of the day the decision to travel is an individual one every business owner needs to decide for him/herself.  I can attest to the fact that it will be beneficial.

Some people like to travel...and some do not. I have a client which always makes it a point to travel overseas to visit the software development team. For him it is a vacation in disguise, fully tax deductible.

That reasoning might not appeal to other business owners...but if you do have the time and like to explore different countries..this is certainly one way to make it tax deductible. And this is often times all the motivation a small business owners need.











Onshore, Nearshore or Offshore Software Development...here are some pros and cons

The day has come where you decide to outsource a software development project. There might be multiple reasons why but you now face the task of how to do it and get it done.

For someone who has never outsourced software development this might seem like a rather daunting task. After all...how do you get from idea to conclusion without having major hiccups on the way.

Business is all about proper execution of strategy...and you should treat your outsourcing approach the same way.

One of the first decisions has to be the geograpic which decision as to what type of outsourcing you want to pursue. There are 3 different categories of outsourcing available to you. Each comes with positives and negatives associated with their relative geographic area.



The table below provides some insight into some of the considerations you may want to entertain. The point of vies used is from a US perspective.

If you are based in Europe the geographic point of view  provided below are obviously  somewhat different.

Definition
The Pros
The Cons
Onshore
Any development partner which resides in your country is typically considered an outsourced onshore development 
No cultural issues which can lead to misunderstandings

Same time zone, cooperation during the day is a breeze

Easy to visit the development partner, domestic flight, train or car trip

Consequently it is easy to supervise

Onshore development is the most expensive. Reputable firms easily charge well above 150 US-$ for contract work

Onshore software development firms frequently outsource their work to offshore providers. As a client you might never learn about it. Hence you might overpay.

In some cases onshore firms are very much tied into business networks which are closely aligned with your business. Ideas or concepts you deem as confidential are leaking to other companies in your space. This can happen through staff attrition or related development work

Nearshore
A company which resides in neighboring countries with a time zone difference  of perhaps up to  4 or 5 hours is usually considered Nearshore. Examples are South America, Canada, Jamaica
The provider is removed but you still have between 4 to 6 hours of overlap in the time zones, enabling you to efficiently cooperate throughout the day.

Pricing will be significantly cheaper than onshore pricing.

There is a certain cultural alignment. Developers in nations mentioned as nearshore providers are used to the US way of thinking.

Nearshore development is not a radical solution. It is more expensive than offshore development as such a lot of the advantages are mitigated.

Nearshore provider are not easy to reach. Travel times are frequently more than 8 or 10 hours and flight is the only option.

Nearshore providers might have significant language barriers.

Offshore
Offshore Development is usually associated with development done on other continents with significant time zone differences. Examples are Asia and Europe
Offshore providers are usually the cheapest by a wide margin.

Not unusual to find development companies with big product portfolios and a lot of related work  experience.

Because true offshore development companies tend to be bigger in size they usually have defined processes to manage a relationship


Offshore Development centers reside on the other side of the clock. Time zone differences are usually 8 hours or more.

The command of the English language is often times average. Only Project Managers and Senior Developers speak good English.

Work hours usually only overlap up to 4 hours.


At the end of the day it really comes down to what the company is prepared to pay...and the trade off the company is prepared to accept if it decides to pursue a lower cost provider.

 There is little doubt that onshore development is the easiest one to manage. The downside is of course that the expense is by far the highest.

Conversely, true offshore development in Asia is usually the cheapest. A lot of corporations are comfortable with offshore development and are prepared to accept some of the difficulties working with a company on the other side of the clock.