Telecom Revenue Assurance Software: Build Custom or Buy Subex
Measure before you buy or build. Export active services from inventory and active subscriptions from billing, join them, and count the unmatched rows on both sides. If that number does not justify a project you have saved one.
On this page
Measure before you buy or build. Export active services from inventory and active subscriptions from billing, join them, and count the unmatched rows on both sides. If that number does not justify a project you have saved one. Large operators with a staffed assurance function should buy Subex or TEOCO. Regional carriers, wholesale fibre operators and mobile virtual network operators usually should build.
What Subex, TEOCO, Mobileum and Araxxe actually do well
A wholesale fibre operator finds a ten gigabit wave carrying customer traffic for fourteen months that has never appeared on an invoice. Engineering lit it early because the customer was waiting on a data centre migration, the order was closed manually to clear the queue, and the billing start step, which in that operator is a person clicking a button, never happened. Nobody found it in billing. The account manager found it while pulling the contract file before a renewal conversation.
Subex and TEOCO are the enterprise suites of this category, built around tier one operator scale, and they carry deep control libraries covering exactly that class of failure. If you have a formal revenue assurance function, tier one usage volumes and the appetite to run a long onboarding, their domain depth is worth what it costs and you should not be writing your own. Mobileum's strength sits in roaming and fraud with assurance alongside, which helps if your loss profile is retail mobile and roaming. Araxxe takes a genuinely different angle: it generates real test transactions and verifies they appear correctly on the bill, which is a strong independent check for retail voice and data products.
None of that is marketing. These products encode years of knowing which controls matter and in what order, and a first custom attempt will not match that library. The reason most regional operators still end up building is not capability, and we would rather say that plainly before describing the gap.
Where they stop: every control is a join against your schemas
Revenue assurance is not a dashboard and it is not a monthly report. It is a set of reconciliations between systems that were never designed to agree, run continuously, with a case workflow attached so a discrepancy becomes somebody's job rather than a line in a spreadsheet.
Leakage runs in three directions and most operators only look at one. Revenue never billed, where the service exists in the network and no subscription sits behind it. Revenue billed wrong, where a promotional price was entered as a permanent adjustment or contract pricing that should have stepped at renewal did not. And cost overpaid, where a disconnected service leaves its underlying off net tail circuit, cross connect or transit port still invoicing to you every month. That third direction is routinely ignored and is frequently the larger number.
Where the suites stop is the same place in every deployment. Every meaningful control has to be expressed against your inventory, provisioning, mediation, billing and ledger schemas, and every leakage rule encodes your product catalogue and your history of acquisitions. A product gives you a control framework. You still write the joins. The question is only whether you write them inside somebody's licensed platform or inside your own.
The practical constraint for a regional carrier is that onboarding is itself a data integration project of considerable length, the commercial model is sized for subscriber counts you may not have, and adding one control against a schema quirk unique to your estate becomes a change request in a queue rather than something your analyst does on a Tuesday. If your team needs to add controls weekly, that queue is the whole problem.
What a custom build actually costs
A first release covering read only connectors from inventory, provisioning and billing, an entity resolution layer, switch to bill reconciliation on your largest product family, supplier invoice to inventory reconciliation and case management runs $80,000 to $180,000 across 12 to 18 weeks. First findings normally appear during the first reconciliation run, around week eight to ten, well before the release ships.
A full platform covering every product family, usage completeness controls with sequence and volume baselines, contract to billing reconciliation, dispute tracking and a recovered value ledger tied back to the general ledger runs $200,000 to $500,000 phased over 8 to 14 months.
Data migration lands at 10 to 25 percent of build cost, and here the work is identifier mapping rather than loading. The same circuit is known by a different string in each system, and that mapping is the actual asset you are building. Expect a resolution layer with confidence scoring and a human review queue for ambiguous cases, because a join on a common key does not survive a real carrier estate that has been through acquisitions.
Year two runs 15 to 20 percent of build cost annually, and most of it is new controls rather than maintenance. Budget for access too, which sounds trivial and is not: if obtaining a read replica of a vendor hosted billing platform requires a change request with a long lead time, that lead time is your project timeline.
The four situations where building wins
- Regulatory and contractual fit. Claims against a supplier live inside a dispute window written into your interconnection or master services agreement, and evidence has to tie to a specific invoice line and a specific circuit identifier. On the revenue side, contract pricing that should have stepped at renewal has to be provable against the executed agreement. When findings must be defensible against your own contracts rather than a vendor's generic workflow, the rules belong in a system you control.
- Scale economics. Past roughly 20,000 subscribers on typical per subscriber pricing, or a few thousand enterprise circuits, the arithmetic above turns. Below that, buy or run controls by hand.
- A workflow that is your advantage. The reconciliation logic is the product and the surrounding platform is commodity. Paying enterprise licensing for a case management workflow while still writing all your own joins is the worst of both options, and it is where most regional operators we speak to have already arrived.
- Integration sprawl across three or more systems. Count them: network discovery, the inventory, provisioning, mediation, billing, the contract repository and the supplier invoice ledger. A two way reconciliation between inventory and billing misses the worst case, which is a service that exists in the network and appears in neither, and finding that needs a genuine three way join.
How to decide in a week
Do this yourself before spending anything. Export active services from inventory. Export active subscriptions from billing. Join them on whatever identifier you have. The unmatched rows on both sides are your first estimate of leakage. It will be wrong in detail and right in order of magnitude, and it takes an analyst a day.
If that produces a number that does not justify a project, you have saved yourself a project and you should stop. If it produces a number with a comma in it, you now have a business case built on your own data rather than on somebody's benchmark, which is the only kind that survives a finance review.
Run the cost side in parallel, because it is faster and usually larger. Take last month's supplier invoices, list every circuit identifier they billed you for, and mark each one against a live off net component in your own records. Anything with no live component behind it is a claim, and the claim has a clock on it.
Third, test completeness. For one mediation source, count expected files per day for the last month, check sequence continuity, and compare record counts against the same weekday in prior weeks. A feed that stopped quietly is the class of loss that becomes unrecoverable once the reprocessing window closes, and it is the least interesting and highest value control you will ever build.
If the tests point to building, take a paid discovery phase rather than a proposal. Digital Heroes runs discovery to a signed product requirements document covering the source inventory, the entity resolution design, the control set and acceptance criteria. The specification is yours to take to any other firm on your shortlist. We are the wrong partner if nobody will own the case queue, because a finding with no owner is not a finding and an assurance system that gets ignored is worse than none, since it provides false comfort. We are an India LLP with US LLC and UK LTD entities so intellectual property assigns under your own law, with more than fifty specialists, over 2,000 projects delivered, a named team you meet before signing, and a public record on Clutch, Trustpilot, Fiverr Vetted Pro and D-U-N-S.
Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- SaaS spend averaged $4,830 per employee (up 21.9% year over year), with large enterprises (10,000+ employees) spending roughly $284M annually and running about 660 apps, while organizations wasted an average of $21M annually on unused licenses. Source: Zylo (2025) →
- The right combination of digital transformation actions can unlock as much as US$1.25 trillion in additional market capitalization across Fortune 500 companies, while the wrong combinations put more than US$1.5 trillion at risk; companies with all three core factors (strategy, aligned technology, and change capability) saw a 5% market-value lift relative to peers. Source: Deloitte (2023) →
- McKinsey Global Institute estimated that about half of all work activities globally have the technical potential to be automated by adapting currently demonstrated technologies, though few occupations can be fully automated. Source: McKinsey Global Institute (2017) →
- Gartner estimates RPA can eliminate up to 25,000 hours of avoidable rework caused by human errors in the finance function each year, equating to savings of roughly $878,000 for an organization with 40 full-time accounting staff (based on interviews with more than 150 corporate controllers and chief accounting officers). Source: Gartner (2019) →
Frequently asked questions
Why do our inventory and billing systems disagree in the first place?
Because provisioning cares that the circuit works and billing cares that a subscription exists, and the link between them is usually a manual status transition. Expedites, trial circuits that quietly became production, capacity upgrades and anything worked during an outage are the orders that skip it. After an acquisition the problem compounds, since two naming conventions and two sets of historic data quality now share one estate.
Does revenue assurance cover overpaid supplier costs or only unbilled revenue?
Cost side leakage is often the larger number and is routinely ignored. Off net tail circuits, colocation cross connects and transit ports keep invoicing after the customer service is disconnected, because the disconnect on your side and the request to the supplier are separate actions. The control joins supplier invoice lines to your record of active off net components, and anything with no live component behind it becomes a claim.
Can this be built without touching production billing and provisioning?
Yes, and it should be. Controls read from replicas or change data capture feeds and never write to production operational systems, which keeps the assurance layer from becoming an operational risk of its own. The practical obstacle is access rather than architecture. If obtaining a read replica of a vendor hosted platform needs a change request with a long lead time, start that request before design work begins.
How long before a build shows a recovered number?
First findings usually appear during the first reconciliation run, which in our experience lands around week eight to ten, well before the first release ships. Converting a finding into recovered money takes longer, because it depends on your commercial teams and, on the cost side, on supplier dispute windows. Build the recovered value ledger early so the programme can prove what it returned at the next budget cycle.
What is usage completeness control and why does it matter more than analytics?
It is the check that every expected usage file from every source arrived, in sequence, with a record count in line with comparable prior periods. When a mediation feed stops, volume dips for reasons that look ordinary and nobody notices until a customer disputes an invoice months later. Once the reprocessing window closes that revenue is unrecoverable, which makes this the highest value and least interesting control you will build.
Who owns the reconciliation logic if an agency builds this?
You should own the repository, the cloud infrastructure accounts and the unrestricted right to hire another firm, written into the contract before kickoff. At Digital Heroes the client owns the code from the first commit. This matters here because the identifier mapping and reconciliation logic encode years of accumulated knowledge about your own estate, and that asset should never sit inside a vendor account you may need to leave.
How do you resolve the same circuit across four systems that name it differently?
With a resolution layer that carries confidence scoring and a human review queue for ambiguous cases, not with a join on a common key. Real carrier estates do not have a common key, especially after acquisitions. The mapping that layer produces becomes the most valuable thing in the system, because every control depends on it and rebuilding it from scratch is months of work nobody budgets for twice.
What is the difference between revenue assurance and fraud management?
Revenue assurance reconciles systems that should agree and finds money quietly not billed or overpaid, running on periodic batches where a day of latency costs nothing. Fraud management prevents deliberate abuse and is judged on time to containment, so it needs live event streams and automated action. They share ingestion and case handling but have opposite latency requirements, which is why one platform doing both is usually tuned for the wrong one.
How do we stop discounts and contract pricing from running forever?
Reconcile contract to billing rather than asking sales to re read agreements quarterly. Parse the commercial terms from the contract record, including term dates, committed volume and any price schedule, then compare the rate actually applied on the invoice line each cycle and open a case where they disagree. The data is small compared with usage, which makes this one of the quickest controls to build and the least glamorous.
What false positive rate is acceptable?
Low enough that your team still opens the queue in month three. A rate above a few percent trains people to ignore the tool within a month, and an assurance system that is ignored is worse than none because it provides false comfort to everyone above it. Test each control against a known period before arming it, and retire controls that produce noise rather than tuning them indefinitely.
Does it matter which tech stack the agency wants to use?
Yes, but not in the way most buyers expect: the goal is boring, popular technology such as React, Node.js or Python, and PostgreSQL, because any future team can maintain it and hiring a replacement developer takes days, not months. The red flag is an agency-proprietary framework or an unusual language, which welds you to that one vendor no matter what your contract says about code ownership. A useful test: could you find three freelancers fluent in this stack within a week? If not, push back.
Will a custom dashboard stay fast once our data hits millions of rows?
Yes, if it aggregates before it displays; no dashboard should scan millions of raw rows on every page load. The standard techniques are pre-aggregated summary tables, incremental refresh, and caching, which keep typical page loads under 2 seconds even on datasets in the hundreds of millions of rows. Ask your vendor how the dashboard behaves at 10 times your current data volume; a good one gives a specific answer about aggregation, not just a bigger server.
Why do agencies charge for a discovery phase instead of quoting for free?
Because an accurate quote requires real work: mapping your workflows, finding the edge cases, and writing a specification, which typically takes 1 to 3 weeks and costs $2,000 to $10,000 at Digital Heroes depending on system complexity. You leave discovery owning a written spec and a fixed price you can take to any vendor, so the money is not locked into one agency. Free estimates are guesses, and the guess usually becomes your budget overrun six months later.
How long does it take to build a custom web or mobile app from scratch?
Plan on 8 to 16 weeks for a focused first version and 4 to 9 months for a larger platform, which is the typical spread across Digital Heroes builds. The first 2 to 3 weeks go to discovery and design before any production code ships. The two things that stretch timelines most are integrations with legacy systems and slow feedback from your side, not developer speed.
Should I hire a freelancer or an agency for my software project?
A skilled freelancer is the right call for a single-discipline scope under roughly $15,000, like a website, a plugin, or one integration. Above that, projects need design, backend, testing, and project management at once, and a solo builder becomes the single point of failure: if they get sick or take a bigger client, your project simply stops. Agencies bill 20-40% more per hour but carry continuity, code review, and someone to escalate to, which is what you are actually buying.
How do I vet an agency or developer for a BI dashboard project?
Ask them to walk you through the data model of a past project, not a portfolio of pretty charts, because dashboard failures are almost always data modeling failures. Good answers mention specifics like star schemas, dbt, incremental refresh, and how they handled a source schema change after launch. Then ask for a fixed-scope discovery phase with a written data audit as the deliverable, so you judge their real work for a small spend before committing to the build.
What usually breaks after a dashboard launches, and who fixes it?
Upstream changes break dashboards, not the dashboard code itself: a source system renames a field, an API version gets retired, or someone edits a spreadsheet column a pipeline depends on. Budget 15 to 25 percent of the build cost per year for maintenance and monitoring, and agree on response times for broken data before launch. A build quote with no maintenance plan attached is a warning sign, because every connected source will change eventually.
How does a custom dashboard handle compliance requirements like SOC 2, HIPAA, or GDPR?
A custom build gives you direct control over the controls auditors ask about: single sign-on, role-based access, audit logs, encryption, data residency, and deletion workflows. For HIPAA specifically, you can keep protected health information inside your own cloud account under a business associate agreement with your host instead of trusting a third-party BI vendor's handling. Expect compliance work to add 2 to 4 weeks and roughly 10 to 15 percent to the build, so raise it in the first conversation, not after design is done.
Do I need a data warehouse before building a custom dashboard?
Not for a small build; a dashboard reading from 1 or 2 sources can query them directly or use a plain Postgres database as its store. You want a real warehouse like BigQuery or Snowflake once you are joining 3 or more sources, keeping history beyond what source systems retain, or serving many concurrent users. Adding the warehouse costs around 2 to 4 extra weeks and is usually the single best investment in the project's future.
How long does it take to build a custom BI dashboard?
A working first version usually ships in 4 to 8 weeks, and a full production build with multiple integrations and permissions takes 3 to 6 months. In Digital Heroes delivery experience, schedules slip on data access, meaning credentials, API approvals, and cleanup of source data, far more often than on the dashboard screens themselves. Lining up access to every data source before kickoff routinely saves 2 to 3 weeks.
Who can build a custom business intelligence dashboards system?
Digital Heroes builds custom business intelligence dashboards systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other business intelligence dashboards companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
More from Eleanor.
Senior Partnerships Manager · New-york · 5 posts on the site
Published · Last updated .
