Skip to main content
Industry · Utilities & telecoms

Provisioning, billing, churn — measured.

Provisioning, billing, churn, regulatory — on one stack. From the customer's first sign-up to OFCOM's quarterly return, owned by you.

provisioning queue14 active
06billing run · in progress
03churn signals · this week
11dOfcom return · countdown
outage queuepriority
01Carrier circuit down · 142 customersHigh
02Read-to-bill mismatch · 28 accountsHigh
03Renewal window opens · 64 customersMed
04Ofcom QoS sample due FridayMed
Utilities ISPs · energy resellers · telco resellers · broadband · regulated−18% Typical churn reduction0 missed Regulatory deadlines, typical−60% Outage support calls, typical
By reseller type

Three flavours of the same instrument.

Same method, different licence. Pick the reseller type closest to yours — each has a deep page with the sector-specific stack, proof, and how we measure.

The reseller stack

Six builds, calibrated to the regulator.

Built for UK ISPs, energy resellers, and telco resellers running 10-100 staff — where every provisioning delay costs revenue, every missed return costs a fine, and every quiet leaver becomes a competitor's win.

01 · Provisioning

Sign-up to live service, hours not days.

Custom provisioning flows wired into carrier APIs. The customer signs up, the order routes, the circuit lights up — without a spreadsheet in the middle.

  • Custom sign-up & verification
  • Carrier API integration
  • Service activation tracking
  • Customer welcome automation
02 · Billing & metering

Read-to-bill, owner-readable.

Usage data, tariff logic, dunning, refunds — reconciled monthly, owner-auditable. Aurora, Inform Billing, Union Street, or custom — built around the tariffs you actually sell.

  • Usage capture & rating
  • Aurora / Inform Billing / Union Street
  • Dunning & failed-payment recovery
  • Per-customer P&L visibility
03 · Churn & retention

Catch the leaver before the cancellation form.

Custom event pipelines that surface usage drops, support spikes, and contract-end windows — before the customer fills in a switch request.

  • Custom churn signal pipeline
  • Renewal-window automation
  • Save-offer routing
  • Reason-coded exit data
04 · Regulatory

Ofcom + Ofgem returns, ready before deadline.

Custom workflows for QoS samples, complaint volumes, switching data, and supplier-of-last-resort obligations. Deadline countdowns, not deadline scrambles.

  • Ofcom GC C1-C5 reporting
  • Ofgem licence-condition tracking
  • Complaint-volume audit trail
  • Deadline calendar & alerts
05 · Outage comms

Customer-facing status before the phone rings.

Statuspage + Twilio wired to your monitoring. Affected customers see the incident, get the SMS, and stop calling support. Mean time to clarity, minutes.

  • Statuspage public incident feed
  • Twilio SMS to affected customers
  • Carrier-circuit monitoring hook
  • Post-incident report automation
06 · BrainBase

Carrier procedures, regulatory framework, training.

The institutional memory of a regulated reseller — carrier escalation paths, Ofcom correspondence, training material — searchable, version-tracked, owned.

  • Carrier procedure library
  • Regulatory framework index
  • New-starter training tracks
  • AI-assisted retrieval
Sample engagement

The ISP that caught the leavers first.

Four thousand customers. Twenty-eight staff. Churn read quarterly, never weekly.

A regional ISP ran provisioning on email, billing on a creaking custom script, and read churn from the accountant's quarterly file. Three-week build: usage signal pipeline into a renewal-window alert, statuspage wired to carrier monitoring, customer-facing outage SMS. Six months in: churn down eighteen percent, support calls during outages down sixty percent, weekly retention review on one screen.

How we measure: churn = customers ending service / customers active at month-start, rolling 90-day average pre-build vs post-build; outage call volume tracked through the Twilio-Statuspage incident window across nine recorded incidents.

−18%monthly churn rate
−60%outage support calls
0 missedOfcom returns, typical
Adjacent industries

Different shape of the same problem.

If your work isn't exactly this, the nearest sectors share the rhythm. Or browse every industry we build for.

Map the reseller stack.

Bring the last billing run, an Ofcom return draft, and a churn cohort. We diagnose from the data.