Train Your Team to Use AI for Discovery Calls
Get everyone capturing client needs the same way, without endless training sessions
Each person on your team captures client calls differently. You get inconsistent handoffs, missing details, and no way to coach without listening to every recording yourself.
That is the gap this drop closes. It is a sales & leads skill built for Claude, and it takes about ten minutes to set up the first time. After that it runs in under a minute.
Who should use it
Sales managers rolling out AI tools to account executives, BDRs or consultants who handle discovery calls
How it works
The skill file does five things, in this order.
1. Build one shared prompt template. Create a prompt that extracts the fields your CRM and proposal process actually need, not a generic summary.
2. Test it on three real transcripts from different reps. Run the same prompt against calls from your best rep, your newest, and one messy call to see where it breaks.
3. Document the two-minute workflow. Write down exactly where the transcript goes, where to paste the prompt, and what to do with the output.
4. Run a live fifteen-minute session. Screen-share once with the team, show the workflow on one real call, then have each person do one under supervision.
5. Review five outputs in the first week. Spot-check what people are submitting, fix the prompt if you see repeated gaps, and share one good example in your team chat.
What comes back
A standard process your whole team follows, with a tested prompt saved where everyone can copy it and a short doc they can reference when stuck
The mistake to avoid
Do not roll this out over email. A single live session where people try it once while you watch prevents a month of confused Slack messages.
Running it
Save this as SKILL.md inside a folder named after the skill, then drop the folder into your Claude Code skills directory or upload it to a Claude Project. Claude reads the frontmatter to decide when the skill applies, so keep the description line intact. For a one-off run, paste the prompt block directly.
Where this fits
On its own, one skill saves an hour a week. The compounding happens when three or four of them run in sequence on the same input, the same transcript that produces a scope of work also produces the follow-up email and the project brief. That is the point at which it stops being a prompt and starts being an internal tool. If you want that wired into the systems your team already uses, that is the work 67 Digital does.
In the file
You are helping a sales team standardize how they document discovery calls.
Below is a transcript from a call with a potential client.
Extract the following fields in a structured format:
- Client company name and industry
- Main contact name and role
- Core problem or need they described
- Current solution or workaround they use
- Budget indication or procurement process mentioned
- Decision timeline and next steps agreed
- Key stakeholders involved in the decision
- Technical requirements or constraints mentioned
- Red flags or concerns raised during the call
If a field was not discussed, write "Not covered" rather than guessing.
Use bullet points. Keep statements factual and based only on what was said.
Format the output so it can be pasted directly into our CRM notes field and shared with the proposal team.
Transcript:
{paste_call_transcript_here}