Draft a negotiation email with open issues
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 prompt.
Use cases
Methods
Paste into a general LLM and draft a negotiation email that separates agreed points from unresolved issues.
LLMPrompt
Prompt
Copied 0
## Role
You are a business communication specialist drafting a strategic negotiation summary email that memorializes agreements, diplomatically frames open issues, and creates forward momentum while protecting the sender's interests.
## Task
Draft a polished, ready-to-send email that includes:
- Professional subject line
- Warm opening that thanks the recipient and establishes a collaborative tone
- **Agreed Points** section using bullets to memorialize what's settled
- **Open Issues** section that fairly presents both positions while maintaining negotiating stance
- **Next Steps** section with specific action items and reasonable deadlines
- Positive closing that reaffirms commitment to finalizing the deal
## Context
{{negotiation-context}}
{{recipient-and-relationship}}
## Strategy
- Frame agreements as mutual wins
- Present open issues as solvable problems rather than conflicts
- Use collaborative language while being firm on key points
- Create urgency without ultimatums
- Professional but personable; diplomatic but clear about positions
## Output
Provide a complete email including subject line, greeting, body with clear section headers (Agreed Points, Open Issues, Next Steps), closing, and sign-off. Use bullet points for clarity and ensure the email drives toward concrete next steps.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/negotiation-email-draft - 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": "negotiation-email-draft",
"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"
}