Posts Tagged ‘saas’

Resolving SaaS Usage and Billing Disputes: Case Study and Best Practices

By Bashyam Anant As a SaaS provider, on occasion, we run into situations where our customers question their usage and bill related to our SaaS offerings. One of the SaaS products I manage helps software publishers and intelligent device manufacturers electronically deliver software updates automatically to end user machines . Our customers are able to lower support calls and costs as a result and also gain valuable insights about their installed base. Pricing for this product is based on the number of distinct end user machines (“endpoints” for short) that receive software update notifications from the software publisher during a given subscription term; one year, in most cases. Recently, one of our customers felt that they were overpaying for the service because they did not believe that the number of endpoints reported by our product was accurate. The customer felt they only had 20,000 endpoints whereas our system was reporting 30,000 endpoints which had resulted in a significantly higher bill than what they were expecting. (Note: their actual data is not being used but this illustrates the problem the customer was facing). While such discrepancies are very rare, it can happen. To resolve such situations, we have developed the following best practices. Best Practice 1: Easily-understood Usage Metric Definition of usage metrics should ideally be self-evident to customers. While the notion of endpoints for our product is relatively clear to most of our customers, it still stumps a few. As a result, we take pains to explain it in terms that the customer can relate to. For example, if the publisher's software runs on a server machine, the number of endpoints correlates to the number of servers on which the software in installed. Nonetheless, a few such publishers tell us that they sold far fewer copies of their software during a year compared to what our product was telling them. The explanation could be as simple as customers deploying the software on multiple servers to enable development, test and production environments to something more serious such as software piracy. Best Practice 2: Self-service Usage Reporting It is important to avoid surprises at the time of invoicing. As a result, our product features a simple dial that shows the current consumption against purchased quota of endpoints each time our customer logs into the system. Should customers feel things are not aligned with their usage pattern, they can flag it right away to our support organization. It's not only important to provide customers with self-service but to also be completely transparent at all times. Best Practice 3: Capture Detailed Reporting Data While customers may never ask for it, we have found it a worthwhile practice to capture and store detailed usage information for each customer. For example, our system captures details such as daily endpoint count, how long a given endpoint was active, the most recent date when a given endpoint called home and so on. An example of such a detailed report is below. This figure shows the number of distinct endpoints that were active for less than 30 days, bucketed by the final month in which the endpoint was active, for the customer mentioned in this article (Note: numbers have been purged to protect privacy). In simple terms, such endpoints represent software that was used for 30 days or less. Figure 1: Endpoints active for less than 30 days by final month of use Such a trend has no particular relevance to us but it made complete sense to the customer, and helped them correlate software usage with ebbs and flows in their business, as we point out below. Best practice 4: Understand the Customer's Story More than anything else, we have found it useful to engage customers in a discussion of what might explain their usage trends based on the detailed report we provide them. This customer, as it turns out, is a leading manufacturer of farm equipment. Like auto and engine manufacturers, they provide software that helps dealers and repair shops diagnose problems with their engines and equipment. Our software

SoftSummit 2011 Software Licensing Conference News and Twitter Chatter

By John Lipsey SoftSummit is the industry's leading event for application producers, who come together once a year to discuss and share knowledge about software licensing, entitlement management, software delivery and enforcement.

Predictable Pay-For-Use Hardware and Software Licensing

