메뉴
Synthesize win-loss interviews, notes, and deal evidence into clear themes and actions. Use when asked why deals were won or lost, how patterns vary by segment or competitor, or what to change in messaging, process, or coaching. For a single competitive asset, route to battlecard-builder.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Build concise, decision-ready account briefs for account reviews, internal deal strategy, and customer meeting prep. Use when asked to prepare an account brief, summarize account risk and upside, map stakeholders, or define account-specific next steps. For executive-facing meeting strategy, use executive-briefing-builder.
Create competitor battlecards for revenue teams with practical talk tracks, proof, and red flags. Use when asked for compete guidance, head-to-head positioning, buyer objections, or seller-ready competitive artifacts. Route broad positioning strategy to value-prop-and-positioning and objection handling systems to objection-library-builder.
Turn call transcripts and notes into an objection playbook update. Use when asked to find recurring pushback, objection themes, or message gaps by segment, persona, or stage. For one-call coaching, use call-review-coach. For the final objection asset, use objection-library-builder.
Review one sales call and turn it into clear coaching priorities and next-practice actions. Use when asked to coach a rep from a recording, transcript, or notes across discovery, demo, objection handling, or closing. Route practice-drill requests to roleplay-scenario-builder and discovery scoring standards to discovery-rubric-auditor.
Extract and structure credible customer case studies from raw notes, transcripts, and outcome data. Use when asked to turn messy source material into customer stories, proof points, or enablement-ready case studies. Route broad feedback synthesis to field-feedback-synthesizer and slide packaging to one-pager-and-slide-outline.
Create role-based readiness certifications with clear scoring, evaluation prompts, and calibration rules. Use when the user asks to design pass/fail standards, assessor guides, or repeatable certification workflows for sales or customer-facing roles. Route broader ramp-planning work to onboarding-program-builder.
| name | win-loss-synthesis |
| description | Synthesize win-loss interviews, notes, and deal evidence into clear themes and actions. Use when asked why deals were won or lost, how patterns vary by segment or competitor, or what to change in messaging, process, or coaching. For a single competitive asset, route to battlecard-builder. |
Turn mixed win-loss evidence into findings that change enablement priorities.
Confirm the minimum analysis scope:
revenue-enablement-context exists, use it first for ICP, stage, competitor frame, and message guardrails. If not, ask for only the highest-impact missing context.Ask for only missing items. If the user wants a fast draft, proceed with labeled assumptions.
Set analysis boundaries. Define what counts as evidence and which deals belong in scope.
Normalize records. Convert source artifacts into a consistent dataset with stage, segment, persona, competitor, and outcome fields.
Code reasons and context. Tag primary and secondary reasons using the shared coding framework.
Separate evidence from inference. Keep raw observations separate from interpretation.
Check coverage and bias. Flag selection bias, missing segments, and skewed deal mix before drawing broad conclusions.
Compare patterns. Look for differences by segment, persona, stage, and competitor.
Prioritize implications. Translate findings into messaging, coaching, process, and product feedback recommendations.
Call out confidence. Highlight sample limits, missing segments, or source quality concerns.
Default output includes: