How Lucien works
Signals → Reasoning → Drafts → Approved actions
Lucien connects to the tools you already use, watches the signals that matter, reasons about what’s happening, and drafts actions for you to approve. This page explains that loop so you know what Lucien can do — and what it will never do without you.
Signals: what Lucien watches
Lucien is only as useful as the signals it can see. That starts with the tools you already use.
Connected tools
- Lucien only sees what you connect. You can start with 1–2 tools and expand easily.
- Typical sources include workspace tools (notes, docs, chat), calendars, email, billing, analytics, support, and task trackers.
- Connected tools generate signals, and signals translate to company context.
Types of signals (examples, not exhaustive)
- Metrics – MRR changes, churn spikes, activation dips, trial activity going stale, SEO conversion.
- Work – stalled initiatives, overdue deliverables, risks blocking a launch, decisions taken, plans made, support tickets.
- Communication – important email threads, customer complaints, exec mentions, meeting notes, Slack discourse.
- Events – calendar events, launches, renewals, key meetings, deadlines, and time‑sensitive commitments.
Lucien treats all of these as inputs into one company‑level high-definition picture.
Reasoning: how Lucien thinks about your company
Reasoning is the step where Lucien turns raw signals into insights, synthesizes company context, deduces signal impact and priority, and decides what action to take.
Proactive
Lucien regularly reviews what's shifted across your connected signals and asks:
- Is this material?
- How impactful is this?
- What’s the best next action? Do I have permission to act on this? How might I measure results?
This lets Lucien operate
Contextual understanding (not just numbers)
Lucien doesn’t stop at "MRR down 1.2%". It ties the change to supporting context — which accounts churned, what tickets or feedback spiked, what initiatives are underway, and what you’ve recently decided.
Every insight aims to answer four questions:
- What changed?
- Why does it matter?
- What should we do next?
- What data supports this?
Guardrails on reasoning
- Explainability by default – outputs are plain language, with supporting context.
- No silent changes – reasoning never edits your tools. It observes and drafts.
Example
Signal – 3 EU customers churned in 7 days, all with recent VAT‑related tickets.
Lucien’s read – "MRR is flat, but churn is up (+1.2%) and concentrated in EU. Likely VAT friction; risk of repeat unless checkout copy and invoicing are clarified."
Next move – "Draft a winback email + propose a small checkout copy update."
Actions
This part is intentionally strict.
What Lucien can do (with explicit approval)
Depending on your connected tools and permissions, Lucien can:
- create tasks in your tracker
- post summaries into specific channels or docs
- send messages you’ve reviewed and approved
What Lucien will never do without approval
Lucien will not:
- contact external customers on your behalf
- change billing settings, delete data, or modify critical infrastructure
- take irreversible actions
Audit trail
Every approved action is attributable: what was approved, when, surrounding context and the results of the executed action.
Data boundaries and control
Lucien is designed for least privilege by default. It only accesses what each integration exposes via scoped permissions, and actions stay tied to explicit approvals.
Key principles:
- No training of foundation models on your company data.
- Scoped integration access via OAuth, where possible; you can revoke any integration at any time.
- Clear separation between "reading signals" and "taking actions".
For the full story, read Security.
Next steps
- New here? Start with Quickstart to see the first‑week experience.
- Evaluating for a team? Read Security next.
- Ready to wire it up? Check Integrations to see what Lucien can connect to.