start

Automating signal-based outbound onboarding involves scanning your GTM directory to capture company ICP, tech stack, and voice, then routing to the correct next step. This Skill structures that data into foundational company, ICP, and voice profiles.

Building an ICP profile for GTM outreach requires gathering user inputs and conducting online research to define your target accounts. This onboarding workflow structures those inputs into an icp.md file to establish your prospecting foundation.

First-run detection for GTM onboarding works by scanning the ./gtm/ directory to check for existing foundational files. If absent, it triggers first-run mode to collect company data, ICP, and voice; if present, it routes returning users to continue profiling.

Yes, you can use this onboarding workflow to optionally update connected tools. After detecting your tool status and gathering onboarding inputs, it prepares foundational profiles and can sync this data to your connected outreach and prospecting platforms.

Routing to the next step after capturing company voice and ICP is handled by applying onboarding logic that directs you to either /profile for deeper profiling or /signal-scout for signal prospecting based on your current GTM directory state.

Yes, you need a ./gtm/ directory to start automated onboarding. The workflow scans this directory to establish a baseline foundation, detect whether it is a first-run or returning session, and route you to the appropriate next step.