Should I move from a perpetual to a subscription, or consumption based licensing model?
Challenge
A software company’s new owners were encouraging product managers to move their flagship product from a perpetual to a subscription or consumption-based licensing model. The product managers needed better information about customers and how they were using the product to fully understand the issues and implications.
Licensing changes are high-stakes decisions: mistakes in structuring, pricing, and packaging could fundamentally undermine the product’s or company’s viability. To plan these changes, product management needed to accurately project how customers would likely react, based on how they currently use the software. Information about user engagement can be viewed on the Product Metrics > User Engagement report:
Solution
With Usage Intelligence event tracking and user engagement reporting, the company came to understand that many users worked with their software intensely for two or three months in connection with a specific project, using a wide range of product features. But, once the project was completed, many did not use the software again for several months, until another project came along.
Avoided a costly misstep when introducing a new licensing model.
Results
If the software vendor implemented a monthly or quarterly subscription plan, as it had been considering, many of its users would likely abandon the software as soon as their projects ended, and then only briefly re-subscribe whenever the next short-term project arrived. This behavior would result in a financial disaster for the company.
Knowing this, executive leadership concurred with the product managers. For this product, if subscriptions were to be offered at all, they would need to be multi-year subscriptions with strong pricing incentives to promote the longest subscription period. By limiting shorter subscriptions, the company avoided a major strategic blunder.
Related Articles
Use Case #11: Deciding When to Eliminate Old Features and Versions That Make It Harder to Evolve Your Product 8Number of Views How to make Product Catalog Field in Request Form as Required 5Number of Views Use Case #10: Deciding When to End-of-Life a Product 8Number of Views Use Case #1: Convincing Customers to Upgrade to the Newest Version 12Number of Views Use Case #17: Discovering What Hardware Environments Customers Are Using 6Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Revenera Assistant
Case id: 00001065
Activity: Status change: 2 hours ago