By: Mike Costa Much has been written lately about pay-for-use hardware and software licensing – including the many benefits and drawbacks compared to the traditional, perpetual approach. Pay-for-use licensing comes in many flavors—SaaS, IaaS, PaaS, cloud computing, utility computing, etc. In general, these license models allow customers to rent all or some of the software and/or hardware for which they would otherwise have to purchase perpetual or ownership rights. One of the primary characteristics that differentiate the various types of software/hardware rental is time granularity – the duration of the rental period. Other time granularities include: multi-year, annual, quarterly, monthly, weekly and so on. Subscription and term are two popular rental models. Subscriptions generally provide for ongoing rental until cancelled with pricing based on specific configurations or products rented during one or more time intervals each. Term licensing is similar to Subscription but allows rental over a predefined period of time, not ongoing. I use the term “pay-for-use” to describe ongoing software and hardware rental types, in this case, all but Term. Pay-for-use, in its most valuable form, is fairly dynamic – within reasonable limits, of course. Suppliers can use it to satisfy customer demand whenever and wherever it occurs, gaining market share and increasing revenue. Customers can use it to improve asset flexibility, access and efficiency. So why aren't more suppliers offering pay-for-use and why aren't customers adopting this model when it is offered? The lack of predictability seems to be one of the most often cited reasons. Ironically, pay-for-use is a very important model for suppliers and customers precisely because it addresses unpredictable asset demand. Let's face it, it's a dynamic world. Customers need the ability to quickly increase software and/or hardware resources to meet peak demands – without having to over-purchase for peak needs or risk onerous audit liabilities. Suppliers would much prefer allowing customers to rent assets during these peak periods vs. having to loan them free of charge or strain relationships with audits. The loan approach is much less feasible due to Sarbanes-Oxley financial controls. So how do we crack this predictability “nut”. Actually, with an adequate infrastructure and a supportive pricing model, it can be fairly straightforward. In fact, the common cell phone pricing model provides a useful basis. The cell phone model usually includes a committed “bucket-of-minutes” plan coupled with the customers' ability to exceed his/her committed volume for a peak per-minute fee. Now, there are two major changes needed to make the cell phone model feasible for business customers. First, the peak per-unit fee has to be much less than 5-10x the committed per-unit fee – 1.25x to 2x is probably more reasonable for the same time granularity. The price difference should be high enough that it fairly compensates the supplier while not being so low that it invites peak usage as the norm. Also, as with cell phone plans, peak usage is billed in arrears and customers should be provided the ability to increase their committed volume under suitable conditions. Second, business customers must be able to proactively control their peak use expenses, not experience the surprise of receiving a “budget-busting” bill for usage run amok, after the fact. This can be accomplished by providing customers the ability to control how much, when and to which employees the peak assets are allocated – preferably without having to contact the supplier beforehand. Supplier predictability is optimized because the relative committed vs. peak pricing difference minimizes peak usage. Customer predictability is no longer an issue because they control peak quantities and licensing durations so they can therefore fix maximum incremental cost exposure. Great theory? Not at all. Flexera Software can help suppliers and customers realize these capabilities today. I've personally had the pleasure of working with two innovative software suppliers that have been providing these capabilities to customers using Flexera Software products since 1996. What is your experience with pay-per-use licensing models? Have you cracked the predictability “nut”?

Pricing “Squall Computing” Part 2 – Cloud-Based Peak Usage Pay-Per-Use Software Licensing Models

By: Cris Wendt Last week we started laying out assumptions for our burst pay-per-use cloud computing model. This week, let's look deeper into some price calculations to get at our hourly rate. So, it's math time! The first step is to start with a time-based reference for a software license price. If a company only offers a perpetual license model, a good first step is to figure out a price for a yearly subscription license model. The way software license

Software Licensing Trends: A Perspective from IDC’s Amy Konary

By: John Lipsey During SoftSummit we had a chance to sit down with Amy Konary of IDC and talk about some of the recent findings from the jointly sponsored IDC/Flexera Software Key Trends in Software Licensing and Pricing survey.

Will SaaS replace locally hosted software?

SaaS stands for software as a service. This means that instead of a business having to purchase a software package and register it for all users, relevant software packages can be accessed via a web browser. With locally hosted software, each time a business wishes to invest in a software package they have to licence it not only per user but per machine. Thus if someone works remotely part of the time, both the office and the home computer have to be licensed. This can be costly, added to which most users only need a part of each software package, not all the components. This is particularly true with software packages such as CRM (customer relationship management packages). However with locally hosted software, each user has the whole package, regardless of how much of the programme they are using.
 
