9 SaaS Pitfalls To Avoid - InformationWeek
IoT
IoT
Cloud // Software as a Service
News
9/5/2016
08:06 AM
Thomas Claburn
Thomas Claburn
Slideshows
Connect Directly
Google+
LinkedIn
Twitter
RSS
E-Mail
50%
50%

9 SaaS Pitfalls To Avoid

Shifting to cloud application providers requires companies to step carefully. Here are 9 potential problems that can prevent a smooth transition.
Previous
1 of 10
Next

(Image: Baranozdemir/iStockphoto )

(Image: Baranozdemir/iStockphoto )

The cloud has won. While on-premises software will continue to exist, cloud computing has so much to recommend it that organizations cannot afford to ignore it.

Clearly, they aren't. In 2016, spending on public cloud infrastructure-as-a-service (IaaS) hardware and software is forecast to reach $38 billion worldwide, according to Statista, and to rise to $55B in 2026.

The application layer of cloud computing, software-as-a-service (SaaS), exemplified by vendors like Adobe, Microsoft, and Salesforce.com, shows similar health. Spending on SaaS should reach $50 billion by 2024, up from $12 billion projected for the end of 2016, according to Better Buys.

Gartner paints a similarly rosy picture, predicting the worldwide market for cloud application services (SaaS) will reach $37.7 billion by the end of this year, up from $31.4 billion in 2015.

"The market for public cloud services is continuing to demonstrate high rates of growth across all markets and Gartner expects this to continue through 2017," said Sid Nag, research director at Gartner, in a statement earlier this year. "This strong growth continues reflect a shift away from legacy IT services to cloud-based services, due to increased trend of organizations pursuing a digital business strategy."

Gartner anticipates that approximately 28% of human capital management systems used worldwide will be SaaS-based by 2019, up from 13% in 2014. Other enterprise systems look like they're headed in a similar direction.

Enterprises now have the option to reduce or avoid the expense and risk of large scale ERP and CRM deployments by integrating SaaS applications instead. In so doing they also have the opportunity to shift their IT groups away from the defensive posture of maintenance and management toward tasks that improve business productivity and advance strategic goals.

[See 10 SaaS Startups Every Enterprise Should Know.]

But ditching desktop applications for SaaS requires some planning. It's not something that should be done lightly. There are technical, economic, and legal issues to consider, along with organizational politics.

To understand the risks, you only need to look back to May 2016, when Salesforce.com suffered a power disruption affecting three of its 45 North American instances. The incident caused hours of downtime for a significant number of Salesforce clients.

Before shifting to cloud-based applications, consider the potential pitfalls that follow.

Thomas Claburn has been writing about business and technology since 1996, for publications such as New Architect, PC Computing, InformationWeek, Salon, Wired, and Ziff Davis Smart Business. Before that, he worked in film and television, having earned a not particularly useful ... View Full Bio

We welcome your comments on this topic on our social media channels, or [contact us directly] with questions about the site.
Previous
1 of 10
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Catherine Hudson
50%
50%
Catherine Hudson,
User Rank: Apprentice
5/12/2017 | 1:26:21 AM
Measures to avoid these 9 pitfalls
Thank you. It's really a great article. I fully agree with all the pitfalls. However, I think it's worth mentioning measures one can take to avoid these pitfalls. For instance, implementing SAM tools, such as Binadox, can be of a great help. These tools can help manage legal entitlements and liabilities, as well as costs.
jmyerson
50%
50%
jmyerson,
User Rank: Apprentice
9/6/2016 | 5:30:12 PM
Possible 10th SaaS pitfall
Whlle I think your blog is great, I think there is a possible 10th pitfall.  The application that runs smoothly on premise may not work properly in the cloud.
Michael12
50%
50%
Michael12,
User Rank: Apprentice
9/6/2016 | 6:40:22 AM
Response
I understand the concept, but as you already said. That disruption was not a thing to ignore.
RajivAb
50%
50%
RajivAb,
User Rank: Apprentice
9/5/2016 | 12:28:10 PM
Adoption versus Customisation
Overall good advice.  worth mentioning the importance of adopting over customisation. 

Its important to adopt internal, business process to meet the standard provided by vendors as opposed to (heavy) customisation of software, no matter how easy the vendors offer. Instead, rely on configuration parameters.  

Although the Business  or Architects want the software to reflect their practices and sometimes idiosyncracies, this can be a burden in the longer term It's a bump in the road and hindrance,  when trying to attain continuous upgrades that happen in the background... with minimal manual testing (perhaps some automated testing) and data validation. 

Often it locks you into the vendor.  When acquiring software as a service, an appropriate exit strategy to an alternative solution or different (business) model must be  technically and commercially straightforward.  If appropriate, prove the concept before signing. 

 

 

 
Register for InformationWeek Newsletters
White Papers
Current Issue
Cybersecurity Strategies for the Digital Era
At its core, digital business relies on strong security practices. In addition, leveraging security intelligence and integrating security with operations and developer teams can help organizations push the boundaries of innovation.
Video
Slideshows
Twitter Feed
Sponsored Live Streaming Video
Everything You've Been Told About Mobility Is Wrong
Attend this video symposium with Sean Wisdom, Global Director of Mobility Solutions, and learn about how you can harness powerful new products to mobilize your business potential.
Flash Poll