| Dear All,
_Not sure if this was discussed earlier_ The Large/Mega Enterprises are still a tad shy of adopting SaaS in their Core Processes.
What do you see are the biggest Hurdles? Say,
- Heavy customizations needed for Business Processes?
- Unable to Host Customer Data outside? (eg. GDPR)
- Deep Integrations needed, to other 3rd Party systems in the landscape.
- Too much legacy code? Context:
Sure, a lot would probably use an Office 365. Or a Social Media CRM System or an Accounting System or an HR System.
They are usually not the core business of most companies, unless you are in the above business. But - what I am referring to here is more of - in the Core Processes.
For example,
- A Telecom company still is reluctant to bring in SaaS offering in the Network Management
- A eCommerce Retailer in it's Customer Management
- A Manufacturer in the core ERP (_Sure, there are exceptions, but the above are just my observations, happy to be corrected_) |
I think any company would be understandably cautious about this because that's their core business. I probably wouldn't adopt a Saas or outsource that either if I was in charge.
I think it's better for a SaaS to focus on doing well something that the business needs to do but is not replacing something along their core stack and offering.
I'm founder at Tesults (https://www.tesults.com) and the biggest hurdles I would say are around the general fears around not having an on premises solution. Some people are totally fine with this, usually those who have already adopted and are used to services like Slack, Asana, Google Docs, Trello, BaseCamp etc. Then there are also concerns about where data is stored. Usually though I think they're concerned most about the fear of embarrassment internally for introducing something that doesn't 'work' as expected or has bad support. Most people want to solve a problem but also want to cover their backs so trust is a big part, often more than the features being offered.