Analyze one won or lost deal for lessons
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 analyze one won or lost deal for lessons.
LLMPrompt
Prompt
Copied 0
I just [won/lost] a deal. Help me analyze what happened and extract lessons. DEAL DETAILS: - Company: [company name] - Deal size: [value] - Sales cycle length: [how long from first touch to close/loss] - Decision maker(s): [who was involved] - Competitor(s): [who we were up against, if known] - Our champion: [who was on our side internally] TIMELINE: [Walk through the deal chronologically — key meetings, turning points, objections, what went well, what went poorly] OUTCOME: [Won/Lost] IF LOST: The stated reason was [what they told you] Analyze this deal: 1. TURNING POINTS: What were the 2-3 moments that most influenced the outcome? 2. WHAT WORKED: What did we do well that we should repeat? 3. WHAT DIDN'T: What should we have done differently? 4. REAL REASON: Based on the timeline, is the stated reason for losing (or winning) the actual reason? What was really going on? 5. SIGNALS WE MISSED: Were there early warning signs (or buying signals) we should have caught sooner? 6. PLAYBOOK UPDATE: What should we change in our sales process based on this deal? 7. PATTERN MATCH: Does this remind you of any common deal patterns? (e.g., 'champion left mid-deal', 'bought on emotion then got cold feet', 'committee decision killed momentum')
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/analyze-a-single-won-or-lost-deal - 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": "analyze-a-single-won-or-lost-deal",
"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"
}