Published on


Published in: Education, Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • SaaS

    1. 1. Mahesh Panchal(0703024400) Khushbu Desai(07030244003) Pooja Mantri(07030244010) Poonam Bhasin(07030244011) Sushant Kumar(07030244024) Software As A Service
    2. 2. SaaS
    3. 3. SaaS Vs. ASP Parameter ASP SaaS Application Deployed Borrowed Built Time to Implement Long Immediate Usability Cumbersome Easy to use Multi-Tenant scalability No Yes Upgrades and Enhancements Infrequent Often Integration Expensive Inexpensive IT Support Depends upon degree of customization and integration Included as a part of service
    4. 4. SaaS Vendors Perspective
    5. 5. Paradigm Shift Moving from on-Premise software to SaaS requires paradigm in three areas
    6. 6. Application Architecture
    7. 7. Business Model <ul><li>The cost of hardware and services is shared among all the customers </li></ul><ul><li>SaaS application installed in a load-balanced farm of five servers may be able to support 50 medium-sized customers, meaning that each customer would only be responsible for a tenth of the cost of a server </li></ul>
    8. 8. Marketing Strategy <ul><li>Branding </li></ul><ul><ul><li>If an established ISV moving to a SaaS model, may require a new brand, identity and communication strategy. </li></ul></ul><ul><li>Sales </li></ul><ul><ul><li>SG&A expenses in SaaS Model across industry averages about 49% of revenue </li></ul></ul>
    9. 9. Integration of Other Web Services <ul><li>Form strategic partnerships with companies whose service offerings dove-tail with your product </li></ul><ul><li>Example: A software solution for the mortgage industry that Trigent built, works with over 60 credit reporting agencies and with over 6 Loan Origination software solutions. </li></ul><ul><li>Integrate with applications that your customers often use, even though they are offered only in the traditional installed software model. </li></ul><ul><li>Example: has built an application </li></ul><ul><li>framework, API and tools that help other developers </li></ul><ul><li>to built widgets and integrations to other applications. </li></ul>
    10. 10. Licensing or Pricing Strategy <ul><li>Good Billing Platform that provide different priced offerings quickly </li></ul><ul><li>To get new business – Free Limited offerings ( days or features) </li></ul><ul><li>Pricing based on </li></ul><ul><ul><li>Volume of transactions or operations </li></ul></ul><ul><ul><li>Support level needed </li></ul></ul><ul><ul><li>Per user based </li></ul></ul><ul><ul><li>Monthly subscription </li></ul></ul><ul><li>Software system developed must contain hooks to </li></ul><ul><li>make flexible pricing strategies possible </li></ul>
    11. 11. Examples of Licensing Models <ul><li>Basecamp offers multiple license types - all based on the number of projects and storage space. All plans are free to try for the first 30 days. </li></ul><ul><li>TickSpot a time tracking service provider that provides a limited featured, single project free forever. </li></ul><ul><li> offers different editions and </li></ul><ul><li>the license is usually based on the number of users. They too offer a free 30 day trial – without </li></ul><ul><li>a credit card. </li></ul>
    12. 12. Operational Structure <ul><li>Data </li></ul><ul><ul><li>Ensure that the data is secure, safe, adequately backed up and portable. </li></ul></ul><ul><ul><li>Customer retain owner ship of data. </li></ul></ul><ul><ul><li>Infrastructure is regularly tested and certified to comply with SAS70, and PCI Data Security Standards. </li></ul></ul><ul><li>Billing and Provisioning </li></ul><ul><ul><li>Needs robust billing and provisioning system </li></ul></ul><ul><li>Support </li></ul><ul><ul><li>To gain customer trust – provide adequate support </li></ul></ul><ul><ul><li>Structured email or telephone support </li></ul></ul><ul><ul><li>Define expected response times </li></ul></ul>
    13. 13. Case Study: Intacct <ul><li>Location: San Jose, CA </li></ul><ul><li>Industry: Professional Services </li></ul><ul><li>Employees: 100+ </li></ul><ul><li>Customers: 2500+ </li></ul><ul><li>Advantages through SaaS </li></ul><ul><ul><li>The company could scale up its multi tenant architecture infinitely with 99.8% uptime </li></ul></ul><ul><ul><li>The model is highly secure and reliable </li></ul></ul><ul><ul><li>Lower Total cost of Ownership and Optimizations </li></ul></ul>
    14. 14. Customers Perspective <ul><li>A big question for customers today is “Should I go in for SaaS or is Independent Software Vendor Better for me” </li></ul>
    15. 15. 1.The Reach <ul><li>Do you need to collaborate with others inside and outside your company? </li></ul><ul><li>Do you work with people in multiple locations, including mobile workers, partners and suppliers around the world? </li></ul><ul><li>Do you change or add new team members frequently? </li></ul>
    16. 16. 2.Cost of Ownership
    17. 17. Cost of Ownership
    18. 18. 3.Upgrading Issue <ul><li>Is it critical that your software application evolve as your needs change and new technologies emerge? </li></ul><ul><li>New Version of software </li></ul><ul><ul><li>Upgrade the application at high cost and </li></ul></ul><ul><ul><li>delay </li></ul></ul><ul><ul><li>Continue operating on the older version </li></ul></ul><ul><ul><li>of the software package </li></ul></ul>
    19. 19. SaaS Address the Issue <ul><li>Software package is one instance of the application </li></ul><ul><li>No software to install at each client site </li></ul><ul><li>New ideas and feature refinement </li></ul><ul><li>Customizations are stored above the shared code </li></ul><ul><li>Customer becomes part of this virtuous cycle </li></ul>
    20. 20. 4. 80/20 Rule <ul><li>Can you accomplish your goals with an 80 percent solution, one that provides all the key functionality that you need, but maybe not every bell and whistle that you desire? </li></ul><ul><li>Some customized applications do require specialized functionality that cannot be met by a SaaS application, even with configuration and integration </li></ul>
    21. 21. 80/20 Rule <ul><li>Does an on-demand solution cover you basic needs? </li></ul><ul><ul><li>Specify what do you want to accomplish </li></ul></ul><ul><ul><li>Share your definition with the vendors you are considering. </li></ul></ul><ul><ul><li>Request a demonstration of the SaaS system </li></ul></ul><ul><li>It is a tradeoff between the incremental benefit of a truly customized solution and the cost, </li></ul><ul><li>deployment, and evolution benefits indicated </li></ul>
    22. 22. 5. The Speed <ul><li>Do you need a solution now or three to 12 months from now? </li></ul><ul><ul><li>Traditional software projects follow a proven process. This process may work well, it could take months to complete. </li></ul></ul><ul><ul><li>With SaaS , the implementation is painless and system can be up and running literally in hours. </li></ul></ul><ul><li>So if time to business impact is your key project criteria – SaaS offers valuable benefits to your organization. </li></ul>
    23. 23. Case Study: Rutgers <ul><li>Rutgers Offers Fully Online and Hybrid Courses Powered by Pearson eCollege. </li></ul><ul><li>The Challenge: High Cost Barriers for Development and Delivery of Online Education. </li></ul><ul><li>The Solution: Pearson eCollege’s Software as a Service Model Enables Rutgers to Support Increasing Enrolments. </li></ul><ul><li>The Result: Rutgers Saves Time and Resources with Pearson eCollege While Growing Their eLearning Program </li></ul>
    24. 24. Major SaaS Players