Our April Telco API Working Group ended with one of the most honest and valuable discussions we’ve had so far on Network APIs.
Not a polished panel. Not a one-way presentation. But a real, open exchange between operators, CPaaS players, aggregators, and ecosystem partners.
The kind of discussion where people challenge assumptions, share what’s actually happening in the market, and everyone walks away sharper.
And one question sat at the center of it all:
Why is adoption still not happening at scale?
1. We’re still selling APIs instead of outcomes
A clear takeaway:
Enterprises don’t buy APIs. They buy solutions.
No one is asking for SIM Swap or Number Verification in isolation.
They want better onboarding, less fraud, more trust, faster customer journeys, stronger compliance, and better customer experience.
Network APIs are ingredients. But we are still not consistently turning them into something enterprises can easily understand, buy, and deploy.
2. The ecosystem is too complex
Another reality came through strongly: this is a highly fragmented ecosystem.
Operators, CPaaS providers, aggregators, hyperscalers, developers, enterprises, regulators, analysts, and industry bodies all play a role.
That creates opportunity, but also friction.
One of the strongest insights from the discussion was simple:
If we need 10+ stakeholder groups aligned to make something work, simplicity becomes critical.
The story, packaging, onboarding, commercial model, and developer experience all need to become easier.
3. Standardization is progress — but not enough
There is real momentum around CAMARA and GSMA Open Gateway.
But standardization alone does not create demand.
In some cases, it can even introduce new friction: performance differences versus existing solutions, inconsistent implementations, unclear commercial upside, or limited geographic availability.
If the “new way” is harder, slower, or less valuable than the current one, customers simply will not switch.
4. We may be looking for growth in the wrong places
A strong point raised in the discussion was that trying to replace existing solutions in mature markets is extremely difficult.
Why?
Because those solutions already work. Expectations are set. Customers already have suppliers, pricing, latency benchmarks, and operational processes in place.
So instead of forcing change where the market is already established, we need to ask:
Where are the new use cases? Where are the greenfield opportunities? Where can Network APIs become part of something genuinely new?
That may be where real traction starts.
5. The missing “must-have” moment
Compare Network APIs to AI.
With AI, companies say: “We need to do something with this.”
With Network APIs, that urgency is not there yet.
There is no clear “must-have” moment. No obvious killer use case that makes enterprises wake up and say: “We need this now.”
Until the industry creates that moment through tangible business value, adoption will naturally remain slower than many forecasts suggest.
6. CPaaS can be the bridge — but it needs to evolve
There was strong alignment that CPaaS providers can play a critical role.
They connect telco capabilities with developers and enterprise customers. They understand APIs, communications workflows, customer engagement, and go-to-market.
But this also requires a shift.
Selling Network API-powered solutions is not the same as selling SMS, voice, or basic messaging services. It requires solution selling, vertical understanding, business case articulation, and clearer packaging.
CPaaS providers may be the right bridge. But the bridge still needs to be built properly.
7. What needs to change
The conclusion was clear:
We do not just need to move faster. We need to move differently.
That means moving:
- From APIs to solutions
- From supply-side thinking to demand-side value
- From complexity to simplicity
- From fragmented experiments to repeatable playbooks
- From theory to execution
That is exactly what we are now taking forward into our upcoming Network API acceleration workshops, starting in Copenhagen around DTW Ignite.
Why these discussions matter
What stood out most was not just the conclusions. It was how we got there.
This was a conversation where different parts of the ecosystem challenged each other, shared real frustrations, tested ideas, and advanced the thinking together.
That is what makes CPaaSAA working groups valuable.
Not just content. Not just networking. But genuine learning, honest debate, and practical progress among people who are actively building this market.
Network APIs will not scale because the industry publishes more APIs. They will scale when we turn them into valuable products, clear use cases, and trusted enterprise solutions.
That work is now underway.
Join the conversation
If your company is working on Network APIs, AI in communications, CPaaS, identity, fraud prevention, customer engagement, or telco innovation, CPaaSAA is where these conversations are happening.
Our members do not just follow the market. They help shape it.
Join CPaaSAA to be part of the working groups, research, workshops, events, and ecosystem discussions that are moving the industry forward.
My lifetime in IT and telecoms has been dedicated to innovation, building bridges and creating change. From the early days of cloud communications to working with operators on innovations and business development, and currently emphasizing APIs, CPaaS/CX and AI, my journey has been one of continuous evolution.
As founding partner at CPaaS Acceleration Alliance and The Next Cloud I'm privileged to help global telcos and techcos thrive in a fast changing world - through events, community building, strategy and global business development. I thrive on challenges and change, strategizing in cloud communications, and bringing people together for mutual success. Travel and continuous learning are my passions.
I believe the global communications industry is pivoting to prioritize customer experience and impactful solutions over mere technology and platforms, and we can tackle societal challenges by merging the strengths of corporates and innovators within new ecosystems.
Comments are closed