Generate a note-taking template for your sales motion
Designs a discovery note template where every field has a downstream customer — the follow-up email, demo build, forecast, or handoff — plus a during-call versus after-call split, one-keystroke red-flag codes, and both plain-text and markdown formats. Kills both blank-page notes and the 40-field CRM form nobody fills.
You are a sales operations designer who builds call documentation systems reps actually use. You know the two failure modes: the blank page (notes become a transcript of vibes, unusable a week later) and the over-engineered form (40 CRM fields nobody fills after week one). Your templates capture exactly what the sales motion needs downstream — for the follow-up email, the demo build, the forecast call, the handoff — and nothing else. Every field must have a customer: if no downstream step consumes it, it dies. Design me a discovery note-taking template. Output format: 1. THE TEMPLATE: 6-9 fields max, each with: the field name, a one-line description of what goes in it, a filled example, and its downstream customer (what consumes this field — the summary email, the demo storyline, the CRM forecast, the manager 1:1). Must include a VERBATIM field for exact prospect quotes, because their words power every good follow-up. 2. THE LIVE-CALL VERSION: which 3 fields to capture during the call versus which to complete in the five minutes after — because typing through a conversation kills discovery. 3. THE RED-FLAG CODES: 4-5 shorthand marks for things worth flagging in the moment (competitor named, budget signal, skeptic identified, timeline stated) so capture takes one keystroke, not a sentence. 4. FORMAT OPTIONS: the template rendered two ways — as a plain-text block I can paste into any tool, and as a markdown table. 5. THE HANDOFF CHECK: if my motion includes an SDR-to-AE or AE-to-CS handoff, the 3 fields the receiving person says they never get but always need. Before you write anything, interview me. Ask me these questions ONE AT A TIME, waiting for my answer each time: 1. Describe your sales motion — who runs discovery, what happens after, and where handoffs occur. 2. What tools hold your notes today — CRM, docs, a call recorder that transcribes? 3. What information do you most often realize you failed to capture, when it's too late? 4. Do you qualify against a framework (MEDDICC, BANT, your own), or informally? Once you have my answers, produce the template. If I use a call recorder, design the template to capture what transcripts DON'T — judgments, reads, and flags — rather than duplicating what they do.
How to use it
- 1
Copy the prompt into Claude, ChatGPT, or any LLM.
- 2
Answer question 3 carefully — the information you keep losing is the template's reason to exist.
- 3
Pilot the template for five calls before changing anything; most objections dissolve with use.
- 4
Complete the after-call fields within five minutes of hanging up, while judgment is fresh.
- 5
If you use a recorder, let transcripts hold the words and the template hold your reads — never duplicate.
Best practices
The verbatim field is the highest-value real estate — exact quotes power the mirror email and demo cold open from this category.
Defend the field cap: every addition must name its downstream customer or it doesn't ship.
The red-flag codes work best as physical habit — same marks, every call, until flagging is automatic.
Teams: adopt one shared template so manager 1:1s and handoffs read the same fields in the same places.
Example: what this looks like in practice
A sales leader at a 12-rep insurance-tech company finds every rep takes notes differently — one writes essays, two write nothing, and AE handoffs from the SDR team routinely miss who else was on the call. He answers the interview: notes live in HubSpot, they loosely use MEDDICC, and the thing they always lose is why deals stall. The template comes back with seven fields including 'Stall risk (your read, one line)' consumed by the forecast call, and a verbatim field consumed by follow-ups. The handoff check adds the three fields his AEs confirm they never get: other attendees, competitor mentions, and what was promised. Two weeks in, his pipeline reviews shorten by half because every deal's notes finally answer the same questions.
Best fit
This prompt is one gear in a bigger machine. We orchestrate 20+ tools into outbound systems our clients own — and guarantee the results.
Apply for a Pilot Spot → →Frequently asked questions
During the call, only three things: exact quotes worth mirroring later, red flags (competitor named, budget signal, timeline), and numbers. Everything else — your judgments, qualification reads, next-step notes — belongs in the five minutes after, while memory is fresh. Typing continuously through a conversation is the fastest way to miss what the prospect is actually telling you.
More discovery calls & demos prompts
Build a discovery question bank tailored to one persona
Generates a 15-question discovery bank built around one persona's actual responsibilities and failure modes, organized by call stage, with listening notes on what strong and weak answers sound like. Beats generic question lists because the interview forces your product, competitor, and deal-death context into every question.
Write a post-discovery summary email that mirrors their words
Produces a sub-180-word summary email built on the prospect's verbatim phrases, with impact-paired bullets, an invitation to correct you, and next steps with your commitments listed first. Mirroring their language proves you listened in a way no template can, and the email becomes the artifact your champion forwards internally.
Build a demo storyline from your discovery notes
Converts raw discovery notes or a transcript into a three-act demo storyline that opens on the prospect's problem in their own words, sequences scenes by deal importance, tells you what NOT to show, and scripts the close. It's the difference between a feature tour and a demo the champion replays internally.