Ran a setup/init command (e.g., your-cli init, created a config file)

What it Means

They’re starting to configure your tool—typically the first hands-on step after installation.

GTM Implication

Indicates serious hands-on interest. It’s useful for identifying developers who’ve moved beyond curiosity and are actively trying to get the tool running. Prioritize follow-up if others from the org are active too.

RELATED PLAYBOOK

Find Accounts Interacting with Your Code Commands

Uncover accounts that are actively engaging with your product’s code commands, a strong indicator of technical interest and early-stage integration efforts.

Explore Playbook

RELATED Guide

Capture High-Intent Dev Actions with Code Interaction Tracking

Learn how to track when developers run install commands or execute key workflows—powerful signals of real product usage. This guide shows you how to configure command tracking in Reo.Dev, set up filters, and build segments around developer engagement that actually matters.

Read Guide

Related Playbook Collection

Developer PLG

Identify Accounts with High Purchase Intent on your first party assets like — Docs, Product Trials, Code Interactions, Website Visits

This playbook collection helps you focus on high-potential accounts engaging with your assets, allowing you to segment them based on activity signals, developer behavior, and funnel stages.

Explore Collection

Convert developer-intent signals into revenue

Book a Demo

Ran a setup/init command (e.g., your-cli init, created a config file)

What it Means

GTM Implication

Find Accounts Interacting with Your Code Commands

Capture High-Intent Dev Actions with Code Interaction Tracking

Identify Accounts with High Purchase Intent on your first party assets like — Docs, Product Trials, Code Interactions, Website Visits

Explore Other Signals

Repeat and sustained visits to documentation

Watch - Own GitHub Repo

Logged in multiple times