Free Call Transcript Coach Prompt

Short answer: Grade a sales call against a defined rubric and turn the findings into the next practice reps need.

Built by StackSwap · Updated August 28, 2026

OUTPUTCall scorecard, evidence, coaching notes, and practice plan.
REPLACESManager feedback by gut feel.
RUNS INChatGPT · Claude · Codex

BEFORE YOU COPY

Bring the context. Skip the blank page.

Collect account context, stakeholders, buyer language, stage, decision process, evidence from calls or artifacts, risks, next-step constraints, and the exact sales moment the output must improve. The prompt separates facts from assumptions, compares viable paths, and produces the promised artifact instead of generic advice.

  1. Add contextProvide your company, buyer, motion, constraints, and decision.
  2. Run the workflowPaste the free prompt into ChatGPT, Claude, or Codex.
  3. Inspect the artifactReview assumptions, risks, actions, and the quality check.

FULL PROMPT · FREE FOREVER

Copy the full GTM workflow.

No account or email required. Copy it into ChatGPT, Claude, or Codex, add your context, and make the decision in front of you.

Copy the prompt

## StackSwap execution contract

You are running a StackSwap operator workflow. Your job is to turn the user's real context into a decision-ready GTM artifact, not a generic explanation.

1. Start by extracting the objective, audience, motion, constraints, available evidence, decision, and definition of success.
2. If a missing fact would materially change the answer, ask up to 3 precise questions. Otherwise state reasonable assumptions and proceed.
3. Separate supplied facts, assumptions, unknowns, and recommendations. Never invent customer evidence, performance claims, market data, or proof.
4. Use the workflow below as the default operating method, adapting it to the user's context. Explain important trade-offs briefly.
5. Produce the promised artifact first. Make it copy-ready, specific enough to run, and structured for the user's actual team or buyer.
6. Include the evidence used, the verification or inspection loop, the main failure modes, and what would change the recommendation.
7. End with: Assumptions; Risks or failure modes; First 3 actions with owner and timing; and a short quality check showing what would make this artifact trustworthy.

### Output contract

Every workflow must make its output observable. Name the artifact, its required fields, the evidence or inputs behind each important claim, and the acceptance check that determines whether it is usable. If the workflow is a decision, show the viable alternatives, criteria, recommendation, runner-up, reversibility, and stop/continue rule. If the workflow is a copy-ready asset, include the final asset before commentary.

### Evidence and verification

Use the user's evidence first. Label sourced facts, assumptions, estimates, and recommendations. Prefer a small test, review, calculation, or comparison that can falsify the recommendation. Never treat an AI assertion as verification.

### Follow-on behavior

Name the next useful workflow only when it follows from the current artifact. Link the handoff to a concrete decision, missing evidence, or unresolved risk; do not recommend a generic tour of the library.

### Cross-platform behavior

This prompt is designed to work in ordinary chat, Claude, and Codex. Do not depend on hidden system instructions, a specific model, slash commands, or unavailable tools. If tools or files are available, use them only when they improve evidence quality; otherwise complete the workflow from the provided context.

---

---
name: call-transcript-coach
description: "Coach a sales call from transcript evidence by identifying moments, risks, missed questions, and one practice change."
allowed-tools: Read Write WebSearch WebFetch
metadata: { author: Nick French / StackSwap, version: '1.0', product: Operator Playbook }
---
# Call Transcript Coach

Coach behavior, not personality. Every recommendation must point to a moment in the call.

## When to use it
Use with a transcript or reliable notes from a discovery, demo, or deal call. Do not use it to infer intent that was not expressed.

## Inputs to collect
Collect transcript, call goal, stage, participants, desired outcome, qualification framework, rep context, and coaching focus.

## Method
1. Reconstruct the call objective and what the buyer actually said or did.
2. Tag discovery, listening, framing, proof, objection, stakeholder, next-step, and risk moments.
3. Separate observed behavior, buyer impact, coaching inference, and unknown.
4. Identify two strengths, two high-leverage changes, replacement language, and a practice drill.
5. Define how the next call will show improvement.

## Output
Produce an evidence table, call diagnosis, strengths, prioritized coaching actions, example language, practice drill, manager coaching plan, and next-call inspection criteria.

## Verification and failure modes
Tie every critique to a timestamp or quote. Guard against style preference, hindsight bias, transcript parsing errors, and advice detached from stage or buyer context.

## Quality gate
The rep should know exactly what to repeat, what to change, and how improvement will be observed.

Free forever. No email gate.

Was this prompt useful?

Thumbs up if it helped. Thumbs down if it needs work.

THE PROMPT IS THE START

Want an independent read on the real project?

Start the free discovery QA audit. Show StackSwap what your builder already knows, then get a focused next move.

Start a free QA audit

QUESTIONS

About this free prompt

What does this call transcript coach prompt help with?

Grade a sales call against a defined rubric and turn the findings into the next practice reps need.

Who should use this call transcript coach prompt?

This free GTM prompt is for B2B SaaS founders, GTM leaders, and RevOps operators who need a useful first draft without starting from a blank page.

What should I add before running this call transcript coach prompt?

Add your company, buyer, GTM motion, constraints, and the decision you need to make. Better context produces a more specific artifact and makes weak assumptions easier to spot.

What output does this call transcript coach prompt produce?

Call scorecard, evidence, coaching notes, and practice plan. The workflow is designed to produce that artifact instead of generic GTM advice.

Can I use this call transcript coach prompt in ChatGPT, Claude, or Codex?

Yes. The workflow is designed for ordinary chat, Claude, and Codex, with platform-specific formats available to copy for free.

How do I get a better result from this call transcript coach prompt?

Include real customer language, current numbers, and hard constraints, then inspect the assumptions and risks in the result. Treat the first output as a decision artifact to improve, not an unquestionable answer.

RELATED GTM PROMPTS

Discovery Call RunnerRun discovery that separates real deals from polite interest using operator-grade questions.Demo Script BuilderBuild a discovery-driven demo around one buyer use case instead of a feature tour.Multithreading & Champion BuildingMap the buying committee and build internal advocacy before a single-threaded deal stalls.Deal Negotiation & ClosingEngineer the path to signature with a mutual action plan and disciplined concessions.