// Prep for a discovery call — research the account, the attendee, set hypothesis for their pains, write the question stack, define success. Use on "prep for my discovery call", "research this account before tomorrow", or "what should I ask <prospect>?".
Generate a targeted lead list with Apollo — filter by title, company size, industry, tech stack — and export to CSV/HubSpot/Sheets. Use when the user says "build me a prospect list", "find 100 VPs of X", or "source leads for the campaign".
Build a competitive battlecard — when to land-grab vs. when to walk away, key wedges, objection handling, landmines to set. Use on "build a battlecard against <competitor>", "how do we beat <X>", or "compete review".
Check Google Calendar availability and book meetings — find slots across time zones, send invites, hold prep time. Use on "find time with X", "book a demo", "check my availability next week".
Write high-response cold emails — short, specific, prospect-centric. Use when the user asks to "write a cold email", "rewrite my outbound", or "this email is getting no replies". Produces 3 variants with rationale.
Run a cold email outreach campaign via Gmail. Use when the user wants to send personalized cold emails to a list of prospects, draft outbound sequences, or launch a small outreach batch from a CSV/sheet of leads. Proactively invoke when the user mentions "send cold emails", "outreach campaign", or "blast my leads".
Send follow-up emails on threads that haven't replied — 3, 7, 14 day cadence with fresh angles. Reads sent folder, identifies no-reply threads, drafts context-aware follow-ups. Trigger on "send follow-ups", "bump my cold emails", or "who hasn't replied?".
| name | discovery-call-prep |
| description | Prep for a discovery call — research the account, the attendee, set hypothesis for their pains, write the question stack, define success. Use on "prep for my discovery call", "research this account before tomorrow", or "what should I ask <prospect>?". |
| allowed-tools | ["Read","Write","WebSearch","AskUserQuestion"] |
A great discovery call is an earned conversation, not a generic script. Prep is where the edge comes from.
./prep/<account>-<date>.md.# <Account> — Discovery — <date>
## Snapshot
- Stage/size/funding
- Recent signals (hires, launches, news)
- Why meeting now: <source + any context from prior touches>
## Attendee
- <Name> — <Title> — <tenure>
- What they likely care about: <metric/KPI>
- Prior-company pattern: <if relevant>
## Pain hypotheses (ranked)
1. <Pain> — signal: <X> — their words: "<probable phrasing>"
2. …
3. …
## Question stack
Opening: "Walk me through how you handle <workflow> today."
Going deeper:
- "What changed that put this on your plate?" (trigger)
- "Who else is affected when <current pain>?" (committee)
- "What's the cost of not solving this in <timeframe>?" (stakes)
- "What would have to be true for you to pick a solution this quarter?" (criteria)
Verification:
- "If I'm hearing you right — <paraphrase>. Is that fair?"
## Landmines (questions we don't want surfaced yet)
- Pricing before value is established
- <Competitor> comparison before pains are clear
## Desired next step
<Specific next meeting / output / access> by <date>.
## Reference ammo
- <Lookalike customer> — outcome — available for reference? Y/N
- <Case study link>