Telness Tech

Name: Telness Tech
Brand: Telness Tech

AI Native

Become Seamless. Launch, upgrade or turn into a mobile operator using Seamless OS from Telness Tech

Est 2020|Raised $16.1M

LinkedIn 3K|Web traffic 2K|FTEs 40|HQ Stockholm, 01, SE

Published Sep 19, 2026

01Common complaints

- When the procurement process requires independently validated security and compliance documentation (SOC 2 Type II, ISO 27001) and the vendor cannot provide those reports promptly. - When the operating model is highly bespoke and the organization expects the vendor to custom-build extensive workflows; heavy customization can negate the benefits of a standardized platform approach. - For Tier-1 operators that require maximal module breadth (network inventory, orchestration, assurance, complex enterprise constructs) and multi-decade vendor track records; incumbents or larger suites may be more appropriate. - When procurement relies heavily on third-party review platforms for benchmarking; limited coverage on major review platforms will make comparative assessments more difficult.

Deal disqualifiers (poor fit)

The buyer requires published SOC 2/ISO certifications as a hard procurement gate and the vendor cannot provide audit reports promptly.
The organization requires extensive legacy on-prem integration and cannot accept migration risk.
The buyer requires many years of Tier-1 public references and large-scale case studies as procurement prerequisites.

Vendor-acknowledged limitations

No explicit published limitations or roadmap caveats were found in the sources accessed.

Evidence-based limitations / risks

Security and compliance transparency gap: no public trust center or published compliance certificates located in accessible sources.
Limited third-party review coverage on mainstream platforms, which reduces independent validation opportunities.
Organizational execution risk signals from employee reviews (architecture and management concerns) that could impact delivery and support quality.

Why some customers left (churn reasons)

No public narratives describing customer churn were found in the sources accessed.

02Why they buy

Unique selling points supported by evidence or concrete signals

Public API documentation: an OpenAPI/REST documentation set for Seamless OS indicates a developer-oriented integration model.
Named market reference: a U.S. MVNO deployment provides a concrete market reference for U.S. entry.
Operator-origin narrative: origin as software derived from an operator environment is a credible formation story but does not constitute independent proof of product performance.

Areas where competitors have clearer advantages

Competitors with explicit published pricing for specific functions (for example, cloud charging) can offer clearer commercial modeling for those modules.
Larger incumbents provide established procurement comfort and broader product depth for complex operator needs.

Why customers chose Telness Tech (as evidenced)

From public customer and press statements, decision drivers cited include:

Customization and flexibility in product features (example: New York Mobile)
Automation‑oriented operations and digitally enabled workflows
Ability to operate on major network wholesales in particular markets

03Field reports

Availability of mainstream B2B review coverage

Important limitation: Telness Tech / Seamless OS appears to have limited presence on mainstream B2B review platforms. Attempts to locate product-specific review pages on major third‑party review platforms did not yield credible product‑specific listings in accessible results. As a result, the "voice of customer" available for this report draws primarily on public customer/partner press announcements, employee reviews as an indirect execution signal, and the consumer operator reputation of Telness (the operator) as a proxy for customer experience concepts — not as direct evidence of the B2B platform quality.

Positive quotes (customer / partner / public references)

1) New York Mobile (customer) on customization (press quote): - Giovanni Perone (Co‑Founder & CEO) is quoted saying Seamless OS was the only platform that met their demands in customization, enabling a fully digital, highly customized value proposition including a vanity‑number marketplace and a custom plan builder. 2) Consumer reviews for the Telness operator reflect favorable customer service sentiment; these refer to the consumer operator and are not direct assessments of the B2B software product.

Negative / critical quotes

Main public negative feedback available is primarily from employee reviews rather than customers. Examples cited on public employee review platforms include comments about architectural complexity, management practices, and workforce volatility. These are not product reviews but can correlate with delivery risk for enterprise software vendors.

Case Study 1: New York Mobile (U.S. MVNO on a U.S. mobile network)

What happened: Public announcements describe New York Mobile as a U.S. MVNO launching on Seamless OS, with features including a vanity-number marketplace and create-your-own-plan options. Quantified metrics provided: The public release did not include quantified results for typical KPIs such as cost savings, launch time, churn, NPS, ARPU, or ticket reduction. Credible versus marketing-aligned content: - Credible: named customer, named executives, and concrete product features described in the announcement. - Less verifiable: implications about operational outcomes or exceptional performance without supporting metrics. Adoption challenges not disclosed: No public discussion in the announcement of integration pain points, test cycles, incident handling, or billing reconciliation.

