Skip to content
§
§ · hiring guide

How to Hire a Telecom Mediation and Rating Software Development Company

Judge every candidate on one scenario: re-rating three weeks of one partner's traffic after a bad rate load. If they propose updating rated records in place, end the call.

Accounting Software architecture and database illustration for Telecom Mediation AND Rating Software.
The short answer

Judge every candidate on one scenario: re-rating three weeks of one partner's traffic after a bad rate load. If they propose updating rated records in place, end the call. Expect $120,000 to $260,000 for a first release with declarative parsing, persistent deduplication and effective dated tariffs, over 16 to 24 weeks. Below a few million records a month with flat rating, buy JeraSoft.

Nothing pages anyone when this goes wrong. A file lands at 02:14 with an unexpected trailer, the collector writes a warning to a log, and eleven hours of one switch's traffic is never rated. You find out six weeks later, when a wholesale partner's settlement statement disagrees with yours by an amount small enough to argue about and large enough to matter. The undercharges are worse, because no customer has ever reported one.

The category is hard to buy for a reason that has nothing to do with technology. The work is high volume stream processing, which engineering owns, and the output is every invoice you send, which finance owns. So the specification belongs to nobody, the demo impresses the wrong department, and acceptance testing runs on clean sample files that behave exactly as the vendor documentation says. Your real sources do not.

What a telecom mediation and rating development company actually does

Throughput is table stakes and it is not what you are buying. You are buying the ability to take any number on any invoice and produce the raw records behind it, the rate applied, why that rate applied, and proof that nothing was dropped on the way.

That single sentence drives the whole build. Parsers become declarative and versioned per source, with a schema contract validated on every file, so a deviating source drops to suspense with the violation attached while everything else keeps flowing. Deduplication becomes a persisted index with a retention period set by how badly your worst source misbehaves, not by what is convenient, and every suppressed duplicate is logged with both record identifiers. Tariffs become versioned data with effective dating on every element, including billing increments, jurisdiction determination, committed volume tiers and the grandfathered plans nobody is allowed to touch. Rating becomes a pure function of raw records plus a rule version, re-runnable in isolation, so a correction produces a new run beside the old one and the adjustment is the difference between them.

Then traceability, exposed to account managers rather than to engineers. If answering a dispute needs someone who can write SQL, the feature does not exist in any way your business can use.

What it really costs in 2026

Bands from Digital Heroes delivery experience across 2,000+ projects, for a wholesale voice, carrier or CPaaS operator.

ScopeCostTimeline
Collection, declarative parsing with suspense, persistent deduplication, one usage type end to end$70,000 to $150,00010 to 16 weeks
First platform release adding the rating engine with versioned effective dated tariffs across your primary usage types$120,000 to $260,00016 to 24 weeks
Full platform with enrichment against routing and customer data, back dated re-rating and adjustments, settlement outputs, roaming files, commercial traceability$350,000 to $900,00010 to 20 months
Run, plus a new parser each time a source changes12% to 18% of build per yearRetainer

Two things are almost never in the quote.

The parallel run. The only acceptance test that means anything is rating a full month of real production traffic beside your current system and reconciling every difference. Three to six weeks, and most of the effort is explaining the discrepancies rather than fixing them, because roughly half turn out to be errors in the incumbent that nobody had noticed. Insist this sits in the plan with named people, not in a sentence about testing.

Retention. Compute gets estimated, storage rarely does. If your commercial reality is that a partner can dispute eighteen months back, you must hold eighteen months of raw records and eighteen months of dedup index, and that is a running cost with a line in your budget forever. Decide the retention period before anyone designs the schema, because retrofitting it means rebuilding.

Signals of a strong partner

  • They ask how badly your worst source misbehaves before naming a dedup window. Anyone who states a window unprompted has not been burned yet, and will be, on your data.
  • They ask about billing increments in the first hour. One second versus six second increments with a thirty second minimum changes revenue on identical traffic, and a rating estimate given without that answer is a guess.
  • Partial failure never becomes total failure. A malformed trailer at two in the morning sends those records to suspense and raises an alert. The pipeline keeps running.
  • They store the rating explanation per record. Which rate, which tier, which jurisdiction determination, which rule matched. It costs almost nothing at design time and turns a five week dispute into a five minute one.
  • They treat correction files as a designed case. Overlapping resends with a defined supersede rule, not an operational emergency handled by hand at month end.
  • They ask which TAP3 roaming and settlement obligations apply. Those files carry their own specification and their own return and rejection procedure, and pretending otherwise is expensive later.
  • Your repository, your cloud, from the first commit. Including the tariff configuration, which is your commercial history in machine readable form.

