Running a pilot with the Business School at
Pecan is an agentic system that sits on top of your CRM. It turns one event invite list into hundreds of individually personalised messages, sends them, and tracks who actually turns up.
Most event outreach goes out as one message to a whole list. It is quick, but generic, and generic invites get ignored.
Pecan does the opposite. Its AI writes a different invite for every person on your list, grounded in what you already know about them, then sends and tracks the lot. Built for events in regulated industries, where every message has to be considered.
Point Pecan at an event and it writes outreach for the whole invite list at once. Each message is shaped by who the person is, what they care about, and why this event is worth their evening.
Pecan reads the connections around your invite list, drawing on your own records and wider signals, and works that into the invite. Knowing a friend or old colleague will be in the room is often the reason someone says yes.
Send every invite from one place, through your own email. Pecan follows each one through, tracks opens and replies, and gives you a clear report once the event is done.
Pecan is a small team of agents. The Drafter does the writing, and the others exist to make every draft sharper before it reaches a real person.
Pulls together what is known about each invitee, and maps who is connected to whom.
Steps into the shoes of the person being invited and asks whether this message would actually get them to come. Sends notes back.
Takes everything the Scouter and Critiquer provide and writes the message, revising on each round of notes until it is ready.
Pecan plugs into the tools you already run on. No migration, no new database to keep up to date.
If you run events in a regulated industry, we would like to hear about your next one.
Talk to usA mass email sends one message to everyone. Pecan writes a different invite for every person on the list, built around what you know about them and who they are connected to. The reasons to attend are theirs, not generic, and that is what gets a reply.
Before an invite is finished, the Critiquer steps into the shoes of the person it is addressed to. Using what is known about them, it judges whether the message would genuinely make them want to come, and sends notes back to the Drafter. The draft is revised until it holds up. It is a quick back and forth that makes each invite sharper.
Pecan pieces connections together from a mix of internal and external sources, including your own records and wider public signals. It uses this to see who knows whom across your invite list, so an invite can mention a familiar face who is already attending.
No. Pecan is built for events teams, not engineers. You connect your CRM, point it at an event, review what its AI drafts, and send. Everything happens through a simple interface.
Pecan is built for teams running events in regulated industries, where outreach has to be considered and every message holds up to scrutiny. We are currently running a pilot with the Business School at Imperial College London.