Give a Small ISP Big-ISP Controls First

Small does not mean simple

A small ISP may have fewer subscribers but the same categories of risk: shared credentials, undocumented fiber, untraceable cash adjustments and one router acting as a single failure domain. Early systems should create discipline without demanding a large team.

Establish one customer identity

Choose an immutable internal customer ID and link sessions, invoices, payments, tickets and equipment to it. Usernames and phone numbers can change; history must not split when they do.

Separate duties early

Create roles for network, support and accounting even if one person currently holds several. Permissions then scale when staff join, and sensitive actions can require review without redesigning the system.

Document the physical path

Record site, router, OLT, PON, splitter and drop associations as the network is built. Reconstructing them after hundreds of installations costs far more than capturing them during each job.

Automate reversible work first

Start with reminders, reconciliation queues and read-only monitoring. Add suspension or provisioning only after retries, audit and recovery behavior are proven.

Put it into operation

1. Inventory. List customers, devices, links, integrations and owners
2. Normalize. Create stable identities and remove shared accounts
3. Reconcile. Compare money, service state and network sessions daily
4. Document. Capture topology and field changes at the source
5. Review. Revisit permissions and recovery as subscriber count grows

Research basis: CIS Controls v8; IETF RFC 2866; Google SRE Workbook. Implementation details must be verified against the deployed release and local policy.