Warm-path introductions
You know someone who knows the person you need. Working out who, and how well, is the slow part. This agent searches your own email and meeting history for people with a live connection to a target organisation, ranks the paths by how recent and substantial the contact is, and drafts the note asking for the introduction.
Step by step
Start from the target you name
You name the person or organisation you want to reach and why, which shapes how the ask is written.
Search your own history
The agent looks through connected mailboxes and calendars for contact between your team and the target.
Rank the paths by strength
Paths are ordered by how recent, frequent and two-sided the contact has been.
Show the evidence for each
For every path you see the threads and meetings behind it, so you can judge whether the relationship is real.
Draft the introduction request
The agent writes a short forwardable note explaining who you are and what you want, in your own register.
You send it yourself
The draft waits in your mailbox. The agent never contacts a connector or a target on your behalf.
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 modelFounders and executives raising, hiring or selling into a named list of organisations, where a warm path beats a cold approach and the network data sits in colleagues' inboxes.
Escalation
When it asks a personYou send the introduction request yourself; the agent only drafts it
Applications & Rights
Which tools it uses, and what it may do in each
Google CalendarRead only
SlackRead only
GmailReadWrites 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
Founders and executives raising, hiring or selling into a named list of organisations, where a warm path beats a cold approach and the network data sits in colleagues' inboxes.
What you’ll need
- Mailboxes and calendars in scope connected
- Colleague consent to search their history
- An agreed target list
- A person who sends every request
What you get
- A ranked list of possible introduction paths
- The evidence behind each path
- A drafted, forwardable introduction request
What it doesn’t do
It only sees the history you connect, so a strong relationship held on a personal phone is invisible to it. It does not enrich from outside contact databases and it never messages a connector directly.
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
Do colleagues have to share their inbox?
They have to agree to it, and we scope the search to sender and recipient patterns rather than message content wherever that is enough. This is a conversation to have before the co-build session rather than after, because consent shapes what the agent can be.
How does it judge a relationship is real?
By recency, frequency and whether messages go both ways. A thread where your colleague wrote and never heard back ranks below a running exchange. The evidence is always shown, so you are not asked to trust a score on its own.
Does it use LinkedIn connections?
Not directly. It works from your own communications history, which is the better signal anyway: a connection list says you met once, a mail thread says you talked.
Can it handle several targets at once?
Yes. Give it the list and it returns paths per target with the same evidence attached. Most teams run it across a target account list rather than one person at a time.