Pricing models for Outsourcing and BPOs

Outsourcing in current times is more value adding exercise done to enhance competitive advantage by focusing on the areas of core competency rather than just a cost saving practice, as it used to be. Its role as a business-value-creator is established across the world in terms of long-term gains like increased customer satisfaction and decreased customer churn along with short term cost cutting. Along with changes in outsourcing objectives and practices, the pricing models also keep changing in the outsourcing industry.

A transaction based pricing model is based totally on the number of transactions. It draws theory from the concept of economics of scale from resource sharing and usage based pricing. In this pricing model the client typically pays the service provider for individual transactions or per unit of work performed by the resources deployed. In such a model, SMEs benefit drastically from resource sharing with overall lower cost of outsourcing. An average base level of transaction is defined in the SOW, the fluctuation from which impacts the per-transaction base level pricing, in this model.

Similarly, an FTE based pricing model is one where the client pays for the time & material invested directly by the service provider. Often in outsourcing contracts, this is further broken down into multiple categories dependent on the expertise of the resources deployed, complexity of tasks performed (which impacts turn-around time of task completion), degree of domain experience and onshore/offshore presence. Typically these are fully loaded costs with often standardized SOWs including factors like number and level of resources deployed; infrastructure and external dependencies bundled into the price points.

While another variation of pricing models that can under serious contemplation is the Risk/Reward sharing pricing models, where the benefits and the losses of the services outsourced are shared amongst the partners. This is a move towards greater collaboration between separate partners in a value chain. However, for such a pricing model to be really successful there has to be significant maturity in the process level which can then be mapped to quantifiable benefits. As of now, since the services rendered by BPOs/KPOs are yet to reach the required level of maturity, these pricing models are yet to be adopted as industry standards.

Next comes the big question: When to choose which pricing model? Typically transaction-based pricing models would be more suitable for Small or Medium sized organizations where transaction count would not be significantly high. In such organization, keeping a dedicated division (with active resources) would be more cost-intensive than sourcing it to third party service providers. Thus in such scenarios, a transaction based costing would be more beneficial. Similarly, if the transaction volume is on the higher side, a FTE based pricing model (and outsourcing SOW) would be more cost effective and thus more suitable for the organization. Also, if the transaction levels are subject to high degree of fluctuation, a transaction based model (and thus the SOW) is more suitable and beneficial for both the parties involved in the deal.
Do let us know if you have any feedback in this context.

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?