There aren't many companies that can honestly say they changed an industry.
Twilio is one of them.
Before Twilio, adding SMS or voice to an application meant working directly with carriers, managing telecom infrastructure, and dealing with protocols that most software teams had no interest in learning. Twilio abstracted all of that complexity behind a simple API. Suddenly, communications became something every developer could build into an application.
That wasn't just a successful product. It fundamentally changed software development.
If you wanted to add messaging to your application ten years ago, Twilio was the default answer.
Today, I think something has changed.
It's not that Twilio has become a worse company. In many ways, they're stronger than they've ever been. What's changed is the market around them.
When I talk with founders and engineering teams today, the conversation rarely starts with, "Should we use Twilio?"
Instead, it starts with a different question.
What do we actually need from our communications platform?
That may sound like a subtle difference, but I think it represents one of the biggest shifts happening in infrastructure software.
For a long time, communications APIs were viewed as interchangeable utilities. If you needed to send a text message, you integrated an API. If you needed to place a phone call, you made another API request. The communications provider was simply another service in your stack.
That's no longer how most engineering teams think about it.
Communications have become part of the product itself.
A healthcare company isn't just sending appointment reminders. It's verifying patient identities, protecting sensitive information, coordinating with providers, and making sure critical notifications arrive when they should.
A fintech company isn't simply delivering one-time passcodes. It's trying to prevent fraud, reduce customer friction, and communicate within seconds when something looks suspicious.
An AI company isn't just generating responses. It has to know when to text a customer, when to make a phone call, when to escalate to a human, and how to communicate across multiple channels without creating a fragmented experience.
Those are infrastructure problems, not messaging problems.
The result is that developers have started evaluating communications platforms differently than they did a decade ago.
Price matters, but it isn't the only consideration.
Reliability matters.
Deliverability matters.
Compliance matters.
Developer experience matters.
Support matters.
The ability to scale globally matters.
Increasingly, AI readiness matters too.
Every engineering team will weigh those priorities differently, which is exactly why the communications market has become more competitive.
That's healthy.
Companies like Signal House, Telnyx, Sinch, Infobip, and others aren't trying to recreate the communications market that existed in 2016. They're building for the applications being developed today. Some are focused on pricing. Others emphasize carrier connectivity, compliance, AI integrations, global infrastructure, or developer experience. Each reflects a different view of what modern software teams value most.
One of the biggest changes I've noticed is that developers aren't thinking in terms of channels anymore.
Ten years ago, the question was, "Should we send an SMS?"
Today it's, "What's the best way to reach this customer?"
Sometimes that's SMS.
Sometimes it's a phone call.
Sometimes it's WhatsApp.
Sometimes it's RCS.
Increasingly, I think those decisions won't even be made by developers. They'll be made by AI systems that choose the best communication method based on context, urgency, customer preferences, and expected outcomes.
When that happens, the communications platform becomes much more than an SMS API.
It becomes part of the decision-making layer of the application itself.
That's why I believe communications infrastructure is entering another period of transformation.
Twilio created the modern communications API market. Every company in this space owes something to the path they paved.
But software doesn't stand still.
Developer expectations don't stand still.
Infrastructure doesn't stand still.
The next generation of communications platforms won't win simply because they offer more APIs. They'll win because they help developers build applications that communicate more intelligently, more reliably, and with far less operational complexity.
For developers, that's a good thing.
Competition drives innovation, creates better products, and gives engineering teams more freedom to choose the platform that best fits the software they're building instead of adapting their software to fit a single platform.
And I think that's exactly where the industry is headed.
About the Author
Jason Perkins is the Founder and President of Signal House, a communications infrastructure platform that helps developers build SMS, voice, phone numbers, verification, and AI-powered communications into modern applications.
Comments
Loading comments…