Case Study 2 (proxy): Telness operator outcomes cited in analyst interview

Analyst and interview material for the Telness operator describe high-level operational outcomes for the operator (service availability, reductions in support activity, and lower churn). These operator-level outcomes reflect combined effects of brand, pricing, operations, and product design rather than being a controlled, vendor-only performance measurement. Critical evaluation: The reported outcomes are informative but do not isolate the software's contribution, and the reporting format does not include methodology or independent validation.

04Best fit

Company sizes

Based on vendor positioning and MVNO economics:

Primary fit: small-to-mid-size MVNOs and digital brands that can use standardized, automated operating models.
Secondary fit: larger telecom groups launching challenger sub-brands.

Industries / verticals

Telecom: MVNOs, MVNEs, MNO digital units
Potential adjacency: brands embedding connectivity (vendor statements on this capability have limited public evidence)

Roles and personas

CTO / Head of Engineering (integration and API strategy)
COO / Head of Operations (automation and ticket-reduction objectives)
Head of Product (catalog and plan experimentation)
Wholesale/partner management (MNO relationship managers)
Compliance/security (procurement diligence)

Qualification criteria (good fit)

The buyer seeks a digital-first onboarding and self-service model rather than a call-center-centric approach.
The organization can align internal processes to a platform approach and is prepared to adopt standardized operational journeys rather than extensive bespoke workflows.
The organization requires strong API integration capabilities and is comfortable operating a modern SaaS stack.

05The pitch

What the product does (core value proposition)

Telness Tech is a B2B telecom software provider focused on supporting mobile operators—especially MVNOs/MVNEs and digital challenger brands—to launch and operate mobile services with a cloud-based, automation-oriented OSS/BSS stack called Seamless OS. The platform is intended to provide an end-to-end operational and business-support layer covering functions such as onboarding, product/catalog management, ordering, billing/subscriptions, payments, provisioning, number management, and network integrations via APIs. The vendor states that a high degree of automation and self-service can reduce operational burden (support tickets, manual workflows) and improve customer experience; these assertions reflect lessons cited from the operator Telness, from which the software was spun out.

Target market and positioning

Primary buyers/users: - MVNOs launching new brands (particularly digital-first, eSIM-friendly propositions) - MVNE/MVNA-style enablers that need to support multiple brands/operators - Established MNOs exploring digital brand models and rapid experimentation - Non-telco companies exploring embedding connectivity (the vendor asserts this is possible, though public evidence is limited) Reported positioning themes from vendor messaging and press coverage include: - Automated, low-touch operations - Cloud-native, API-first OSS/BSS - Faster launch and change management compared with legacy BSS/OSS and reduced dependency on systems integrators These positioning themes appear consistently across company messaging and external press coverage.

Get a comprehensive analysis of Telness Tech including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →

Published Sep 19, 2026

01Common complaints

When the procurement process requires independently validated security and compliance documentation (SOC 2 Type II, ISO 27001) and the vendor cannot provide those reports promptly.
When the operating model is highly bespoke and the organization expects the vendor to custom-build extensive workflows; heavy customization can negate the benefits of a standardized platform approach.
For Tier-1 operators that require maximal module breadth (network inventory, orchestration, assurance, complex enterprise constructs) and multi-decade vendor track records; incumbents or larger suites may be more appropriate.
When procurement relies heavily on third-party review platforms for benchmarking; limited coverage on major review platforms will make comparative assessments more difficult.

Deal disqualifiers (poor fit)

The buyer requires published SOC 2/ISO certifications as a hard procurement gate and the vendor cannot provide audit reports promptly.
The organization requires extensive legacy on-prem integration and cannot accept migration risk.
The buyer requires many years of Tier-1 public references and large-scale case studies as procurement prerequisites.

Vendor-acknowledged limitations

No explicit published limitations or roadmap caveats were found in the sources accessed.

Evidence-based limitations / risks

Security and compliance transparency gap: no public trust center or published compliance certificates located in accessible sources.
Limited third-party review coverage on mainstream platforms, which reduces independent validation opportunities.
Organizational execution risk signals from employee reviews (architecture and management concerns) that could impact delivery and support quality.

Why some customers left (churn reasons)

No public narratives describing customer churn were found in the sources accessed.

02Why they buy

