Roadmap · v0.1

From zero to a system that scales.

Phases are deliberately sequential. Nothing builds until the planning phase produces a defensible architecture. No code is written until the stack is chosen. One exception reorders the rest: Phase M — a minimum-viable cutover ships first, so the legacy systems are replaced early and the remaining phases build on a live platform.

PHASE 0

Planning & Architecture

  • Vision and product principles
  • Catalog of past mistakes (anti-patterns to avoid)
  • Core entity model (first draft)
  • Stack evaluation (backend, frontend, realtime, DB)
  • Integration inventory and key-management strategy
  • Security and threat model
  • Reference research (similar systems to learn from)
  • Workflow diagrams for ingestion, sending, multiplayer
  • Schema draft v1 (leads, phones, identity attributes, messages)
PHASE 1

Foundation

  • Stack locked in. Repo scaffolded. Local dev story.
  • Deployment pipeline (clone, configure, run on any server)
  • Passkey-first auth with account recovery
  • RBAC: super_admin + admin, audit logging
  • Theme system, icon-pack abstraction, custom component primitives
  • Health, metrics, structured logs, error reporting
PHASE 2

Data Ingestion

  • File upload pipeline (massive CSVs, streamed, resumable)
  • Parser registry: property-centric vendor exports, contact-centric vendor exports, generic CSV
  • Identity attribute extraction + typed promotion
  • Deduplication strategy with provenance preserved
  • Full source row retention (no lossy ingest)
PHASE 3

Lead Universe

  • Lead schema in production form
  • Phones, addresses, attributes as normalized side tables
  • Indexed search and filter at scale
  • Internal DNC registry
  • DNC.com integration with caching
  • Google geocode + reverse cache
  • AI grading via OpenRouter, model + price tracking
PHASE 4

Campaign Builder

  • Node-based UI for assembling campaigns
  • Templates (SMS + MMS), media via ImageRouter
  • Number assignment + area-code routing
  • Map-based geographic builder
  • Preview + dry-run
PHASE 5

Crusades & Scheduling

  • Grouping campaigns into crusades
  • Scheduling primitives (time windows, throttles, jitter)
  • Multi-account Twilio rotation with per-account caps
  • 10DLC campaign assignment
PHASE 6

SMS Pipeline

  • Sender engine, partitioned time-series send log
  • Conversations as first-class entities (not message-pairs)
  • Inbound webhook handling, STOP / opt-out compliance
  • Per-pair history checks without OR-explosion
  • Retext rules: per-vertical windows, configurable
PHASE M · MILESTONE

Legacy Migration & Cutover

Gates on a minimum-viable cutover — a compliant send path — not the full feature set. Strangler-style and reversible until the final step. See the Minimum-Viable Cutover and Cutover Runbook docs.

  • Backfill: suppression/consent, send-history, numbers + A2P/warmup state
  • Recent-contact suppression seed (don't re-text who legacy texted inside the cooldown window)
  • Shared from-to history dual-write + bidirectional, near-real-time opt-out bridge
  • Sequence: shadow → backfill → shadow-run → canary → ramp → full → sunset
  • Reversible at every step; legacy decommission is the only point of no return
PHASE 7

Live Multiplayer

  • Presence: see who's viewing what, in real time
  • Ephemeral message drops with fade
  • Avatar generation via OpenRouter on first login
  • Realtime grid: files → campaigns → numbers → crusades
PHASE 8

Outbound Integrations

  • GHL webhook out + API
  • Postmark transactional email + recovery flows
  • Internal opt-in / lead-capture forms
  • Operator direct-contact via shared numbers
PHASE 9

Operator Polish

  • Multiple skins + dark/light, switchable per user
  • Swappable icon packs via variable abstraction
  • Card / node / explorer / tabular view parity
  • Motion design pass + accessibility audit (ARIA, focus, contrast)
  • Mobile-friendly responsive pass
PHASE 10

Nurture & Outbound (v2)

  • Sequenced follow-ups beyond the initial message
  • Appointment-setting flows
  • Per-vertical retext policies
  • Step toward a unified GHL-class operator surface
PHASE 11

Open-Source Prep (conditional)

  • License selection
  • Secret-leak audit and config hardening
  • White-label config surface
  • Public docs site
  • Threat-model published