SaaS works differently. Users access a software package via their web browser, meaning that wherever they are in the world they can access a programme instantaneously. Organisations pay the licence fee holder a monthly fee either per users or for a group, meaning that businesses can change who uses a package rather than re-registering all the time. In addition users can just access the parts of a programme they need.
 
For small businesses in particular, there are several advantages of SaaS. The set up costs are much lower. There is no need to invest in costly IT infrastructure such as servers to host a software programme. This also has the added benefit of speeding up start up times. Users can access software within hours of signing up rather than wait for the implementation stage to be complete, which can take weeks or even months. This also means that there are no large start up costs to be budgeted for. SaaS works by paying a monthly fee to the software holder, which means that it is much easier for a small business to find the money.
 
SaaS packages do not specify a minimum number of users, which is also helpful to a small business. In addition it means that they can use and benefit from the relevant features of software packages such as CRM software, without having to invest in the infrastructure to support them. A CRM programme for example would allow them to manage their contact base efficiently and perform key marketing functions such as sending emails and SMS directly.
 
However one concern that some businesses have is that data is stored and held by a third party. This gives some organisations security concerns and for this reason they decide that potential data security issues outweigh any benefits of SaaS. Larger organisations also have more complex infrastructure in place and so can bolt on additional programmes and packages with relative ease. For a large organisation it might be more cost efficient to invest in a software package and host it locally, with one large upfront payment rather than ongoing monthly payments.
 
Therefore, although SaaS has many advantages, particularly for smaller organisations, it is unlikely that it will totally replace locally hosted software.

SAAS: The new model for recruitment software

Software as a Service (SaaS) is the term used to describe software provided to users over a network e.g. the internet, in a pay as you go model. Not to be confused with cloud computing which refers to the slightly broader concept of web based technology-enabled services shared across the internet. Simply put, SAAS applications run ‘within the cloud’.
Continually growing in popularity SAAS is putting the old school form of the traditional software licence model into the shade for a number of reasons. 
Much, much lower start-up costs
Traditionally those looking to implement licensed based software were required to make a large up front payment to buy their software outright, which was a huge burden on cash flow particularly for those small to medium size businesses. With SaaS applications smaller recurring payments are made on an on demand subscription basis which makes them much more affordable for all.
Hassle free recruitment
SaaS providers are the ones in charge of all your ongoing maintenance & version upgrades which is a huge shift from the traditional model which would require users to have an internal IT resource to deploy and provide any ongoing support for the software. With providers constantly working on improving their recruitment software  to keep up with the market it’s essential that users receive system upgrades however this is much more practical through the SAAS model. Availability is also down to the provider therefore customers aren’t required to add any further software or bandwidth as the volume of data increases.
Life in the cloud
With web based recruitment software  this allows employees to have immediate remote access from any web browser 24 hours a day wherever they are across the globe. No software is required to be downloaded onto machines which as well as slowing them down would increase startup time. Less training time is also required as today’s users are now much more familiar with web based applications.
Higher level of service
Whilst provided in the Software as a Service model users are effectively renting software from vendors. With vendors therefore aiming to retain clients for the longest possible term there is much more of an emphasis placed on the quality of service received than there would be if there was a large upfront purchase. Crucially with outside vendors involved this takes away the responsibility of the particularly delicate area of data security.

Pay-Per-Use, SaaS and Subscription Software Licensing Model Blog Posts are the Most Popular of 2010

We took a few minutes to identify the most read Entitlement and Compliance Management: Talking Successful Software blog posts of 2010 and here is what we found… The Myths of Pay-Per-Use Software Licensing & Pricing Models What Licensing Technology is Most Effective—To Dongle or Not? Enterprise Software License Models Under Attack Don't be Afraid of Subscription License Models Floating Software Licensing 2.0 – Virtual Machines & Cloud Computing Some New Twists on Current Themes in 2010 Thinking Pay-Per-Use Software Licensing – Consider Remix! The Inevitable Move to Usage-Based Software Licensing Will Have a Profound Impact on Software License Management SaaS is More Than a Software License Model SaaS Software License Models – Can Traditional Independent Software Vendors Adapt? What topics would you like to see us address in 2011?

