As SaaS investment is shown to increase strongly over the next 18 months, how should insurers and IT groups prepare? Charles Juniper, Principal Insurance Analyst at Ovum has laid out three key recommendations for insurers to keep in mind as they begin their SaaS transformations:
SaaS strategies must incorporate benefits beyond just cost reduction
Cost reduction is already seen as an obvious benefit of cloud and SaaS, but this is only one of many. Ovum believes most cloud strategies in the insurance industry today need to be more comprehensive and more fully encompass the potential for organizational transformation. "In planning their SaaS strategies, insurers must focus on the transformative role SaaS can have on their organisation in the context of wider industry change. SaaS and cloud technology can play a critical role in supporting an insurer’s overall business goals and in supporting its wider ambitions whether that includes new products and services, regional expansion or entering completely new sectors.”
All insurers must plan to adopt SaaS within the next 24 months
"As SaaS becomes increasingly mainstream, all insurers must have a clearly defined and widely internally communicated strategy for SaaS and cloud. For the minority of insurers that do not have some level of SaaS strategy, it must become an urgent priority. They should not wait for the technology to mature further or for remaining issues to be completely resolved, as this delay will significantly reduce the benefits of adoption."
IT groups should look to evolve towards a "SaaS broker" model
"One of the consequences of SaaS adoption is that the IT function of many insurers will need to undergo significant change in their role and structure, and this is likely to give rise to some challenges in terms of change management. In reaction to this, the IT function of insurers needs to evolve towards assuming a "broker" role, bringing together an insurer’s wider business functions with relevant SaaS vendors - this change in role marks a distinct contrast to the more reactive stance of many IT groups currently."
|