Architecture · one-page view
LeadStack — what's in the box Eight product domains drawn as tube lines. Every line passes through Contact and is gated by Sub-Account — the central interchanges. Dashed bridges show how leads flow between domains: capture or AI conversations land as a Contact; the operator (or automation) reaches out via Comms; deals progress through the Sales line.
LeadStack architecture — eight product domains, one platform Tube-map view of LeadStack’s product surface. Eight horizontal coloured lines, each one product domain: Platform (slate, top), Capture (blue), AI Agents (purple), CRM (red, the central trunk), Sales (amber), Comms (green), Automation (pink), Public API (cyan, bottom). Stations along each line are labelled rounded rectangles for the features in that domain. Contact in the CRM line and Sub-Account in the Platform line have thicker borders to mark them as central interchanges — every line conceptually passes through them. Four dashed bridges show the lead lifecycle flow: Capture and AI Agents feed into Contact; Contact feeds into Comms and Sales. A legend strip at the bottom maps each colour to its domain name. LeadStack — eight lines, one platform Eight product domains. One sub-account. Everything an agency CRM needs. Agency Sub-Account Members Roles Territories Gates Billing Forms Web Chat Booking Submission Attribution Persona Web Chat Bot SMS Bot Voice Bot KB (KB scrape) Notes Activity Task Event Contact Deal Pipeline Product Quote Public /q/ Accept Invoice Paid Email SMS Templates Broadcasts Opt-out Trigger Recipe QStash Send History Keys REST Webhooks Replay Recipes Docs interchange interchange Lines: Platform Capture AI Agents CRM Sales Comms Automation Public API Bold-bordered stations are interchanges where every line passes through. Dashed lines show how leads flow between domains: Capture/AI -> Contact; Contact -> Comms; Deal -> Sales.