[Feature Gap] Map & visualization: Vertical market intelligence overlays and claims-style targeting

[brycejohnson1417]

Feature Gap: Vertical market intelligence overlays and claims-style targeting
Category: Map & visualization
Priority: Medium
Source: Competitive research

What comparable field-sales CRMs do
Comparable field-sales CRMs offer vertical intelligence add-ons that turn external market or claims datasets into map-ready heat maps, scored targets, provider/facility pins, referral relationships, and routeable priority accounts.

What map-app currently has
Partial: map-app has tenant-specific scoring, orders, social signals, and map overlays, but no reusable vertical-data ingestion and spatial intelligence module for external market datasets.

Why this matters
Vertical data can turn the product from CRM visualization into territory strategy. It helps reps prioritize high-value accounts and helps leaders allocate coverage by real demand signals.

Suggested approach
Introduce a vertical intelligence package boundary for curated datasets, scoring rules, heat map layers, target review, export, and route handoff.

Labels

• feature-gap
• competitive-research
• medium-priority
• mapping

Full working requirements

• Vertical intelligence package supports importing/enriching external market datasets with source, freshness, confidence, and licensing metadata.
• Admin can map dataset fields to accounts, territories, target scores, heat layers, provider/facility pins, and relationship/referral edges.
• Users can filter targets by metric, score, geography, specialty/category, date range, and current customer status.
• Insights can be routed, exported, saved to segments, and attached to account/deal records.
• UI labels data limitations and never implies unsupported provider/customer facts.

Acceptance criteria

• An admin can load or configure a vertical intelligence dataset and preview mapped records.
• A rep can view scored targets/heat layer on map and create a route from them.
• Unmatched records go to review rather than disappearing.
• Data freshness/source labels are visible in map and detail.
• Exports obey licensing/permission configuration.

UI completeness contract

• The feature must be fully usable from the running browser UI by the target role; no backend-only, CLI-only, mock-only, or hidden-admin implementation counts.
• Use real tenant-scoped runtime data and persisted configuration. Demo placeholders are allowed only in unauthenticated marketing/docs surfaces, not inside the product workflow.
• Include loading, empty, error, permission-denied, unsaved-change, save-success, and destructive-action confirmation states where relevant.
• Support desktop and mobile layouts for field-rep workflows; manager/admin-heavy tables may be desktop-first but must not break on mobile.
• Respect organization_id scoping, tenant-session authorization, provider-secret boundaries, audit logging, and existing adapter/package patterns.

Validation expectations

• Add deterministic unit/service coverage for business rules, transforms, scoring, permissions, or sync conflict logic introduced by the feature.
• Add integration/API coverage for tenant scoping, unauthorized access, validation errors, and successful persistence.
• Add browser coverage for the primary user flow using real visible controls and persisted state, not implementation internals.
• Run the repo verification baseline plus the targeted checks documented in the PR.

[linear-code]

BRY-100