Telecom expense management is priced four ways: a fixed managed service fee, a per-unit fee on lines, circuits or invoices, a percentage of spend under management, or a contingency share of recovered credits. Most contracts blend two of them. The model you agree to matters more than the headline number, because each one rewards the provider for a different outcome.
Almost nobody in this market publishes prices, which leaves buyers comparing proposals that are not comparable. One quote is a monthly fee. Another is thirty-five percent of whatever it finds. A third is a fraction of a percent of spend. All three can describe the same scope of work and land in wildly different places over three years. This page explains how to normalize them.
Key Takeaways
- Four pricing models exist. Each creates a different incentive for the provider, and the incentive predicts behavior better than the rate card.
- Ask every provider to model three years assuming recoveries collapse after year one. A working program produces fewer recoveries by design.
- Line and circuit count, carrier count and invoice format drive price far more than spend volume does.
- Implementation is usually a separate one-time fee, and inventory build is the bulk of it.
- Percentage of spend under management quietly rewards the provider when your bills grow. Cap it or avoid it.
The Four Pricing Models
| Model | How it is calculated | What it rewards | Buyer risk |
|---|---|---|---|
| Fixed managed service fee | A monthly or annual fee for a defined scope and service level | Operational efficiency and clean invoices | Scope creep if the estate grows and the contract has no review trigger |
| Per unit | A rate per wireless line, per circuit, per meter or per invoice processed | Neutral. Cost tracks estate size. | Cost rises with growth, which is fair but should be forecast |
| Percentage of spend under management | A share of the invoice value flowing through the platform, often a fraction of one percent to a few percent | Rising spend, which is the opposite of the goal | The provider earns more as your bills increase |
| Contingency on recovery | A share of credits actually recovered, commonly twenty to fifty percent | Finding historical error, not preventing future error | Nothing structural changes, so the same errors reaccumulate |
Blended contracts are common and often sensible: a modest base fee that funds the ongoing operation, plus a smaller recovery share that rewards the provider for chasing credits hard. The structure to interrogate is the one where the provider earns nothing unless errors exist.
Ask what the provider earns in a year when your telecom spend is flat and your invoices are clean. That is the year the program is working. It should not be the year the provider loses interest.
What Actually Drives Your Price
Buyers often assume total spend sets the price. It contributes, but the real drivers are volume of things to reconcile and how messy the data arrives.
| Driver | Why it moves the price |
|---|---|
| Number of wireless lines | Each line is an inventory record that changes with every hire, leaver and role change |
| Number of circuits and locations | Circuits carry contracts, rates and term dates that all need testing every cycle |
| Number of carriers and billing accounts | Each carrier means separate record requests, separate dispute processes and separate formats |
| Invoice delivery format | Electronic data interchange is cheap to process. Portal downloads cost more. Paper costs most. |
| Number of invoices per month | Volume of documents, independent of their value |
| Allocation complexity | Splitting one charge across many cost centers is more work than coding it to one |
| Scope of categories | Adding wireless, utility or waste to a telecom program adds reference data, not just line items |
| Starting data quality | No existing inventory means the provider builds it from carrier records, which is the largest single cost in implementation |
Two organizations with identical telecom spend can differ by a large multiple in price if one has three carriers on clean electronic billing and the other has fourteen carriers, half of them delivering PDFs to individual site managers.
What Is Usually Included, and What Is Usually Extra
| Typically included in the core fee | Typically quoted separately |
|---|---|
| Invoice capture, loading and exception handling | Implementation and inventory build |
| Line-item validation against rates and inventory | ERP or accounts payable interface development |
| Dispute filing and pursuit | Historical audit of invoices predating the contract |
| Inventory maintenance through moves, adds, changes and disconnects | Contract negotiation and carrier sourcing support |
| Cost allocation and coded output | Custom reporting beyond the standard set |
| Standard reporting and quarterly business review | Device logistics, staging, kitting and recovery for mobility |
| Named account contact | Bill payment services, where the provider pays carriers on your behalf |
The two lines worth pinning down early are implementation and the ERP interface. Both are one-time, both are frequently underestimated in proposals, and both are where a cheap-looking annual fee quietly becomes expensive.
Normalizing Quotes That Look Nothing Alike
Three quotes arrive. One is a fixed monthly fee. One is per line and per circuit. One is contingency only. Reduce all three to the same shape before comparing.
- Pick a three-year horizon. One year flatters contingency pricing because recovery peaks early. Five years overstates the difference. Three is the honest middle.
- Model two recovery scenarios. Scenario A: recoveries continue at year-one levels. Scenario B: recoveries fall by seventy percent after year one because the estate is now clean. Scenario B is what happens in a working program.
- Add every one-time fee. Implementation, inventory build, interface development, historical audit.
- Add the internal cost each option leaves behind. A software-only quote is cheaper on paper and leaves the labor with you. Cost that labor honestly, including finance and accounts payable hours.
- Divide by something stable. Cost per line per month, or cost per invoice processed, gives you a number you can compare across models and re-check at renewal.
Run that exercise and contingency-only proposals usually reveal themselves. They are the cheapest option in year one and frequently the most expensive across three, because the provider takes a share of every dollar it finds and has no structural reason to stop finding the same dollars.
Total Cost Against the In-House Alternative
The comparison that matters is not provider against provider. It is provider against what you are spending today, which is usually invisible because it sits across several cost centers.
- Telecom and IT hours spent on invoice review, carrier calls and disconnect verification.
- Accounts payable hours spent coding uncoded invoices and chasing approvals.
- Finance hours spent building accruals from incomplete data and explaining variances after the fact.
- Procurement hours spent reconstructing contract terms because no rate table exists.
- Unfiled disputes. The dollar value of billing questions that expired because nobody reached them before the carrier window closed. This is a permanent write-off and it never appears as a line item.
That last item usually settles the business case on its own. It is worth calculating before you read a single proposal, because it tells you what the ceiling on value looks like regardless of which provider you choose.
How RadiusPoint Prices
RadiusPoint prices telecom expense management as a managed service scoped to the client’s estate rather than as a share of recovered credits. Pricing is built from the volume of lines, circuits, meters and invoices under management, the number of carriers and billing accounts in scope, and the categories included, since RadiusPoint processes telecom, wireless and utility invoices through the same ExpenseLogic workflow. Implementation is quoted separately and is driven primarily by inventory build, because ExpenseLogic validates every invoice line item against the maintained inventory of record and the contract rate table, and neither exists until they are constructed from carrier data.
The reason RadiusPoint does not price purely on contingency is structural. A contingency fee is earned when errors are found. A managed service fee is earned when errors stop happening. Those are different products, and only one of them compounds. For the broader decision this sits inside, see our guides to telecom expense management and outsourced telecom expense management.
Pricing Red Flags
- Savings guarantees with no written baseline. A guaranteed percentage means nothing until the baseline calculation is agreed in writing.
- Fees indexed to spend with no cap. Your bill goes up, the provider’s revenue goes up. Cap it or change the model.
- Implementation quoted in days for a complex estate. Fast implementations usually mean invoices were loaded and inventory was skipped, which makes the validation cosmetic.
- Auto-renewal with no performance exit. Tie renewal to agreed service levels, measured on days to credit and validation coverage.
- Exit costs left unspecified. Your inventory, rate tables and dispute history are your assets. Name the export format and the transition assistance period in the contract.
- A rate card with no coverage percentage. If the contract does not state what share of line items gets validated, the price has no defined unit of work behind it.
A cheap program that validates ten percent of line items is not cheaper. It is a smaller purchase being sold as the same one.
Frequently Asked Questions
How much does telecom expense management cost?
There is no single market rate, because pricing depends on line and circuit count, carrier count, invoice format and the categories in scope rather than on spend alone. The useful question is not the headline number but the model: fixed fee, per unit, percentage of spend, or contingency on recovery. Ask for a three-year projection under the assumption that recoveries fall sharply after year one.
Is contingency pricing cheaper?
In year one, usually yes, because the provider carries the risk and you pay only from recovered money. Across three years it is often the most expensive structure, since the provider earns a share of every error found and has no economic reason to eliminate the source of those errors.
What is percentage of spend under management?
A fee calculated as a share of the invoice value processed through the provider’s platform. It is simple to quote and easy to administer, but it aligns the provider’s revenue with your spend rising rather than falling. If you accept it, negotiate a cap and an annual review.
Are implementation fees normal?
Yes. Implementation is typically a separate one-time fee, and the majority of it covers building the inventory of record from carrier data rather than configuring software. A proposal with no implementation fee and a very short timeline usually means inventory build has been deferred.
Does adding wireless or utility invoices multiply the cost?
Not proportionally. Adding a category adds reference data and analyst time, but running telecom, wireless and utility through one workflow removes duplicate reconciliation effort that would otherwise sit with three separate internal teams.
How do we compare a software licence quote against a managed service quote?
Add the internal labor the software quote leaves with you, costed honestly across IT, accounts payable, finance and procurement, then compare totals. Software is cheaper on the invoice and is the right purchase only if you have the analysts to operate it.
Should the provider be paid for cost avoidance as well as recovery?
It can work, but avoidance has to be measured against a baseline written down at the start of the engagement. Without that baseline, avoidance claims are unverifiable and the arrangement becomes a source of dispute rather than alignment.
What should be in the contract regardless of pricing model?
The validation coverage percentage, days-to-credit service levels, who files disputes, ownership and export format for inventory and rate tables, a performance exit, and a review trigger if the estate changes materially.
Related: telecom expense management · ExpenseLogic · About RadiusPoint