Sales Blueprint

Book of Business Folder Creator

Richard R.Account ManagerG2 April 2026

Automates organization of sales account data from multiple sources (Salesforce, ZoomInfo, Gong, Google Drive) into structured per-account folders with enriched summaries, contacts, and engagement metr

1 File Included

book-of-business.md
12 KB

What problem does this solve?

Sales reps managing large books of business (75+ accounts) struggle with scattered account data across multiple systems (Salesforce, ZoomInfo, Gong, Google Drive). The Book of Business Folder Creator organizes this intelligence into a structured, per-account folder system with enriched summaries, contacts, engagement signals, and transcripts — transforming hours of manual work into minutes of automated organization.

How does it work?

Upload a Salesforce report CSV as the foundation. The system creates a folder per account on Desktop. Then sequentially enrich each account folder: parse ZoomInfo contact and scoops CSVs to add contacts and market signals, pull partnership overlap data if available, add Gong call engagement metrics and engagement tiers, search Google Drive for account-specific documents, map downloaded Gong transcripts into transcripts/ subfolders, and optionally clean up Desktop screenshots. All data is written into a single ACCOUNT.md file per account (hot data like recent calls at top, cold reference data at bottom) plus a machine-readable account.json. A CLAUDE.md index at the root provides routing and quick stats. Finally verify folder creation and data coverage.

What's the biggest win?

One upload produces a complete, organized book of business with enriched intelligence for 75+ accounts in minutes instead of hours of manual work. Sales reps get unified account context (contacts, engagement, signals, documents, transcripts) organized by account folder, reducing time spent hunting for data and enabling faster renewal/expansion decisions.

What should I know technically?

Always use latin-1 encoding for CSV imports (Salesforce and ZoomInfo exports contain accented characters that break UTF-8). Account name matching across systems is the hardest part — implement fuzzy matching: exact folder match → case-insensitive → contains → first-word match. Scripts must be idempotent (safe to re-run). ACCOUNT.md uses YAML frontmatter for machine-parseable metadata (account, acv, renewal, tier, calls_12mo, risk, last_updated) followed by sections ordered hot→warm→cold. account.json is the programmatic companion for queries. Gong engagement tiers: 🟢 High (10+ calls), 🟡 Medium (5-9), 🔴 Low (1-4), ⚫ None (0). Risk flags: ⚠️ for zero calls, low engagement; ⚡ for watch-level accounts. Filesystem-safe folder names strip <>':"/\|?* and replace dots with underscores.

What are the constraints?

Account name matching across Salesforce, ZoomInfo, Gong, Google Drive, and filesystem is error-prone due to inconsistencies (double spaces, suffixes like Inc/LLC, punctuation differences, and unicode characters). Reps must know how to pull a Salesforce report with the correct columns (Account Name, ACV, Renewal Date, CSM, Adoption Score, etc.) — if the report is misconfigured or missing key fields, enrichment will be incomplete or fail to match accounts correctly. Always use latin-1 encoding for CSV imports to handle accented characters. Gong transcript matching depends on consistent naming conventions in downloaded filenames.