Write an SDR-to-AE handoff for a booked meeting
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 prompt.
Use cases
Show all 6Show fewer
Methods
Paste into a general LLM and write an SDR-to-AE handoff for a booked meeting.
LLMPrompt
Prompt
Copied 0
Write a handoff note from me (SDR/BDR) to the account executive for a meeting I booked. **Prospect and company:** [NAME, TITLE, COMPANY, SIZE, INDUSTRY] **How the meeting was booked:** [cold call / email reply / inbound / event / referral] **What they said, in their words:** [PAINS, CURRENT TOOLS, WHY THEY AGREED TO MEET] **Qualification so far:** [budget, authority, need, timeline - what's known and unknown] **Other people at the account:** [NAMES/ROLES, if known] **What I promised them the meeting would cover:** [DETAILS] **Meeting time and attendees:** [DETAILS] Rules: - Lead with why this meeting is worth the AE's time in one sentence. - Separate facts the prospect stated from my impressions; label impressions clearly. - Flag anything that could make the meeting go badly (e.g. low authority, just exploring, a competitor contract until next year). - Keep it under 200 words, skimmable in 60 seconds. Return: 1. The handoff note with headings: Why it matters, Who, What they said, Qualification, Expectations set, Risks, Suggested opening questions. 2. A one-line version for the CRM or Slack. 3. A short email introducing the AE to the prospect, confirming the meeting and agenda.
No methods for that filter.
Add a method
How you would do this use case, in plain words. Anyone can post.
The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.
- All use cases:
GET /api/jobs - This use case:
GET /api/jobs/sdr-to-ae-meeting-handoff - Schema:
GET /api/jobs/schema - Add a method:
POST /api/jobs/method— same fields as the form. No API key yet.
A bad request returns JSON like {"error":"Method description is required"} with status 400.
| Field | What it is |
|---|---|
jobId | This use case. Review queue uses useCaseTitle + email instead. |
summary | Method description. Shown on the card. Also accepts title. |
products | Optional. Array of { name, url }. Legacy: tools. |
prompts | Optional. Array of prompt strings. Legacy: one prompt string. |
skills | Optional. Array of { text, url }. Legacy: skill + skillUrl. |
authorName | Author name. Legacy live field: postedBy. |
author | Optional 𝕏 handle. Legacy live field: creditHandle. |
parts | Optional. Inferred from products, prompts, and skills if omitted.standalone-product, ai-agent, ai-tool, skill, prompt. Do not send a prompt/product/agent/skill radio. |
{
"jobId": "sdr-to-ae-meeting-handoff",
"summary": "Turns a Zoom recording into notes and action items with owners",
"products": [
{
"name": "Claude",
"url": "https://claude.ai"
}
],
"prompts": [
"Turn this transcript into notes and action items with owners."
],
"skills": [
{
"text": "Watch a folder. When a transcript lands, write notes with owners.",
"url": "https://example.com/zoom-notes.md"
}
],
"authorName": "Alex Rivera",
"author": "@handle"
}