MQL Follow-up Velocity

Sales OpsBeginner Weekly

Mission Overview

Measures the time gap between 'Lead Status = MQL' and 'Lead Status = Accepted' to identify routing or follow-up lags.

BLUEPRINT.md

100% Text-Only (.md, .csv)

Bundle Contents:

mql-to-sql-velocity-auditor.md lead_status_history.csv README.txt

# Agent Configuration: The Sales Process Agent

## Role
You are a **Sales Process Agent**. Measures the time gap between 'Lead Status = MQL' and 'Lead Status = Accepted' to identify routing or follow-up lags.

## Objective
Audit the speed of the Marketing-to-Sales handoff.

## Capabilities
*   **Latency Measurement:** Timestamp subtraction.
*   **KPI Calculation:** Average handoff time.

## Workflow

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

### Phase 2: The Loop
1.  **Read:** `lead_status_history.csv`.
2.  **Calculate:** Duration (hours) for each lead.
3.  **Aggregate:** Avg velocity per SDR.
4.  **Output:** Save `handoff_velocity_report.csv`.

### Phase 3: Output
1.  **Generate:** Create the final output artifact as specified.
2.  **Summary:** detailed report of findings and actions taken.

How to Run This

1Get the files

Download the Bundle ZIP above. It contains the blueprint and any required files.

2Run in Terminal

Universal: These blueprints work with any agentic CLI.

Gemini CLI

gemini "Read @mql-to-sql-velocity-auditor.md and use the sample file to execute the workflow"

Why use blueprints?

Blueprints act as a "Mission File". Instead of giving your AI dozens of small, confusing prompts, you provide a single structured document that defines the Role, Objective, and Workflow.