The Lumenbase Model
How contacts flow from sources through Lists, Leads, Deals, and Accounts, with Codex playbooks and Lumo on top.
By Sebastian StreiffertPublished Jan 10, 2026Updated May 29, 20268 min read
What Is the Lumenbase Model?
The Lumenbase Model is how your workspace organizes relationships and revenue work from first touch through long-term customer growth. People enter as Contacts, get grouped into Lists, progress through Leads and Deals, and become Accounts when you win. Codex playbooks and Lumo sit alongside that flow so every stage has strategy and prioritized next steps.
You will see this model on the marketing home page, in Getting Started onboarding, and throughout the Help Center as the mental map for where records live and how work should move forward.
The Flow at a Glance
Data flows in from external sources, moves left to right through entity types, and is enriched by Codex and Lumo on the way:
Sources
Codex
Strategy per cohort: tone, sequence, qualification, signals.
Lumo
CRM data plus Codex context: recommendations, Feed, and Chat.
Sources: How Records Enter
Contacts are created and kept current from multiple channels. You do not need all of them on day one. Add integrations as your team needs them.
- LinkedIn: extension capture, Monitor, and message sync. See LinkedIn Integration and LinkedIn Monitor.
- Email: Gmail or Microsoft 365 sync for threads and calendar. See Email Integration.
- WhatsApp: link your number to sync WhatsApp chats with contacts. See WhatsApp Integration.
- Meeting recording: transcripts and summaries from Google Meet, Teams, and Zoom via the browser extension. See Meeting Recording.
- Import & Sync: CSV/Excel uploads, CRM migrations, and outreach/enrichment tool sync (Apollo, Reply, Snov, Zapier). See Data Import.
Pipeline Stages
Contacts
The person record: name, role, company link, engagement history, and custom fields. Everything else in the model references contacts. Contacts guide · Companies guide
Lists (step 1)
Segment contacts by campaign, region, event, or initiative. Lists are where you attach Codex playbooks and optional Lumo auto-classification so membership stays aligned with your strategy. Lists guide
Leads (step 2)
Company-level qualification and nurture: typically after a list cohort is ready for active pursuit. Kanban stages, LumenScore, and optional Lumo kanban auto-move live here. Leads guide · Lead Scouting (pre-list targeting)
Deals (step 3)
Opportunities with value, stage, and forecast impact. When a lead is ready for a formal sales process, create or convert to a deal. Deals guide · Forecasting
Accounts (step 4)
Won customers: health, renewals, expansion, and Company Bands. Deals closed won promote the company into account management. Accounts guide · Company Bands
Codex and Lumo
Codex
A Codex is a structured playbook applied to one or more Lists: who to target, how to message, what counts as success, and whether LinkedIn activity monitoring is on. Without Codex on a list, Lumo still sees CRM data but lacks segment-specific strategy. Codex guide
Lumo
Lumo reads workspace data plus Codex context to power the Feed, contact recommendations, Chat, list classification, lead column moves, and more. For inputs, outputs, and settings, see the dedicated Lumo overview in the Help Center.
Model vs. Customer Lifecycle Funnel
These two frameworks complement each other:
- Lumenbase Model: entity types and how contacts move through Lists → Leads → Deals → Accounts, plus Codex and Lumo.
- Customer Lifecycle Funnel: operational phases (Lead Scouting, Leads, Deals, Accounts) with dedicated workspaces and metrics. Funnel guide
Lead Scouting tracks early-stage contacts already in the workspace (confidence bands, focus areas). Lists organize those contacts into cohorts and attach Codex playbooks. They do not run prospecting or outreach. Add contacts via import, email sync, or the LinkedIn extension; run sequences in Reply, Snov, Apollo, or similar; use Communication for 1:1 email and LinkedIn.
Where to Start
Quick Reference
Lumenbase 101 · Step 2 of 8
Was this article helpful?
