Every serious CRM was built decades ago and never fully rebuilt.

Lumenbase is a new CRM for the AI age that helps you prioritize your day and engage with the right people in your network.

Full-funnel CRM with lists, leads, deals, and accounts; Lumo AI for daily priorities and outreach; automations, lead scoring, forecasting, and integrations with Gmail, Outlook, Slack, LinkedIn, and more.

Try for free · Features · How it works · AI site digest

    Lumenbase

    Tasks

    Core Workflow

    Execute follow-ups and operational work with structured task lists, due dates, and ownership.

    By Sebastian StreiffertPublished Jan 10, 2026Updated May 29, 20267 min read

    What Are Tasks?

    Tasks are the execution layer of Lumenbase. They turn strategy into concrete, assigned next actions: calls, follow-ups, research, prep work, and operational checklists.

    Tasks connect directly to pipeline and relationship work, so follow-through is visible and measurable.

    A pipeline without tasks is intent without execution. Use tasks to make momentum explicit.

    Task Structure

    AttributePurposeBest practice
    OwnerWho is responsibleAlways assign one clear owner
    StatusExecution stateKeep status updated in real time
    Due dateTime boundaryAvoid undated tasks for critical work
    PriorityRelative urgencyReserve high priority for true blockers
    Linked recordContext anchorAttach to company/contact/deal when possible

    How Tasks Are Used in the App

    Daily execution

    • Feeds the Today workflow with actionable follow-ups.
    • Supports overdue and due-today prioritization.
    • Creates a shared execution cadence across reps and managers.

    Automation and repeatability

    • Created manually or via automations from trigger events.
    • Codex/runlist workflows can generate standardized task sequences.
    • Task completion patterns improve operational predictability.

    Task Workflow

    1. Create task with clear title, owner, and due date.
    2. Link it to the relevant company/contact/deal.
    3. Set status as work progresses (pending → in progress → completed).
    4. Log outcome notes when done to preserve context.
    5. Review overdue tasks weekly and re-plan where needed.
    Pair task execution with Codex so recurring workflows stay consistent across team members.

    Quick Reference

    Open Tasks: Sidebar → Tasks
    Runlists view: Tasks → Runlists
    Codexes: Lists → Codexes
    Mark complete: Task row/detail → status update
    Related guide: Knowledge Base → Automations

    Was this article helpful?