Skip to content
Local Lead Legend Docs

What Local Lead Legend Is

Local Lead Legend is a standalone CRM and operating system for Local Lead Legend. It is an internal tool — for us and our clients only (invite-only; no public self-serve SaaS posture). The production app lives at your-domain.example.

Identity

Section titled “Identity”

Local Lead Legend is two things at once:

  1. The agency’s own agentic ops platform — the single place the team and its agents run attribution, analytics, media/ads, sales/coaching, funnels, and telephony.
  2. Custom-fit client portals — the system clients get a curated window into, as part of a done-for-you service and infrastructure.

There are no white-label/self-serve productization plans where a client signs up unattended: client logins are curated portals configured per client, not a self-serve product.

The monorepo (8 apps)

Section titled “The monorepo (8 apps)”

Local Lead Legend is one monorepo that owns the entire stack — maximum consolidation, minimal external dependencies.

App What it is
apps/api FastAPI + SQLAlchemy 2.0 async + Celery/Redis. Owns the Postgres crm schema. This is the API documented here.
apps/web Next.js 15 dashboard (the operator + client UI).
apps/telephony In-house Telnyx engine: SMS, voice, dialer, call intelligence, Retell agents.
apps/attribution Ad → lead → booked → revenue attribution (the hyros schema).
apps/funnels SvelteKit funnels + an Astro site generator.
apps/analytics P&L, unit economics, and month-close (internal-only).
apps/media Ad-creative factory and operator engine (the content schema).
apps/mobile The Local Lead Legend phone app (Expo / React Native).

Core doctrine

Section titled “Core doctrine”
  • Standalone monorepo = the operating system. Local Lead Legend owns the whole stack. The default is to build or port a capability in-house rather than depend on an external system.
  • Duplicate-in, depend-on-nothing-external. The API reads and writes only the crm schema (plus its own apps’ schemas). It never reads another system’s schema at runtime.
  • Multi-tenant discipline. Every feature is scoped to a subaccount via the X-Org-Id header. See Subaccounts & X-Org-Id.
  • GHL one-for-one parity. Where Local Lead Legend has a surface that GoHighLevel also has, it mirrors GHL’s information architecture and interaction model on Local Lead Legend’s own primitives. Where Local Lead Legend exceeds GHL (coaching, attribution, analytics, media) it is additive.

Where to go next

Section titled “Where to go next”