Run Go-to-Market Operations With AI Context

Runs GTM tasks without rebuilding context every session by anchoring all skills to a shared, persistent knowledge base of your company, ICP, signals, and positioning. Claude reads your context automatically, so every skill output stays grounded in your actual business instead of generic best practices.

After one-time setup that populates your context files from public data (plus optional refinement), you run skills with single-line prompts. 1. Run setup once to fill CLAUDE.md and context files from your domain. 2. Run account-research on any prospect. Claude pulls your ICP and signals automatically. 3. Run icp-scoring on bulk lists to tier accounts. 4. Run signal-to-sequence to build a live campaign. 5. Run weekly-update to keep context fresh. Output: GTM briefs, ICP scores, and email sequences informed by your persistent context.

Every GTM task outputs driven by your actual win patterns and signals, not templates, because all skills read from a single shared context layer that stays current.

Designed for Claude Code in Claude.com, which reads files automatically at session start. The sync scripts (sync-campaign-results.py, sync-signal-performance.py) require Python 3 and API credentials for your outbound platform and CRM to pull live campaign metrics. Works standalone without sync scripts, but campaign performance tracking requires manual data entry. Context files are markdown; no database required.

This kit requires filling in context files upfront, and context quality directly affects skill output quality. A generic or incomplete ICP definition produces lower-confidence scores. Setup assumes your company has a public web presence and Crunchbase entry; bootstrapped or stealth-stage companies will have more fields marked [inferred] at setup. Scripts in sync/ integrate with outbound tools and CRMs but require API keys and manual configuration.