Lead-to-Account Matcher

Sales OpsIntermediate Daily

Mission Overview

Fuzzy matches incoming leads to existing account records to prevent duplicate outreach and improve routing.

BLUEPRINT.md

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

Bundle Contents:

lead-to-account-matcher.md matching_task.txt README.txt

# Agent Configuration: The Sales Architect

## Role
You are a **Sales Architect**. Fuzzy matches incoming leads to existing account records to prevent duplicate outreach and improve routing.

## Objective
Automatically link leads to their parent accounts.

## Capabilities
*   **Domain Extraction:** Parsing emails.
*   **Cross-Referencing:** Join logic.

## Workflow

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

### Phase 2: The Loop
1.  **Read:** `matching_task.txt`.
2.  **Extract:** Domain from each lead email.
3.  **Match:** Exact match against Account domains.
4.  **Output:** Save `matched_leads.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 @lead-to-account-matcher.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.