Collections planning worksheet
ISP billing ROI calculator
Estimate what late collections tie up and how much manual reconnect and payment-matching time your team could recover. Start with your own numbers.
Free to use. No email required. Calculator inputs stay in this page and are not saved or sent.
Your monthly scenario
Illustrative inputs, not operator benchmarks. Replace them with your records.
Monthly estimates
No guaranteed savings. Validate each assumption in your own workflow.
Estimated revenue at risk from late collection
KES 35,000.00
Subscribers × monthly ARPU × late share ÷ 100 × min(days late, 30) ÷ 30
Estimated cash-flow exposure within one 30-day cycle. It is neither lost revenue nor money you will recover.Estimated hours recovered per month
21.7 hours
Manual team hours/week × 52 ÷ 12 × assumed recovery share ÷ 100
Assumes 50% of entered manual time can be removed. Actual recovery can be zero.Estimated value of recovered time per month
KES 6,500.00
Unrounded estimated hours recovered × staff hourly cost
Capacity value, not a payroll reduction. Excludes software, setup, provider fees and ongoing oversight.Read the estimates before using them
This worksheet is a starting point for a collections conversation, not a financial forecast. The initial 500 subscribers, 20% late share and 50% time-recovery share are illustrative inputs, not industry benchmarks or customer results.
Estimated revenue at risk is time-weighted cash-flow exposure. We assume every billed subscriber has the same monthly ARPU and the late-paying group has the same ARPU as everyone else. We model one 30-day billing cycle. A seven-day delay weights the late-billed amount by 7/30; delays of 30 days or more use 30/30. This excludes accumulated arrears, partial payments, bad debt, taxes and financing costs. If nobody pays late or the delay is zero, the estimate is zero.
Estimated hours recovered assumes the entered manual work repeats weekly, using 52/12 weeks per month. Enter combined staff hours for reconnects and payment matching, counting overlapping tasks only once. Change the recovery share to reflect the work you expect to remove; zero is a valid scenario. It is independent of the late-payment estimate because payment matching and reconnect work can also involve on-time payers.
Estimated value of recovered time uses unrounded hours, then formats the final amount in the selected currency. Hours display to one decimal place. This measures potential staff capacity, not cash saved. Software subscriptions, setup, training, payment-provider fees and ongoing oversight are excluded. Do not add cash-flow exposure to staff capacity value or present either as a guaranteed return.
Inputs must be finite and non-negative. The worksheet accepts up to 1,000,000 whole subscribers, 1,000,000,000 currency units for ARPU or hourly cost, 365 days late, 100,000 combined team hours per week and percentages from 0 to 100. These are calculation bounds, not supported product scale or realistic operating benchmarks. Invalid or empty inputs hide estimates until corrected.
How ISPAgents helps
Available — basic subscriber management: subscriber records, search and device assignment/removal provide a place to connect a subscriber with their device. This is not an accounting-grade CRM claim.
Guided pilot — customer billing and reconciliation: invoice, payment, ledger, allocation, provider evidence, reconciliation and settlement foundations can be evaluated with explicit onboarding limits. Statements, aging, tax, refunds and production recovery workflows remain outside this claim. Review the billing scope.
Guided pilot — mobile-money/payment adapters: provider-neutral abstraction, presets and webhook evidence foundations exist. Live M-Pesa, MTN, Orange, Airtel, Wave and other provider API clients are not shipped. A currency option in this calculator does not imply provider or country availability.
Guided pilot — automatic suspension and reconnection policies: previews, queued jobs, approvals, result recording and a mock-safe worker exist. Live router/RADIUS mutation remains gated pending real adapters, credential resolution, rollback evidence and monitoring. Review the access-policy boundaries.
Measure a workflow before expanding it
Record the actual manual hours and collection delays for a small reconciled sample. In a guided pilot, agree on one workflow, its supported adapter path and the evidence to compare before and after. Keep exception handling and human oversight in that measurement. A calculator result is not evidence that an integration is available or that money will be recovered.
Frequently asked questions
Does this calculator predict guaranteed savings or ROI?
No. Every output is an estimate from your inputs. The editable recovery share is a scenario assumption, not measured ISPAgents performance. There is no net ROI percentage because implementation costs, software prices and actual recovered cash are not known.
What does revenue at risk mean here?
It is estimated cash-flow exposure within one 30-day billing cycle: subscribers × monthly ARPU × late share ÷ 100 × min(days late, 30) ÷ 30. It is not bad debt, total unpaid invoices or a forecast of cash recovered. Delays beyond 30 days are capped at one cycle; older arrears are excluded.
How are hours recovered and their value estimated?
Team hours per week × 52 ÷ 12 × assumed recovery share ÷ 100 gives estimated monthly hours recovered. Multiplying the unrounded hours by staff hourly cost estimates capacity value, not payroll savings. Actual recovery can be zero.
Do I need to provide an email or upload billing records?
No. Results are available without a form or account. Calculator inputs are processed in this page, are not saved or sent, and reset when you reload. With JavaScript disabled, the illustrative example, formulas and explanatory content remain readable.
Does changing currency convert my amounts?
No. KES, NGN, XOF, MAD, ZAR and USD select the display currency and regional number format only. Enter ARPU and hourly cost in the selected currency. XOF displays whole francs; the other supported currencies display two decimal places.
Is automatic reconnection after a mobile-money payment available beyond guided pilots?
This is not a generally available promise. Mobile-money/payment adapters and the service-policy engine are Guided pilot foundations. Live provider clients and router/RADIUS mutations remain gated; the provider, adapter, credential resolution, rollback evidence and monitoring must be verified for a specific pilot.
Test your assumptions in a guided pilot
Agree on one workflow, its limits and the evidence to measure.
