HQ Sales & Marketing privacy boundary

The rule this page follows

The HQ Sales & Marketing page shows how well your network wins work: a network median job value, offices ranked against each other, a set of growth benchmarks, and how fast a lead moves through your network's own pipeline. Every one of those numbers is built from real franchisee data, and every one of them is an aggregate. Verinode's rule for this page, and for HQ generally, never moves: HQ sees per-office medians and rankings, consented through group membership. HQ never sees a single franchisee's job timelines, case IDs, or raw books.

This article is the trust layer under HQ Sales & Marketing: section overview. That article tours the hero, Top Job Value, Sales & Marketing Benchmarks, and Network Lead Response rows. This one explains exactly what data can and cannot cross into each of them, how office names are handled, how the industry reference line protects operators outside your network, and how the boundary is enforced in the database, not just in the interface.

Where this applies

Everything here governs Sales & Marketing, at hq.verinode.ai/sales-marketing, in the sidebar's Revenue group alongside Accounts and Reputation. It also covers the same growth metrics wherever they resurface: the Sales & Marketing category inside Benchmarks (hq.verinode.ai/benchmarks), and the Network Lead Response tiles that deep-link into the Network Flow row on Network Health (hq.verinode.ai/network). All three read from the same consented, aggregated numbers described below.

What crosses the boundary: a median, a rank, never a job

Every figure on Sales & Marketing is one of two things: a rollup across your own offices, or a single reference figure drawn from operators outside your network. Neither path ever exposes an individual job, lead, or invoice.

• Your network's own numbers. The hero's Network Median Job Value, the Top Job Value ranking, and each tile's network figure in Sales & Marketing Benchmarks are all built the same way: Verinode computes one representative value per office (a median billed job value, a close rate, a marketing-spend ratio) from that office's own facts, then takes the median, the ranking, and the spread across the offices in your group. What HQ ever reads is that one number per office, consented by the franchisee's membership in your group, never the underlying jobs, leads, or line items that number was built from.
• The industry reference line. Wherever a tile shows "Industry [value]," that figure is the median of operators entirely outside your network, protected by its own anonymity floor described below. It is never a named business, never a per-operator breakdown, just a single median.

There is no drill path anywhere on this page from a network figure back down to a franchisee's actual invoices, job records, or lead detail. A franchisee's business stays in their own IQ account. What flows up to HQ is the rollup, and only the rollup.

Office names: the entity-model gate

Whether an office appears by name on Sales & Marketing depends on your network's entity model, the same setting that governs office naming everywhere else on HQ:

• Same entity (one enterprise operating multiple company-owned locations): real location names appear throughout, including on the Top Job Value ranking. There is nothing to anonymize, since it is one business looking at its own branches.
• Independent operators (franchise and association networks, the default): every office is labeled with a stable code, "Franchisee #XXXX", derived from that operator's own account rather than their business name. The same franchisee always carries the same code across the Top Job Value row, the Sales & Marketing Benchmarks drill-down inside Benchmarks, and the Network Flow per-office list, so you can track a pattern for one office over time without its identity ever being disclosed.

This gate applies uniformly. Every office name reaching a Sales & Marketing tile, whether the network median headline, the Top Job Value ranking, or the per-office list behind a benchmark's deep-dive, passes through this same anonymization step before it renders. There is no separate, looser naming rule anywhere on this page.

The industry reference line has its own floor

Office naming protects your own network's identity from being disclosed inside the page. The industry reference line protects a different set of people: the operators outside your network whose data forms that single median. Before Verinode will publish "Industry [value]" on any Sales & Marketing tile, the anonymous cohort behind it has to clear a minimum number of distinct contributing operators, counted as operators, never as rows of data. An operator with a lot of history behind it (many jobs, many snapshots) still only counts once. One operator with plenty of rows is still a cohort of one, and publishing a "median" built from a cohort that thin would hand a competitor that operator's exact private number wearing a benchmark label.

That floor is not the same for every growth metric. Marketing % of Revenue draws from an office's normalized profit and loss statement, the same sensitive plane as margin and other cost-structure figures, so its industry cohort has to clear a noticeably wider bar than an operational metric like Average Job Value or Close Rate before its reference line will show. This is a legal commitment in Verinode's published data-use policy, not just an engineering preference, and it does not bend for any one network's request. Below the floor, there is no line, no partial figure, no "based on N operators" caveat sitting next to a thin number. The tile reads "Industry, " and stays that way until enough independent outside operators have contributed.

Network Lead Response: aggregates only, same discipline

The fourth row on Sales & Marketing, Network Lead Response, reads a different kind of data: how many days a lead sits at each stage on its way to becoming a signed job. This is process mining, not a benchmark, but it follows the identical doctrine. What crosses the boundary is a stage's median duration, pooled across every in-order case from every office that has one, and, where enough outside data exists, a single industry median for that same stage transition. Verinode never surfaces an individual lead's record, its stage history, or which franchisee it belongs to. The tile shows a process label, a stage transition, a network median in days, and a comparison line, nothing that would let you trace a number back to one lead or one office's specific pipeline.

