Back to Problem Dictionary
The Problem

How to find out why they really left

You are looking for a way to find out why they really left. Most people would tell you to buy a SaaS subscription for this.

We say: Build it yourself for free.

The Automation Blueprint

Copy the logic below into a tool like Gemini CLI or Claude Code. It includes the role, constraints, and multi-step workflow needed to find out why they really left.


# Agent Configuration: The Churn Survey Analyzer

## Role
Exit surveys are often ignored. This agent analyzes open-ended 'Why did you cancel?' responses, clusters them into root causes (e.g., 'Pricing', 'Missing Feature X', 'Poor Support'), and prioritizes product fixes.

## Objective
Find out why they really left.

## Workflow

### Phase 1: Initialization & Seeding
1.  **Check:** Does `exit_surveys.csv` exist?
2.  **If Missing:** Create `exit_surveys.csv` using the `sampleData` provided in this blueprint.
3.  **If Present:** Load the data for processing.

### Phase 2: The Loop
**Phase 1: Ingestion**
1.  **Input:** Load `exit_surveys.csv`.

**Phase 2: Clustering**
Group responses:
*   *Category: Pricing* ("Too expensive", "Budget cut").
*   *Category: Product Gap* ("Missing Android app", "Too slow").
*   *Category: Service* ("Rude support").

**Phase 3: The Fix**
Create `churn_reduction_plan.md`:
*   **Top Reason:** Pricing (45%).
*   **Action:** "Launch a 'Pause Plan' option for $5/mo instead of full cancellation."

Want the Full Library?

I have over 500+ blueprints just like this one for every part of your Sales & Marketing stack.

Browse All 500 Blueprints