Question 1

What does per-location competitive density mapping for multi-location operators actually deliver?

Accepted Answer

An orchestration layer that sits above the operator POI + foot-traffic + commercial-real-estate + reviews + demographic + geospatial + trade-area-modeling + warehouse + policy-as-code + WORM-storage stack and produces a per-location per-competitor per-category density score + per-trade-area saturation calculation + per-whitespace opportunity surface with operator-counsel-approved substantiation pointers. The skill is a three-skill bundle on the local-context agent. Skill 1 — Score: ingest per-location per-competitor per-category density signals across multiple vendors (Google Maps Platform + Google Places API + Yelp Fusion + Foursquare Places + SafeGraph + Placer.ai + Esri Business Analyst + Nielsen Spectra + Datafiniti + ListAlpha for POI + density; CoStar + LoopNet + Reonomy + Crexi for commercial real-estate; Yelp + Google Reviews + TripAdvisor + Facebook + Birdeye + Reputation.com for reviews) and compute per-competitor per-category density across the canonical competitor taxonomy (direct, indirect, substitute, adjacent, aspirational, budget, premium, mass, specialty, independent, franchise, regional-chain, national-chain, international-chain, online-only, brick-and-mortar, omnichannel, click-and-collect) and density-scoring dimensions (storefront density, SKU density, service-line density, staff density, hours-of-operation density, foot-traffic density consumed from the continuous foot-traffic ingestion sibling skill, review-volume density, review-recency density, review-rating density, ad-spend density, social-presence density, SEO-presence density). Skill 2 — Saturate: compute per-location per-trade-area saturation across multiple trade-area definitions (0.5-mile, 1-mile, 2-mile, 3-mile, 5-mile, 10-mile, 15-mile, 25-mile radius + drive-time 5/10/15/30/45/60-minute polygons computed via operator-chosen routing engine — Mapbox Isochrone + Google Distance Matrix + ESRI Network Analyst + HERE Routing) using the operator-data-science-team-chosen gravity-model coefficient (Hotelling for symmetric duopoly cases, Huff for probabilistic catchment, Reilly + Converse for retail-gravitation, Christaller + Lösch for central-place hierarchy, gravity-model coefficient for parameterized cases). Skill 3 — Surface: emit per-location per-whitespace opportunity recommendations with per-whitespace per-trade-area action (expand, contract, shift, add coverage), per-whitespace per-category action (add, expand, contract, shift, specialize, cross-sell, up-sell), per-whitespace expected outcome with operator-counsel-approved substantiation pointer, and per-whitespace counterfactual validation against operator-finance-team-approved holdout-control. Every Score, Saturate, Surface decision routes through the 5-anchor compliance gate and writes to the WORM audit trail. The POI, foot-traffic, commercial-real-estate, reviews, demographic, geospatial, and trade-area-modeling vendors below ship strong primitives. The orchestration above them — competitor taxonomy, cross-vendor density-scoring reconciliation, gravity-model coefficient selection + parameterization, whitespace surfacing with substantiation, compliance gate, audit trail — is operator-side architecture.

Question 2

Where does single-vendor competitive analytics stop compounding for multi-location operators?

Accepted Answer

