01793nas a2200121   4500008004100000022001400041245007700055210006900132260004200201520137600243100001601619856003601635       2010                        eng d  a1913-610200aCommunications Enabled Applications: Building Value, not Monetising APIs0 aCommunications Enabled Applications Building Value not Monetisin  aOttawabTalent First Networkc05/20103 aOver the past decade there have been numerous attempts at opening telecom infrastructures to developers. As each attempt evolves to the next, there is an equal desire to monetise the exposure of telecom capabilities using traditional and well understood mechanisms: charge for necessary equipment upgrades and license the application programming interfaces on a per-invocation or "block of simultaneous invocations" basis. However, the various vendors and development companies involved in creating applications with embedded communications capabilities have had to re-examine their business and technology models in an increasingly competitive applications market where the rate of applications failing to gain market traction far outweighs the rate of success.

This article looks at the history of telecommunications APIs and the predominant business models that have accompanied those interfaces. By analysing the history of telecom APIs and recognising the gradual shift from a strongly vendor controlled environment to a highly accessible component of IT networks, we can recognise the shift in revenue generation from a typical monetisation model to a value based model. Additionally, we can examine how incumbents and new entrants are dealing with the more unpredictable business models and emerging methods for de-risking value based revenue opportunities. 
 1 aPyke, Craik  uhttp://timreview.ca/article/347