agency-setup

Agency configuration for CRM onboarding is set up through an interactive questionnaire that collects ICP details, services, tooling, and outreach preferences, then validates and outputs a comprehensive agency.config.json file. This config serves as a single source of truth that downstream skills automatically consume.

An agency.config.json file is a structured configuration file that stores your agency's ICP, services, tools, cadences, and scoring preferences. You need one when initializing a B2B agency GTM workflow so that all downstream skills read from a single, consistent configuration source.

Yes, you can generate a tailored GTM config without dependencies or prior technical setup. The guided onboarding process requires only your knowledge of the agency's details, such as domain, founder, case studies, and tool preferences, to produce a validated JSON configuration.

Case studies and outreach preferences are captured during agency initialization through an interactive questionnaire that prompts you for relevant agency details, services, and tool choices. The collected data is then compiled into a complete agency.config.json saved at your repo root.

Yes, the generated agency config works directly with downstream pipelines like signal-scanner and lead enrichment. The validated JSON output is designed to be automatically consumed by other skills, allowing them to adapt to your agency's ICP, tone, cadences, and scoring rules.

The best way to configure CRM tools and outreach cadences is through a questionnaire-driven setup that gathers your specific tool choices and cadence preferences, then auto-generates a comprehensive agency.config.json. This ensures every skill references a consistent configuration tailored to your agency.