Billing
Invoice-and-pay versus automatic charging
Two ways to collect money for hosting, with different cash flow, different disputes and different failure modes. Which one you have is often an accident.
9 min read · Reviewed 2026-09-21
Count recurring revenue from active services at their current price, normalised to a month, excluding anything one-off and anything unpaid beyond your grace period. Measure churn on customers and on revenue separately, because losing ten small customers and one large one are different events that a single number hides.
Hosting is a subscription business, so the subscription metrics apply — and they are all easy to compute in a way that flatters. The errors below are not exotic; a reporting screen makes them unless somebody decided it would not.
Monthly recurring revenue is the sum of active recurring services at their current price, normalised to one month. The word doing the work is recurring.
| Measure | What it answers | What it hides |
|---|---|---|
| Customer churn | How many relationships ended | That the one you lost was 20% of revenue |
| Revenue churn | How much recurring revenue left | That you lost thirty small customers |
| Net revenue churn | Lost revenue minus upgrades | Whether you are growing by retaining or by upselling |
Compute all three. They diverge in useful ways: customer churn rising while revenue churn is flat means you are losing your smallest customers, which is often fine. The reverse is an emergency.
The usual formula — average revenue divided by churn rate — assumes churn is constant, which it is not: it is high in the first months and much lower afterwards. Applied to a young business it produces enormous numbers. If you use it, state the assumption and prefer a cohort view: what did customers who joined in a given quarter actually pay over the following year? That is measured rather than projected.
Beware any dashboard whose headline number is bigger than the sum of the rows beneath it. The first suspect is a join multiplying something — and if the same query feeds an invoice, a customer may find it before you do.
For a small hosting business, three operational figures are worth watching alongside revenue, because each can show trouble before revenue does: time to first reply on support, count of unresolved provisioning outcomes, and domains expiring in the next thirty days that are not paid. Each one is a small list of specific things somebody can act on today.
GENV records invoices, payments, credits and billing subscriptions as separate facts pointing at each other, which is what makes a part payment or an overpayment representable rather than forced into a status. Services carry the state that decides whether work may begin, and that state is computed from the same functions on the list and the detail screens so the two cannot disagree — which was, in fact, a bug fixed during development.
No. Tax is collected on behalf of an authority and is not yours. Report it separately, and be consistent: a mixture is worse than either choice.
It varies enormously by segment and published benchmarks are rarely comparable, because everybody counts differently. Compare against your own previous quarters rather than against a number from an article.
Monthly for revenue figures, weekly for the operational lists. The operational ones are actionable today; the revenue ones are only meaningful over several periods.