What HQ sees on Commercial, and what it never does

What Commercial is for

Commercial is the third pill in the Accounts cluster (Carriers, TPAs, Commercial), which sits under the Accounts entry in the HQ sidebar at hq.verinode.ai/commercial. It rolls up the network's commercial book: the direct business-to-business clients each franchisee bills, as opposed to residential or insurance-driven retail work. If your network works property managers, banks, REO desks, or facility accounts directly, this is where HQ sees the shape of that book across every membership at once.

Commercial is not a client list. Verinode does not hand HQ a spreadsheet of every franchisee's customers. It is a network intelligence surface: aggregates, rankings, and concentration signals, built so HQ leadership can see patterns across the network without ever opening a single franchisee's private business data. That boundary, what rolls up and what never does, is the subject of this article.

Where this fits in HQ's positioning

Verinode HQ is the network intelligence layer for restoration franchise HQ, multi-location, and PE-backed leadership. It is not a job-management tool, an LMS, a CRM, or an accounting system, and it does not replace any of those. Franchisees keep running their businesses in whatever tools they already use. Verinode reads what already exists (jobs, billing, collections) and surfaces the pattern across the network.

Every membership in the network owns its own data. HQ's access is aggregates and compliance, never a single franchisee's raw client-level detail. That boundary is not a limitation bolted on after the fact, it is the reason franchisees trust the network enough to let their data flow in at all. A membership that believed HQ could see its named customer list, or single it out by elimination in a small cohort, would have no reason to keep sending data. The privacy boundary is what makes the aggregate valuable.

The two views on Commercial

