For B2B telecoms and connectivity providers
Which customers have twelve sites on your network and forty in total. Which accounts buy connectivity and nothing else. Which account manager holds sixty logos and has quoted eight this quarter. From billing and the CRM, customer IDs only.
A telecoms customer is a set of sites, and every site is a sale. Covirage counts sites on-net against sites in total, layers product lines on top, and values the gap at your average revenue per site.
Sites served against the customer's estate, from the CRM or a public register.
Products per site against the norm for that customer type.
Logos per manager against quotes logged, so the gap list fits the quarter.
Three steps, in this order.
Revenue by customer, site and product.
Site lists from the CRM where you hold them. Otherwise the norm for the segment is used.
Managers get sites and product gaps. Sales leaders get the roll-up.
Short answers. The Help centre has the long ones.
This page is for business sales. Consumer is a different product.
Site addresses are hashed on the way in. Customer IDs only.
Any export with customer, site, product and revenue. Most billing platforms export it directly.
Analytics software for telecoms and connectivity, compared · Alternatives to named products
Written for this desk: the measures, the data you already hold, and the arithmetic.
How a business telecoms provider builds the renewal calendar from the contract register: contract value ending per month per account manager, the accounts within the notice window with no logged renewal activity, the co-terminus opportunities where a customer's services end months apart, and the identity that ties the calendar's total to the contracted base.
16 Sept 20262 min readSite penetration is only as good as the site count it divides by. This guide sets out where a business telecoms provider gets each customer's estate, how to date and source it, how to reconcile it to billing so closed sites do not linger, and the review cadence that keeps the number honest.
16 Sept 20262 min readHow a business telecoms provider measures the days from a service order to activation per customer and per site from the order and provisioning exports, the norm per service type from its own history, the customers whose recent orders took twice the norm, the correlation with contract non-renewal from the provider's own outcomes, and the list that reaches the account manager while the customer is still installing.
16 Sept 20262 min readHow a business telecoms or connectivity provider measures wallet share by site rather than by logo: sites on-net against the customer's estate, product attach per site against the norm, account manager load, and the reconciliation to billed revenue.
16 Sept 20263 min readHow a business telecoms provider reads its usage data per site against each site's contracted capacity: peak utilisation against the circuit's bandwidth, the sites above a stated share of capacity for a stated number of days, the customers with several such sites, the upgrade value at the next tier, the sites whose usage fell to nothing and may be closing, and why the upgrade list beats the fault ticket as the moment to sell more.
16 Sept 20262 min readThe ten questions a business telecoms sales director puts to the account managers, what is site penetration and is the estate current, which sites are near their capacity, which contracts end in the notice window untouched, which orders are stuck in provisioning and where, which customers' estates have closed sites still billed, what is product attach per site against the norm, which customers could co-terminate, which sites went quiet, which account managers cover at cadence, and what changed, each with the table from billing, the estate file, the contract register and the usage export, and the answer to send back.
16 Sept 20263 min read