The problem this solves
New leaders change vendors. In their first quarter they review the stack they inherited, replace what they dislike and bring in what they trust, and they are unusually open to conversations because everything is on the table. A target account that hires a new VP of Marketing is, for ninety days, a different account from the one on the list.
Catching the hire in the week it is announced is what makes the opportunity usable. The announcement names the person and the role; people data confirms the profile; the email finder supplies the address. Written into Pipedrive with the announcement as a note, the new leader appears where the account owner already works, with the reason to reach out attached.
How the mission runs
- Check the accounts for new appointments. Each week the Signals Agent reads news and people data for the companies on list <name>, looking for VP-level and C-level appointments announced in the last seven days.
- Confirm the person and the role. Each appointment is matched to a person profile with the new title and, where known, the start date and previous employer. Internal promotions are included and marked, since a promoted leader also reviews the stack.
- Find and verify the email. The email finder produces a work address at the new employer and verification checks it. Where the leader is too new for an address to exist, the row is kept with a re-check scheduled.
- Add to Pipedrive with the announcement. The new leader is added as a person linked to the organization in Pipedrive, and a note on the organization records the appointment with its source. The batch is reviewed before it is written.
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
New VP-level and C-level leaders at accounts on list <name> added to Pipedrive every week as people with title, verified email and previous employer, plus a note on each organization recording the appointment and its source. A weekly summary lists the appointments found and the ones still awaiting an address.
Make it yours
- Limit to the functions your product serves - marketing and revenue leadership, for example.
- Create a Pipedrive activity for the account owner due two weeks after the leader's start date.
- Deliver to HubSpot or Attio instead, or to a Slack channel for a lighter touch.
- Draft a congratulations note per leader with the personalization playbooks, staged for the account owner to send.
Frequently asked questions
How are appointments detected?
From announcements and from changes in people data - a new person holding a senior title at the company - with the source recorded so the note is verifiable.
What about leaders who joined quietly without an announcement?
People data changes catch many of these; the row marks them as detected from profile change rather than announcement.
When should the first touch go out?
Most teams wait two to four weeks after the start date; the suggested activity date reflects that, and you can change it.
Can it find the leader's previous employer?
Yes. The previous company and role are recorded from the profile, and where the previous employer was a customer of yours the row is highlighted as a warm introduction.
Does it cover promotions from within?
Yes, marked as internal promotions, since a newly promoted leader also reviews the stack.
How long until a new leader's email is findable?
Often a few weeks; the mission re-checks each pending leader on later runs and fills the address when it appears.
Can I be told about departures as well?
Yes. Ask for departures and the mission notes when a leader on your contact list leaves, which is its own reason to reach the successor.