Subex

Name: Subex
Brand: Subex

Subex is a telecom-focused software suite that provides fraud management, revenue/business assurance, and partner ecosystem management using analytics and machine learning for anomaly detection, root-cause analysis, and near-real-time decision support.

Est 1992|Valuation $119.9M|Raised $703.7M|36 Ref Customers

LinkedIn 70K|Website|FTEs 632

MarketsFraud Detection Telecom BSS/OSS

Published Oct 14, 2026

01Common complaints

- Company sizes or stages where this product is overkill or insufficient - Overkill for small MVNOs with limited fraud exposure, early-stage digital providers requiring low-cost or self-serve point solutions, or organizations unable to support multi-system integration work. - Industries or use cases where competitors are clearly superior - If the primary need is cross-industry online fraud detection for e-commerce/marketplaces (outside telecom), specialized online-fraud vendors may be a better fit than a telecom-focused RAFM suite. - Technical requirements that this product cannot meet - If procurement requires public trust/security artifacts and the vendor cannot provide SOC 2/ISO certificates or pen-test summaries during diligence, the vendor may fail basic procurement gates. - Budget constraints that make alternatives more appropriate - If the organization lacks budget for integration, ongoing tuning, or managed services, narrower point solutions or internal analytics may be more appropriate. - Specific workflows or integrations where the product may be unproven - Where ingestion latency, alert explainability, or case-management integration are critical, require proof-of-concept (PoC) focused on these areas. - Red flags in the buying process - Lack of transparent pricing and limited public documentation increase commercial and implementation risk. Absence of relevant regional reference customers for similar stack complexity should be treated as a procurement risk. - Current limitations acknowledged in public materials - The vendor’s public materials do not explicitly enumerate current functional limitations in a centralized manner. - Features on the roadmap (not yet available) - A public product roadmap with feature dates was not located in the accessible sources. - Scale limitations (at what volume/size does it break down?) - No public documentation was found specifying scale limits; procurement should perform scalability testing during PoC phases. - Security or compliance gaps - The most notable publicly observable gap is the absence of clearly published SOC 2 or ISO 27001 certificates in the sources reviewed. - Technical debt or architectural limitations mentioned in reviews - No public evidence located in accessible product-review samples. - API limitations or integration constraints - Not documented in the accessible public materials; confirm supported APIs and connector lists during technical diligence.

Deal disqualifiers: what makes a POOR fit

Insufficient data maturity or inability to integrate required feeds, a firm procurement requirement for publicly documented SOC 2/ISO certificates that the vendor cannot provide, or a preference for self-serve pricing and rapid SMB-style procurement.

Why some customers left for competitors (churn reasons)

Direct evidence of customer churn reasons was not available in the accessible product-review corpus. Independent industry commentary has suggested competitive displacement in certain markets.

02Why they buy

- Competitive advantages observable from public sources and vendor materials - The vendor describes capabilities including machine learning-based anomaly detection and root-cause analysis, combined coverage across fraud and assurance domains, and partner-ecosystem management workflows in a modular product set. - Third-party verification of uniqueness is limited in the accessible public review corpus; competitors make similar claims in public materials. - Unique features and capabilities (vendor-described) - Integrated suite spanning fraud management, revenue/business assurance, and partner ecosystem workflows; platform and legacy-suite approach (HyperSense and ROC); machine learning models for scoring and anomaly detection. - Differentiation from competitors based on available evidence - Publicly available evidence is insufficient to conclude clear functional uniqueness versus products from Mobileum or WeDo; procurement should use feature-by-feature evaluations and reference checks. - Areas where competitors have public advantages - Competitors may provide more public-facing security/compliance collateral, different packaging or pricing transparency, or larger documented libraries of adjacent apps and integrations.

Why customers chose this product over alternatives

Vendor materials and market narratives indicate buyers select Subex for its telco domain focus, broad coverage across fraud and assurance domains, and its analytics/ML tooling for anomaly detection and automation of workflows.

03Field reports

Review platform summaries and availability

- Gartner Peer Insights: Subex has a product profile for fraud management that lists validated user reviews; full review text and likes/dislikes may be gated on the platform. - G2: The Subex vendor page shows a high aggregate rating with a small review footprint. The sample available in this research is limited; review-site sampling and invitation practices can influence reported averages. - TrustRadius / Capterra: No clearly accessible product review pages for Subex were identified in the search results used for this report. - Community forums: Reddit posts located during the research relate primarily to employment experiences and investor discussions rather than product buyer reviews.

Representative positive signals (from available sources)

Vendor and third-party review pages indicate generally positive sentiment and a high aggregate rating, though the public sample is small and not consistently extractable.
Vendor case studies report quantified improvements (vendor-authored), which indicate outcomes some customers report after deployment, subject to verification.

Representative negative signals (from available sources)

The most visible negative material found in public forums related to employment and interview experience rather than product functionality or buyer dissatisfaction.
Public negative product reviews for core RAFM products were not readily available in the accessible sample.

Balance and limitations

The accessible sources did not provide a representative distribution of low-star product reviews for Subex’s core telecom platforms. As a result, this section emphasizes the limitation of available public review data and recommends reference checks and pilot engagements as part of procurement.

Common criticisms and complaints (support issues, bugs, missing features)

Product-specific complaint patterns were not extractable at scale from the accessible review sources used for this research.
Market-level caution about review-platform biases (not Subex-specific) was observed; procurement teams should apply customary reference-check rigor.

Specific outcomes customers achieved (with metrics when available)

Vendor-published case studies report outcomes such as substantial ROI claims; these are vendor-authored and lack independent methodological disclosure in the public previews.

Customer pain points and frustrations mentioned in reviews

Not reliably available from the accessible product review text in this research.

Deal-breakers and reasons customers didn't purchase

Not reliably available from the accessible product review text in this research.

Case Studies

- Detailed customer success stories with metrics - Vendor-published case study summaries include: a Tier-1 North American operator reporting a substantial ROI from Subex’s Revenue Assurance and Managed Services; a Tier-1 operator reporting a high ROI multiple from Subex’s Business Assurance and Managed Services; and a case study focused on mobile-money fraud mitigation for a Tier-1 African operator. - Specific results and quantified business impact - Vendor-published outcomes cite specific ROI figures and multipliers; these vendor-provided figures are not independently validated in the publicly accessible previews. - Implementation details and time to value - Implementation timelines and detailed methodology are not consistently described in publicly accessible previews of these case studies. - Challenges faced during adoption and how they were resolved - The public previews of vendor case studies did not consistently disclose adoption challenges or remediation steps. - Note on vendor-published metrics and methodology gaps - All ROI and outcome metrics cited above are vendor-published; independent verification is not provided in accessible public sources. Typical methodology gaps reported in previews include missing baseline leakage levels, unclear attribution methods, unspecified cost bases, and undefined time horizons. - Mixed results or failed projects - No public failed-implementation case studies were identified in the accessible sources used for this research. Independent industry commentary suggests historical market-share challenges in some regions.

04Best fit

Company sizes

Best fit appears to be established CSPs (mid-to-large operators) with substantial BSS/OSS complexity and non-trivial fraud exposure.
Practical heuristic:
- Operators with multiple data sources and meaningful subscriber/traffic volumes
- Organizations with dedicated fraud management and revenue assurance teams

Industries and verticals where adoption is strongest (with customer examples)

Telecom / CSPs (primary)
Mobile money / fintech services connected to telecom operators
Public case studies are commonly anonymized (e.g., "Tier-1 operator") in public previews.

Roles and personas: decision makers AND end users

Decision makers: Chief Risk Officer / Head of Fraud, Head of Revenue Assurance / Business Assurance, CIO/CTO, VP/Director of BSS/OSS transformation
End users: Fraud analysts and investigators, Revenue assurance analysts, Data engineering/integration teams, Operations managers handling alerts and case management workflows

Pain points and challenges the product addresses

Fraud losses (IRSF, bypass/SIM box, subscription and device fraud, roaming fraud), revenue leakage and margin erosion, operational inefficiencies in root-cause detection across telco processes, and manual partner settlement/onboarding workflows

Qualification criteria: what makes a GREAT fit

The CSP has accessible data sources (CDRs, billing, CRM, roaming, payments), established processes to operationalize alerts, and budget for multi-year transformation and services if required.

Public customer names

Publicly named customers are not disclosed in accessible case-study previews; many references are anonymized as "Tier-1 operator." Procurement should request relevant references during the buying process.

05The pitch

What the product does (core value proposition in objective terms)

- Subex is a telecom-focused software vendor that supplies analytics and machine-learning-enabled products used by communications service providers (CSPs) to detect and reduce revenue leakage and operational risk via: - Fraud Management (e.g., IRSF, SIM box, subscription fraud, roaming fraud, spam/scam calls) - Business Assurance / Revenue Assurance (revenue & cost assurance, margin assurance, migration assurance, etc.) - Partner Ecosystem Management (B2B2X partner onboarding, orchestration, settlement-type workflows) - The vendor describes the suite as using machine learning models for anomaly detection, root-cause analysis, and near-real-time decision support.

Target market and market positioning

Primary target: telecom operators/CSPs (Tier-1 through mid-market), including operators expanding into 5G and digital services such as mobile money/fintech.
Positioning: the vendor markets the suite as an analytics-led alternative to traditional RAFM (Revenue Assurance & Fraud Management) stacks, offering a platform product (HyperSense) alongside a legacy suite (ROC).

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

Download full report →