Pricing of Information Technology

There are multiple approaches to pricing of information technology products and services.  Although pricing strategies differ based on whether the software or system is getting sold as a product or getting leased as a service, there are certain basic generic strategies for pricing the same. These strategies are being discussed in this article.

Cost-based pricing of technology is historically the most popular method since it relies on more readily available information from the cost-accounting system. Since often, information technology post deployment is treated with Activity based costing, while developed in-house for many firms, a cost based pricing strategy becomes extremely lucrative to developers for the simplicity of development. Cost of development of a software product is often calculated based on the COCOMO model or from the COCOMO – II model.

The problems of a cost-driven pricing strategy arise from the assumptions that must be made about product costs. But then, one needs to consider the fact that unit costs are volume dependent while fixed cost per unit is allocated such that it varies with projected volume. The allocation procedures, be they direct labour hours, or some other surrogate metric, are not very precise. Therefore, product costs are not too dependable and offer technology developers lower returns on their investments.

Another pricing strategy for software products and services is based on Function Point analysis and Full Function point analysis. Function Point Analysis is one of the most popular techniques for pricing of technology.  Function Point Analysis has been proven as a reliable method for measuring the size of computer software in terms of Kilo Lines of Code (and more recently, Millions of Lines of Code), based on which and its complexity of development the software is priced. Function Point Analysis has been established as being extremely robust in estimating projects, managing change of scope of implemented engagements, measuring productivity, and communicating functional requirements.

A few other pricing techniques are  MIPS-based pricing, tiered pricing, user based pricing, flat pricing and usage based pricing.

In a MIPS-based pricing strategy, software prices are based on the on the theoretical throughput of the system (MIPS) on which the software is running.

In a flat pricing contract, customers pay a fixed price for unlimited use of the software product. This approach enables customers to more easily predict what they will pay for the use of the software. In a tiered pricing strategy, vendors attempt to package software benefits according to user requirements and their willingness to pay. This approach to pricing is an attempt to link software product costs to perceived customer value.

In an user based pricing strategy, the customer is charged based on the number of users that utilize a collection of software features over a given period of time by assigning costs to a particular number of users or workstations and sum up individual cost allocation.

In an usage based pricing strategy, customers is charged by the vendor firm only for what they actually use on a transaction basis, during a contract period, say in months, but more popularly for larger IT firms and engagements, in years.

Today another popular pricing technique is based on the economic value that a client firm may get from a technology product or service level agreement. Such a pricing strategy is called value based pricing. This is slowly becoming the most popular pricing strategies followed in research labs for emergent technologies, like that of IBM Research, Microsoft Research and SAP labs.

value-based-pricing

However, which pricing strategy to deploy and at what stage is entirely dependent on multiple factors like whether it is a service level agreement or not, whether it is a product or not, whether it is being licensed as a technology platform to another implementer or not, which stage of the product life cycle is it into, what is its competitive scenario, what is the industry structure of the product or the nature of the industry where it will get implemented (say automobile vs telecom), is it entering a new market or an established one, etc etc.

Do let us know if you have any queries.

How to price IT products in 7 steps?

The technical team or the product development team has come up with a ground breaking product. The technology can have a deep impact on the customer. The technical team knows it, and so does the customer. The contract for a long term engagement is about to hit off, and then the customer asks how much will this technology cost his pockets? In this competitive world, the technology developers do want the best price for the technology, but at the same time, they really do not know what the best price is to which your customer will give the green signal for a long term engagement. So how does one price an IT product?

Since IT products are  intangible, it has been recognized that the best price for intangible products should never be determined by production costs. Cost can be the “floor” of pricing alternatives and the customer’s quantified benefit in monetary terms should be the “ceiling.” The best price lies somewhere in between and that should be based upon the value of the technology to the customer.

This pricing can be done in the following steps:

  1. Decide the various unique benefits from your product, such that there is no overlap.
  2. Quantify the objective of deliverables for each benefit, by discussing the same with your client.
  3. Map each benefit to its monetary value from the client’s data (or industry average).
  4. Ask the client how much percentage deviation is acceptable from the quantified objective of deliverables mentioned earlier.
  5. Discount the monetary value of each objective with the deviation percentage.
  6. Sum up the discounted benefits.
  7. Discount that sum by the operating profit margin of your client, and quote the calculated price.

The major point of debate for any firm, when it decides to go for an investment, is what would be the return on its investment, as the ROI figures are what often drive investment decisions. This methodology helps the client deduct the exact ROI from his investment.

Read the linked paper to know more about how you can implement value based pricing.

This paper is a must read for product development managers in IT product companies. This paper has recorded as one of the top 10 downloaded papers of SSRN.

Did you read our article on the various pricing strategies used to price information technology products and service engagements?