claude-code-growth-os CLAUDE.md

Claude Code Growth OS — Project Config

This project uses Claude Code as a go-to-market operating environment — marketing, sales, product, and retention run as one motion, not four silos. The kit spans all four functions across both sides of the bowtie: acquisition on the left, and the post-sale half (onboarding, adoption, renewal, expansion) on the right. Plain-text playbooks in ops/, rituals as commands in .claude/commands/, go-to-market skills in .claude/skills/. The handoffs that connect the four functions — H1–H6 plus the loop close — are mapped in docs/operating-model.md.

Conventions

• Markdown is the source of truth. Operating playbooks live in ops/ as plain markdown. Edit them like docs; commit them like code.
• Both sides of the bowtie have a surface. The left side is ops/pipeline.md (deals); the right side is ops/customers.md (the post-sale account book) and ops/roadmap-signals.md (product's triage queue). The renewal motion starts at day 60, not day 85.
• Rituals are commands. A recurring task — a morning briefing, an end-of-day wrap-up — is a slash command in .claude/commands/. Invoke it by name.
• One ritual at a time. Don't port your whole working life on day one. Pick the task you dread most, make it a command, run it daily for a week, then add the next.
• Commit often. Your ops get a history. git log ops/ is your audit trail.
• Straight answers. When a session evaluates your work — a plan, a draft, a pipeline read — the assistant's first duty is an accurate assessment, not an agreeable one. Verdict first, then reasons; plain disagreement before you decide; alignment once you have decided. Hedges express real uncertainty, never politeness.
• Plain language first. The plain statement carries the meaning; the specialist term is a label attached after it, never the sentence itself. This applies to internal output too — headings in your playbooks, PR titles, commit messages, the summary a ritual hands back — not just customer-facing copy. Avoid the audience exemption ("they're technical, they'll know it"): that is what you grant yourself at the moment you most want the jargon. The test is mechanical — delete the specialist word and see whether the sentence still stands. If it collapses, the word was doing the sentence's job. A position nobody can restate from memory is not governing anything.