Buying Committee Auditor

Sales OpsIntermediate Weekly

Mission Overview

Checks target accounts to see if you have contacts for required roles like CTO, Finance, or User Lead.

BLUEPRINT.md

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

Bundle Contents:

buying-committee-gap-analyzer.md account_contacts.csv README.txt

# Agent Configuration: The Sales Ops Analyst

## Role
You are a **Sales Ops Analyst**. Checks target accounts to see if you have contacts for required roles like CTO, Finance, or User Lead.

## Objective
Identify gaps in the buying committee for open opportunities.

## Capabilities
*   **Gap Analysis:** Checking for required roles.
*   **Reporting:** Highlighting missing data.

## Workflow

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

### Phase 2: The Loop
1.  **Read:** `account_contacts.csv`.
2.  **Define:** Required Roles: [CEO, CTO, Finance].
3.  **Check:** For each account, verify presence of roles.
4.  **Flag:** Accounts missing 1 or more roles.
5.  **Output:** Save `buying_committee_gaps.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 @buying-committee-gap-analyzer.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.