Search Drive for any prior relationship before cold outreach
Images on this page are for illustrative purposes only. Example outputs in this play are illustrative — the structure, fields, and format reflect real Lusha, Gmail, and Google Drive connector output, but were not pulled from a live session. Run the prompt with your own data and connectors to see live results. Personal details in any live examples are masked or abbreviated for privacy.
Cold outreach to a company with existing history — a failed evaluation, a bad support experience, a colleague’s ongoing relationship — can damage more than it helps. This Claude prompt searches Google Drive and Gmail for any prior history before the first touch, validates the right contact via Lusha, and returns a pre-outreach brief with the recommended approach. Know what happened before, not after.
The prompt
This prompt may contain placeholders — look for [BRACKETS] and fill them in.
<context>
Before I reach out to a company for the first time, I want to check whether our company has any prior history with them — a previous evaluation, a failed deal, a support issue, an existing relationship at a different level. I don't want to cold-call a company where we already have context that should shape how I approach them.
My target:
- Company I'm about to contact: [COMPANY NAME OR DOMAIN]
- Contact I'm planning to reach: [NAME AND TITLE — or "find via Lusha"]
- What I sell: [PRODUCT / SOLUTION]
- Why I'm reaching out now: [SIGNAL / REASON / OR "FIND ONE FROM LUSHA"]
</context>
<task>
1. Search Google Drive for any internal documents that mention this company:
- Previous proposals, evaluations, or pricing documents
- Meeting notes or call notes
- Any deck or presentation created for this company
- Any internal notes or strategy documents that reference the company
- Note the document name, approximate date, and what it contains
2. Search Gmail for any prior email history with this company's domain:
- Any prior outreach — sent or received
- Any prior conversation — what was discussed, outcome
- Whether any prior contact replied or engaged
- Whether any deal was created and what happened to it
3. Use Lusha to validate and find the right contact:
- Confirm the planned contact is still at the company in the same role
- Check for any account signal in the last 30 days
4. Build a pre-outreach intelligence brief:
PRIOR RELATIONSHIP: what Drive and Gmail found — summarized
KEY CONTEXT: anything that should change how the outreach is framed
CONTACTS TO AVOID: any prior contact who had a negative experience or is no longer at the company
BEST ENTRY POINT: based on history, who is the right first contact and what angle works
RECOMMENDED APPROACH: reference existing history / fresh start / use internal connection
5. Draft the opening line of the outreach — adjusted for what was found:
- If prior history: acknowledge it — don't pretend it didn't happen
- If clean slate: use the Lusha signal or ICP fit as the angle
- One sentence only — the opening line, not the full email
</task>
<constraints>
- If Drive or Gmail surfaces a negative prior experience: flag it prominently.
- If a prior deal was lost to a specific competitor: note it — that shapes the positioning.
- If an existing internal relationship exists: surface it — the rep may be able to use a warm intro instead.
- The recommended approach must be specific: not "reach out carefully" but exactly what to reference and how.
</constraints>What you'll get back
The situation: A new SDR is about to cold-call Briarwood SaaS. The company looks like a clean prospect. Running the check before the first outreach.
PRIOR RELATIONSHIP
⚠ Drive found: “Briarwood SaaS — Discovery Notes Q3 2024” — a doc from 19 months ago. A previous AE ran two discovery calls, created a proposal, and the deal was closed-lost. Notes indicate the deal was lost to a competitor on pricing. The prospect at the time was R.F., VP of Operations — who is no longer at Briarwood per Lusha.
Gmail found: 6 emails between the previous AE and R.F. between August–October 2024. Last email from R.F.: “We’ve decided to go in a different direction this time — happy to revisit in the future.” No further contact since.
KEY CONTEXT
Briarwood evaluated the product 19 months ago and chose a competitor on pricing. R.F. (the prior contact) has left the company. The current VP of Sales — P.O. — joined 8 months ago and has no prior relationship with the product. This is a fresh start with a new decision-maker, but the pricing objection history is worth knowing before the first call.
Account signal: Briarwood headcount up 24% in the last 60 days — active hiring in the sales function. Strong timing signal.
CONTACTS TO AVOID
R.F. (VP Operations) — no longer at Briarwood. Do not reach out to that email address.
BEST ENTRY POINT
P.O., VP of Sales — joined 8 months after the previous evaluation. No prior relationship with the product. The pricing objection from 2024 is not an active barrier for a new VP who wasn’t involved in that decision.
Contact: p.o@[briarwood].com ✓ verified · direct mobile available
RECOMMENDED APPROACH
Fresh start — don’t reference the prior evaluation unless the prospect brings it up. P.O. wasn’t involved in the 2024 decision and has no reason to carry that history forward. Lead with the hiring signal: “Your sales headcount is growing fast — SDR data quality is the first thing that breaks at this scale.” If pricing comes up on the call, acknowledge the prior evaluation directly rather than avoiding it.
Opening line: “Hi P.O. — I saw your sales team is growing fast at Briarwood. Data quality for the SDR layer is the first thing that breaks at 24% headcount growth — wanted to check whether it’s on your radar.”
Illustrative example — fictional company names used. Run with your own data to see live results.
Why use Lusha in Claude
The 2024 evaluation is the finding that changes everything about this outreach. Without the Drive and Gmail check, the SDR calls P.O. cold with no context. With it, the SDR knows: the deal was already evaluated 19 months ago, the objection was pricing, the prior contact has left, and the current VP has no history with the product. That’s not a reason not to call — it’s a reason to call differently. The opening line leads with the hiring signal rather than the product, and the rep is prepared if pricing comes up rather than blindsided. A 2-minute check before the first touch is worth significantly more than discovering the prior evaluation mid-call.
Data drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.
FAQ
What if Drive and Gmail find nothing at all?
Clean slate — no prior history. The brief returns “no prior relationship found” and the outreach angle defaults to the Lusha signal or ICP fit. A clean result is just as useful as a finding — it confirms the company hasn’t been approached before and the rep can proceed with a genuine first touch.
What if an existing colleague is already in a relationship with this account?
The Gmail search will surface prior threads from anyone in the team. If a colleague has an active relationship, the brief flags it as an internal connection — the rep can request a warm intro rather than going in cold. This is the most valuable finding the play can return: a cold call that could have been a warm intro.
What if the prior evaluation was very recent — 3 months ago?
The brief flags the recency prominently. A company that evaluated the product 3 months ago and chose a competitor is not a fresh cold prospect. The recommended approach shifts to re-engagement rather than cold outreach — acknowledging the prior evaluation and providing a specific reason the conversation is worth revisiting now.
Does this work for enterprise accounts with complex org structures?
Yes — Drive searches all accessible docs and Gmail searches all accessible threads. For large enterprise accounts with multiple prior contacts across different functions, the brief surfaces all contacts and flags which are still at the company. The “contacts to avoid” section becomes particularly useful for accounts with a complicated history.
How is this different from the research prospect before outbound prompt?
The research prospect before outbound prompt builds a prospect brief from Lusha data and public signals — answering who the prospect is and what’s happening at the account. This play answers “what history do we have with them” — it looks inward at Drive and Gmail rather than outward at the account. Run this one first to check internal history, then the research prompt for external context.
Ready to build this?
Get started with Lusha and set up this play in minutes.