Red flags

  • Re-rating by updating records in place. You lose what was originally billed, and your finance team can no longer reconcile an adjustment without taking someone's word for it.
  • Deduplication on a hash of the record. Two genuinely distinct short calls on a high volume route can carry identical fields, and you will suppress real revenue.
  • A quote that scales only with volume. Source diversity drives this cost far more than record count. Every new format is a parser, a set of quirks and a discovery period.
  • Real-time online charging scoped as an extension. Prepaid credit control is a different system with different safety requirements, not a phase two of file based mediation.
  • No suspense queue in the design. Records that cannot be parsed have to go somewhere visible. If they do not, they go missing and the invoice is quietly short.

Questions to ask on the first call

  1. Walk me through what happens when a source sends a file with a malformed trailer at two in the morning.
  2. Re-rate three weeks of one partner's traffic after a bad rate load. Describe every step.
  3. How long do you retain the deduplication index, and how did you arrive at that number?
  4. How does an account manager get from an invoice line to the underlying records without an engineer?
  5. How do you handle a duration field that is seconds on one switch and milliseconds on another running the same software?
  6. How are effective dates applied when a tariff element changes mid cycle?
  7. How do you detect a partner who quietly starts sending a new record type?
  8. What does your parallel run plan look like, and how long does it run?
  9. Who owns the code, the tariff configuration and the infrastructure accounts if we part ways?

A simple way to decide

Buy a paid discovery phase, not a build. Four to six weeks, commonly $10,000 to $25,000, and the deliverable is a written specification you own: every source with its real behaviour rather than its documented behaviour, the tariff constructs your commercial team has actually sold, the retention period, the re-rating requirement, the parallel run plan and a phased estimate. Send the same document to three firms and their prices finally mean something.

Then do the cheap thing first. Take one month of production traffic and rate it against your current system. The differences will scope the project better than any workshop.

Digital Heroes is the wrong choice at moderate volume with conventional wholesale voice rating. Buy JeraSoft, which is built for exactly that and costs a fraction of a build. We are also wrong if you need prepaid online charging, where MATRIXX or Optiva have solved a genuinely hard problem you should not rebuild. We fit operators whose rating logic is a commercial differentiator and whose back dated reprocessing is routine rather than exceptional. We work product requirement document first, you own the code from the first commit, and we contract through an India LLP, a US LLC or a UK LTD so intellectual property assigns under your own law. Checkable through D-U-N-S, Clutch and Trustpilot.

Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.

Research & sources

The evidence behind this guide

Independent findings on why this investment pays off. Every link goes to the primary source.

  1. APQC's Open Standards Benchmarking data on the monthly financial close found median performers take about 6.4 calendar days to close the books, while top performers (top 25%) do it in 4.8 days or fewer and bottom performers (bottom 25%) take 10 or more days. Source: APQC (2018) →
  2. McKinsey found that currently demonstrated technologies can fully automate about 42% of finance activities and mostly automate a further 19%, indicating roughly 60% of finance work is technically automatable. Source: McKinsey & Company (2018) →
  3. Qualtrics research (Q3 2023 survey of ~28,400 consumers across 26 countries) estimated bad customer experiences put roughly $3.7 trillion in global revenue at risk annually, a 19% jump from the prior year's $3.1 trillion; 64% of customers say they will switch companies over poor service regardless of how much they like the product. Source: Qualtrics XM Institute (via Forbes) (2024) →
  4. PMI's Pulse of the Profession research found organizations waste an average of roughly 9.9% of every dollar invested in projects due to poor performance - equivalent to about $1 million wasted every 20 seconds collectively worldwide. Source: Project Management Institute (PMI) (2018) →
FAQ

Frequently asked questions

What is the difference between mediation, rating and online charging?

Mediation collects usage records from network elements, normalises the formats, removes duplicates and enriches them. Rating applies your tariff to produce a chargeable amount. Online charging does both in real time against a prepaid balance, with credit control that can cut a session off mid call. The first two work on files after the fact. The third has safety requirements that make it a separate system, not a later phase.

How long does it take to replace an existing rating engine?

Sixteen to twenty four weeks to a first release covering your primary usage types, then a parallel run of three to six weeks before you cut over. Full replacement including settlement outputs and back dated reprocessing runs ten to twenty months in phases. The variable that stretches the schedule is source diversity, not volume, because every undocumented quirk is discovered rather than planned.

Can a new rating engine run in parallel with the old one?

It should, and this is the only acceptance test worth having. Feed both systems the same month of production traffic, compare the rated output line by line, and investigate every difference. Expect a meaningful share of the discrepancies to be errors in the incumbent that nobody had noticed. Budget three to six weeks and name the people who will do the reconciling before the build starts.

