📁 Sales

B2B Sales Call Plan from Account and Discovery Notes

Paste account facts and discovery notes to get a call agenda, discovery questions, objection handling, and a mutual next-step email draft from your notes only.

0.0
0Reviews
P
October 15, 2026

Prompt

Act as a B2B sales coach who builds call plans from the seller's account facts and discovery notes, and who never invents customer quotes, competitors, or pricing the seller did not provide.

Inputs:
- Account name, industry, and size cues you know: [Account]
- Your product or service and the outcomes you can honestly claim: [Offer]
- Stakeholders and their roles on the buying side: [Stakeholders]
- Discovery notes from calls or emails (problems, metrics, timeline): [DiscoveryNotes]
- Stage and goal for the next live conversation: [CallGoal]
- Known objections or risks: [Objections]
- Pricing or packaging you may discuss: [PricingNotes]

Generate:
1. Call agenda with minute marks that add up to the planned length stated in CallGoal (default 30 if not given).
2. Discovery question set: 8 questions keyed to gaps in DiscoveryNotes; mark which stakeholder each question suits.
3. Talk track: 5 bullets tying Offer outcomes to pains already in DiscoveryNotes only.
4. Objection prep: for each item in Objections, a clarifying question and a response outline that does not invent discounts.
5. Mutual next-step options: 3 concrete closes that match CallGoal (demo, pilot scope, intro to economic buyer).
6. Follow-up email draft under 160 words using only facts from Inputs.
7. Honesty ledger: claims to avoid because Inputs do not support them (competitors, ROI numbers, customer logos).

Rules:
- Use only pains and metrics present in DiscoveryNotes.
- No fake social proof or invented case studies.
- Humans decide; this is a coaching plan, not pressure tactics.

Instructions

Paste real discovery notes into ChatGPT, Claude, or Gemini before the call. Edit the email so it matches what was actually said. Do not invent customer metrics or discounts. Follow CAN-SPAM in every commercial email: include your postal address and a working opt-out, honor opt-outs within 10 business days, and never use scraped or bought lists.

Generated Output

This image was generated using the prompt above.

B2B Sales Call Plan from Account and Discovery Notes - Result

Examples

Example Input

Account: BrightHarbor Clinics, regional outpatient group, about 12 locations.
Offer: ClinicOps scheduling software; reduces no-shows with SMS reminders and waitlist fills; we integrate with their current EHR via FHIR APIs we already support.
Stakeholders: Maya Chen, COO (champion); Dr. Patel, medical director (skeptical on staff burden); Luis Ortega, IT manager (security review).
DiscoveryNotes: no-show rate about 11% on new patients; front desk spends ~6 hours/week on manual waitlist calls; want improvement before summer volume; IT needs SOC 2 summary and SSO; budget owner is Maya; decision target late November.
CallGoal: 30-minute working session to agree on a 2-clinic pilot scope and security packet list.
Objections: "staff will ignore another inbox"; "we tried reminders before and patients muted them"; "IT bandwidth is thin until January".
PricingNotes: pilot lists at $1,200/month for 2 clinics for 90 days; standard annual later; no custom discount approved.

Example Output

1. AGENDA (30 minutes)
0-3: Goal check and attendees
3-10: Confirm no-show and front-desk time numbers from notes
10-18: Pilot scope for 2 clinics (workflows, SMS rules, waitlist)
18-25: Security packet list with Luis (SOC 2, SSO, FHIR)
25-30: Mutual next steps and owners

2. DISCOVERY QUESTIONS
1. (Maya) Which two clinics should pilot first and why?
2. (Maya) What no-show rate would count as a win after 90 days?
3. (Front desk lead if present) Where do muted-SMS patients show up in your process today?
4. (Dr. Patel) What staff steps are non-negotiable to keep during reminder send?
5. (Luis) Is SSO via your current IdP required on day one of pilot?
6. (Luis) Who signs off on the SOC 2 review and typical turnaround?
7. (Maya) Besides late November, any board or budget freeze dates?
8. (Maya) Who else must see a pilot readout to expand beyond 2 clinics?

3. TALK TRACK (from notes only)
- 11% new-patient no-shows is the pain we will measure against.
- 6 hours/week of manual waitlist calls is the staff time we aim to shrink with automated fills.
- FHIR integration path matches IT's stated interface need.
- Summer volume deadline frames why a 90-day pilot starting soon matters.
- Security packet (SOC 2 + SSO) is on the table this call, not deferred.

4. OBJECTION PREP
- Staff inbox fatigue: Ask which channel they already monitor; respond with workflow that uses existing SMS vendor templates they approve, not a new app for clinicians.
- Muted reminders: Ask what cadence failed before; respond with quieter cadence options and waitlist pull as the backup, without inventing open rates.
- IT bandwidth: Ask what can be async review; respond with a document-only security pack Luis can review without build work until January.

5. NEXT-STEP OPTIONS
A. Agree 2-clinic pilot SOP draft by Friday (Maya owns clinic pick).
B. Send SOC 2 summary + SSO questionnaire today (Luis owns review date).
C. Schedule 45-minute pilot kickoff after security OK.

6. FOLLOW-UP EMAIL (148 words)
Subject: BrightHarbor: 2-clinic pilot scope and security list
Hi Maya, Dr. Patel, and Luis, thanks for today's working session. We aligned on a 90-day pilot for two clinics at $1,200/month, focused on SMS reminders and waitlist fills tied to your FHIR-capable EHR path. You flagged an ~11% new-patient no-show rate and about 6 hours/week of manual waitlist calls as the baselines to measure. Next steps we proposed: Maya confirms the two clinics by Friday; I send the SOC 2 summary and SSO questionnaire for Luis; we book a kickoff once IT marks the packet reviewable. No new discount was discussed. Please reply with any corrections to these notes.

7. HONESTY LEDGER
- Do not invent ROI % or competitor names.
- Do not claim SOC 2 details beyond sending the summary we actually have.
- Do not promise January IT build work.

Reviews (0)

Please login to leave a review.
Loading reviews...