TrackCTL

Concept alignment — fresh start after desk-flip · 2026-05-21

Value Wedge

The only product analytics tool an AI coding agent can fully configure, deploy, and manage without ever opening a browser. An agent runs init, edits YAML, runs deploy, and analytics are live.

Primary Beneficiary

Agent-native developers — developers who routinely use AI coding agents (Claude Code, Cursor, Codex) and want their agent to handle analytics setup alongside code generation. Their pain is binary: their agent literally cannot set up analytics today.

Validation Gate

An AI agent (Claude Code or Codex) successfully runs init / deploy / check against a real PostHog Cloud project with zero human intervention.

Must happen in week 1

Scope

Ships now (CLI)
  • trackctl init
  • trackctl deploy
  • trackctl check
  • YAML config schema
  • Lockfile state management
  • PostHog API client
Deferred
  • Browser SDK
  • Managed hosting
  • Web dashboard
  • Enterprise governance
  • CI/CD integration
  • Auth layer

Riskiest Assumptions

HIGH A4: An AI agent can complete init/deploy/check with zero intervention
MEDIUM A2: Agent-native developers are a meaningful and growing segment
MEDIUM A3: Click-ops analytics setup is painful enough to drive adoption
RESOLVED A1: PostHog API covers enough for config-as-code (full CRUD confirmed)

What Changed from Old Brief

Scope 3-package monorepo (CLI + SDK + web) → CLI-only, single package
Beneficiary Solo devs broadly → Agent-native developers
Validation Phase 18 of 18 → Week 1
Roadmap 18 phases planned upfront → Build minimum to validate, then decide

Generated by /concept-exploration · Prior research archived at archive/research/