Create a copy-paste AI prompt pack for a BDR prospecting [TARGET MARKET] for [PRODUCT OR SERVICE]. Our ideal customer profile and qualification rules: [ICP AND QUALIFICATION]. Approved messaging and proof: [APPROVED MESSAGING]. Prospect or account information available: [PROSPECT INFORMATION]. Prospecting goal: [PROSPECTING GOAL]. Return exactly eight standalone prompts, each 100–140 words and written in first person for use in ChatGPT, Claude, or Gemini. Every prompt must contain its own square-bracket placeholders and a precise requested output. Provide prompts in this order: 1. Public-source account research plan. 2. Account-fit assessment. 3. Persona-specific pain-point hypotheses. 4. First-touch email. 5. LinkedIn connection note and follow-up message. 6. Call opener and qualification questions. 7. Inbound-reply triage and response draft. 8. Qualified-meeting handoff to an account executive. Make the pack appropriate for a BDR: research only public or user-provided information; label assumptions; focus on relevance rather than fake familiarity; use one specific trigger or hypothesis per outbound message; keep a first email under 110 words; and ask for a clear, low-friction next step. Qualification must cover fit, problem, current approach, stakeholders, timing, and next meeting without forcing a framework label onto incomplete information. The handoff must separate what the prospect explicitly said from BDR inference. Do not invent funding, headcount, technology, competitor use, intent, mutual connections, customer logos, ROI, or meeting outcomes. After the eight prompts, provide a seven-point pre-send checklist for deliverability, claims, personalization, consent, and CRM accuracy. Before answering, check that every prompt has its own usable inputs and that no task requires private data. Ask up to 3 clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [TARGET MARKET] | Enter the industry, company size, geography, and buyer personas the BDR should target. | US logistics companies with 200–1,500 employees; VP Operations, Director of Fleet, and Safety Manager personas. |
| [PRODUCT OR SERVICE] | Enter what you sell and the primary workflow or problem it addresses. | Mobile inspection software for fleets that replaces paper vehicle inspection forms and reports defects to maintenance teams. |
| [ICP AND QUALIFICATION] | Enter firmographic fit rules, disqualifiers, qualification criteria, and meeting-acceptance requirements. | At least 75 vehicles; US operations; disqualify owner-operators; meeting requires a stated inspection workflow issue and an operations or safety stakeholder. |
| [APPROVED MESSAGING] | Enter approved value propositions, proof points, restrictions, and claims the BDR may use. | Offline mobile inspections, configurable forms, and maintenance alerts; use only published customer quotes; do not claim regulatory compliance or guaranteed time savings. |
| [PROSPECT INFORMATION] | Enter the public research, CRM facts, role, prior touches, and any inbound context available. | Cedar Route Logistics, 420 employees; website lists regional refrigerated freight; prospect is Dana Lee, Director of Fleet; no prior outreach. |
| [PROSPECTING GOAL] | Enter the desired result, such as a discovery meeting, event follow-up, or re-engagement response. | Book a 20-minute introduction with Dana or identify the correct operations owner. |
How to use
- Add only information you can support from public sources, CRM notes, or approved collateral; do not ask the model to fill gaps with guesses.
- Use one account hypothesis per first-touch message and keep the CTA easy to decline or redirect.
- Before a booked meeting, run the qualification and handoff prompts so the account executive receives facts, not optimistic interpretation.
- Follow up with: “Create two alternative emails for this account, each based on a different verified trigger, and list the source behind each trigger.”
Variations
First-touch email
Use when you have a verified account fact and need a concise outbound message.
Write a first-touch BDR email to [PROSPECT NAME], [ROLE] at [COMPANY]. Verified public facts: [VERIFIED FACTS]. What we offer: [APPROVED OFFER]. Relevance hypothesis: [HYPOTHESIS]. CTA: [CTA]. Write two versions under 100 words with subject lines. Each must use one factual trigger, connect it cautiously to a plausible workflow issue, and make a low-pressure ask. Do not claim the prospect has a problem, use false familiarity, or add customer proof not supplied. Flag any fact that needs source verification.
Qualification call
Use immediately before a short inbound or outbound qualification call.
Prepare a 15-minute BDR qualification call for [PROSPECT] at [ACCOUNT]. Inbound or prior context: [CONTEXT]. ICP rules: [ICP RULES]. Approved product scope: [PRODUCT SCOPE]. Create a minute-by-minute outline, eight natural questions, listening signals for qualification or disqualification, and three next-step outcomes. Cover current workflow, problem, impact, stakeholders, timing, and fit without interrogating the prospect. Do not assume authority, budget, or implementation plans. Mark questions that should be saved for an account executive.
AE handoff
Use after a meeting is qualified and before passing it to an account executive.
Create an AE handoff from these BDR notes: [MEETING NOTES]. Account facts: [ACCOUNT FACTS]. Qualification rules: [QUALIFICATION RULES]. Next meeting details: [NEXT MEETING]. Produce a CRM-ready summary with explicit prospect statements, BDR hypotheses, confirmed pain, current process, stakeholders, timing, risks, agreed next step, and open questions. Add a 120-word internal handoff email. Do not convert interest into commitment or fill missing qualification fields with assumptions. Flag every field the AE should validate.
Tips
- A BDR email needs one verified reason for relevance; piling on three weak personalizations usually makes the message less credible.
- Keep research notes separate from hypotheses in the CRM. A website fact and your inference about a pain point are not the same thing.
- Use disqualification rules early so a booked meeting is useful for the buyer and the account executive.
- When a prospect redirects you, record the correct owner and their stated reason; do not reuse the old message with only a new name.
FAQ
Can BDRs use AI for prospect research?
Yes, for organizing public information and forming clearly labeled hypotheses. Verify important facts at the source before using them in outreach.
How should a BDR use AI without sounding automated?
Give it one real account fact, one relevant product capability, and a modest CTA. Edit out claims that the prospect did not make or that you cannot support.
What belongs in an AE handoff?
Include what the prospect said, what is verified about fit, the current process, stakeholders, timing, risks, and the agreed next step. Mark unknowns rather than smoothing them over.