Win/Loss Analysis & Churn Diagnostics

What it does

Win/Loss Analysis & Churn Diagnostics is a Cursor skill: a SKILL.md playbook that AgenticKit installs at .cursor/skills/win-loss-analysis. Cursor's agent loads it when the task matches the skill description, instead of stuffing the same rules into every chat.

Systematically analyzing why customers buy and why non-buyers leave, feeding findings back into positioning, product roadmap, and copy.

Post-purchase surveys, cancellation feedback, and positioning refinements. The file is domain knowledge, not a slash macro. You do not type it. The agent reads it when the job is win loss analysis.

Why it exists

Default Cursor has no memory of how your team ships positioning, copy, and launch assets. Founders paste the same conventions into chat, then watch the model drift on the next turn. This skill exists so those conventions live on disk and load only when relevant.

It ships in the Marketing Kit. It is wired to the Market & Competitor Analyst (competitive-analyst) and User & JTBD Researcher (market-researcher) agents. It is wired to the /positioning: Product Positioning & ICP Strategic Framework and /feature-spec: PRD & Product Feature Requirement Spec commands. That graph is the point: the skill is the standard, the agent is the role, the command is the trigger.

When to use it

• Use Win/Loss Analysis & Churn Diagnostics when the work is specifically about post-purchase surveys, cancellation feedback, and positioning refinements.
• Load it before a long session that will touch this surface more than once. A one-line edit does not need the full playbook.
• Use it when you are writing something a buyer will see: landing copy, launch posts, SEO pages, or positioning docs.

When not to use it

• Do not treat the skill as a replacement for a slash command. Skills teach. Commands run a pipeline.
• Do not paste the whole SKILL.md into chat. If Cursor is not loading it, fix the description or invoke the matching command.
• Do not use it to generate spam or spray the same launch post across every channel.

Example workflow

1. Install the Marketing Kit so .cursor/skills/win-loss-analysis lands in the repo.
2. Open a new Cursor agent chat pointed at the files this skill governs.
3. Ask the Market & Competitor Analyst (competitive-analyst) to read the skill, or run /positioning: Product Positioning & ICP Strategic Framework.
4. Review the first artifact against the practices below. If it violates one, stop and correct the file. Do not prompt 'just finish it'.
5. Commit the skill-guided files with the rest of the slice so the next session inherits the same standard.

Example usage

Example prompt: "Read .cursor/skills/win-loss-analysis and apply it to this change. Do not invent extra conventions."

Or trigger the pipeline: /positioning: Product Positioning & ICP Strategic Framework. That command is written to load this skill.

Check the output against: Send a 1-question survey post-purchase: 'What almost stopped you from buying?'

Example output

• The skill itself does not write a single output file. It changes what the agent is allowed to produce in positioning, copy, and launch assets.
• When you run /positioning: Product Positioning & ICP Strategic Framework, expect repo files plus notes under docs/, not a chat-only answer.

Best practices

• Send a 1-question survey post-purchase: 'What almost stopped you from buying?'
• Analyze exit feedback and cancellation reasons to identify unmet expectations
• Update FAQ sections with direct answers addressing the top non-buyer concerns
• Refine pricing and tier packaging based on customer perceived value

Common mistakes

• Ignoring "Send a 1-question survey post-purchase: 'What almost stopped you from buying?'" and hoping a later prompt will clean it up.
• Copying the skill into .cursor/rules as always-on. That burns context and fights Cursor's load-on-match design.
• Running two overlapping skills that contradict each other in the same turn.
• Publishing generated copy without a human pass. The skill is a playbook, not a publisher.