One reconciled subscriber base for the board, the lender, and the grant auditor

The one your credit agreement defines, drawn off a reconciled base. The three readers legitimately need three definitions: the board reports revenue-generating units, the lender counts subscribers under the covenant definition in the credit agreement, and the grant auditor counts locations deployed and served at funded locations. Billing counts active accounts, the ACS counts ONTs online, and the subsidy filing counts funded locations. Synopsis lands all three sources in one warehouse keyed to the same address and itemizes every difference: lit-but-unbilled drops, disconnects still lit, dark-but-billed accounts, and duplicates. Each definition then reads off the same base, and you can show how one becomes another. Synopsis brings the records together for analysis; it doesn't replace your systems of record.

Yes. Every subscriber in the bridge traces back to a billing account, an ONT serial, and an install work order at a funded location, so audit fieldwork starts from evidence instead of a spreadsheet hunt. Grant filings count locations deployed and served, so the location list and the subscriber list stay separate and each traces to its own evidence. Your grants manager still reviews and files; Synopsis assembles the evidence behind each number.

Nightly. Billing, the ACS, GIS, and the GL reload each night, and every exception list rebuilds with them: lit-but-unbilled drops, disconnects still lit, dark-but-billed accounts, and duplicates. A question asked in the middle of a quarter gets the same reconciled base the quarter-end report will use.

Yes. Sonar billing accounts and Calix Cloud device inventory land in one warehouse keyed to the same subscriber and service address, so lit-but-not-billed reads as one query. The same holds for Powercode, Splynx, Visp, Azotel, NISC iVUE, Adtran Mosaic, and the rest of an operator's systems.

Usually, yes. The AI builds the connector from an export or an API, and a new system is typically flowing in days. If it can produce a file, it is a candidate.

Your first connected systems are answering questions in about 48 hours, and a full rollout lands in days, not a multi-quarter data project.

No. We configure your warehouse with you and connect the systems you already run; your team just asks questions in plain English. Nobody has to write SQL or babysit pipelines unless they want to.

No. Your systems of record — ERP, CRM, accounting, and the rest — stay exactly where they are. Synopsis sits on top and joins them into one place you can query, so you report across everything instead of exporting from each tool.

Your data stays in your own warehouse — we don't keep a copy. Access is governed per user and every query is audit-logged. Synopsis is SOC 2 Type II, and you can review our live security posture in the Trust Center.

BI tools chart data that something else already had to clean and join. Synopsis does that upstream work — connecting your systems, resolving entities, and enforcing your metric definitions — then answers in plain English, builds the dashboards, and traces every number back to its source.