SoftSummit 2010 Wrap-Up: Top News from the Premier Software Licensing and Entitlement Management Conference

By: Randy Littleson Looking back at all the sessions delivered last week during SoftSummit by many leading software vendors and high-tech manufacturers and recalling how they use software licensing and entitlement management to transform the way they do business, it's hard to pick just the top stories, so I decided to highlight the keynote speakers: Tom Reilly, CEO of ArcSight , shared how his organization (HP previously announced the purchase of ArcSight for $1.5B) overcame the following business challenges: Shifting from single product to platform with multiple offerings Adding new distribution channels (Distributors, VARS, Resellers, SIs) Expanding internationally Customers requesting flexibility & new licensing models Multiple deployment options (SW, Appliance, Cloud, MSSP) Increasing frequency of software update due to threat landscape With software licensing and entitlement management solutions that have enabled his organization to: Deliver software faster, cheaper, and easier for customers around the clock Introduce new licensing models, distribution models and offerings easily Controlled international expansion Reduce risk of quarter close and revenue recognition Respond within months to competitive threat Leverage third parties One of the key takeaways from Tom's presentation that I think we can all learn from is why a CEO should care about software licensing and entitlement management. For Tom and ArcSight, growing competition, global expansion and ability to enter new markets quickly meant that his company needed to become more agile. For ArcSight, a strategic solution for software licensing and entitlement management was the key enabling technology that allowed them to quickly and easily scale and be responsive to these changing needs. Amy Konary, Director, Software Pricing and Licensing for IDC , delivered the final keynote address by sharing the preliminary results of the 2010 Software Licensing and Pricing Survey. During her presentation she playfully used song lyrics to connect the survey results to sentiments in the song. Some of the key findings included: Most ISVs (60%) believe that their licensing will need to change in some way in the next 24 months to adapt to cloud computing, with around 30% expecting significant change Around 20% of software publishers offer usage-based pricing today, and 20% more expect to offer it in two years 70% of enterprises indicated that tracking usage is either important or very important One-third of ISVs that have or plan on implementing usage-based pricing do not track usage at all today (not even manually) Most enterprises have difficulty tracking usage for the purposes of software license compliance 12% of publishers have no enforcement today, compared to 28% in last year's survey Most ISVs are increasing the flexibility of licensing by adding more choice, in order to generate more revenue (72%) and improve customer relations (69%) As I mentioned earlier, with over 25 sessions to choose from, I focused just on the keynotes. The good news is that the presentations given during SoftSummit 2010 will be posted to the SoftSummit website in about a week, so be sure to check the site to access all the presentations. In addition, the final Software Licensing and Pricing Key Trends report will be published soon. Register now to receive the complete survey results. In the meantime, Sandhill.com recently published the following: Software Pricing & Licensing Trends – 2010

The Ten Step Process: Step 2 – Use Software Licensing Methodology to Enable Product Agility in the Marketplace – Converting Your High-Tech Company…

