---
title: Interview with Jonas Cedenwing, CTO of Telness Tech
description: We sat down with Jonas Cedenwing, CTO of Telness Tech, to discuss the real cost of building everything yourself and the advantages of a platform designed for automation from day one.
pubDate: 2025-11-21
updatedDate: 2025-11-27
---

We sat down with Jonas Cedenwing, CTO of Telness Tech, to discuss the real cost of building everything yourself and the advantages of a platform designed for automation from day one.

## Q: **Everyone talks about APIs as the modern way to build a telco. What’s your view?**

_APIs are absolutely essential. They’re the backbone of any modern telecom architecture. They give you flexibility, extensibility, and the freedom to integrate with anything._

_But APIs alone are not enough to run a telco. APIs should extend your business — they shouldn’t become your business. It’s where API-only vendors fall short — leaving you to build the hard parts yourself._

![](./d1d1e84798-api-error.png)

## Q: **What do you mean by “API-only”?**

_When a vendor gives you endpoints but no orchestration, you’re left building all the telecom processes yourself: provisioning, activation, portability, top-ups, suspensions, dunning, billing — the list never ends._

_What starts as “freedom to build” almost always turns into rebuilding the basics. Your engineers suddenly have to become telco experts, and that’s not what most operators want to spend their time or budget on._

![Telness Tech goes beyond just API:s - Seamless OS handles automation and the full lifecycle of a customer.](./c3e0634769-workflows.png)

_Telness Tech goes beyond just API:s - Seamless OS handles automation and the full lifecycle of a customer._

## Q: **So the real issue isn’t the APIs themselves?**

_Exactly. The challenge isn’t APIs — it’s the lack of a platform around them._

_APIs should be used where you want to differentiate. But if APIs are the only tool you get, you end up owning orchestration, lifecycle logic, workflows, error handling, and integrations._

_You’re effectively handed the entire telco complexity._

## Q: **What problems do operators typically run into with API-only solutions?**

_Three things show up very quickly:_

1. _**No orchestration or logic**\_\_: APIs connect systems, but they don’t coordinate or manage your business rules._
2. _**Endless integration work**\_\_: Every feature you want to launch becomes another development project — more code, more testing, more maintenance._
3. _**Invisible costs**\_\_: Devs, infra, bugs, delays — none of that shows up in the vendor pitch, but it absolutely shows up in your budget._

_APIs are powerful, but only when used purposefully and supported by a real platform._

## Q: **How can an operator tell if a vendor is giving them a toolkit rather than a platform\*\***?\*\*

_There are a few simple questions that reveal everything:_

##### _**How can I change what happens when an API is called?**_

_If the answer is “you implement it yourself,” it’s a toolkit._

##### _**How is automation built?**_

_No workflow UI or rules engine? You’ll be building automation yourself._

##### _**How are new products launched?**_

_If every plan or add-on requires developer work, it’s not a platform._

##### _**How are updates rolled out?**_

_If every change needs code deployment or reintegration, you’ve bought the plumbing, not a platform._

##### _**How many engineers do I need?**_

_If the vendor expects a large integration team, that tells you everything._

##### _**What actually drives time-to-market?**_

_If it depends on how quickly you can code — not how quickly you can configure — you're dealing with a toolkit._

_These questions cut through the marketing very quickly._

## Q: **What does a modern approach look like instead**?

_The principle is simple: Use plug-and-play whenever possible. Use APIs to differentiate._

_Operators need:_

- _Ready-made orchestration_
- _Pre-built lifecycle logic_
- _Battle-tested workflows_
- _Fast configuration tools_
- _APIs and webhooks for deep customization_

_But they also need:_

- _Flexibility_
- _Extensibility_
- _The ability to build unique customer journeys_

_You shouldn’t have to choose between the two._

_We should be using APIs where they actually differentiate — customer experience, bundling models, pricing logic, partner integrations — not for the baseline plumbing every operator already needs. If the foundation is already built, teams can finally spend their time on APIs that move the product forward instead of recreating the ones that simply keep it alive._

## Q: **How does Seamless OS solve this, and what’s the real impact for an operator choosing Seamless OS over an API-only vendor?**

_Seamless OS combines both worlds. It’s a full operating system for telecom with everyting they need._

_We handle the telecom complexity so operators can focus on their business — not on wiring together infrastructure. It’s the difference between building a telco and running one._

_While others are still solving number portability, our customers are already live and planning their next campaign._

_With Seamless OS, you launch quickly, operate efficiently, and extend intelligently — using plug-and-play where it makes sense and APIs where you want to differentiate._

_That balance is what modern telecom requires._

![](./4c97d73cad-seamless-os.png)

## Curious how we do it?

Our team is always open to chat — whether you're exploring or ready to move.

[Let's talk](/contact)