Commercial has two lenses stacked on one page: a per-franchisee view (how each membership's commercial book is doing) and a cross-franchisee client view (which named commercial accounts appear across the network, and how many memberships bill them). Both lenses are gated by the same privacy boundary, applied differently because the two views carry different re-identification risk.

Hero: Network commercial book

At the top, the hero panel reads Network commercial book with a headline count of total commercial clients across the network, and a pill showing how many franchisees have commercial billing (or No data yet if none do). Below the headline:

• The number of commercial jobs billed over the trailing 36 months, with retail job count appended if the network also runs retail work (for example, "142 commercial jobs over 36mo · 89 retail").
• The name of the network's single top commercial client by billed dollars, when one exists.
• If your network's data posture is set to Independent operators (see below), a line reading "Franchisee rows are anonymized (independent-operator network)." so nobody mistakes the per-franchisee rows below for named identities.

Three secondary metrics sit beside the headline:

• Commercial billed 36mo, the network's total commercial billing, with retail billed as a sub-line when it exists.
• Top client billed, the dollar total billed to the network's single largest commercial client, with that client's name underneath.
• Avg days-to-pay, the network-wide weighted average time a commercial invoice takes to collect. Inside 30 days reads as on-target; longer reads as a collections watch item.

If the network has zero commercial clients recorded anywhere, the subtext reads: "Commercial clients will appear as franchisees register direct B2B accounts." That is not an error state, it means no membership has billed a named commercial account yet.

Top Commercial Clients by Spend

A row of tiles, one per commercial client, ranked by 36-month billed dollars. Each tile shows the billed amount, the client's display name, how many franchisees serve that client and how many jobs, and average days-to-pay. Clicking a tile opens that client's detail page (see below).

Empty or partial: if no cross-franchisee client data has flowed in yet, the row reads: "Cross-franchisee commercial clients will appear here once jobs flow through with named clients." If some clients exist in the network but are hidden under the anonymity floor described below, the same message appends a count: "N single-franchisee clients hidden under K-anonymity."

Most Shared Commercial Clients

A second row, filtered to clients billed by more than one franchisee, ranked by how many franchisees serve them. This is the row that surfaces genuine cross-network relationships, the same bank, property manager, or facility account showing up in multiple memberships' books. Each tile shows the franchisee count, client name, job count, and total billed.

Empty state: "No commercial clients are served by more than one franchisee yet. Cross-network clients appear here when the network bills the same client through multiple operators."

Concentration Risk

A row surfacing franchisees whose commercial book leans heavily on a single client, defined as more than half of that franchisee's 36-month commercial billing coming from one account. Each tile shows the concentration percentage, the franchisee's name, the top client's name (or "Commercial book" if unnamed), and the dollar amount from that top client. Tiles at the higher end of the concentration range render in a stronger accent to flag the sharper risk.

This is a genuine operational signal for HQ: a membership overexposed to one commercial relationship is one lost contract away from a revenue cliff, and HQ is positioned to notice that pattern (and offer support, an introduction, or a diversification conversation) faster than the franchisee might catch it alone.

Empty state: "No franchisee shows more than 50% of its commercial book on a single client."

Largest Commercial Books

The network's largest commercial books by 36-month billed dollars, up to eight franchisees. Each tile shows billed dollars, franchisee name, client count, job count, and the top client. HQ uses this row for recruitment and case-study material: proof that the commercial channel works inside this network, without ever exposing who the clients are outside the boundary already described above.

Empty state: "Largest commercial books will surface here once franchisees record commercial-job revenue."

All Franchisees

Every franchisee with a commercial rollup, sorted by commercial billed dollars, up to 18 tiles. Each shows billed dollars, franchisee name, a commercial-versus-retail client split, and a job count with days-to-pay. Clicking a tile opens the franchisee's commercial detail as a compare overlay rather than navigating away.

Empty state: "No franchisees rolled up yet. Data appears after the next nightly aggregation." Commercial numbers refresh once per night, not live, so a franchisee's newest job or invoice will not appear on this page until the following day's aggregation run.

Clicking into a client: what the drill-in shows

Clicking any commercial-client tile opens that client's detail page. The header repeats the client's display name, its type (for example, Property manager or Facility account), how many franchisees serve it, and the date of its most recent completed job.

Below the header, two rows of tiles:

• Billed (36mo) with collected dollars underneath, Franchisees serving (labeled "Cross-network client" when more than one, "Single-franchisee client" when exactly one), and Avg days to pay (flagged above 60 days as a collections risk, above 45 days as a watch item).
• Jobs (36mo), Jobs (last 30d), and Collection rate (collected divided by billed).

A closing note explains the matching logic: clients are matched across franchisees on case-insensitive name only. The same client billed under two different spellings (the page's own example: "Bank of America" versus "BoA") will not currently merge into one row, a fuzzy-match improvement is on the roadmap.

When the client is suppressed, the page shows no metrics at all. Instead: "Aggregate-only view. This client is currently served by fewer than 2 franchisees in your network. Per-client metrics are suppressed to protect operator privacy (single-franchisee identification risk). The client will surface here in full once cohort size reaches 2+."

The privacy boundary, in full

Three separate mechanisms combine to enforce the Commercial page's privacy guarantee. Each answers a different question.

1. Aggregation is the default shape

Every number on this page is already a rollup: dollars billed across 36 months, job counts, days-to-pay averages. Verinode does not surface a franchisee's individual invoices, individual client contracts, or line-item billing on this page. The per-franchisee rows you see are pre-aggregated summaries built by a nightly network refresh, not a live read of a franchisee's private records.

2. Single-franchisee client suppression (K-anonymity)

The cross-franchisee client rollup (Top Commercial Clients by Spend, Most Shared Commercial Clients, and the client drill-in) exists because the same commercial client sometimes appears in more than one franchisee's book, and that overlap is a genuine network signal worth surfacing. But if a client is served by only one franchisee, showing that client's row would tell HQ exactly which franchisee holds it, defeating the anonymity the rest of the page relies on. Clients served by too few franchisees are suppressed from every client-facing view and rolled into a hidden count instead, shown qualitatively (for example, "N single-franchisee clients hidden") rather than exposing which franchisee holds them. This suppression applies automatically; there's no per-client toggle to override it.

Note that this specific gate (client-level suppression) is not the same rule as the per-franchisee tile gate below, it protects a different surface (named clients) using the same underlying principle: a group small enough to identify a single member by elimination doesn't get shown as a named row.

3. Small-network suppression for per-franchisee tiles

Separately, the per-franchisee tile rows (Concentration Risk, Largest Commercial Books, All Franchisees) carry their own risk: each tile is inherently a group of one franchisee, so name anonymization alone (see below) doesn't fully protect a very small network from being reasoned out by its metrics alone. When a network has too few active franchisee memberships, Commercial (and its sibling pages: Facilities, Fleet, Equipment) suppress the entire per-franchisee tile arrays and show only the hero aggregates. A disclosure banner explains why:

Aggregate-only view. Your network currently has fewer than three active operators, so per-franchisee commercial book tiles are suppressed to protect operator privacy (small-cohort identification risk). Hero aggregates still surface. Tiles return once the network reaches 3+ active operators, or change the network data posture in Settings → Group → Data posture.

This banner only appears for networks running the Independent operators data posture (see next section). Growing past the threshold, or switching data posture, brings the tiles back automatically on the next page load.

4. Franchisee-name anonymization

Whether per-franchisee names are shown at all depends on the network's data posture, a setting HQ admins control at Settings → Data posture (visible on every HQ page that drills into individual operators: Commercial, Facilities, Fleet, Equipment, Network drill). Two modes:

• Independent operators (the default for every new network, marked "Default · privacy-safe"). Use this for franchise networks, associations, co-ops, and PE roll-ups where each operator is a separate legal entity. Per-franchisee rows render as Franchisee #XXXX, a stable label derived from the operator's account ID so the same franchisee always gets the same label across sessions, but the label itself never reveals who they are. City, state, and contact email are hidden alongside the name. Aggregate metrics keep flowing in full.
• Same entity, for enterprise multi-location operators running under one tax ID. HQ sees the network's own data: franchisee names, city, state, and contact email all surface raw. This mode exists because there's nothing to anonymize, an enterprise's own regional offices are its own data, not a peer's.

Only HQ admins can change this setting, and a change applies to every operator-facing HQ page on the next page load, network-wide. There is no per-franchisee override: the whole network runs one posture at a time.

Why raw client-level data never surfaces to HQ

The design intent behind Commercial mirrors the boundary that runs through the entire HQ product: franchisees own their data. HQ's job is to see the network, not to see inside any one membership's business.

Concretely, that means:

• HQ never receives a franchisee's full client list. Only clients that clear the cross-franchisee cohort floor above appear as named rows, and even then, only aggregated billing and job metrics, never invoice-level or contract-level detail.
• A franchisee's commercial book is never exposed at a level of detail finer than the tiles described above (billed dollars, job counts, days-to-pay, top-client concentration). There is no path from Commercial to a franchisee's raw commercial ledger.
• Small networks get less resolution, not more risk. Where K-anonymity can't hold (too few franchisees, too few operators serving a client), Verinode suppresses the row rather than showing it with a caveat. The floors described above exist for exactly this reason: when the group being aggregated is small enough that a single row could be reasoned back to one franchisee, that row does not get shown, full stop.
• Verinode surfaces and recommends. HQ leadership decides what to do with a concentration-risk flag or a shared-client pattern, Verinode does not rank franchisees against each other in a way that exposes one's raw numbers to another, and it does not make personnel or contract decisions on HQ's behalf.

This is the same commitment that runs through Verinode's broader independence posture: the network's intelligence layer only works if every membership trusts that contributing data can never be turned against them individually. Commercial's suppression rules, anonymization defaults, and aggregate-first design are that trust made concrete in one page.

Best-practice example

Say your network runs Independent operators posture with six active franchisee memberships. On Commercial, the hero shows 340 total commercial clients and $2.1M billed over 36 months. The Most Shared Commercial Clients row surfaces a facility-management account served by three franchisees, a genuine cross-network relationship worth a broadcast to the network about how those three memberships won and grew that account (see Broadcasting to your network). Meanwhile, Concentration Risk flags one franchisee (shown as Franchisee #4B2C) at 78% of its commercial book on a single client, a real risk HQ can act on: a support call, an intro to a second account, or a conversation about diversification, without HQ ever seeing which named client that franchisee actually serves, or that franchisee's other business details. A seventh commercial client appears in the network but is served by only one franchisee, so it never renders as a named row anywhere on the page, it's folded into the suppressed count instead.

If that same network only had two active franchisee memberships, the entire per-franchisee tile section (Concentration Risk, Largest Commercial Books, All Franchisees) would be replaced by the aggregate-only disclosure banner, and only the hero numbers would show, until a third membership came online or the network switched to Same entity.

Related reading

• What HQ sees: the platform shell Commercial lives inside.
• Network Health: the network-wide pulse this page's numbers roll into.
• HQ Benchmarks: how HQ compares memberships on standardized metrics under the same anonymity principles.
• HQ Compliance: the compliance-only side of HQ's access model.
• HQ Standards: how HQ sets and monitors network standards without seeing raw operator data.