The problem this solves
A job posting is written by the person with the problem, in their own words, and it says exactly what they are trying to fix. 'We need someone to own our outbound data and keep the CRM clean' is a sentence a vendor could never write as well, because it comes from the buyer. Quoting it back - respectfully, accurately - shows the recipient that the email is about their situation and was written by someone who read what they published.
Doing this at scale is a matter of matching contacts to postings and reading each posting carefully enough to find the sentence worth quoting. The Personalization Agent does both, writes two lines per contact - the quoted line and the bridge to your product - and puts the first twenty into Gmail as drafts so they can be read in the client you send from. Twenty is a deliberate number: enough to test the approach on real replies before committing the rest of the list.
How the mission runs
- Match contacts to postings. The Personalization Agent reads list <name>, finds the companies currently hiring a <role>, and pairs each contact with the relevant posting, preferring postings in the contact's own department and recording the posting title, date and link on the row.
- Find the sentence worth quoting. Each posting is read for the line that best states the problem the role exists to solve - a responsibility, a goal, a pain the description names - and the agent extracts it verbatim, short enough to quote in one line, with the surrounding context kept for the reviewer.
- Write the two-line opener. Line one quotes the posting and names where it came from; line two connects that need to what you do in a sentence that could only follow that quote. The agent writes in the voice you describe and avoids any phrasing that would read as scraped.
- Create Gmail drafts for the first 20. The first 20 openers, ordered by fit score if the list has one, are created as Gmail drafts addressed to the contact with a subject line that references the role, ready to be read, adjusted and sent from your own account. The remaining openers are saved on the list.
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
Twenty Gmail drafts, each a two-line opener that quotes the recipient's own job posting and bridges to your product, with the posting linked in the draft for reference, plus the openers for every other matching contact on list <name> saved as a column with the quoted line and the posting link. The summary lists the postings used and any contacts whose company's posting was too generic to quote.
Make it yours
- Extend each opener into a full first touch with a proof point and an ask, still under 90 words.
- Deliver the openers into Lemlist or Instantly as the first line of a sequence instead of Gmail drafts.
- Draft all matching contacts rather than the first 20 once the approach has proved out.
- Quote from the company's careers page or an executive's public statement when no single posting fits.
Frequently asked questions
Is quoting a job posting appropriate?
Postings are public and written to be read; quoting one accurately and briefly, with its source named, is a sign of attention rather than intrusion. The agent never paraphrases the quote in a way that changes its meaning.
What if the posting has closed by the time I send?
The posting date and link are on each draft; the agent can re-check postings before a send and flag any that have closed, and an opener can still reference the recent hiring push.
Who is the best recipient for a posting-based opener?
The manager the role reports to, since they wrote or approved the posting. The list's contact is used as given, and the agent notes where a different person at the company would be a better fit.