AI Playbooks for Outreach, Not a Generic Chatbot
Lumenbase runs on Routines, playbook definitions that continuously drive Lumo's recommendations in the Feed. The AI follows your process instead of waiting for prompts like a chatbot.
A generic chatbot waits for you to type. It forgets your process between sessions. You re-explain what good follow-up looks like every time.
Lumenbase works off playbooks instead. They're called Routines. You define your process once, and Lumo applies it continuously.
What a Routine is
A Routine is a playbook-style definition. You set the rules for how a kind of contact should be worked. Lumo reads those rules and turns them into action.
Routines live under Lists at `/lists/codexes`. They feed two things:
- The Feed recommendations
- Automations that act on your rules
How playbooks beat a chat box
A chatbot answers one question, then goes quiet. A Routine keeps shaping your priorities. Your follow-up logic stays consistent without re-prompting. You still send via email, LinkedIn, or your outreach platform.
That shows up in the Feed. Lumo gives you a ranked list of who to contact, and the reason comes straight from your Routine.
Where Lists fit
Lists in Lumenbase organize contacts you already have. You segment your existing contacts, then attach a Routine to drive how Lumo works that segment.
Lists don't go find new prospects. They sort and group what's already in your CRM, so your playbooks have a clean set to run on.
What you can encode
A few examples of what a Routine can capture:
You write the playbook. Lumo uses it to build your Feed queue and draft next steps. You send every message and confirm every CRM change.
- Cadence: how often to follow up with this segment
- Triggers: what activity should bump a contact up the list
- Priority: which contacts Lumo surfaces first in the Feed
Who this is for
Revenue operators at $2M to $30M ARR companies who already have a process and want the CRM to run it. People tired of an AI that forgets context every chat.
Frequently asked questions
What's a Routine in Lumenbase?
A playbook definition. You set rules for how a contact segment gets worked, and Lumo applies them.
How is this different from a CRM chatbot?
A chatbot reacts to single prompts. Routines run continuously and drive Lumo's recommendations in the Feed.
Do Lists find new prospects?
No. Lists organize contacts already in your CRM. You segment them, then attach a Routine.
Where do the AI recommendations show up?
In the Feed, as a ranked list of who to contact, with the reason from your Routine.
Was this article helpful?