Event management
Event management takes the administrative weight off an LP dinner, an annual meeting or a founder roundtable. It segments your contact base by profile and by how the relationship actually sits, drafts the invitation and the follow-ups, and keeps the attendee list current as replies arrive. Your IR lead approves the list and the copy before anything is sent.
Step by step
Define the guest profile
You describe who the event is for. The agent works from that description rather than from a generic list.
Segment the contact base
Contacts are grouped by profile and relationship strength, using the records your team already keeps in Notion.
Draft invitation and follow-ups
An invitation is written per segment, along with the reminder and the thank-you that follow it.
Track responses as they land
Replies are read and the attendee list is updated, including the maybes that usually get lost.
Prepare the room list
Before the day, the agent assembles who is coming, who they know in the room and what each has previously attended.
IR lead approves before anything sends
The segment list and the copy both go to the IR lead. No invitation, reminder or calendar hold leaves the fund without that approval.
Exactly what this agent can see, touch and change
The same five controls sit behind every ollo agent. These are this one's settings — visible before you build it, not buried in an admin screen afterwards.
Context
What reaches the modelIR and platform teams running LP and founder events without dedicated event staff, where the list, the chasing and the room notes all land on one person.
Escalation
When it asks a personThe IR lead approves the segment list and the copy before any invitation is sent
Applications & Rights
Which tools it uses, and what it may do in each
NotionRead only
GmailReadWrites newCreates new records or documents. Never edits, moves or deletes anything that was already there.
Google CalendarReadWrites newCreates new records or documents. Never edits, moves or deletes anything that was already there.Verification
How you know it’s rightEvery claim links to the document it came from. A statement the agent cannot cite does not make it into the output — which is what makes the result reviewable in minutes rather than re-read end to end.
Who it’s for
IR and platform teams running LP and founder events without dedicated event staff, where the list, the chasing and the room notes all land on one person.
What you’ll need
- Contact records connected
- Guest profile agreed
- Invitation tone and template supplied
- IR lead named as approver
What you get
- A segmented invitation list
- Drafted invitations and follow-ups
- A live attendee and response list
What it doesn’t do
It drafts invitations and keeps the list current. It does not book venues, commit spend, sign with a supplier, or contact anyone who is not on the approved list.
We build the first one with you
Not a template you configure alone. We sit with your team, build it on real data, and hand over the controls.
Scope
One session with the people who actually do the work. We agree what the agent reads, what it may write, and who approves.
Co-build
Built on your own data, not a sandbox. You watch it being made, so you know why it behaves the way it does.
Handover
You own the controls. Change the context, tighten the rights, move the approval gate — without coming back to us.
Parts of the work currently spread across the categories below. It does not replace any of those products outright.
Frequently asked
Will it email a contact we have not cleared?
No. It only drafts to the segments in the approved list, and even those drafts wait for the IR lead. If a contact is not in the approved segment, the agent cannot reach them.
How does it judge relationship strength?
From the fields your team already maintains: how the contact was introduced, the meetings recorded, prior attendance. It uses your records rather than inventing a score of its own, and it shows the reason behind each segment.
What about people who reply with a maybe?
They stay visible as maybes with the date of their reply, and the follow-up drafted for them is different from the one drafted for a firm no. Losing the maybes is the most common way an attendee count goes wrong.
Can we reuse the setup for the next event?
Yes. The segments, the tone and the follow-up sequence live in the agent's controls, which your team owns after handover. The next roundtable starts from the last one rather than from scratch.