Evgeny Shibanov’s Post

View profile for Evgeny Shibanov, graphic

🚀 Rethinking & Building new #Telco

𝙊𝙣 𝙩𝙚𝙡𝙘𝙤 𝘼𝙋𝙄 𝙧𝙚𝙫𝙚𝙣𝙪𝙚 𝙥𝙧𝙤𝙨𝙥𝙚𝙘𝙩𝙨... A couple of loose thoughts (untested), inspired by discussion (here: https://lnkd.in/g63wn-7w) around this publication: https://lnkd.in/gScCW_su 1️⃣ Any extra revenue is usually based on USP. There is no USP in APIs by design, because of *interoperability* and *openness*. Linux does not make money by being open 2️⃣ Everyone talks about the universe of APIs, but I wonder what the pricing will look like, because some APIs in CAMARA generate different cost pressure (SCEF/NEF, HSS/UDM, etc.). 3️⃣ Complicated pricing = unforecastable TCO for Enterprise = Procurement/Finance does not like budget with huge error margins in the EBITDA. Meaning Telcos will have to offer either bundles and/or caps. Just like their vendors ;) 4️⃣ Obviously, developers are key and marketplace is an interesting but not the only sales channel. A marketplace in the absence of USP will tend to lower the prices but making comparisons. A better channel would be through "Solutions" (aka System integration). 5️⃣ Revenue sharing works reasonably if Telco controls the garden. But: see 1 and 4 6️⃣ In fact, the availability of APIs may well lead to closed garden solutions OUTSIDE of any marketplace. The marketplace will host low-cost apps. Scalability becomes a challenge. But there could be interesting ways for Telcos to gain edge

What it will take for telcos to unlock value from network APIs

What it will take for telcos to unlock value from network APIs

mckinsey.com

To view or add a comment, sign in

Explore topics