Who is liable if the new system undercharges customers for a month?

Commercially, you are. A development contract can give you a warranty period and a defined response time on defects affecting money, and it should, but no supplier indemnity will make a customer accept a retrospective invoice for traffic they consumed three months ago. That asymmetry is the real argument for a parallel run and for keeping the old system available until the new one has closed a full billing cycle.

Should we hire a general data engineering firm or a telecom specialist?

The pipeline engineering is well understood and a strong data team can build it. What they will not know is where the money hides: billing increments, jurisdiction determination, grandfathered plans, correction file supersede rules, roaming return files. Hire either, but insist that whoever writes the specification has rated real traffic before, and test that with the re-rating question rather than a portfolio.

How much raw usage data do we have to keep, and what does it cost to store?

Your retention period is set by commercial reality, not by engineering preference. If a partner can dispute eighteen months back, you hold eighteen months of raw records plus the deduplication index over the same period. Compressed columnar storage on object storage makes this affordable at most volumes, but it is a permanent running cost that belongs in the budget from day one rather than appearing in year two.

Can an account manager investigate a billing dispute without involving an engineer?

That should be a required feature in the first release. A drill path from any invoice line to the rated records, grouped by destination and route, compared against the prior period, with no query writing involved. Without it, disputes take a week each, credits get issued because nobody could prove the charge, and your commercial team learns not to argue. That habit costs more than the credits.

What happens if a partner changes their file format without telling us?

In a properly built system the schema contract fails validation, those records go to suspense with the specific violation recorded, an alert is raised, and everything else keeps processing. In a scripted pipeline the job either fails entirely or, much worse, succeeds with fields silently misread. Ask any candidate to describe this exact scenario, because the answer separates production experience from a proposal.

Is DigitalRoute MediationZone worth it compared to building?

It handles enormous complexity and it is the strongest dedicated product in the category. The trade is that configuration happens in its own toolkit, so you either build that expertise in house or buy it perpetually from consultants. If every tariff change puts your commercial agility on someone else's calendar, that cost is real and recurring. Weigh it against a build rather than against the licence alone.

Who owns the tariff configuration if an agency builds the platform?

You should, and state it explicitly alongside the code. The tariff configuration encodes years of commercial decisions, including deals nobody remembers signing, and it is often more valuable than the software around it. Require it in a readable, exportable format inside your own repository, with no residual licence to the developer and no dependency on a proprietary editor to change a rate.

How much does custom accounting software cost for a small business?

Most small business accounting builds land between $25,000 and $75,000 for a working first version, while a full double-entry platform with invoicing, payroll, and reporting runs $100,000 to $250,000. Across 2,000+ projects at Digital Heroes, the biggest cost driver is how many external systems the software must connect to, not the accounting logic itself. A tool that automates a single painful workflow, like reconciliation or job costing, can come in under $20,000.

Can we migrate years of data out of our current system into new custom software?

Almost always yes, through CSV exports or the vendor's API, and migration should be scoped as its own workstream with field mapping, a dry run, and a planned cutover window rather than an afterthought. The real time sink is rarely moving the data; it is cleaning it, since years of duplicates, free-text fields, and inconsistent formats surface all at once. Pull a full export from your current vendor before committing to anything new, because some SaaS plans restrict exports on lower tiers.

What does it cost to maintain custom accounting software each year?

Budget 15 to 20 percent of the build cost annually, so a $100,000 system needs $15,000 to $20,000 a year for hosting, security patches, dependency updates, and small fixes. Accounting software carries one extra obligation most software does not: keeping tax rates, filing formats, and bank feed connections current as banks and tax authorities change their systems. Skipping maintenance for two years usually costs more to repair than the maintenance would have cost.

Should I hire a freelancer or an agency to build my accounting software?

A strong freelancer is fine for a reporting dashboard or one integration; anything that holds your books needs a team. Ledger software requires backend, frontend, QA, and accounting domain knowledge, and one person rarely covers all four while staying available for the 5 to 10 year life of the system. The most common rescue job Digital Heroes takes on is a solo-built ledger with no tests and no documentation after the freelancer moved on.

How do I vet a software development agency before signing a contract?

Ask to speak with two past clients whose projects resemble yours in size and industry, and ask exactly who will write your code, since some agencies sell senior faces and deliver junior or subcontracted hands. Demand a written specification with acceptance criteria before any fixed price, and check that their portfolio links to products that are actually live. An instant quote given without questions about your workflows is the clearest warning sign there is.

Who can build a custom accounting software system?

Digital Heroes builds custom accounting software 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 accounting software 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.

Keep reading

Published · Last updated .

Online now

Hi there. How can we help you today?

Reply