Featured

ISV Viewpoints

Knowledgebase

Latest News

Video & Podcasts

Home » Latest News

Time to Review Your Software Licensing Policy?

Submitted by SL.TV Editor on April 21, 2010 – 11:32 pmNo Comment

In days gone by many software developers had little in the way of a software licensing policy.  Licensing agreements were drawn up on the fly by sales execs as a part of negotiating individual deals with potential customers.

This approach to software licensing could be seen as flexible or chaotic, depending on your point of view.  It may or may not have helped sales to clinch more deals, but it certainly has led to a lack of transparency for customers and a good deal of licensing confusion for ISV’s.

In a recent report the IDC sets out the case for developing a coherent software licensing policy.  Some of the key benefits they see include:

  • A shorter and more efficient software sales cycle
  • Reduced time spent re-inventing the software licensing wheel
  • Reduced software licensing contract administration time and costs
  • Reduced opportunity for error
  • The ability to create a strategy for addressing important issues that impact the way software is licensed that works for the vendor from a profitability perspective while addressing the needs of the customer.
The IDC paper covers a list of 10 software licensing policy areas which ISV’s should consider. You can read the full report here.
The IDC’s final point centres around License communication and urges ISV’s to offer customers more transparency.  As customers ourselves we all recognise the situation where we identify a piece of software we are interested in, search the website for some indication of pricing and licensing terms, have to resort to calling a sales exec to get that information and then feel that the sales rep is probably selling us the license package that is most advantageous to him at the highest price he thinks we can afford.

IDC points out that whilst a price list published on an ISV’s website probably doesn’t bear much relation to what many customers are actually going to pay – it will nevertheless be welcomed by customers along with any other information that helps them to understand your licensing policy, the rationale behind it, and the options open to them.

For example, Software License Management vendor Nalpeiron publishes a fixed price for it’s services whereas many providers in this space has a % of revenue charging model, CEO Jon Gillespie-Brown says that “price transparency is very important to our Customers, they like the ability to plan going forward based on a fixed set of costs and to be able to understand and test the return on investment in their software purchases. Also, showing the cost of goods in a clear and easy to understand way promotes trust and a long term relationship”.

Increasingly both business and private customers are no longer happy to take a passive role in the software buying process and simply be “sold to”.  They are demanding the information needed to make educated buying decisions themselves and as the IDC points out an ISV who offers that information will have created a point of differentiation for themselves.

The IDC recommends that software licensing policy communication should:

  • Outline the key elements of your policy.
  • Show sample scenarios to help customers navigate choice.
  • Explain the rationale behind your approach.
  • Offer a tool or calculator to help customers make choices and understand what
  • they might need to pay.
  • Make it easy for customers to obtain this information — don’t put it behind a registration page.

In an age of rapidly changing software licensing models, and rapidly changing consumer behaviour, regular review of licensing policy is probably going to become a necessity.

Popularity: 13% [?]

No related posts.

Leave a comment!

Add your comment below, or trackback from your own site. You can also subscribe to these comments via RSS.

Be nice. Keep it clean. Stay on topic. No spam.

You can use these tags:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

This is a Gravatar-enabled weblog. To get your own globally-recognized-avatar, please register at Gravatar.