# Sales Call Script

> Generate a discovery or demo call script tailored to the prospect's role and known pains — opener, discovery questions, demo path, objection handling, close. Use on "prep a script for my demo", "discovery call with <role>", or "script for the call tomorrow".

- Skill: `composio-community/sales-call-script` (Agent Skill)
- Install (CLI): `npx skillmds@latest add composio-community/sales-call-script`
- Raw SKILL.md: https://api.skillmd.com/api/skills/composio-community/sales-call-script/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: composio-community (https://skillmd.com/u/composio-community)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/composio-community/sales-call-script

---


# Sales Call Script Generator

Build a call script that guides — not a monologue that reads.

## Workflow

1. **Inputs.** Call type (discovery, demo, technical deep-dive, close), attendees + roles, what was said in prior touches, desired next step, time box (30 / 45 / 60 min).
2. **Pick the call skeleton** based on type (see below).
3. **Personalize** each question with names, their stack, their known pains.
4. **Write the script** to `./scripts/<account>-<date>.md`.

## Discovery skeleton (30 min)

```
0:00–2:00  Rapport + agenda set
"Great to meet you. I've set aside 30 — does that still work?
Agenda: 10 min on what you're trying to solve, 15 on whether we'd fit,
5 on next step. Anything you want to add?"

2:00–15:00  Discovery (80% listening)
- "Walk me through how <current process> works today."
- "What changed recently that put this on your plate?"   ← trigger
- "What happens if you don't solve it this quarter?"     ← stakes
- "Who else is affected?"                                 ← buying committee
- "If this worked perfectly, what would be different in 6 months?"

15:00–22:00  Targeted show-and-tell (not a full demo — 1-2 workflows mapped to their pain)

22:00–27:00  Objection handling + pricing-teaser if they ask
Common objections:
  - "We could build this" → <response>
  - "We're using <competitor>" → <response>
  - "Timing's not great" → <response>

27:00–30:00  Next step
"Based on what you shared, I think the right next step is <X>.
Should we put it on the calendar while we're here?"
```

## Demo skeleton (45 min)

1. Re-ground in the pain (5 min) — "Before I show anything, remind me what success looks like"
2. One workflow, end-to-end, tied to their pain (15 min)
3. The "holy-crap" feature (5 min)
4. Q&A (10 min)
5. Mutual plan + next step (10 min)

## Objection library (include 3-5 most likely)

For each: restate → acknowledge → reframe → evidence → check-in.

## Guardrails

- Discovery calls should never become demos. If pulled, the script must include: "Happy to show that — before I do, can I ask two more questions so I show the right thing?"
- Script in bullets + question prompts, not full paragraphs. Reps should sound human.
- Always include a literal next-step ask with date on the call.