This is Lumo. Drag to look around, or give it a proper fling.

    Lumenbase Motion Orchestrator

    Meet Lumo

    Lumo is short for Lumenbase Motion Orchestrator: the part of Lumenbase that keeps your pipeline moving, with you making the calls.

    Lumo combines relevant information from the workspace sources available to you, including records, captured conversations, meetings, and learned context. It watches for the moments that need a person, suggests next steps, and writes drafts in your voice. Drafts wait for your approval unless you enable automatic sending.

    How it works

    How a card gets made

    Five stages, in order. The first three are mostly rules, so Lumo can explain every card it raises.

    1. 01

      Something happens

      20 watchers run on the clock and on events: a reply lands, a deal goes quiet, an invoice slips, a follow-up comes due. Each one raises a signal with its reason attached.

      Quiet deal: Velora Systems has been silent for 21 days on a deal marked to close this month.

    2. 02

      Is now the moment?

      Of everything due, Lumo picks who goes out now. Hard rules first: only contacts on a list with an active Routine, never someone you muted. Then a ranking tuned to each contact's own reply rhythm.

      Sofia answers on Tuesday mornings, so her follow-up waits until Tuesday.

    3. 03

      The reason first, then the words

      Before writing a word, Lumo builds a brief: where the relationship stands, which attempt this is, a fresh angle, the right channel. Then one pass writes the draft and a second polishes it into your voice.

      Third attempt, new angle: pick up Tuesday's meeting notes, four lines, email because she never answers on LinkedIn.

    4. 04

      Nothing sends itself

      The draft lands in your Feed with its reason, its evidence, and a confidence tier. Approve, edit, snooze, or dismiss. Select several and act on them together.

      High confidence: clean guardrail pass, grounded in last week's thread.

    5. 05

      Extracted, saved, applied

      What you approve, edit, and dismiss feeds the next loop: your voice, which angles get replies, when each contact answers, and what to stop suggesting.

      You cut the sign-off twice. The style memo now reads: no sign-off on LinkedIn.

    Always on

    What Lumo watches for

    Every card starts here. The watcher that raises a signal also writes its reason, and that reason is never rewritten.

    • On a schedule

      Follow-up due

      A contact on a Routine passes the next touch date.

    • Instant

      They wrote back

      A reply lands by email, LinkedIn, or WhatsApp.

    • Instant

      Wrote from a new address

      Someone you know emails from an address you do not have, often after a job change.

    • On a schedule

      Thread went quiet

      A chat goes silent with their last message unanswered.

    • Instant

      Call or meeting logged

      A call or meeting is recorded, so the follow-up can start.

    • Instant

      Email opened

      Someone opens a tracked email for the first time.

    • Opt-in

      Campaign link clicked

      Someone clicks a link in one of your email campaigns for the first time.

    • Opt-in

      Left your campaigns

      Someone unsubscribes from your email campaigns or marks one as spam.

    • On a schedule

      Promise coming due

      Something you said you would do reaches its date.

    • On a schedule

      Quiet deal

      An open deal goes silent.

    • On a schedule

      Account cooling off

      A whole account stops talking to you.

    • On a schedule

      People worth a minute

      A few people a day: a regular conversation that stopped, a new job, a post taking off, a renewal coming up.

    • On a schedule

      Invoice overdue

      A payment passes its due date.

    • Opt-in

      Meeting coming up

      A meeting is about to start. Switch it on per workspace.

    • On a schedule

      Task due

      A task reaches its date.

    • On a schedule

      Connection accepted

      A LinkedIn request you sent is accepted.

    • Instant

      Deal moved

      A deal changes pipeline stage.

    • On a schedule

      Revenue at risk

      Exposure on an account is flagged for review.

    • On a schedule

      Routine milestone

      A milestone is crossed or an objective is met.

    • While reading

      Unhappy reply

      Lumo reads a message as unhappy and softens the next touch.

    Straight from the product

    The Feed, exactly as you will meet it

    The Feed

    A live stream of drafts, approvals, and advice as the work arises. Lumo prepares each card; you decide.

    Worth knowing

    Prioritize advancing late-stage deals and reactivating stalled opportunities across the pipeline this week. Sarah Chen has an open $45k deal in Negotiation, so send a short contract-alignment email today.

    SC
    Sarah Chen
    List: Inbound Leads
    Lead · Nordic Systems
    S
    Write email
    5d

    Send a short follow-up aligning on contract terms and next steps.

    • The reason

      Written by the watcher that raised the card. Never rewritten.

    • The evidence

      The email, meeting, or signal behind the card, one click away.

    • The draft

      Editable in place, in the contact's language.

    • Confidence

      High-confidence cards are marked so you can clear them at a glance. Review cards say why they need a careful look.

    • Dismiss with memory

      Snooze until tomorrow, a week, or a month. Mute a person, or one kind of suggestion. Lumo learns from it.

    • Three tabs

      Feed for the work waiting on you. Knowledge for what Lumo learned about each contact and company. Notices for dated commitments, meetings, and deal events.

    Learning loops

    Lumo learns how you work

    Your voice

    A voice card built from mail you already sent, per channel, plus a style memo from how you edit its drafts. You can see both, and reset them.

    Reply rhythm

    When and where each contact answers decides the channel and the send window.

    Angles that work

    After 5 graded sends, Lumo leans on the angles that got replies and keeps 20% exploring.

    Your dismissals

    Mute a person or a kind of suggestion and it stays muted. Enough wrong calls silence a whole class.

    Knowledge

    Facts from emails, messages, and meetings become a standing profile per contact and company, each with its source and confidence.

    Who decides

    Prepared by Lumo. Sent by you.

    Approval is the default. Autonomy is a dial you set, per kind of work.

    Every draft waits

    Outreach, tasks, deal moves, notes: each lands as a card and waits for you. Deal moves ask even when the dial is on.

    Autonomy dials

    Off, Ask, or Always on for each kind of work. Email goes unattended only when the workspace gate and your own opt-in both agree. LinkedIn always queues to your browser.

    New Routines calibrate

    A new Routine drafts a small sample and holds the rest until you review them and roll it out.

    Seats and gates

    Only full seats get Lumo. Viewers and collaborators have no AI access. Admins can switch the Feed, Chat, and Routine co-create off per workspace.

    Four ways in

    Lumo's tools, wherever you work

    Lumo's read and write tools are open to Claude and any MCP client. Your own code talks to the REST API.

    App UI

    You work in the signed-in web app. Contacts, deals, the Feed, and Lumo share your normal login.

    Claude and ChatGPT

    Claude or ChatGPT connects to your workspace over MCP and runs CRM tools from chat.

    MCP

    Agent frameworks such as OpenClaw and Hermes connect over MCP with a personal token.

    REST API

    Your servers send HTTPS requests with a workspace API key and read or write JSON.

    Same workspace CRM data across all four channels.

    Under the hood

    Everything Lumo ships with

    Built into Lumenbase, not bolted on. Open any card on the features hub to see how it connects to the rest of the workspace.

    Feed

    A live stream of cards, each with a reason, its evidence, and a draft. Approve, edit, snooze, or dismiss; select several and act on them together.

    Approvals

    Outreach, tasks, deal moves, and notes wait as cards until you act. Autonomy dials decide what may run unattended.

    Worth knowing

    Advice that needs no reply: a deal to tidy, a list to build, and yesterday's misses in one quiet digest.

    Lumo Chat

    Ask about any contact, deal, or number. Charts inline, help center answers, web search, files. Writes apply after you confirm. On mobile, talk to it.

    Propose times

    A scheduling message with real open slots from your calendar, inside your working hours, plus your booking link. Email or LinkedIn.

    Content library

    Keep guides, posts, and case studies in one place. Lumo links only real resources when a draft needs one.

    Voice and personality

    Drafts sound like you. Chat can take a personality or mirror your own writing. Each person picks theirs.

    Routines

    A playbook per list: who to work, how often, in what tone, and what counts as done. Co-write it with Lumo.

    Meeting summaries

    Record Meet, Teams, or Zoom from the extension. Transcript, summary, and action items land on the contact's timeline.

    Knowledge and Notices

    What Lumo learned about each contact and company, with sources and confidence, plus the dated record of commitments, meetings, and deal events.

    Lumo steps in Automations

    Ask a question, classify a record, extract fields, enrich it, or decide which branch runs, inside any automation.

    Self-sorting lists

    Lists keep their membership in sync from your instructions, and Leads columns move by per-stage rules.

    Autonomy dials

    Off, Ask, or Always on for each kind of work, with hard caps on runs and credits.

    Claude and MCP

    Lumo's tools work from Claude, OpenClaw, Hermes, or any MCP client with a personal token.

    Questions about Lumo

    Not by default. Every draft waits in the Feed for your approval. Email can run unattended only when a workspace admin sets the email gate to Always on and you opt in yourself. LinkedIn messages always queue to your browser, and you can pause Lumo for yourself at any time.

    Only contacts on a list with an active Routine. Nobody else, however active they look. A new Routine drafts a small sample first and holds the rest until you roll it out.

    Yes. Lumo builds a voice card from mail you already sent and a style memo from how you edit its drafts. Both are visible under My Lumo, and you can reset them. A Routine can also draft in Lumo's own voice instead.

    Lumo answers in your app language: English, Swedish, Ukrainian, or Portuguese. Drafts follow the contact's preferred language.

    Only what its capability gates allow, and only at the autonomy level set for that kind of work. Reads are always on. Writes such as a task, a note, or a deal update follow the dial, and pipeline moves always ask.

    Yes. Add Lumenbase as a custom connector in Claude, or connect OpenClaw, Hermes, or any MCP client with a personal token. Your own systems use the REST API with a workspace key.

    Your plan includes one monthly pool of Lumo credits shared by the team, and each full seat adds to it. Top-ups add one-time credits, and pay as you go, billed per credit, is a switch you control.

    Try the full workspace free for 30 days. No credit card required.