Two coverage rules sit underneath this row, both about whether there is enough of your own data to trust a number, not about hiding anyone's identity:

• The tile itself stays hidden, not empty, until the network has at least one lead-response stage transition reporting a live median. This process was only recently registered on the network-level rollup, so the row stays quiet rather than showing a placeholder number while offices ramp up lead-stage reporting.
• An office only enters a stage transition's per-office breakdown once it has logged enough of its own in-order cases on that specific stage to trust a median. Below that, the office's data stays off the list rather than publishing a figure built on too few cases.

The industry median beside a stage transition follows the same anonymity floor as every other cross-network reference line on this page: it only appears once the anonymous peer cohort behind it is broad enough that no single outside contributor could be identified from it. Read the fuller mechanics of a Network Flow tile, including the office spread fallback when no industry figure exists yet, in Network Flow: how work moves through the network.

Enforced in the database, not just the interface

None of the above is a display choice HQ's frontend could accidentally bypass. Every read behind Sales & Marketing, the per-office growth benchmarks and the Network Lead Response rollup alike, goes through hqAdmin, the only database client HQ-side code is permitted to use. hqAdmin's connection role has a hard, schema-level revoke on the PII database where a franchisee's actual jobs, invoices, and adjuster correspondence live: a query against that schema from HQ's server fails at the database itself, successful login or not. There is no code path on this page that could reach a franchisee's raw records, because the database refuses the connection before any application logic runs.

The industry side of the boundary has a second, independent layer. Inside Verinode's intelligence layer, an operator is never stored by name or account ID. Every fact contributed to a cross-network benchmark, including the growth metrics behind Sales & Marketing, is keyed by a one-way cryptographic hash of the operator's ID. HQ can resolve that hash back to one of your own franchisee's office names only because your group's own roster already maps its members' hashes to names, the same names your directory already has. HQ has no equivalent lookup for an operator outside your network: the intelligence layer has never stored that operator's name in the first place, only their hash and their contributed value, so there is nothing for HQ, or anyone else, to resolve it into.

Empty states

Sales & Marketing states these gaps in plain language rather than showing a placeholder number:

• Hero, before any office has reported growth data: the headline shows a blank dash, and the context line reads "Network sales & marketing numbers appear as members share their books, jobs, and leads."
• Top Job Value, before any office has a ranked value: "Office rankings appear as members share their job data."
• Sales & Marketing Benchmarks, before any growth metric clears the floor: "Network benchmarks appear as members share their books, jobs, and leads."
• Network Lead Response, before the network has a live lead-stage median: the row is omitted entirely, not shown with a placeholder tile.
• Any tile's industry line, below the anonymity floor: the tile reads "Industry, " rather than a number with a caveat attached.

None of these are errors, and none of them require you to do anything. Coverage on this page moves in one direction only, more offices reporting jobs, leads, and financials, more outside operators contributing to the reference lines, so cards and figures that are quiet today fill in on their own as the data behind them grows.

How to use it

1. 1Treat every network figure on this page (the hero headline, the Top Job Value ranking, a Sales & Marketing Benchmarks tile) as your own network looking at itself. Franchisee membership in your group is what consents that office's rollup into the page, not a separate permission you need to request.
2. 2Treat every "Industry [value]" line as a single outside reference, never a lookup. There is no way, on this page or anywhere else on HQ, to see which operators sit behind that median or drill into their individual numbers.
3. 3If an industry line reads "Industry," read that as coverage still building outside your network, not as a gap in your own data. Your network's own median and ranking are unaffected either way.
4. 4If your network is set to independent operators, expect "Franchisee #XXXX" labels on every office tile. That label is stable for one office across every Sales & Marketing surface, so you can track its pattern over time without ever seeing its real name.

Related help

• HQ Sales & Marketing: section overview: the full page tour this article's privacy rules sit underneath.
• The six growth metrics on HQ Sales & Marketing: what each metric measures and which one carries the stricter, sensitive-category anonymity floor.
• Network Flow: how work moves through the network: the full mechanics of a stage-transition tile, including the office spread fallback when no industry median exists yet.
• Coverage labels and the anonymity floor: the general confidence ladder and anonymity floor used across every HQ benchmark, not just growth.
• The per-office benchmark engine: how a network median, an office ranking, and an industry reference line are computed for every HQ metric family.
• What HQ sees: the network privacy boundary: the full trust model across HQ, including the database-level enforcement this article summarizes for Sales & Marketing specifically.
• Benchmarks: how HQ reads the network: the full Benchmarks tab the Sales & Marketing Benchmarks row deep-links into.

Data sources