Analyze Deal Velocity
Requirements
CSV file with at least two date columns (created/opened and closed/won dates)
1
If the CSV path was not already provided, ask the user for it.
Must include: deal creation date and close date (for closed deals).
Establish for the subtask:
- Output path:
Parsed Sales Data
- Column types to detect: dates (created/closed), amounts, stages, reps
5
Analyze deal velocity:
- Identify date columns from interpreted columns (need at least 2)
- If unclear which is start vs end date, ask the user
- Calculate days between start and close for each deal
- Group by quarter or month to show trends
- Calculate average, median, fastest, and slowest deals
- Identify outliers (deals taking 2x+ the average)
Present results following the Deal Velocity Analysis template.
Show the trend over time—is velocity improving or worsening?
6
Provide insights on what affects velocity:
- Are larger deals slower?
- Do certain reps close faster?
- Any seasonal patterns?
To run this task you must have the following required information:
> CSV file with at least two date columns (created/opened and closed/won dates)
If you don't have all of this information, exit here and respond asking for any extra information you require, and instructions to run this task again with ALL required information.
---
You MUST use a todo list to complete these steps in order. Never move on to one step if you haven't completed the previous step. If you have multiple read steps in a row, read them all at once (in parallel).
Add all steps to your todo list now and begin executing.
## Steps
1. If the CSV path was not already provided, ask the user for it.
Must include: deal creation date and close date (for closed deals).
Establish for the subtask:
- Output path: `./documents/tmp/sales-data.json`
- Column types to detect: dates (created/closed), amounts, stages, reps
2. [Gather Requirements for Parse and Interpret CSV] The next step has the following requirements: "CSV file path to parse. Column type hints (e.g., "scores, customers, dates, categories"). Output file path for the interpreted data.". Search the user's data for this information or ask them directly if needed. Do not proceed until you have this information.
3. [Execute Parse and Interpret CSV Task]: Spawn a subagent and provide it with the requirements gathered above and instructions to read `./skills/sauna/[skill_id]/references/recipes/stdlib.csv.interpret.md` for its task list
4. [Read Parsed Sales Data]: Read the file at `./documents/tmp/sales-data.json` and analyze its contents (Load the parsed and interpreted CSV data)
5. [Read Sales Analytics Guide]: Read the documentation in: `./skills/sauna/[skill_id]/references/sales.analytics.guide.md` (Deal velocity output format)
6. Analyze deal velocity:
1. Identify date columns from interpreted columns (need at least 2)
2. If unclear which is start vs end date, ask the user
3. Calculate days between start and close for each deal
4. Group by quarter or month to show trends
5. Calculate average, median, fastest, and slowest deals
6. Identify outliers (deals taking 2x+ the average)
Present results following the Deal Velocity Analysis template.
Show the trend over time—is velocity improving or worsening?
7. Provide insights on what affects velocity:
- Are larger deals slower?
- Do certain reps close faster?
- Any seasonal patterns?