Copilot

Memory gives Lucien a long‑term picture of your company. Copilot is how you interact with that brain in real time.

You can think of Copilot as:

The conversational layer where you ask for help, review drafts, and steer Lucien’s behavior.

Where you use Copilot

Copilot shows up wherever you naturally work:

Lucien app – the main chat interface in the browser.
Slack – via /lucien or @Lucien and drafted replies.
Email / other surfaces – wherever Lucien is allowed to send drafts or summaries.

Regardless of surface, the idea is the same: you talk, Lucien responds, using memory and your tools as context.

What Copilot is (and isn’t)

Copilot is:

A way to ask questions about your company and get grounded answers.
A way to request drafts: emails, briefs, plans, status updates.
A way to approve or reject Actions (the things Lucien wants to do in your tools).
A place to debug Lucien’s reasoning: “Why did you recommend this?”

Copilot is not:

A generic, stateless chatbot.
A separate product from Lucien – it’s just one face of the same Chief of Staff.
A place where Lucien acts on its own without you knowing.

Typical things you ask Copilot for

Here are some prompts founders actually use:

Company understanding
- “Given our current metrics and roadmap, what are the top 3 risks this month?”
- “Summarize what happened in the last 7 days across Stripe, Postgres, and Slack.”
Planning and execution
- “Draft a weekly plan for me, based on our goals in Notion and current pipeline health.”
- “Turn this doc + this Slack thread into a launch checklist with owners and dates.”
Communication
- “Draft an investor update that explains the MRR plateau and what we’re doing about it.”
- “Write a follow‑up to Acme about their renewal in a month; keep it direct and founder‑to‑founder.”
Review and critique
- “Critique our GTM plan and point out missing pieces.”
- “You’ve seen our support backlog – what patterns stand out?”

You don’t have to remember exact commands; normal language is fine.

How Copilot uses Actions

Copilot is also where you turn ideas into Actions.

For example:

You ask: “Identify trials idle more than 3 days and draft follow‑ups.”
Lucien calls into memory + integrations (Postgres, Stripe, analytics, Slack).
It surfaces an Action queue – draft emails/messages/tasks.
You review in Copilot and choose Approve, Edit, or Dismiss.

Nothing happens in your tools until Copilot shows you what’s about to change and you approve it (unless you’ve explicitly enabled more autonomy for specific flows).

Copilot vs. other assistants

Compared to a generic assistant (ChatGPT, Claude, etc.):

Copilot is wired into your company’s data (metrics, docs, Slack, DB) via Lucien’s memory.
It has an opinionated job: keep your company on track, not just answer trivia.
It is tightly coupled to Actions and approvals – the goal is to get real work done, not just generate text.

Compared to “AI in a single tool” (Notion AI, Gmail smart replies):

Copilot sees across tools, not just one document or inbox.
It can reason about a metric change, a Slack thread, and a Notion plan in one go.

How to get the most from Copilot

A few habits go a long way:

Use it for real work, not just experiments – investor updates, renewal plays, weekly plans.
Point it at sources when you ask for help: “Based on our Company OS page and #sales channel…”
Approve or correct drafts instead of rewriting from scratch; Lucien learns your style and preferences over time.
Ask it to explain itself when something feels off – “Walk me through how you got to this recommendation.”

If Memory is Lucien’s long‑term brain, Copilot is the way you have a conversation with that brain and turn it into movement.