Unique selling points supported by evidence or concrete signals

Public API documentation: an OpenAPI/REST documentation set for Seamless OS indicates a developer-oriented integration model.
Named market reference: a U.S. MVNO deployment provides a concrete market reference for U.S. entry.
Operator-origin narrative: origin as software derived from an operator environment is a credible formation story but does not constitute independent proof of product performance.

Areas where competitors have clearer advantages

Competitors with explicit published pricing for specific functions (for example, cloud charging) can offer clearer commercial modeling for those modules.
Larger incumbents provide established procurement comfort and broader product depth for complex operator needs.

Why customers chose Telness Tech (as evidenced)

From public customer and press statements, decision drivers cited include:

Customization and flexibility in product features (example: New York Mobile)
Automation‑oriented operations and digitally enabled workflows
Ability to operate on major network wholesales in particular markets

03Field reports

Availability of mainstream B2B review coverage

As a result, the "voice of customer" available for this report draws primarily on public customer/partner press announcements, employee reviews as an indirect execution signal, and the consumer operator reputation of Telness (the operator) as a proxy for customer experience concepts — not as direct evidence of the B2B platform quality.

Positive quotes (customer / partner / public references)

New York Mobile (customer) on customization (press quote):

Giovanni Perone (Co‑Founder & CEO) is quoted saying Seamless OS was the only platform that met their demands in customization, enabling a fully digital, highly customized value proposition including a vanity‑number marketplace and a custom plan builder.

Consumer reviews for the Telness operator reflect favorable customer service sentiment; these refer to the consumer operator and are not direct assessments of the B2B software product.

Negative / critical quotes

Case Study 1: New York Mobile (U.S. MVNO on a U.S. mobile network)

What happened: Public announcements describe New York Mobile as a U.S. MVNO launching on Seamless OS, with features including a vanity-number marketplace and create-your-own-plan options.

Quantified metrics provided: The public release did not include quantified results for typical KPIs such as cost savings, launch time, churn, NPS, ARPU, or ticket reduction.

Credible versus marketing-aligned content:

Credible: named customer, named executives, and concrete product features described in the announcement.
Less verifiable: implications about operational outcomes or exceptional performance without supporting metrics.

Adoption challenges not disclosed: No public discussion in the announcement of integration pain points, test cycles, incident handling, or billing reconciliation.

Case Study 2 (proxy): Telness operator outcomes cited in analyst interview

Critical evaluation: The reported outcomes are informative but do not isolate the software's contribution, and the reporting format does not include methodology or independent validation.

04Best fit

Company sizes

Based on vendor positioning and MVNO economics:

Primary fit: small-to-mid-size MVNOs and digital brands that can use standardized, automated operating models.
Secondary fit: larger telecom groups launching challenger sub-brands.

Industries / verticals

Telecom: MVNOs, MVNEs, MNO digital units
Potential adjacency: brands embedding connectivity (vendor statements on this capability have limited public evidence)

Roles and personas

CTO / Head of Engineering (integration and API strategy)
COO / Head of Operations (automation and ticket-reduction objectives)
Head of Product (catalog and plan experimentation)
Wholesale/partner management (MNO relationship managers)
Compliance/security (procurement diligence)

Qualification criteria (good fit)

The buyer seeks a digital-first onboarding and self-service model rather than a call-center-centric approach.
The organization can align internal processes to a platform approach and is prepared to adopt standardized operational journeys rather than extensive bespoke workflows.
The organization requires strong API integration capabilities and is comfortable operating a modern SaaS stack.

05The pitch

What the product does (core value proposition)

The vendor states that a high degree of automation and self-service can reduce operational burden (support tickets, manual workflows) and improve customer experience; these assertions reflect lessons cited from the operator Telness, from which the software was spun out.

Target market and positioning

Primary buyers/users:

MVNOs launching new brands (particularly digital-first, eSIM-friendly propositions)
MVNE/MVNA-style enablers that need to support multiple brands/operators
Established MNOs exploring digital brand models and rapid experimentation
Non-telco companies exploring embedding connectivity (the vendor asserts this is possible, though public evidence is limited)

Reported positioning themes from vendor messaging and press coverage include:

Automated, low-touch operations
Cloud-native, API-first OSS/BSS
Faster launch and change management compared with legacy BSS/OSS and reduced dependency on systems integrators

These positioning themes appear consistently across company messaging and external press coverage.

Get a comprehensive analysis of Telness Tech including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →