Speeding up deployment time with SaaS.

addtoany linkedin

More and more independent software vendors that deliver their software via the on-premises model, will look to create a Software as a Service (SaaS) offering in order to be competitive.  Why are more and more software companies making this transition?  Because customers are looking for the benefits SaaS offerings can provide.  The benefits are well documented:

  • Quick start to deployment
  • Ease of maintenance
  • Predictable Total Cost of Ownership (TCO)
  • Faster Return on Investment (ROI)
  • Shorter deployment time
  • No upfront infrastructure costs
  • Better use of internal IT resources
  • Service Level Agreements
  • Etc.

Since I run the professional services team, I see firsthand how the implementation of SaaS shortens the deployment time.  The first way is creating a software instance(s) for the customer -with SaaS this can be done in hours not weeks.  There is no lengthy wait to procure hardware only to find out it wasn’t sized appropriately and no waiting weeks for a software installer to come onsite to spend days if not multiple weeks (for many ERP vendors) installing software on your hardware.  Instances are created almost instantly as the hardware is already available.  This means an implementation can almost start the next day versus waiting 1-3 months from signing up with a software vendor to beginning a deployment project. There is also global user availability instantly as there is no “roll-out” of software to sites -just an internet connection required.  Imagine all your users around the globe having access in day one.  This is a huge timesaver in our global world. In my previous life with on-premises software there was also a lag time during deployment because the customer’s IT department needed to be trained on how to administer the software.  With SaaS, this obviously goes away and eliminates any lag time on the project due to learning curve of the IT staff.  The system is already being administered by experts. Many times during deployment projects, patches or fixes may need to be applied. This seemingly simple activity could delay an on-premises activity as the IT administrator struggled with learning how to do this.  With SaaS this task, and all upgrades, are being performed by the experts and thus the process is typically invisible to the project team.  Software fixes and upgrades go in without notice and impact to the project. The Service Level Agreements with a SaaS vendor typically guarantee there will be no system downtime. This is very beneficial during a deployment project as there is almost a guarantee that system downtime will not delay the project. And last, but not least, most deployments of SaaS software do not involve hours and weeks of customization.  Most customers choose SaaS to take advantage of the out of the box functionality and best business practices built into the software, so the deployments are inherently quicker. For a little humor on this topic, check out this week’s ‘New Kinexions’ episode on Quick Deployment. In this episode Ari Cole is very behind on his promise ‘deployment time.’

Enhanced by Zemanta

Leave a Reply