86 lines
2.5 KiB
Markdown
86 lines
2.5 KiB
Markdown
---
|
|
name: sales-followup
|
|
description: Draft sales follow-up messages that move deals forward with the right mix of urgency, clarity, and low-friction next steps after calls, demos, proposals, and stalled threads. Use this whenever users ask to follow up, re-engage, nudge, check in, request a decision, client follow-up, 商談フォロー, 提案後フォロー, or 検討状況確認 after a demo, quote, meeting, or proposal; use it for sales progression, not for complaint handling or tone-only rewrites.
|
|
category: Writing & Reporting
|
|
---
|
|
|
|
# Sales Follow-Up
|
|
|
|
## Overview
|
|
|
|
Create sales follow-up messages that maintain momentum without sounding vague, repetitive, or overly aggressive.
|
|
|
|
This skill is for:
|
|
- Post-demo follow-ups
|
|
- Proposal check-ins
|
|
- Re-engaging stalled leads
|
|
- Clarifying next steps after meetings
|
|
- Nudging for decisions, feedback, or scheduling
|
|
|
|
## Triggering Cues
|
|
|
|
Use this skill when user messages include:
|
|
|
|
- follow up with the client
|
|
- re-engage this lead
|
|
- nudge them for a decision
|
|
- post-demo email
|
|
- check in after proposal
|
|
- no reply from customer
|
|
|
|
## Input Requirements
|
|
|
|
Ask for or infer:
|
|
|
|
1. What happened previously (demo, meeting, proposal, quote)
|
|
2. Desired next step
|
|
3. Relationship stage (new lead / active deal / late-stage)
|
|
4. Deadline or urgency level
|
|
5. Preferred tone (warm / direct / firm)
|
|
|
|
If details are missing, make reasonable assumptions and state them briefly.
|
|
|
|
## Output Format
|
|
|
|
Always output:
|
|
|
|
1. **Subject Line Options** (2-3)
|
|
2. **Primary Draft**
|
|
3. **CTA**
|
|
4. **Fallback Follow-Up Line** (short version for another nudge)
|
|
|
|
## Workflow
|
|
|
|
1. Identify the sales stage and likely customer context.
|
|
2. Clarify the single most important next step.
|
|
3. Write a concise message with clear value and low friction.
|
|
4. Keep the ask specific and time-bound when appropriate.
|
|
5. Offer a shorter fallback line for later reuse.
|
|
|
|
## Examples
|
|
|
|
### Example 1
|
|
Input:
|
|
- We sent a proposal last week after the demo and the client has not replied.
|
|
|
|
Output style:
|
|
- Professional and warm
|
|
- Reference the proposal without sounding pushy
|
|
- Ask for a review decision or a short call
|
|
|
|
### Example 2
|
|
Input:
|
|
- The prospect sounded interested but went silent after pricing discussion.
|
|
|
|
Output style:
|
|
- Re-engagement tone
|
|
- Lower-friction CTA
|
|
- Emphasize willingness to adjust scope or answer questions
|
|
|
|
## Guidelines
|
|
|
|
- Keep the message short and action-oriented.
|
|
- Avoid generic “just checking in” language when possible.
|
|
- Make the next step easy to say yes to.
|
|
- Do not invent prior conversations or promises.
|