Build the quarterly account contact change log

<context>
I want to build a contact change log for this quarter — a structured record of every key contact who left our accounts, whether we've found their replacement, and which accounts now have a coverage gap.

My account base:
- Account list: [PASTE COMPANY NAMES — one per line]
- Contact tier to check: [ALL CONTACTS / DECISION MAKERS ONLY / ECONOMIC BUYERS ONLY]
- Quarter: [Q1 / Q2 / Q3 / Q4 YEAR — or "last 90 days"]
- What I want to track: [DEPARTURES ONLY / DEPARTURES + ROLE CHANGES / ALL CHANGES]
</context>

<task>
1. For each account, use Lusha to identify contacts who have left or significantly changed roles in the last 90 days:
   - Cross-reference the account against expected key contacts in the relevant function
   - Flag anyone whose Lusha record no longer shows them at this company
   - Flag anyone whose title has changed significantly — seniority shift or function change

2. For each departed contact, use Lusha to find their replacement:
   - Who now holds the equivalent role at the account?
   - How long have they been in the role?
   - Return verified title, email, and direct phone
   - If no replacement found: flag as structural gap

3. Build a quarterly change log with three categories:

   COVERED: contact left, replacement found and verified
   - Old contact, new contact, replacement tenure, verified details

   GAP: contact left, no replacement found
   - Old contact, account, how long the gap has existed
   - Recommended next action: who at the account is most likely to own the relationship now

   ROLE CHANGED: contact still at the company but significantly different role
   - Old title, new title, whether the change affects their relevance to our relationship
   - Flag if they moved into or out of the buying function

4. Return a summary:
   - Total accounts checked
   - Total contacts who departed this quarter
   - Total COVERED vs GAP
   - Accounts with the longest-running gap — highest priority for outreach
   - One recommended action per GAP account

5. Flag any account with multiple changes in the same quarter — sign of broader org instability, not just normal attrition.
</task>

<constraints>
- Only flag changes Lusha verifies. Don't infer departures from email bounces or LinkedIn activity alone.
- COVERED means the replacement is verified in Lusha — not just assumed from an org chart.
- Role changes only matter when they affect the buying function or decision-making authority. Don't flag every internal promotion.
- The change log is a tool for RevOps and managers — keep it structured and exportable. One row per change.
</constraints>

The situation: A RevOps lead runs the prompt at the end of Q2 across 12 mid-market accounts. Decision makers only. Looking for departures and significant role changes.

Output: 7 departures detected across 6 accounts. 4 COVERED, 3 GAP. 1 account flagged for multiple changes — broader instability signal. One account has a 61-day gap with no replacement.

Q2 Contact Change Log — 12 accounts · 7 changes detected

4 COVERED · 3 GAP · 3 ROLE CHANGED

Run: May 19, 2025. Decision makers, Q2 (last 90 days). Validated via Lusha.

COVERED — replacement found and verified

GAP — no verified replacement found

Cartway Technologies · 61 days · ⚠ Longest-running gap

• Departed: S.V., Head of Procurement
• Context: Cartway was acquired 9 weeks ago. Procurement function under integration review — no equivalent role confirmed in Lusha yet.
• Recommended action: Ask the main account contact (A.K., VP of Operations) directly who now handles vendor approvals. Don’t wait for the role to be posted.

Finova Group · 34 days

• Departed: B.R., CFO
• Context: No replacement confirmed. Interim budget decisions being made at VP level.
• Recommended action: Confirm with the CS owner whether budget sign-off has temporarily moved to the COO or a VP-level owner. Update before the next renewal conversation.

Thornwick Media · 28 days

• Departed: P.N., Director of Procurement
• Context: Promotion out of procurement into a broader ops role — no direct replacement in procurement confirmed.
• Recommended action: P.N. is still at the company in a new role. Reach out directly — they may be the best path to whoever now owns vendor approvals.

ROLE CHANGED — still at company, function or seniority shifted

⚠ Multiple changes — org instability flag

Cartway Technologies — 2 changes this quarter S.V. (Procurement) departed + broader restructuring signals post-acquisition. Two changes in one quarter at an acquired entity is a pattern, not coincidence. Treat this account as structurally unstable until the integration settles.

Summary

All contact changes validated via Lusha connector, May 19. Names masked to initials, emails abbreviated for privacy.