Cloud Computing Models: Private, Public and Hybrid
•Transferir como PPTX, PDF•
2 gostaram•1,156 visualizações
Analysts project that SaaS applications will significantly outpace traditional software product delivery in the near future. As ISVs facing this ever-changing cloud landscape, you need to make critical decisions about your application lifecycle and hosting models. Evaluate some of those considerations, and learn how the platform you choose can support the model you determine.
Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Semelhante a Cloud Computing Models: Private, Public and Hybrid
Semelhante a Cloud Computing Models: Private, Public and Hybrid (20)
Mais de Evilázaro Alves
Mais de Evilázaro Alves (8)
Último
Último (20)
Cloud Computing Models: Private, Public and Hybrid
- 2. Challenges Opportunities On-Premises SaaS Apps • Expanding Market Opportunity: Reach new customers in broader markets • Sell directly to business decision makers • More predictable revenue • Lower infrastructure support costs • Requires business model adjustments - new pricing approaches , selling, and more • Revenue increases slowly, harder to invest back in business • Legal and regulatory concerns with storing data outside the customer’s datacenter • Limited opportunities for customization • Low margins and price sensitive customers cause churn Hybrid
- 3. Cloud and SaaS model adoption Opportunities Challenges Expanding Market Opportunity Sell directly to business decision makers More predictable revenue Lower infrastructure support costs Requires business model shifts Revenue builds up more slowly, harder to invest back in business Legal and regulatory concerns around data SLA management - Requires high level operational disciplines Requires re-architecting existing applications
- 4. Balancing SaaS delivery with core software and solving customer problems. Software+ Customer workflows Core Competencies Essential value for ISVs to build As-a-Service (Platform & Infrastructure Management) Non-core, but Necessities Limited value for ISVs to build
- 5. ISVs are experiencing more challenges and burdens managing their own infrastructure
- 6. Choosing the right cloud platform is critical when expanding your business to the cloud and SaaS Software+ Customer workflows Core Competencies Essential value for ISVs to build Choosing the Right Cloud Platform Non-core, but Necessities Limited value for ISVs to build
- 7. Application Architecture Complexity & Customization Complexity of solutions – data layer/app layer Core vs. new/extended solutions APIs Solution integration: 3rd party solution integration, APIs support Customization – enabling partners Tenancy Single tenant vs. Multi-tenant Operations Customer Needs & SLA Reliability/Availability Performance Security/Compliance Scalability Support Easy on-boarding Service management: Provisioning, usage metering, billing DevOps ALM DevOps collaboration Versioning Business Model & Strategy Pricing /Cost Structure Pricing model – monthly, annually Funding model: CAPEX vs. OPEX Cost to scale (COGS) Target Market Target market and geo presence, expansion Macro environment – data sovereignty, regulatory compliance Channel model Business Goals Cloud First or Cloud Both strategy Grow – organic or through acquisition Funding – get sold, get invested
- 8. Hybrid Cloud: Across On-Premises, Managed Hosting, and Public Cloud 80%of SaaS ISVs are self-hosted today Key Drivers < 2% Cloud-based infrastructure (Public Cloud) Fast time to solutions, rapid deployment for new services Global reach with broad geo coverage 18% Enhanced Managed Services and Hosted Managed Services Delegate operations and infra management to capable managed hosting partners 39% Co-location Specific geo coverage or local presence while maintaining operational control to meet customer’s expectations and SLA Infra HW operational efficiency 41% ISV On-premises Complex solution architecture and customization Full operational control to meet customer expectations and SLA Cost to scale. CAPEX funding model Source: IDC Direction 2014, Transformation Everywhere How SaaS Gets Built, March 2014
- 9. Complete Hybrid Cloud Platform ONEConsistent Cloud Platform to Support ISVs’ Business Needs < 2% Cloud-based infrastructure (Public Cloud) 18% Enhanced Managed Services and Hosted Managed Services 39% Co-location 41% ISV On-premises Source: IDC Direction 2014, Transformation Everywhere How SaaS Gets Built, March 2014 Microsoft Cloud OS Customer Service ProviderMicrosoft Consistent Platform ONE Allows ISVs to expand SaaS business seamlessly with a consistent hybrid platform
- 10. The Platform for Your SaaS Business Common Identity Integrated Virtualization Data platform Multi-Tenant Flexible Deployment Microsoft On-Premises Service Provider One Consistent Platform Deliver a consistent platform to run your applications across on-premises, Microsoft public cloud, and service provider’s cloud Unified Management
- 11. Grow your business with Microsoft no matter where you start Service ProviderMicrosoft Azure Develop Deploy Manage Monitor On-Premises
- 12. Designed for Cloud Applications Windows Server 2012 R2 Web Applications Remote Desktop Services Networking Storage Management Active Directory Virtualization with Hyper-V Multi-Tenancy Availability / Scalability / Security System Center 2012 R2 Service Provider Foundation API OS & Application Monitoring Automation & Self-Service Infrastructure Provisioning Foundation for Hosting Service Provider Offers ISV Control Panels Custom Control Panels Service Management Portal Service Management API (REST OData) Compute Storage (File/Block) Network Application Hosting (SaaS/PaaS/IaaS) Desktop Hosting through RDS Windows Server 2012 R2 Provides the comprehensive, highly scalable platform System Center 2012 R2 Provides the cost efficient, unified management platform Windows Azure Pack & Service Provider Foundation API Provides standard management API
- 13. 24 x 7 x 365 1 billion 20 million 76 280 years ₩ ¥ € руб $ $ £ $ Rp TL chf kr kr $R $ $
- 14. June 2013 250,000 50% of the Fortune 500 companies
- 15. Dynamics CRM serves over 3.5 million users Nearly 50 million Office Online users
- 16. Contextual awareness Key app adoption Data Azure
- 17. .NET Hyper-V Visual Studio System Center Active Directory Programming languages + tools .NET, Visual Studio, TFS + Git, Java, NodeJS, PHP, Python, Ruby, C++ Microsoft cloud infrastructure Web Mobile Gaming Cloud services Data Analytics Media Identity IaaS Windows VMs Linux VMs Storage Networking PaaS
- 18. Regulatory compliance is a feature set of O365, Azure and CRM Online. Microsoft continues to adapt and evolve in building regulatory compliance features into our services No other cloud provider offers the breadth of regulatory- related and other trust features across cloud platforms Routinely collaborate and seek input from regulators to validate our approach Microsoft’s services are engineered to help customers to meet their regulatory compliance needs Microsoft is a thought leader and innovator in the cloud on regulatory compliance
- 19. Standard process for development of secure software International standards ISO 27034-1 Comprehensive application security program Flexible controls, measurements and secure coding requirements
- 20. Data security Lock box processes for Encryption at rest protects data on Microsoft servers Encryption in transit with SSL/TLS protects data transmitted between customer and Microsoft Threat management, security monitoring, and file/data integrity prevents or detects any tampering of data Physical security 24-hour monitoring of data centers Multi-factor authentication, including biometric scanning for data center access Internal data center network is segregated from the external network Role separation renders location of specific customer data unintelligible to the personnel that have physical access Logical security Lock box processes for strictly supervised escalation process greatly limits human access to data Servers run only processes on whitelist, minimizing risk from malicious code Dedicated threat management teams proactively anticipate, prevent and mitigate malicious access Port scanning, perimeter vulnerability scanning, and intrusion detection prevent or detect any malicious access Admin and user controls Rights Management Services prevents file-level access without the right user credentials Multi-factor authentication protects access to the service with a second factor such as phone S/MIME provides secure certificate-based email access Data loss prevention prevents sensitive data from leaking either inside or outside the organization
Notas do Editor
- Key Point: Cloud and SaaS provide a new level of opportunities and challenges to ISV partners. ISV partners will have more opportunities by build and expanding your business to cloud-enabled applications. ISV partners can: Expanding Market Opportunity: reach new customers in broader markets Sell directly to business decision makers More predictable revenue Lower support costs SaaS reduces the need for on-premises resources, like servers and IT people. The application runs in the cloud, and so customers don’t need to invest in the hardware and the staff to run this application on premises. On the other hand, cloud-enabled apps and SaaS bring a new level of challenges that ISV partners haven’t considered in your traditional SW business. Requires business model adjustments - new pricing approaches , selling, and more Revenue builds up more slowly, harder to invest back in business Legal and regulatory concerns with storing data outside the customer’s premises Limited opportunities for customization Low margins and price sensitive customers cause churn
- So what are the key criteria to choose the right platform that supports your business growth to the cloud while protecting your and your customers’ existing investment? Business Criteria Increase speed to market Scale to global market Cost efficient Flexible platform to meet diverse customer’s needs: scalability, data sovereignty, compliance, governance, security, customization, SLA, etc. Technical Criteria Seamless connection with existing environments - hybrid cloud A platform supporting cloud enablement: multi-tenancy, self-service, etc. Enterprise class high availability, security and performance Open and portability
- Microsoft’s cloud platform, Cloud OS, is uniquely positioned to ISV partners to get all the benefits of scale, speed, and agility while still protecting existing investments, allowing them to move to the cloud with confidence. The key to the Microsoft Cloud OS approach is to provide one consistent platform and a set of common capabilities that allow customers to flexibly extend services across on-premises, private cloud and public cloud. ISV partners can grow your business with Microsoft Cloud OS no matter where you start. This is powerful because we will deliver a flexible development environment for the developer so that it can code once and deploy anywhere; deploy on premises, deploy out to a partner cloud, deploy out to Azure cloud. But they only have to write the app once on the power of our .NET framework. Unified management is our ability to use System Center, sitting in your datacenter to administer all the automation scripts to manage and pool the resources of that datacenter. Well while you’re looking in that pane of glass, to be able to provision and move VMs, objects, data from your datacenter out through a service provider or out to Azure for bottomless storage, for redundancy, for disaster recovery. Common identity is a third element of our consistent platform, using Active Directory group policies that you’ve already set up in your enterprise. You merely get the benefit of those group policies extended through Active Directory Federation Services and Azure based Active Directory, so that the group policies you set, extend out to the cloud automatically. You don’t have to manage multiple federation common identity across different clouds. Integrated virtualization is a fourth area. You no longer have to have a third part bolt on to virtualize your compute. Not only are we giving you compute capability, virtualization of your compute capability imbedded in Windows Server, we’re giving that to you around software defined networking and around virtualization of storage, also. Lastly, being able to have a complete data platform where your data can reside anywhere across these three clouds in a seamless way is a value proposition that’s huge as well. You can optimize your storage costs in this dimension. All that capability integrated in how we think about the complete data platform for a customer across all clouds. Our hybrid design gives you the ability, from a one view, to manage apps and data beyond your own private cloud -- to a partner cloud -- to a public cloud -- in a consistent way. Removes complexity so you can focus on answering those business questions and apps Helps you be very flexible in thinking about how you deploy your apps across the three clouds
- 16
- Key Points: Microsoft’s service platform is extensible. Microsoft is a partner-driven company. So we make these services a platform. That means, for example, that Office 365 can be the front end for your LOB applications. Bing can provide text-to-speech translation, mapping, language translation, Bing entities – those are Microsoft services that partners can leverage. That ecosystem continues to grow – services from Microsoft and services from Microsoft partners as well.
- Key Points: Microsoft offers an open and flexible, complete cloud platform that enables you to quickly build, deploy and manage applications across a global network of customer-managed, partner-managed or Microsoft-managed datacenters. You can build applications using any language, tool or framework and deploy it as you choose, across private, hybrid or public cloud. Your customers can integrate your public cloud applications with their existing IT environment. It all means you can offer cloud on your customers’ terms. Microsoft is the only public cloud vendor to be named a Leader for both PaaS and IaaS by Gartner. We have long maintained that customers need choice and flexibility to navigate this mobile-first, cloud-first world and that Microsoft is uniquely equipped to deliver on that by enabling customers to use public, hybrid or private clouds for maximum flexibility and business benefit. Always up. Always on. Microsoft Azure delivers a 99.95% monthly SLA and enables you to build and run highly available applications without focusing on the infrastructure. It provides automatic OS and service patching, built in network load balancing and resiliency to hardware failure. It supports a deployment model that enables you to upgrade your application without downtime. Open Microsoft Azure enables you to use any language, framework, or tool to build applications. Features and services are exposed using open REST protocols. The Microsoft Azure client libraries are available for multiple programming languages, and are released under an open source license and hosted on GitHub. Unlimited servers. Unlimited storage. Microsoft Azure enables you to easily scale your applications to any size. It is a fully automated self-service platform that allows you to provision resources within minutes. Elastically grow or shrink your resource usage based on your needs. You only pay for the resources your application uses. Microsoft Azure is available in multiple datacenters around the world, enabling you to deploy your applications close to your customers. Powerful Capabilities Microsoft Azure delivers a flexible cloud platform that can satisfy any application need. It enables you to reliably host and scale out your application code within compute roles. You can store data using relational SQL databases, NoSQL table stores, and unstructured blob stores, and optionally use Hadoop and business intelligence services to data-mine it. You can take advantage of Microsoft Azure’s robust messaging capabilities to enable scalable distributed applications, as well as deliver hybrid solutions that run across a cloud and on-premise enterprise environment. Microsoft Azure’s distributed caching and CDN services allow you to reduce latency and deliver great application performance anywhere in the world.
- First, with respect to strengthening secure development, we begin with a simple fact: nearly all ICT companies are global companies. We must create products and services that can be sold and utilized across national borders with ease. In this globally interconnected marketplace, all nations benefit when international, rather than domestic, standards are applied to technology. One area that has been ripe for international standardization has been around software assurance. In 2013, the ISO issued a new standard ISO 27034-1. SDL is incorporated, which integrates this into our compliance capabilities…. It is focused on providing processes needed to build and operate a comprehensive application security program, but flexible enough to allow the choice of specific controls, measurements, and secure coding requirements. I want to underline that ISO 27034 is an internationally-recognized standard that is based upon delivering security through a process -- not geography.
- Key Point: This presentation is intended for Business Decision Makers(BDMs) within an independent software vendor(ISV) organization. The goals of this guide are to: Provide an understanding of the momentum around cloud computing and what makes it attractive for ISVs Describe the Microsoft Azure its features & some successful ISV case studies And finally, to discuss the pricing of the Microsoft Azure , illustrated by some cost examples of ISVs applications with their monthly costs on Microsoft Azure Each of the 3 sections provides details on one of these goals.
- Key point: Cloud computing is a model for enabling convenient, on-demand network access to a shared pool of configurable computing resources. National Institute of Standards and Technology definition: Cloud computing is a model for enabling convenient, on-demand network access to a shared pool of configurable computing resources that can be rapidly provisioned and released with minimal management effort or service provider interaction Cloud computing is composed of five essential characteristics. Essential Characteristics: On-demand self-service. A consumer can unilaterally provision computing capabilities, such as server time and network storage, as needed automatically without requiring human interaction with each service’s provider. Broad network access. Capabilities are available over the network and accessed through standard mechanisms that promote use by heterogeneous thin or thick client s (e.g., mobile phones, laptops, and PDAs). Resource pooling. The provider’s computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to consumer demand. There is a sense of location independence in that the customer generally has no control or knowledge over the exact location of the provided resources but may be able to specify location at a higher level of abstraction (e.g., country, state, or datacenter). Examples of resources include storage, processing, memory, network bandwidth, and virtual machines. Rapid elasticity. Capabilities can be rapidly and elastically provisioned, in some cases automatically, to quickly scale out and rapidly released to quickly scale in. To the consumer, the capabilities available for provisioning often appear to be unlimited and can be purchased in any quantity at any time. Measured Service. Cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported providing transparency for both the provider and consumer of the utilized service. Source: http://csrc.nist.gov/groups/SNS/cloud-computing/cloud-def-v15.doc
- Key Point: While all applications can realize benefits from moving to the cloud, applications with certain workload patterns are particularly well suited to the cloud. They include: On and off: parallel processing applications, when large amounts of capacity are needed for a very short time frame for example an online state exam taken by thousands of students in one day Growing fast: start-up applications which may start with a few customers but may grow quickly to add many customers Spiky Unpredictable bursts: consumer applications like online games, social networks Predictable bursts: seasonal applications like shopping websites during the holiday season
- Key point: As your organization evaluates the multiple environments available to create a cloud based offering, it is important to understand that only Platform as a Service takes away all of the extraneous management tasks that are not directly related to your value add. However with Microsoft Azure you have the option to do Infrastructure as a Service as well. Across different types of hosted and cloud offerings the resources your organization manages are different: On-Premise: If you develop, test and help customers deploy your offering on-premise, all the components of the stack starting from the base hardware to middleware and right up to the application are managed by you. The place where your organization adds value however is at the very top where the application and the data sits. Managed hosting: If you have already moved part of the way to a hosted environment that manages some of the components of the hardware and may manage middleware partly as well, you still spend a lot of energy on managing the remaining parts of the stack where you don’t add value. You also have to predict usage, rent servers and hope you predicted right. There is no inbuilt process for scaling. IaaS: In an IaaS offering some of this headache of managing non-value added components of the stack goes away however you still manage the databases and security and integration services….so this is better than the 2 prior alternatives but still not ideal. PaaS: This is the offering where your organization is able to use its energies and talent most effectively – in creating more innovative applications, in reaching new markets, and in overcoming your businesses challenges versus managing infrastructure or middleware. The only components of the stack that you manage and focus on are those where you add value and therefore those that are tied to your revenue-stream directly.
- Key Point: There are many challenges that ISVs face today – here are some of the key ones and how the cloud helps: Remaining competitive: Cloud computing allows ISV to rapidly create and deploy new solutions. With no upfront hardware investments – innovations can occur at the speed of thought. Staying Focused: With the cloud, the ISV need not spend time and resources managing and provisioning servers, hardware and load- balancing. They can concentrate on providing the most innovative and comprehensive solutions to their customer base. Reducing Costs: Upfront hardware costs that mean CAPEX expenditures are tough in this economic environment both for the ISV and their end customer. Cloud computing allows for a utilization based OPEX model. Managing Datacenter: Planning for peak demand would make data centers too expensive for average loads. Planning for average demand means that applications don’t scale well and fail when there is high demand With cloud computing the ISV can ensure that demand and capacity are always in sync without idling expensive hardware. Maintaining Security, Privacy and Continuity: The goals of secure applications and increased access are always in conflict within the on-premises world. It is not so with the cloud paradigm. Embracing Globalization: Globalization is both, a hurdle when it comes to distributed teams and an opportunity when it comes to reaching new markets. Cloud computing helps with both – in connecting dispersed teams and reaching new markets. So what’s the right cloud for you?
- Key Points: To create a cloud based SaaS offering, apart from technical considerations, many components of your business need to be thought through differently including Financial Metrics, Sales and Marketing and Operations How Cloud Services Are Different Financial Metrics: Cloud will require you to understand and track a whole new set of financial metrics. Details provided on the next slide. Marketing and Sales are also different for the cloud, there are new licensing models, different sales cycles and marketing tactics that are needed to be successful. With delivery over the internet and instant upgrades, promised SLAs and 24/7 support the cloud business needs an entirely different model from the existing on premise one.
- Managing your cash flow is critical. Find out quickly if you’re getting into trouble.
- Key Point: One component of your business that you need to rethink is the Financial Metrics. Arguably, metrics are more important for a SaaS business than for a traditional packaged-software business. The metrics that you see here are the new financial drivers and levers that are key to monitoring and managing the health of your cloud services business. The good news is that a SaaS model, in theory, gives you a strong recurring revenue base that grows over time. The bad news is that it doesn’t happen overnight. To read more about these refer to the BVP – 10 Laws of Cloud SaaS included in the Analyst Reports. Source: http://www.bvp.com/saas/default.aspx CMRR is the Committed or Contracted Monthly Recurring Revenue and obviously the driver of business revenue. Regardless of your pricing model, CMRR is the combined value of signed contracts on a monthly basis. The goals are to have a healthy flow of new and existing committed contracts as well as the monthly dollar amount of each contract being as high as possible. For example, if a customer upgrades from a basic level into a premium level package, the CMRR will increase regardless of whether any new contracts have been added. Churn is a critical element of CMRR as it indicates the value of the monthly recurring revenue that is expected to be lost from customers that have announced they will stop the service. It’s also a metric that should be monitored closely in its own right as high customer churn can be disastrous. It varies greatly from solution to solution but fundamentally if your cloud offering is not quickly providing real business value to a customer, and not continuously providing that value, then that customer will likely cancel their account at their first opportunity which may be the next payment date or renewal date. The concept of providing ongoing value to your customers in order to keep churn rates low is discussed in more detail in webinar 5. Again, according to Bessemer, the top most successful companies selling software as a service have a renewal rate of more than 90%. The reason this isn’t higher is that you really can’t avoid situations such as acquisitions and failed businesses that create a situation where a client discontinues the use of the solution. C-pipe is your forward looking indicator for CMRR and CAC and another very important metric to determine the expected future health of the business. A 4th key metric is cash flow. This arguably has always been a key metric for software companies. For cloud services specifically, however, it’s critical for staying afloat when payments are made in small ongoing incremental amounts over the lifetime of the contract, and for helping to cover the initial outlay required to get the cloud services business up and running. Many companies often use discounts for pre-payment to improve their cash flow position. These 2 metrics, Customer Acquisition Costs (CAC) and Lifetime Value of the Customer (LTV) are focused on long term financial health. For nearly all companies selling software as a service, customer acquisition costs are frequently the single largest expense on the income statement. As such, it’s important to measure and track how quickly you are able to recoup those costs on a per customer basis. According to Bessemer, the “non-official” standard in the market is that the sales and marketing costs should be recouped within a year, with the following year covering the cost of administration, product development etc. With respect to LTV, the idea that companies should consider the lifetime value of their customers has become one of the core premises of sophisticated marketing over the past decade. It’s particularly important to cloud services where the overall success of the company is based not only on acquiring new customers but also on sustaining and growing the customer relationship over time. The goal is to have a continued stream of profitable payments that will increase in value over time as the customer upgrades their account and takes on additional products and services.
- As a SaaS company becomes larger, the size of the subscription base becomes large enough that any kind of churn against that base becomes a large number. That loss of revenue requires more and more bookings coming from new customers just to replace the churn. As a result growth slows substantially. To illustrate this point, I built a very simple model and graphed the output below. The model starts with MRR (Monthly Recurring Revenue) at zero, and bookings from new customers at $10k in the first month, increasing by $2k every month after that (represented by the dotted blue line in the graph below).
- Negative churn occurs when your expansions, up-sells and cross-sells to your current customer base exceed the revenue that you are losing because of churn. In this example, we have negative churn of 2.5% through upsells to the current customer base. You can see the dramatic result. Check out the monthly recurring revenue – you can see that with the 2.5% negative churn, the business is nearly three times bigger than one with 2.5% churn. Negative churn (or offsetting churn to the point near zero) is a tremendous driver of business growth. To get there, you need to do one or more of three things: Expand revenue from your existing product portfolio Upsell customers to a more valuable feature set Cross-sell customers additional products from your portfolio
- Key point: Managing churn is anything but a passive activity. You need to figure out what makes your products sticky – and how you can make them stickier. The more indispensable they are, the less churn you’ll experience. Track customer engagement – and react to it. Follow up with customers and enable them. Give them ways to make more and better use of the products they’ve bought. Help them get going when they first sign up. Put top sales talent on cancellations, to save potentially lost business. But don’t be Comcast. Consider lengthening the standard contract to increase commitment to the product. And always, always – understand your churn rate. Understand what’s causing churn, and manage it actively.
- Key Point: Let’s turn now to talk about what the demand generation funnel looks like for cloud services. Because cloud services customers keep PAYING for a product if, and only if, they are actively using it and getting value from it, the role of demand generation in cloud services shifts the traditional focus on getting leads into the top of the funnel, and extends it throughout the customer lifecycle. Demand generation in the context of cloud services is focused on achieving 3 critical and measurable marketing goals: To acquire customers – here demand generation activities are focused on generating awareness or capturing existing interest and ultimately turning that interest into orders. If your demand generation activities are successful, they will result in an increase in your Contracted Monthly Recurring Revenue (or CMRR). Also, optimizing your marketing spend will ensure that you are keeping your Customer Acquisition Costs (or CAC) down. To activate usage – here demand generation and cultivation activities are focused on increasing both CMRR and reducing Churn. Helping customers to quickly realize value, often even before they have made a buying decision, will shorten the sales cycle. Getting them educated so that they start using your solution in depth will help to ensure that they keep on paying. To cultivate fans – here the demand generation activities are focused on increasing customer Lifetime Value (that is, LTV) and reducing Churn. Your efforts should ensure that your customers are extensively using your cloud solution and realizing additional value from any complementary products and services. More than this. They should also turn them into loyal advocates and provide them with tools and forums that enable their comments to reach and influence other customers and prospects. The metrics I’m referring to here, CMRR, CAC, Churn and LTV are discussed in more detail in module 2 of this workshop series. They are fundamental to the financial health and success of Cloud providers so if you haven’t watched this webinar, I encourage you to do so.
- Key Point: The sales process for SaaS is also very different from the traditional sales cycle for on-premise products Digital Marketing and a clean web presence become more important for a product online. Also, many buyers like to taste the goods before committing to paying so trials are important. In many cases, if the audience is fragmented like SMBs or consumers, the traditional sales force is not even a requirement as the internet and a tele-sales team become the primary sales channel. Also, reviews, forums, community and blogs are big drivers of awareness and perception.
- Key Point: This presentation is intended for Business Decision Makers(BDMs) within an independent software vendor(ISV) organization. The goals of this guide are to: Provide an understanding of the momentum around cloud computing and what makes it attractive for ISVs Describe the Microsoft Azure its features & some successful ISV case studies And finally, to discuss the pricing of the Microsoft Azure , illustrated by some cost examples of ISVs applications with their monthly costs on Microsoft Azure Each of the 3 sections provides details on one of these goals.
- Key Point: Microsoft Azure can help ISVs throughout the application development lifecycle of developing, selling, deploying and managing applications. The case studies below amply illustrate some of the benefits. Thinking back to the challenges and top of mind issues outlined at the beginning of this deck, Microsoft Azure can help address each of them: Remaining competitive; Staying focused; Reducing costs; Managing data centers; Maintaining security, privacy, continuity; Embracing globalization When developing applications It can help you innovate quickly via an open, comprehensive on which to develop new applications or migrate existing ones or even create hybrid applications. http://www.microsoft.com/casestudies/Case_Study_Detail.aspx?CaseStudyID=4000010792 (Vela Studios, Germany - used Java and PHP to develop mobile apps) http://www.microsoft.com/casestudies/Case_Study_Detail.aspx?casestudyid=400000000081 (Gigaspaces, US - provides tools to ease Java app development on Azure) When selling applications It can help you grow revenue by Monetizing existing IP, or reaching new customers and new geographies Extending your on-premise applications via a hybrid model Generating leads through an application marketplace And by providing a rich partner support eco-system that includes sales, marketing and technical resources http://www.microsoft.com/casestudies/Windows-Azure/Talentsoft/Human-Resources-Solution-Vendor-Uses-Cloud-to-Capture-New-Markets-Cut-Costs/4000011149 (Talentsoft UK- Human Resources Solution Vendor Uses Cloud to Capture New Markets, Cut Costs) http://www.microsoft.com/casestudies/Case_Study_Detail.aspx?CaseStudyID=4000010842 ( Spikes Cavell UK - Government Spending Analytics Provider Uses Cloud to Scale Solution, Expand Overseas) When deploying & managing applications Once your applications are in market, Azure helps you deploy and manage applications with greater efficiency You can scale reliably and cost effectively with fully managed hardware and software, reducing costs for you and your customers You no longer have to manage multiple versions of on premise software, nor plan and manage infrastructure capacity, performance, and availability. You’re free to return to the beginning of the cycle and develop and sell more applications. http://www.microsoft.com/casestudies/Windows-Azure/Soluto/TechCrunch-Disrupt-Winner-Chooses-Windows-Azure-Scales-to-3-Million-Downloads/710000000248 - (Soluto Israel - TechCrunch Disrupt Winner Chooses Microsoft Azure, Scales to 3 Million Downloads) http://www.microsoft.com/casestudies/Windows-Azure/SIVECO-Romania/Ministry-Creates-National-Cloud-Service-to-Ensure-Top-Performance-of-Exams-Website/435000000081 (SIVECO Romania - Ministry Creates National Cloud Service to Ensure Top Performance of Exams Website)
- Key Points: There are 2 ways in which Microsoft works with ISVs using Microsoft Azure The ISV is the direct interface with the customer The customer buys application and Microsoft Azure from the ISV, then the ISV pays Microsoft The ISV builds the app for the customer, but Microsoft owns the billing relationship with the customer
- Key Point: There are several ways to buy Microsoft Azure. Microsoft provides flexibility via a variety of purchasing options, allowing customers to control costs and choose how services are priced. Pay as You Go: allows you to pay-as-you-go for consumption, based on a variety of usage meters. There are no minimums or commitments, and you can cancel anytime. That’s Microsoft’s most popular and flexible payment plan. Enterprise Agreement: To further optimize costs for large-scale cloud service offering, volume discounts are available for coordinated purchasing through EA. Any Enterprise Agreement customer can add Azure to their EA by making an upfront monetary commitment to Azure. That commitment is consumed throughout the year by using any combination of the wide variety of cloud services Azure offers from its global datacenters. If a customer’s usage exceeds their commitment, they will be billed in-arrears for that usage, either quarterly or annually depending on whether that additional use is more than 50% beyond their original commitment Open Licensing: (New as of August 1, 2014) When you resell Azure in Open Licensing, you purchase tokens from your preferred Distributor and apply the credit to the customer’s Azure Portal in increments of $100. The credits can be used for any consumption-based service available in Azure. To add more credit, you simply purchase new tokens and add them to the account. This gives you the opportunity to manage your customer’s portal, setup services, and monitor consumption, all while maintaining a direct relationship.
- Key point: There are multiple methods for monetizing cloud offerings….and they are not all mutually exclusive. Many cloud providers successfully combine several methods to arrive at a hybrid pricing model. Details for each pricing model are included below Free models: Providing a basic level of service for free and then offering premium upgrades. There is much to be said in favor of incorporating this method into your pricing model since it significantly reduces any barriers customers may have in trying out your software. Once they have started to derive business value from it, they will quickly outgrow the limited number of features available to them and want to upgrade. Your challenge here of course is to package your features and functions in such a way as to increase the number of customers who are upgrading. Ad Based Revenue is a valid pricing method, though a tough one to successfully implement. Having said this, Google and Facebook have both generated significant revenues from advertising while providing their services free of charge for users. Other companies can also make this model work for them. Related Services charged – in this model the application is free but you may have to pay for some related service or virtual goods. Most commonly this is leveraged in free games where you can do micro transactions and in consumer websites Per Unit Per Meter - this has applicability only in certain situations. It is good, for example for file sharing or backup applications. When it is applicable, it is often used in combination with other methods such as per user pricing. The growth goal in this scenario is to increase storage per customer. Per transaction pricing is also a common pricing method, but not applicable to every application where it may be hard to carve out discrete transaction units. The growth goal here, of course, is to increase the number of transactions per customer. Per User pricing is one of the most common pricing mechanisms. This may include number of seats or named users. Once again packaging your offering in such a way as to make premium upgrades available will help to ensure that you are providing a low end, easy point of entry for your customers and then quickly encouraging them to upgrade in order to have access to an expanded set of functions and features and/or additional users, thereby increasing your average revenue per customer. Payment types A monthly subscription is one of the most common payment mechanisms though lack of robust billing systems means that this is often billed annually in commercial sales. Consumer sales however require the billing systems to be in place even before the service is offered. Revenue Share many services which are sold via a reseller require the ISV to take a cut of the revenues and share the rest. The share is most often higher for whoever owns the brand and customer relationship. Perpetual License Fee this is seen most often in companies that offer on-premise software and have not yet fully transitioned to the cloud business model.