The problem this solves
The best moment to write to a buyer is while they are researching the problem you solve, and the worst way to use that moment is a generic email that could have arrived any week. Intent data tells you the company is researching <topic> now; the email should show that you know the topic is live for them without claiming to know what they read. The line between relevant and unsettling is thin, and it is a writing problem as much as a data problem.
The Personalization Agent writes first touches that reference the topic rather than the behavior: 'a lot of teams looking at <topic> this quarter run into...' rather than anything that implies surveillance. The lines are short, specific to the topic and the company's situation, and loaded into Apollo as the first step of a sequence that stays paused until you review them. The verified buyer at each company is found in the same pass, so the sequence reaches a person rather than an inbox.
How the mission runs
- Find this week's researchers on the topic. Intent data returns companies with research activity on <topic> in the last seven days, ranked by score and momentum, and the agent keeps those inside your ICP and outside your customer list, recording the score on each row.
- Identify and verify the buyer. People search finds the person who would own a purchase in the topic's category at each company, and the email finder plus verification produce a deliverable address; contacts that fail verification are held back with the status shown.
- Write the topic-referencing first line. For each contact, a first-touch line is written that names the topic and connects it to a specific consequence for a company of their size and stack, in your voice, without implying knowledge of their browsing. The agent avoids any phrasing that would read as tracking.
- Push into a paused Apollo sequence. Contacts are added to an Apollo sequence named <name>, created paused, with the first-touch line as the opening of step one, the intent score and topic as fields, and the remaining steps left for your standard follow-ups or written on request.
The prompt
This is the exact objective the agent receives. Swap the obvious placeholders for your own domain, segment or channel and run it as-is from the console, Slack, or the API.
What comes back
A paused Apollo sequence named <name> containing the verified buyers at ICP-fit companies researching <topic> this week, each with a first-touch line that references the topic and their company's situation, plus the intent score and topic stored as fields. The summary shows how many companies showed intent, how many produced a verified buyer, and lists the contacts held back for failed verification.
Make it yours
- Ask for the full three-step sequence per contact rather than the first line only.
- Run it weekly and add each week's new researchers to the same sequence.
- Deliver to Lemlist or Instantly instead of Apollo.
- Combine with technographics so the line also references the incumbent tool the company runs.
Frequently asked questions
How does the email avoid feeling like surveillance?
It references the topic as a trend for companies like theirs, never their activity. The agent's writing rules exclude phrases such as 'I noticed you were looking at', and the review step lets you check the tone before the sequence starts.
What if the buyer cannot be verified?
The company stays on the list with the contact and status shown, and you can ask for a second contact or a phone number rather than dropping the account.
Can the sequence start automatically once approved?
Starting it is your action in Apollo; the agent creates it paused and never activates a sequence on its own.