Choose what Lampi can use
Select the inboxes, folders, calendars, files, or workflow sources the routine is allowed to use.
Routines by Lampi
Tell Lampi once what to prepare, where to look, and when to start. When a new email, file, meeting, or schedule calls for it, Lampi prepares the work for review.
What routines are
A Routine is a repeatable AI workflow that turns approved signals into work your team can review.
Instead of asking the same question again and again, you define the work once: which sources Lampi can use, what should start it, what output you expect, and which actions need approval.
Routines are built for recurring finance work: deal screening, diligence intake, IC preparation, portfolio monitoring, market updates, reporting cycles, CRM updates, legal follow-up, and inbox triage.
How it works
Select the inboxes, folders, calendars, files, or workflow sources the routine is allowed to use.
Set the objective, expected output, trigger type, frequency, source context, and approval rules.
When the routine starts, Lampi coordinates the agents needed for research, analysis, modeling, writing, review, or deck preparation.
Outputs come back through Marc or Lampi as concise work products: briefings, summaries, drafts, one-pagers, model updates, action cards, or slide materials.
You stay in control. Edit the output, reply to Marc, or continue the work in the linked Lampi run or chat.
What can start a Routine?
Routines can start from the signals that already drive professional work. Triggered routines are being rolled out progressively, with user-controlled permissions and approval gates.
Turn new asks, CIMs, follow-ups, and revised documents into prepared work.
Run daily briefings, weekly reviews, reporting prep, and market monitoring on time.
Prepare context before ICs, board meetings, management calls, and diligence sessions.
React when CIMs, VDDs, models, legal docs, board packs, KPIs, or templates change.
Connected signals
Approved apps feed repeatable routines.
Approved email, file, meeting, or schedule
Relevant material and history are gathered
The right Lampi agents are staffed
Research, model, draft, or deck work runs
Marc returns the result to your team
Routine examples
A daily Marc briefing with priority deal threads, upcoming meetings, unanswered asks, new files, changed source context, and action cards for the work that needs attention.
Automatically organizes your inbox by labeling new email, identifying what needs action, drafting replies, and helping with scheduling.
Before an investment committee, board meeting, management call, or lender discussion, Lampi collects calendar context, related files, email history, open questions, and recent updates.
When a new CIM, teaser, VDD, model, or management presentation lands in an approved inbox or folder, Lampi prepares a first-pass review with risks, questions, and next diligence steps.
When a thread, file, or pipeline update suggests a company needs review, Lampi drafts a one-pager using source material, public context, and your preferred template.
On a weekly or monthly schedule, Lampi reviews portfolio KPI updates, board materials, management emails, and market signals to flag variance drivers and follow-up questions.
For a selected sector, theme, or watchlist, Lampi refreshes competitor movements, funding news, valuation signals, pricing benchmarks, market maps, and positioning.
Before recurring LP reporting deadlines, Lampi gathers portfolio updates, recent performance commentary, KPI changes, and draft sections or exhibits for the report.
When revised legal documents or diligence materials arrive, Lampi prepares a risk summary, flags key contract points, and suggests follow-up questions.
Easily create your routines and discover a new way to work with AI.
Control, approval, and auditability
Lampi only uses the sources you approve. It can prepare work automatically, but external messages, file changes, calendar changes, and sensitive actions require human approval.
Approved context only: choose which inboxes, folders, calendars, and files each routine can use.
Clear trigger rules: define what can start a routine, what should be ignored, and when the routine should ask first.
Human review: review outputs, drafts, model updates, and deck materials. No external use without approval.
Approval gates: external emails, irreversible actions, file changes, calendar changes, or sensitive workflow actions require approval.
Run history: every routine run keeps a history of outputs, delivery status, and follow-up context inside Lampi.
Pause or edit anytime: adjust the trigger, context, output format, delivery channel, or approval rules as the workflow evolves.
Set the routine once, let Lampi run from approved triggers, and review the finished work through Marc or Lampi.