Lead list building
Prospect lists get built once, quickly, and then nobody trusts them. This agent works from your written criteria — sector, size, the signals that suggest a need — gathers candidates from the sources you allow, and returns a list where every inclusion carries the evidence behind it. Your reps argue with the criteria rather than with the list.
Step by step
Write the criteria down
The co-build session turns your idea of a good account into explicit rules, including the disqualifiers.
Agree the sources it reads
We set which public and licensed sources the agent may use, and which it may not.
Gather candidates from those sources
The agent collects organisations matching the shape of the criteria, before any scoring happens.
Check against existing records
Candidates already in your systems as customers, open deals or recent rejections are marked so the list does not repeat work.
Score and evidence each one
Every candidate gets a result against each criterion, with the source line that justifies it.
A rep approves the list
The list is reviewed and accepted by a person before any record is created or any outreach begins.
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 modelSales and revenue leads who want prospecting to follow a written definition of a good account rather than each rep's instinct, and who want to see why an account made the list.
Escalation
When it asks a personA rep accepts the list before any record is created or outreach starts
Applications & Rights
Which tools it uses, and what it may do in each
NotionRead only
ZapierRead only
Google DriveReadWrites 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
Sales and revenue leads who want prospecting to follow a written definition of a good account rather than each rep's instinct, and who want to see why an account made the list.
What you’ll need
- A written ICP with disqualifiers
- Agreed sources the agent may read
- Read access to existing customer and deal records
- A rep who accepts each list
What you get
- A scored prospect list with evidence
- A duplicate and existing-customer flag per row
- A record of the criteria used for that run
What it doesn’t do
It researches and scores; it does not buy contact data or read sources you have not approved. Where a criterion cannot be established from an allowed source, the row is marked unknown rather than guessed.
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
Where does the contact data come from?
From the sources you connect and any data provider you already license. ollo does not sell contact data and will not read a source you have not approved. If you need email addresses, they come from your existing provider through the connection we set up.
How do we stop it rebuilding the same list?
It checks candidates against your existing records first and marks anything already known as a customer, an open deal or a recent rejection, so a rerun skips the names it has already seen.
Can each rep have their own criteria?
Yes, within the same agent. Territory and segment variations are configuration, and each version keeps its own approver. What we discourage is criteria that live only in one rep's head.
What if the criteria are wrong?
You will find out quickly, because every row shows why it qualified. Criteria change a lot early on, and changing them is your job rather than a support ticket.