Find the most relevant case study in Google Drive when a prospect asks for one
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.
A prospect asks for a case study. The rep spends 20 minutes hunting through Drive, picks one that’s close enough, and sends a generic email. This Claude prompt does it differently — Gmail pulls what the prospect actually asked for, Google Drive finds the most relevant match, Lusha confirms the send-to address, and Claude drafts an email that connects the case study to the prospect’s specific situation. One pass, under 5 minutes.
Tools: Claude, Lusha, Gmail, Google Drive
The prompt
This prompt may contain placeholders — look for [BRACKETS] and fill them in.
<context>
A prospect just asked for a case study — in an email, on a call, or in a thread. Before I send anything, I want to find the most relevant one from our Drive library, confirm the contact details are current, and have the follow-up email ready to send — referencing what the prospect specifically asked for, not a generic "here's a case study."
My request:
- Prospect name and company: [NAME, COMPANY]
- What they asked for: [EXACT QUOTE OR PARAPHRASE — e.g. "a case study from a SaaS company similar to ours" or "something showing ROI on SDR ramp time"]
- What I sell: [PRODUCT / SOLUTION]
- Thread to reply to: [GMAIL THREAD SUBJECT OR "CHECK GMAIL FOR MOST RECENT THREAD"]
</context>
<task>
1. Search Gmail for the most recent thread with this prospect to confirm:
- What exactly was asked for — the specific language used
- Any context that narrows the search: company size, industry, use case, persona
- Whether any case study was already promised or mentioned
2. Search Google Drive for the most relevant case study:
- Match by: industry, company size, use case, or persona — whichever criteria the prospect gave
- If multiple matches: return the top 2–3 with a one-line description of why each one fits
- If no exact match: find the closest alternative and flag that it's not an exact match
- Note the doc name, Drive link, and key result or stat from the document
3. Use Lusha to validate the prospect:
- Still at the company in the same role?
- Title changed since the last email?
- Verified email to send to
4. Draft the follow-up email:
- Subject: references the specific ask — not "Case study as promised"
- Opening: one sentence that connects the case study to what the prospect said
- Body: one or two sentences on why this specific case study is relevant to their situation
- Include the Drive link inline — don't attach, link
- Closing: one specific question or next step
- Under 100 words
5. Return:
- The matched case study: doc name, Drive link, key stat or result
- Why it matches the prospect's ask
- Draft email ready to send
- Flag if no exact match was found
</task>
<constraints>
- The email must reference something specific from the Gmail thread. Don't send a generic case study email.
- If Drive returns no matching case study: flag it clearly — don't send an irrelevant doc.
- Under 100 words. Count them.
- Link the doc, don't attach it.
</constraints>What you'll get back
The situation: D.R. at Ashford Platforms asked in a Gmail thread: “Do you have anything showing how companies like ours — mid-market SaaS, around 400 people — used this to cut SDR ramp time?” The rep promised to send something. Running the prompt now.
Gmail thread confirmed
Thread: “RE: Data layer for the SDR ramp — Ashford” D.R.’s exact ask: “something showing how companies like ours — mid-market SaaS, around 400 people — used this to cut SDR ramp time.” Promised in the last reply: “I’ll send you a relevant case study by end of week.”
Drive search result
Best match: Crestline Software Case Study — How a 340-Person SaaS Company Cut SDR Ramp from 8 Weeks to 3 Key stat: SDR ramp time reduced 62% in first quarter. Company profile: 340-person SaaS, RevOps-led deployment, similar use case to Ashford. Drive link: [docs.google.com/…] (returned on live run)
Why it fits: company size matches (340 vs 400), same function (SDR ramp), same deployment model. Not an exact industry match but the use case is identical.
Also worth considering: Dunmore Analytics Case Study — Series B SaaS, SDR data quality at scale. Different size (580 employees) but stronger ROI numbers.
Contact validated (Lusha)
D.R., Head of Sales Strategy and Operations, Ashford Platforms ✓ Verified email: d.r@[ashford].com ✓ · title unchanged
Draft email
To: d.r@[ashford].com Subject: SDR ramp case study — matches your profile
Hi David,
You asked for something showing SDR ramp reduction at a mid-market SaaS company. This is the closest match in our library — Crestline Software, 340 people, cut ramp from 8 weeks to 3 in Q1: [link]
Does the Crestline profile match closely enough, or would you rather see the Dunmore one with stronger ROI numbers?
[Name]
62 words.
Illustrative example — fictional company names used. Run with your own Drive library and prospect data to see live results.
Why use Lusha in Claude
The rep promised to send a case study by end of week. Without this prompt, that means opening Drive, remembering the folder structure, reading three or four docs to find the right one, then writing an email that somehow connects the case study to what D.R. actually said. That takes 20–30 minutes and the email usually ends up generic anyway. Gmail confirms the exact language D.R. used. Drive finds the best match and surfaces the key stat. The email closes an open commitment with a specific reference to the prospect’s words. The closing question — Crestline or Dunmore — advances the conversation rather than just fulfilling a request.
Data drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.
FAQ
What if Drive has no matching case study at all?
The prompt flags it — “no matching case study found in Drive” — and the rep gets a clear output rather than an irrelevant doc sent to a prospect. The rep can then decide whether to send the closest alternative with a caveat, or request that a matching case study be created before the conversation progresses.
How does Drive know which folder to search?
Drive searches the full accessible Drive — all files and folders the user has access to. For large libraries, naming conventions matter: case studies named by company size, industry, or use case (“Mid-Market SaaS — SDR Ramp”) surface more accurately than generic names (“Case Study v3 Final”).
What if multiple case studies match equally well?
The prompt returns the top 2–3 with a one-line description of why each fits. The closing question in the email — “does this match closely enough, or would you prefer the alternative?” — turns the send into a conversation rather than a one-way delivery.
Should the Drive link be public or restricted?
Set the sharing permissions in Drive before running the prompt. The prompt links to the doc as-is — it doesn’t change sharing settings. For external recipients, the doc should be set to “anyone with the link can view” before the email goes out.
How is this different from just searching Drive manually?
The Drive search here is contextualized — it uses what the prospect said in Gmail to narrow the search criteria. A manual Drive search starts from scratch. The prompt starts from the prospect’s words, which means the matching criteria are specific before the search begins.
Ready to build this?
Get started with Lusha and set up this play in minutes.