By: Cris Wendt While there are cases where the up-sell of additional hardware capacities (more channels or throughput), or additional capabilities (more hardware functions) can be facilitated by unlocking these capacities and capabilities with license keys, it's important to understand some of the key ways software is different from hardware. These fundamental differences will enable you to think about ways of bringing new products to market. While a full discussion of these differences and issues is well beyond the space afforded in this blog, the following software licensing considerations should help you understand how the software product marketer thinks and how you, as a high-tech manufacturer, need to start thinking: Think “Right-to-Use” – Customers don't own anything when they buy software. Customers buy a right-to-use the software, based upon the terms and conditions of the software license terms or the software license agreement. Unlike buying physical goods where customers can do pretty much whatever they want with the goods, software usage is limited to terms specified in the license agreement. When thinking about creating software products, an innovative way to think of the software is, software as a service (SaaS) – a service that is performed on an ongoing basis as it is being used or consumed. So in this sense, you may ask yourself how would you price the software if it were a service – what is the service my customers want, what are the metrics of usage that I can price, and how much would I charge? Clearly Define the Terms AND Limits Of Usage Rights – These terms and limits become an important foundation in the pricing and associated revenue models so it's important to be clear about usage terms and limits when creating products and packaging. Extending the terms of a license may be offered commercially, enabling you to generate more up-sell revenue. For example, you may allow a particular software product to be used only on one physical machine. This means you price the software and define the usage limits for a software usage profile based upon usage for a single machine. If you find that customers occasionally want to move the software to another machine, to obtain more value, you can charge an additional transfer fee, or, perhaps provide a concurrent license at a higher fee. Use the Common License Model Attributes As the Key Usage Parameters To Build Your Pricing And Revenue Models License Term – this refers to whether the right-to-use is a perpetual license, or, a time-based right-to-use (subscription license). The industry trend is a movement toward time-based license models. License Metric – this refers to a unit of usage upon which you can base pricing, one that ideally scales with usage. This should match how the customer uses your product and is willing to pay for additional usage. Some common metrics are “per device”, “per user”, “per concurrent user” and “per managed capacity” (e.g. number of channels, channel bandwidth). Product Features/Package – this refers to an aggregation of technical features that form the basis of a meaningful customer product. Build Your Software Products Lines Based On Value And Markets – when building your software products (consisting of different product models with associated price points) be sure to consider the different ways that the software will be used to derive value for different types of users and/or markets. For example, it's possible to sell a virtual appliance software license for $1,000 that is licensed to be used in one physical site for small customers, whereas a price point (for example) of $2,500 can be created that allows the virtual appliance to be used in any geographic location, possibly for cloud computing applications required for large enterprises. Alternatively, a time-based or rental license can be sold that allows a customer to use a virtual appliance for a short period of time, unusually during high usage (such as a tax preparer may see). This is where a good understanding of customers and usage profiles for different markets can pay dividends when creating product lines. Add Programs and Discount Structures – with the product lines in place (and evolving over time), you can create a series of discount structures and various license programs to target different markets or channels (e.g. managed service providers, service providers, channel partners, etc.) Ultimately, you will want to trade-off simplicity and precision when making decisions in order to balance revenue opportunity with operational costs, but thinking about the fundamentals above will help you think about new ways to monetize your offerings. Next Week – Step 3: Balancing Revenue Recovery and Customer Satisfaction with Your Compliance Strategy

Cloud Computing as an Innovator’s Solution

by: Basham Anant There is a lot written about Cloud Computing as a disruptive technology trend. Software-as-a-Service (SaaS) is an important Cloud Computing segment. As it relates to packaged software companies, I believe Cloud Computing can be a solution for incumbents that are facing the very real possibility of being made irrelevant by Software-as-a-Service (SaaS) and Open Source entrants. One of the major selling points for SaaS is the near-zero upfront and ongoing costs for customers with respect to procuring prerequisite hardware and software, getting the software installed and configured and managing all of it once in production. With Cloud Computing, you could mimic these benefits of SaaS by packaging your software into virtual appliances, much like Oracle has done for its database software and developer tools (see Oracle Appliance on Amazon EC2 for details ) . This approach can allow incumbents to mimic the “zero software” benefits of SaaS and preempt it in some segments. In particular, virtual appliances, when priced appropriately, can prempt the so-called low-end market disruption that SaaS targets. Low-end market disruption (see this article for a discussion of new market vs low-end disruption ) refers to situations where an entrant offers a cheaper product with a lot less functionality. Virtual appliances, in particular, can potentially help you price and package your products for entry level users and occasional users and push the cost of managing the software and hardware to a cloud service provider like Amazon. Interestingly enough, according to Innovator’s Solution , a technology that is not disruptive to all incumbents does not meet the criteria for a disruptive technology. Which begs the question, is SaaS really disruptive, at least as described in this article?

SoftSummit Shaping up to be a Great Software Licensing and Pricing Event

We're about a month away (October 11-13) from our annual SoftSummit software licensing and software pricing conference in San Jose, CA.