Single-vendor competitive analytics is solved. Placer.ai ships strong retail trade-area + competitive intelligence with built-in dashboards. Esri Business Analyst ships strong trade-area + demographic + retail-saturation analytics. RetailNext, SiteZeus, Tango Analytics, Buxton, and AGS (Applied Geographic Solutions) ship strong site-selection + competitive-density platforms. The compound case the local-context agent has to handle is the one where a multi-location operator runs 50-1,500 locations across 200+ trade areas, licenses two-to-four overlapping competitive-intelligence sources (because no single source covers every long-tail competitor reliably — Placer.ai may have strong panel coverage in urban metros but thin coverage in rural markets; SafeGraph may cover certain POI categories better than others; Yelp + Google Reviews capture different review populations; Foursquare strong in some verticals and not others), runs a commercial real-estate team using CoStar + LoopNet + Reonomy alongside the marketing-ops team for site-selection decisions, faces antitrust exposure when competitive density outputs inform market-allocation or price-fixing-adjacent decisions (the FTC + DOJ have signaled increased scrutiny of multi-location-operator + multi-unit-franchise antitrust behavior in the past several years), faces FTC Franchise Rule + FDD Item 12 territory exposure when competitive density informs franchisee territory grants + encroachment decisions (the FTC Franchise Rule + state franchise-relationship laws are clear that the franchisor cannot weaponize competitive analytics against existing franchisees in ways that violate Item 12), and has SEC Reg S-K + SOX exposure when outputs surface in investor communications + financial reporting. Without an orchestration layer above the POI + foot-traffic + commercial-real-estate + reviews + demographic + geospatial vendors, the cross-vendor density-scoring reconciliation lives in spreadsheets, the trade-area saturation calculations diverge between teams, the per-whitespace opportunity surfacing happens without substantiation pointers, the antitrust + FTC Franchise Rule + SEC exposure compounds, and the compliance evidence for any outward-facing competitive claim fragments across vendor portals. The orchestration above the vendors is what holds the cross-source + cross-vertical + cross-team + cross-jurisdiction invariants.

Question 3

How does Skill 2 Saturate work, and how does the operator-data-science-team choose between Hotelling, Huff, Reilly, Christaller, and gravity-model coefficients?

Accepted Answer

Trade-area saturation modeling is a long-standing field of spatial economics with several canonical models, each fitting different assumptions. Hotelling (1929) models symmetric duopoly competition along a linear market with quadratic transportation costs — suitable when the operator wants to model two-competitor head-to-head trade-area allocation under simplifying assumptions. Huff (1963) models probabilistic catchment based on store attractiveness divided by distance raised to a beta-parameter — suitable when the operator has parameterized customer choice and wants to allocate trade-area probabilistically across multiple competitors. Reilly’s Law (1931) of retail gravitation extends to multi-store cases with population-weighted attraction — suitable for older retail-gravity analysis where catchment correlates with city population and inter-city distance. Converse (1949) extends Reilly with a breaking-point formula — suitable for two-city catchment-boundary calculations. Christaller (1933) central-place theory models hierarchical settlement and retail-hierarchy patterns — suitable for understanding where retail centers cluster in a regional hierarchy. Lösch (1940) extends Christaller with a more flexible market-area geometry — suitable for non-uniform population densities. Gravity-model coefficient with parameterized distance-decay and attractiveness functions is the modern generic case — operator-data-science-team chooses the distance-decay exponent and the attractiveness function from operator-trained calibration against operator POS-data ground truth. The orchestration layer offers all of these as operator-data-science-team-selectable methods + per-method confidence interval + per-method assumption-violation flagging (e.g., Hotelling assumes symmetric competition and is flagged for asymmetric cases). Per-method outputs route through the gate as candidates with the same compliance gating — the substantiation pointer references which spatial-economics method was applied and which calibration data backed it.

Question 4

How does Skill 3 Surface handle whitespace opportunity surfacing with substantiation pointers and counterfactual validation?

Accepted Answer

Whitespace surfacing emits recommendations only when the recommendation can be substantiated. Per-whitespace per-trade-area-recommendation (expand, contract, shift, add coverage) carries a substantiation pointer to the operator-counsel-approved evidence — typically: which competitor + which category + which trade-area + which density-scoring + which gravity-model coefficient + which calibration data backed the recommendation. Per-whitespace per-category-recommendation (add, expand, contract, shift, specialize, cross-sell, up-sell) carries the same substantiation evidence chain. Per-whitespace expected outcome — instead of stating a numeric ROI or payback period as a claim (which would create FTC substantiation exposure if surfaced externally), the orchestration emits an internal-only expected-outcome estimate with explicit operator-data-science-team-set confidence interval, operator-counsel-set caveats about model assumptions + data limitations + external dependencies, and an explicit "for-operator-internal-use-only-unless-operator-counsel-approves-external-surfacing" flag. Per-whitespace counterfactual validation runs against the operator-finance-team-approved holdout-control infrastructure (the operator marketing-mix-modeling sibling skill on the measurement-attribution-engine agent maintains the holdout-control framework). When a whitespace recommendation is acted on by the operator (the operator expands a trade-area, adds a service line, shifts a category), the orchestration tracks the realized outcome against the predicted outcome at operator-data-science-team-set checkpoints (90-day, 180-day, 360-day) and feeds the calibration error back into model recalibration. Surface decisions log to the WORM audit trail with substantiation_evidence_pointer + counterfactual_validation_state + recalibration_metadata + per-statute retention metadata so operator counsel can audit any externally-surfaced claim.

Question 5

What compliance does the per-event gate enforce, and how does it map to FTC + Lanham + UDAP, Antitrust (Sherman + Clayton + state), FTC Franchise Rule + FDD Item 12, per-vendor data-source terms-of-service, and SEC Reg S-K + SOX?

Accepted Answer

Five anchors. Anchor 1: FTC Section 5 + Lanham Act false advertising (15 USC 1125) + state Unfair Deceptive Acts and Practices (UDAP). When competitive density outputs surface as comparative claims ("we have more locations in Denver than [Competitor X]", "we have higher review velocity than [Competitor Y] in trade area Z"), FTC substantiation applies + Lanham Act false advertising standard applies + state UDAP applies. The gate refuses to commit a comparative claim to externally-surfacing destinations without operator-counsel-approved substantiation pointer attached. The Surface skill emits internal-use-only recommendations by default; externally-surfacing requires explicit operator-counsel approval flag with substantiation evidence chain logged. Anchor 2: Antitrust law (Sherman Act Sections 1 + 2 + Clayton Act Sections 3 + 7 + Hart-Scott-Rodino + state antitrust statutes). Multi-location operators using competitive density mapping for market-allocation (carving up territories among competitors), price-fixing-adjacent decisions (using competitor pricing density to set own price ceiling/floor in concert), tying arrangements, or exclusive-dealing exposure face antitrust scrutiny. The orchestration layer composes with the operator counsel-maintained antitrust use-case allowlist — operator counsel defines which use cases are permitted (internal site-selection, internal trade-area-saturation analysis, internal whitespace surfacing) and which are prohibited (any use that smells like horizontal-market-allocation, any joint-pricing decision based on competitor density). The gate refuses to commit Surface outputs to any consumer of competitor density that operator counsel has not pre-approved. Anchor 3: FTC Franchise Rule (16 CFR Part 436) + FDD Item 12 territory + FDD Item 19 Financial Performance Representations + per-state franchise-relationship laws (the 23-state patchwork) + per-state territorial-encroachment laws. When competitive density informs franchisee territory grants, encroachment decisions, transfer approvals, or renewal decisions, FDD Item 12 territory disclosure obligations apply to the franchisor. The gate composes with the per-vertical compliance overlay sibling skill (on the compliance-overlay-manager agent) and refuses to commit Surface outputs to franchisor-side territory-decision workflows without operator-counsel-approved FDD Item 12 substantiation chain. The 23-state franchise-relationship laws govern franchisor obligations around encroachment + non-renewal + termination + transfer; competitive density mapping that informs any of these triggers the per-state franchise-relationship-law compliance check. Anchor 4: Per-vendor data-source terms-of-service compliance. Google Maps Platform Terms restrict use of Maps/Places data to Google-Maps-purposes (the operator counsel typically licenses an enterprise agreement that broadens this; absent enterprise agreement, the gate enforces the standard terms). Google Places API has commercial-use restrictions on POI data extraction at scale. Yelp Fusion API has specific commercial-use terms + redistribution prohibitions. Foursquare Places API has specific terms. SafeGraph + Placer.ai + Esri Business Analyst + Nielsen Spectra + Datafiniti + ListAlpha each have specific licensing terms that govern: (a) which downstream uses are permitted, (b) which third-party redistribution is permitted, (c) which derivative-product publication is permitted, (d) which competitor-comparison disclosure is permitted. The orchestration layer maintains the operator-counsel-approved per-vendor data-source terms-of-service compliance matrix (the same library the buyer-state-aware BANT scoring + multi-source lead ingestion sibling skills use for per-vendor consent provenance, extended here with per-vendor competitive-data-use restrictions). The gate refuses to commit Surface outputs that would violate per-vendor ToS without operator-counsel-approved exception. Per-vendor consent-provenance attestation also applies when any data with PI exposure enters the pipeline (consumer-review data, foot-traffic-derived visit data). Anchor 5: SEC Regulation S-K Item 303 MD&A + Item 506 forward-looking-statement framework + Regulation G non-GAAP financial measures when competitive density outputs surface in investor communications + Sarbanes-Oxley Section 302 CEO/CFO certification + Section 404 internal control attestation when outputs influence financial reporting. Per-location market-share claims + competitive-position narratives + per-whitespace expected-outcome projections that surface in MD&A + earnings calls + investor decks + analyst-day presentations are subject to Reg S-K Item 303 plain-English requirements + Reg G non-GAAP reconciliation (if expressed in non-GAAP terms) + Reg S-K Item 506 forward-looking-statement safe-harbor cautionary language. SOX 302/404 applies when competitive density outputs feed into financial-reporting estimates (impairment indicators on poorly-positioned locations, deferred-revenue allocation across trade areas with different competitive intensity, fair-value measurements that reference competitive context). The gate routes any externally-surfacing competitive density output through the per-vertical compliance overlay sibling skill + refuses to commit without operator-counsel-and-CFO-approved substantiation chain. Broader gate also enforced: NIST AI RMF + ISO 42001 + ISO 27001 + SOC 2 Type II + ADA Title III + WCAG 2.2 AA + EU AI Act Article 12 record-keeping + Article 14 human oversight via policy-as-code (OPA Rego + AWS Cedar + Casbin + Cerbos + Oso). WORM audit trail (AWS S3 Object Lock + GCS retention + Azure Blob immutable + Snowflake Time Travel) with per-statute retention (FTC 7yr + Lanham 4-6yr depending on jurisdiction + SEC 7yr + SOX 7yr + Sherman/Clayton antitrust statute-of-limitations 4yr-civil-8yr-criminal + FDD 7yr after termination + state-AG variable + IRS 7yr + state variable) per operator counsel policy.

Question 6

What does the engagement look like across Tier 1 → Tier 2 → Tier 3, and what does the Tier 3 reporting cycle commit to?

Accepted Answer

Tier 1 AI Readiness Assessment (2-3 weeks, diagnostic): audits the operator current competitive density mapping posture against the 3-skill bundle + 5-anchor compliance gate + per-vendor data-source terms-of-service compliance matrix; deliverable is a gap-pack report identifying which competitive-intelligence vendors lack current ToS compliance review, which competitor taxonomy categories are uncovered, which trade-area definitions are inconsistent, which gravity-model coefficients are mis-calibrated, which antitrust use-case exposures are open, which FDD Item 12 territory decisions are happening without substantiation, which SEC + SOX outputs lack proper substantiation chains, and a recommended remediation sequence for Tier 2. Tier 2 AI Swarm Setup Sprint (4-8 weeks): builds the 3-skill bundle on the local-context agent, wires POI + foot-traffic + commercial-real-estate + reviews + demographic + geospatial + trade-area-modeling vendors (operator-chosen subset), configures operator-counsel-and-data-science-team-approved competitor taxonomy + density-scoring dimensions + trade-area definitions + gravity-model coefficient selection methodology, wires operator-counsel-maintained antitrust use-case allowlist + FDD Item 12 substantiation framework + per-vendor data-source ToS compliance matrix, configures SEC + SOX substantiation chain integration, wires policy-as-code + WORM-storage, runs 30-day shadow + canary period before flipping to enforce-mode. Tier 3 Fractional CMO with AI Swarm (6-month minimum, 1-2 days/wk embedded): continues operating with weekly per-vendor data-feed health checks, monthly cross-vendor density-scoring reconciliation, quarterly gravity-model coefficient recalibration against operator POS-data ground truth, quarterly per-vendor ToS compliance review, quarterly antitrust use-case allowlist review with operator counsel, quarterly FDD Item 12 substantiation framework refresh, quarterly SEC + SOX evidence-package generation. Tier 3 reporting is a 6-workstream pre-engagement-baseline reporting cycle (per-vendor data-feed health + per-competitor-taxonomy coverage trend + cross-vendor density-scoring reconciliation accuracy trend + per-trade-area gravity-model calibration trend + per-whitespace counterfactual-validation completeness + WORM audit-trail completeness) measured against the operator’s pre-engagement baseline. Each workstream surfaces trend direction and the gap to operator-defined targets. Reporting carries explicit caveats: POI + foot-traffic + commercial-real-estate + reviews + demographic vendor SLA + per-vendor panel-methodology changes + per-vendor terms-of-service updates + FTC + state-AG enforcement signals + DOJ antitrust enforcement priorities + FTC Franchise Rule + per-state franchise-relationship-law amendments + SEC Reg S-K + Reg G + Reg FD implementing guidance + SOX guidance updates sit outside Completions control. Attorney-client privilege preservation across operator antitrust use-case allowlist + FDD Item 12 substantiation framework + per-vendor data-source ToS compliance matrix + competitive-claim substantiation library is maintained per operator counsel policy.

Question 7

Who owns the vendor relationships, the competitor taxonomy, the gravity-model coefficient library, and the audit trail?

Accepted Answer

Operator owns every artifact. The POI + foot-traffic + commercial-real-estate + reviews + demographic + geospatial + trade-area-modeling vendor subscriptions (Google Maps Platform + Google Places API + Yelp Fusion + Foursquare Places + SafeGraph + Placer.ai + Esri Business Analyst + Nielsen Spectra + Datafiniti + ListAlpha + CoStar + LoopNet + Reonomy + Crexi + Birdeye + Reputation.com + Esri + Nielsen + Experian + Acxiom + IXI + Claritas + RetailNext + SiteZeus + Tango Analytics + Buxton + AGS — operator chooses subset) all run under operator billing on operator-controlled accounts. The geospatial tooling (PostGIS + ArcGIS + Mapbox + Carto + Kepler.gl + Deck.gl + Uber H3 + Google S2) runs under operator infrastructure. The operator-counsel-and-data-science-team-approved competitor taxonomy + density-scoring dimensions + trade-area definitions + gravity-model coefficient selection methodology live in operator code repo. The operator-counsel-maintained antitrust use-case allowlist + FDD Item 12 substantiation framework + per-vendor data-source terms-of-service compliance matrix live in operator counsel repo. The Score + Saturate + Surface code lives in operator code repo. The WORM audit trail lives on operator-controlled cloud storage (AWS S3 Object Lock + GCS retention + Azure Blob immutable + Snowflake Time Travel). The policy-as-code policies (OPA Rego + AWS Cedar + Casbin + Cerbos + Oso) live in operator code repo, counsel-aligned. The FTC substantiation records + Lanham Act + state UDAP substantiation records + antitrust use-case audit records + FDD Item 12 substantiation chain records + SEC + SOX evidence chain records + per-vendor ToS compliance records are all operator-counsel-maintained. Completions owns the orchestration knowledge — how to design the cross-vendor density-scoring reconciliation for the operator’s actual vendor mix, how to choose between gravity-model coefficients against the operator data-science-team’s domain knowledge, how to compose antitrust use-case allowlist + FDD Item 12 substantiation + per-vendor ToS compliance into a coherent gate, how to design SEC + SOX substantiation chains for externally-surfacing outputs, how to wire counterfactual validation against the operator-finance-team-approved holdout-control infrastructure — and that knowledge transfers under the Tier 3 transition path (30-60 days at engagement end with full hand-off of the competitor taxonomy, the density-scoring code, the gravity-model coefficient library, the whitespace surfacing logic, the substantiation chain wiring, and the compliance evidence-package generation playbook). Completions credentials revoke on engagement-end.

Per-location competitive density mapping for multi-location retail, multi-unit franchise, and multi-location service brand operators — Score + Saturate + Surface 3-skill bundle under a 5-anchor compliance gate anchored on antitrust + FTC Franchise Rule + per-vendor data-source terms-of-service

The real ecosystem this sits above

POI + foot-traffic + mobility data

Commercial real-estate

Reviews + demographic enrichment

Geospatial + trade-area modeling

Spatial statistics + warehouse + reverse ETL

Policy-as-code + WORM storage + legal research

Frequently asked