Konverge

Monday, March 31, 2008

The True Impact of SaaS on your Business – Part 1 – The Operation Group

Although there are still naysayers to the Software as a Service model, we cannot deny the speed in which traditional ISVs are looking to transition their already existing perpetual model into this pay-as-you-go model. As a SaaS Enabler, we constantly respond to questions from Independent Software Vendors who are trying to make the painstaking decision of getting SaaSy. Careful planning will make the difference between a profitable operation and one that is bleeding the company.


For the traditional ISV, the Operations Groups which consists of technical support, customer care and the R&D team have always been considered a "Cost Centers”. Software as a Service offers ISVs the ability to automate some of the processes associated with this team. Provisioning, ordering and billing can certainly be automated using technology. So where does this leave our team? What is the true impact of the SaaS Model on this team?


The SaaS paradigm shift has certainly made an impact on our Operations Group. These professional teams who are supporting a service are now a focal point in a successful business operation. Customer Care is accountable for customers successfully using the service; Help Desk and Support Services are accountable in making sure that the business is meeting Service Level Agreements and the R&D team is accountable in streamlining development to add functionality at a rapid pace.


Here is a quick glimpse of how these three components of the Operations Group have changed:
Customer ServiceTraditional ISVSaaS Model
Cost CentreValued group
Tasked with provisioning and billing issuesOrdering, billing & provisioning can be automated
Tasked with being first line of customer callsAccountable for customers’ utilization of the service
Responsible for
Customer Churn

Help Desk /
Support Services
Traditional ISVSaaS Model
Help Desk is technical solver with both internal & external customersMainly supporting operations
Supporting numerous builds and versions of softwareAccountable for business meeting SLAs
Tasked with being first line of customer support callsFirst Line Help Desk can be automated
Responsible for Customer Churn


R&D TeamTraditional ISVSaaS Model
Focus on bug fixes for dispersed versionsMainly supporting operations
Not developing in the latest & greatest technologies reduces moraleAccountable for business meeting SLAs
Long Software Development Life Cycle Incorporate of Agile methods and reductions in development cycles
Responsible for
Customer Churn



The common denominator is “Customer Churn” which is really the biggest impact on operations. In order to succeed as a SaaS business, Independent Software Vendors must make the internal change from selling perpetual license to a subscription service. This change is NOT limited to Sales & Marketing; it also changes the internal structure of customer Service / Support & R&D. This is not an easy task.


There is however a benchmark tool that can help you in this mind-shift.
You can take the survey at: http://www.konverge.com/SaaS_Benchmarker.aspx

Labels: ,

4 Comments:

  • Uri,

    Nice article. As you've outlined, making the shift to Software as a Service is not just a Sales & Marketing change but rather an entire business change, including culture, operations & support. In fact the hardest change will come not from Sales & Marketing but from the other areas.

    It is great to see companies like Konverge spending time trying to educate the public on the different challenges of SaaS

    Regards,
    Abe Sultan

    By Blogger Abraham, At March 31, 2008 1:15 PM  

  • Agreed. It is too difficult for a large (and successful) software provider to change the corporate culture that has served them well in the past.

    In the business intelligence space, it will be interesting to see how the established players (Oracle, IBM, SAP, Microsoft) deal with the influx of SaaS providers such as LucidEra, Good Data, and Oco, etc. These new companies can really disrupt the economics of the industry, and while some of these companies may eventually be acquired, successful integration will be an extremely difficult challenge.

    By Blogger bigray, At April 1, 2008 8:19 AM  

  • As consultants in the operations space , we are starting to see our fair share of traditional "packaged" software vendors dabbling with the SaaS model. Most of the problems we see with companies who are trying to make the jump to SaaS (as opposed to our e-commerce and pure play SaaS clients who have no roots in traditional delivery models) are rooted in the fact that their company culture hasn't absorbed that fact that they are now in the business of OPERATING software not the business of MAKING software.

    Yes, of course someone has to make the software in order for there to be a service... but that's not the driving point of the company. In a successful SaaS company, everything (including development) exists to support those operations. Operations provides the service and the service is what makes you money. Developers don't like to hear this, salesmen don't like to hear this, and finance and marketing folks often miss the subtlety and don't know how to adjust their budgets and attention.

    Take an informal poll of 20 software companies trying to make the jump. Those companies that get this... probably flourishing. Those that don't... probably stuck in the mud.

    By Blogger Damon Edwards, At April 1, 2008 1:05 PM  

  • Damon,

    Agreed 100%. Those that get the idea of providing a service as opposed to product need to understand that changes in their internal business process & culture is a major hurdle in success.

    By Blogger LedermanU, At April 1, 2008 1:21 PM  

Post a Comment



<$I18N$LinksToThisPost>:

Create a Link

<< Home