As an engineering and product management team tasked with designing license enforcement into your products, you have many decisions around how your products will interact with the licensing code. Here’s a proven technique that will help you control how licensing gets implemented across your product lines while making the product teams’ lives easier at the same time: build an abstraction layer. Read More
My last blog discussed building a business case for implementing a software license enforcement system. A key component of the case should be a plan to minimize negative impact on the customer base. This article offers a handful of practices designed to help you ease your customer roll-out. While not every practice can apply to all cases and to all business, each should provide some food for thought. Read More
In my last blog entry (Show Me The Money, Part 1) we looked at a number of factors that play into software revenue recognition when a vendor (ISV) introduces electronic license enforcement into their product lines. Part 1 focused on the principles and mechanics behind giving customers access to the software upon order execution so that the ISV may recognize revenue. Part 1 concluded by bringing another key element into the revenue recognition equation: time. Time can affect revenue recognition in a number of ways: