Wireframes — Data engine (W13–W19)

Visuals: wireframes-data-engine.html · Slide deck

Low-fidelity layout wireframes: structure, hierarchy, and component placement — not visual design. Surface ownership: W1, W2, W6–W11, W14–W16 are Phoenix LiveView; W3, W4, and W13 (map canvas) are React islands; W5 and W12 are React Native / mobile web.

W13 — Segment builder (prospect data engine)

Criteria rail (location, storm swath, property characteristics, exclusions), map canvas with drawn polygon and swath overlay, and a live results panel: matched count, contact coverage, estimated enrichment cost before spending it, and activation targets. DNC and opt-outs apply at send time, not list-build time. React island (map canvas) over PostGIS queries.

Visual: wireframes-data-engine.html

W14 — Data acquisition & pipeline health

The operator's view of every source: last pull, record counts, monthly cost, and failures, with hygiene stats below. Event-driven storm ingestion surfaces a "build segment" prompt within days of a swath. Phoenix LiveView over the acquisition OTP app.

Visual: wireframes-data-engine.html

W15 — Campaigns & attribution (with CRM valve)

Closed-loop attribution: every campaign traced from spend through leads, appointments, signed jobs, and collected revenue to ROI, with per-campaign tracking numbers and UTM/QR closing the offline loop. The CRM valve panel shows engaged prospects promoted (with attribution attached) to the built-in CRM or JobNimbus, while unengaged records stay out.

Visual: wireframes-data-engine.html

W16 — Prospect record with lineage & compliance

Makes ownership and purge rights operational: every field shows its asserting source and date; contact/consent state per channel is checked at send time; the governance panel counts owned vs. provider fields and exposes "purge broker fields" as a real action tied to the field-level lineage on the event log.

Visual: wireframes-data-engine.html

W17 — Canvassing mobile view

Turf map with door-status pins, knock list ordered by proximity, and one-tap outcome logging with voice notes. Knock outcomes are engagement events: "Interested" trips the CRM valve exactly like a form fill. React Native, offline-capable like W5.

Visual: wireframes-data-engine.html

W18 — Partner lead-routing console

Routing rules, the qualified-overflow queue with partner matching and homeowner-consent status, and partner capacity cards. Ships behind a feature flag in log-only mode until the legal review (referral vs. sale, data-broker registration, provider resale restrictions) clears; the lineage check blocks hand-off of records carrying resale-restricted broker fields.

Visual: wireframes-data-engine.html

W19 — Contact 360 (detailed prospective-client view with behavioral heatmap)

The deep single-contact workspace: property and locally-generated personality profile, per-channel consent, and the Hotjar-style behavioral panel — click/move/scroll heatmap rendered over the visitor's most-viewed page, scroll-depth gauge, session history, engagement timeline, and next-best actions. All web behavior is consent-gated and identity-stitched (PostHog self-hosted + RudderStack — see stack 3.4). Lead score blends property fit, storm exposure, and behavioral intent.

Visual: wireframes-data-engine.html