When should you use it?
- You qualify a handful of accounts a week
- Your research notes end up scattered
- You already work in Google Workspace
Not for: High-volume list building; Sending outreach without a human read
What do you need, and what do you get?
You need
- Company name
- Your scoring rubric
- Sheet for the pipeline
You get
- Scored lead profile
- Outreach draft
- Row in your lead sheet
How does it work, step by step?
- Write the rubricDefine criteria and points, such as a 16-point scale across fit signals.
- Build the GemGive a custom Gem instructions for research, scoring and drafting.
- Command one: researchRun deep research on the company and store sources in a notebook.
- Command two: score and draftScore against the rubric and write a first outreach message.
- Log and decideRecord the score in the sheet and decide yourself whether to reach out.
The prompt
Our own prompt, inspired by Raghav Mehra and written to work in Gemini, ChatGPT and Claude. Values in lime are placeholders.
Research [company] for me as a possible client for [service]. Cover what they sell, recent news, funding, hiring signals and likely decision makers, with sources. Then score them against this rubric (0 to 16): [rubric]. Show the score per criterion with the evidence. Finally draft a short first message referencing one specific finding. Do not send anything.
Inspired by Raghav Mehra: How I Built a Sales Research Pipeline Entirely Inside Google's Ecosystem. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Research can surface outdated facts; check funding or leadership claims before using them.
- A rubric that rewards everything gives every lead a high score.
Our take
Keeping everything in one vendor's tools is pragmatic for anyone already in that ecosystem, and the explicit points rubric is what keeps scoring honest. The written rubric deserves most of the effort. Raghav's zero-to-sixteen scale works because each point maps to a fit signal you can check; a rubric that rewards everything turns every prospect into a hot lead. Write the criteria before building the Gem, then test them on a few accounts you already know well and see whether the scores match your judgment. The research step can pull outdated funding or leadership details, so verify anything you plan to mention in outreach. Keep the outreach draft as a draft; the last step is deciding yourself whether to reach out, and that should stay manual. This suits a handful of accounts a week, not high-volume list building. If your team already lives in Workspace, keeping it all in one place also makes the sheet easy to share.
Where the time goes back: The tab-by-tab digging per prospect becomes two commands and a short review.
FAQ
Does it need code?
How long per company?
Source and credit
Inspired by Raghav Mehra. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- How I Built a Sales Research Pipeline Entirely Inside Google's Ecosystem
- Creator
- Raghav Mehra
- Published on
- cashandcache.substack.com (Substack)
- Original date
- May 22, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Gemini
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.