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
Posts Tagged ‘time’
Resolving SaaS Usage and Billing Disputes: Case Study and Best Practices
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”?
Don’t Put Your Software License Business in Jeopardy – Entitlement Management BI has the Answers
By: Chris Wendt I found a way to beat Jeopardy, especially when my software license business is at stake. When I need answers, I found that I only need to ask the right question, “What can a COTS software licensing and entitlement management system do (provide) for me that an ERP or a homegrown system can't provide?” Software entitlement management systems are an integral part of protecting your organization's valuable IP, generating licenses, and providing the customers with a nice self-serve portal to manage licensing and compliance. But, such a system can also provide you with valuable information from which you may be able to tune your business. An entitlement management system is often integrated with other systems such as CRM, ERP, and LDAP to perform the operations backbone for all business processes. An entitlement management system is also the system of record for software downloads, and license key generators and can provide valuable information for improving processes and increasing revenue. Consider the following, “What can a COTS software licensing and entitlement management system do (provide) for me that an ERP or a homegrown system can't provide?” Determine channel velocity, or, sales effectiveness through a channel –determine the elapsed time from when an order is shipped to a channel partner, to when it is eventually activated by the customer to find interesting patterns in different partners and partner processes, helping you to improve the time to revenue, and perhaps increase revenue. Measure the effectiveness of new upgrade campaigns by measuring the time it takes for customers to activate new versions of products from the time the release is made available. Establish support business readiness parameters for support by knowing, based upon the historical time from shipment to activation, when you may receive the bulk of support calls regarding features/functions in the new release. Find where piracy may be occurring, or, where there are up-sell opportunities, via standard reports to determine which licenses are activated multiple times, or attempted to be activated multiple times and establish patterns. Find sales opportunities by looking how many demo license activations actually convert to revenue licenses, and, if in the process there are patterns around channel partner, geography or type of user that allow the tuning of such programs. When selling through a channel, get more real time-data on which products are selling best by looking at product activation reports. By viewing activation reports in an indirect sales model, tune up-sell programs by knowing which combinations of products are actually used in combination, and correlating that to geography, channel partner, or type of customer. By viewing patterns in activations for new product releases, determine how many products are still active for obsolete or end-of-life products, so that you can determine the need to create a campaign to migrate these customers to new releases?” So, are you ready for some Jeopardy? If you need answers, just ask the right question, “What kind of business intelligence can I get from a COTS entitlement management system ?”
Document Your Software License Compliance Philosophy
By: Cris Wendt If you sell software licenses, has your management taken the time to document your company view on software license compliance? If not, it may be time. Your views on compliance and the associated mechanism you choose to enforce compliance will affect top and bottom line revenue as well as your customer experience. The software market is certainly maturing and evolving when it comes to understanding richer and more nuanced views on software license compliance and enforcement. In fact, if you talk to different individuals within a single company, it's enlightening to discover that many of them have slightly different views on compliance and enforcement, and they often describe their individual views in such a way that they make it sound like it's the corporate position. Within a single company, I hear such diverse positions as: “We trust our customers and need to stay out of their way. Our enforcement behavior should just consist of providing some usage reporting that the customers and our sales force can use to have a conversation about pricing.” “We can't let our customers use software they aren't entitled to use! If they don't have a license to use software, then we should have an enforcement mechanism that shouldn't let them use the software until they pay us!” “We can just suddenly shut down a customer if they're using our software and need additional capacity. For enforcement, we should have license technology that allows them to use some “over-draft” for awhile, and then we should shut them down after providing plenty of messages.” It's good to hear such diverse views, because a single software company can sell to a variety of customers in different markets where the customer behavior toward license compliance varies. Just like products can be targeted to different market segments, so too can enforcement be adjusted to meet market needs. However, such comments as the ones above underscore a more fundamental need. With such potential diversity of positions existing within a company, software vendors should take the time to write down their corporate compliance philosophy. This is a business exercise that should involve senior management, as both the customer experience and revenue are both affected. By writing down the corporate philosophy, everyone can be clear on what the company believes about compliance, even if the philosophy acknowledges diversity of markets. Such an exercise will be quite beneficial in terms of internal and external messaging about compliance, and, as a way to guide investments in the selection and deployment of enforcement technology so that the corporate perspective is reflected. Want to see a sample of a compliance philosophy? If so, let us know and we can send you a sample.
Accelerate Software License Revenue Recognition
By: Cris Wendt Software license revenue recognition is the one accounting process that piques the interest of most executives in software
Track Short Term “Demo” Software Licenses to Improve Business Results
Not all short-term software licenses are created equal, especially non-revenue licenses. Software publishers generally do a good job tracking their revenue licenses, but they will often treat all non-revenue short-term licenses as “demo licenses” to address a variety of pre-sales, administrative and other issues.
Pricing Peak Usage Pay-Per-Use Software Licensing Models in the Cloud (Squall Computing)
By: Cris Wendt Pay-per-use license models are beginning to emerge as software vendors begin to take advantage of the cloud computing fabric. In the technical markets such as electronic design automation, life sciences, and mechanical development, users are often faced with the problem of needing to do a large simulation or analysis that far exceeds the existing supply of software licenses and CPU power. Their providers, the supplier of technical tools, are turning to the cloud to enable peak periods of high performance computing by enabling the creation of virtual machines that run in the cloud for burst periods.
Email from roadrunner (time warner) about copyright infringement?
I received this email from RoadRunner about copyright infringement. Just wondering how many people get these and what happens? I only had one movie I downloaded from utorrent, I deleted it and the program. I know people download tons of movies all the time. Anyone know any facts about this?
Thanks.
Guide to Purchasing Legal Time and Billing Software (Part 1 of 3)
Legal software purchasers beware! The sticker price of a software package may look like a bargain. But if you base your choice of law office billing software on price alone, your final costs may add up to an unpleasant surprise.
Regardless of the ease and purpose of the legal software you’re choosing, or your own skill with technology, it’s important to grasp the price of ad hoc services, charges and other add-ons that make what sounded like a bargain a very bad deal indeed.
First, consider that all law office software requires the following:
• Software Training . Training teaches you, your fellow lawyers, and your staff a) the major features, b) how to adapt technology for your particular need c) the bells and whistles of your new legal software.
Say its legal time and billing software . Everyone that will use this software to enter their time tracking, setup matters, billing, payments, special rates and discounts, and the like (we’ll refer to them collectively as “administrators”) must be newly trained. Cumulative and repetitive training can be both time-consuming and expensive.
• Software Setup . You’ll need to set up your new legal billing software on all employee workstations. Again, cumulative setups—for new workstations, new attorneys, etc.—can get time-consuming and expensive.
• Practice Customization . Customizing your new software to the needs of your specific law office, practice, and state bar requirements is essential. We will cover attorney billing software customization specifically in another post this month.
In our next post, we’ll talk about the hidden costs of the above services.
Guide to Purchasing Legal Time and Billing Software (Part 2 of 3)
In our last post, we talked about the services triggered by new legal time and billing software : software training , software setup , and practice customization . Today, we’ll discuss how an all-inclusive package is mandatory for even the most technologically savvy of attorneys and law firms .
Most legal time and billing software companies offer you email only or limited # of phone calls type technical support. When this runs out, you procure your own—or use their—additional training and setup through a subcontractor typically charging $125/hour and up.
You might say this sounds adequate. But even if you yourself are technically savvy, consider:
• Your fellow attorneys, paralegals, assistants, and any new hires—an unknown factor—might need additional handholding.
• You’ll need to explore your new software extensively—through time-consuming trial and error—to figure out its particular efficiencies and special features. But why reinvent the wheel ?
• You’ll never be in complete control of your PC. Machines go down, and when they do, you’ll need expensive contractors to recover systems and data—unless you have an all-inclusive software package.
In contrast to the standard legal time and billing software package, all of Easy Soft’s software packages are all-inclusive. For one low yearly cost, Easy Soft provides all of the technical support, educational support, and setup advice that you need for every piece of legal software you purchase from us.
We believe we are the only major legal software company in the U.S. whose prices include:
• Software License.
• Complete Unlimited Training for your attorneys and staff
• Unlimited US Based Phone/Email Technical Support —crucial in the event of outages, breakdowns, data loss, etc.
• Personalized Service . During business hours, a human being always answers the phone.
• One Nominal Yearly Fee , so that you can plan your annual budget accordingly.
• No Add-On Fees —ever for these services.
In total, your software costs for the year will probably add up to less than one (1) billable hour for a single attorney in your firm.
So you get a) the incredible price, and b) worry-free technology geared specifically toward making your legal practice the most easy and effective it can be. Click here to view our complete software catalog.



Posted in
Tags: