Company Record
Primary company identity, domain, LinkedIn entity, and registry attributes aligned in one place.
Platform preview
A realistic static shell for the future product surface.
Milestone one keeps the website decoupled from live auth and app state. This preview shows the intended shell structure with the product surfaces that already matter in the current SPA.
Hierarchy review mode
Manual + assisted
Primary output model
Company-first graph
Activation posture
Operator-triggered
Hierarchy Graph
Ordered contacts grouped by leadership layer, functional cluster, and review confidence.
Workflow Queue
Resolution status, enrichment freshness, and exception state exposed without hiding operational truth.
Activation Controls
Lead, campaign, deal, export, and connector actions stay explicit instead of becoming hidden side effects.
Shell structure
Three workspaces are enough for the product truth.
The public preview mirrors the same workspace model the internal SPA now uses: Operations, Intelligence, and Administration.
Live retained surfaces
Operations
The operating shell keeps company intake and downstream activation together without letting them define the whole product.
Workspace overview with queue health and workload flags
Companies, opportunities, leads, and deals
Campaign creation and campaign edit flows
Queue-readyUser-facing in `services/web`Migration phase 4 target
First migration priority
Intelligence
The intelligence workspace is where the product differentiates: hierarchy review, company context, and company-first decision making.
Hierarchy canvas with company selection and cluster review
Hierarchy detail with reporting edges and manual edits
Account context that stays visible before activation
High-fidelity previewUser-facing in `services/web`Migration phase 3 target
Retained control surfaces
Administration
Administration remains explicit and separate: access, scheduler, usage, health, and retained settings all stay reachable but secondary.
Access control, roles, and registrations
Scheduler, API usage, and system health
Revenue settings only if the product scope keeps it
Secondary in the shellUser-facing in `services/web`Migration phase 5 target
Preview anatomy
The shell preview only shows modules that correspond to real retained surfaces.
No fake product areas, no invented automation promises, and no generic starter-template filler.
Workspace rail
Operations / Intelligence / Administration
Segments and documents stay reachable only by direct route during milestone one.
Company context
Registry, LinkedIn entity, ownership, status
The preview models a company-first record instead of a flat prospect table.
Hierarchy review
Layers, reporting edges, confidence, hidden contacts
The preview includes realistic structure states rather than invented AI-only features.
Activation controls
Lead, campaign, deal, export, connector actions
Actions stay explicit so the preview does not imply silent CRM mutations.
Dependencies
Backend cleanup is tracked explicitly instead of being hidden under frontend polish.
Website launch is decoupled from backend cleanup, but authenticated migration work should respect the blockers below.
DependencyRequired cleanupMigration effect
`automotive_employers` naming mismatchNaming cleanup onlyWebsite launch is not blocked; internal UI should prefer `Companies`.
`sales_crm` couplingProduct-boundary cleanupAuthenticated migration is blocked where reads still imply CRM side effects.
Hierarchy read/write side effectsAPI contract cleanupHierarchy pages should not be migrated into a misleading shell until behavior is explicit.
Legacy permission and collection namesNaming cleanup onlyRetain access logic now, normalize vocabulary at the user-facing layer first.
Migration order
Move by domain slice, not by historical route prefix.
The current SPA remains live until each slice has a destination, blocker list, parity criteria, and cutover condition.
Phase 1: public site productionization, shell preview completion, SPA route stabilization
Phase 2: shared app shell concepts and authenticated Next route groups
Phase 3: Intelligence migration first, starting with hierarchy canvas and hierarchy detail
Phase 4: Operations migration second, covering workspace home, companies, opportunities, leads, deals, campaigns
Phase 5: Administration migration last, covering scheduler, access control, API usage, health, and retained settings
Phase 6: retire redirect-era UX once parity is verified
Website launch acceptance stays separate from authenticated migration acceptance.