The problem
Why this system exists
AI work becomes inconsistent when company context is scattered across chat history and every session begins with the same explanations.
Company OS
GTM OS Kit
A Company OS starter kit that gives Claude persistent business context, reusable GTM skills, workflow commands, and safety hooks.
The outcome
What it produces
A portable, version-controlled Company OS centered on CLAUDE.md, supported by structured business context, playbooks, reusable skills, hooks, and workflow commands.
System overview
How the playbook moves from input to outcome.
Each stage has one job. The sequence stays visible while the active state moves through the system.
01
Clone
Bring the blueprint, skills, and optional plugin into your project.
02
Interview
Let Claude collect the company context it needs.
03
Structure
Organize company files, wiki pages, and operating rules.
04
Equip
Add reusable skills, hooks, and workflow commands.
05
Compound
Commit improvements so the shared context grows over time.
01
Company context
Positioning · team · stack · voice
02
Reusable skills
Copy · ICP · strategy · discovery
03
Safety hooks
Guardrails · logs · notifications
04
Workflows
Plan · work · review · compound
Loads firstCLAUDE.mdThe hub that points Claude to every other part of the Company OS.
Inputs
What the system needs
- Company overview and positioning
- Team, tools, and processes
- Brand voice and design rules
- Existing SOPs and raw knowledge
Outputs
What comes out
- A populated CLAUDE.md
- Structured company context
- GTM skill library
- Safety and session hooks
- Repeatable workflow commands
Inside the repository
The important pieces, without the file-system noise.
The explainer shows the operating structure. The repository remains the source of truth for complete setup and implementation details.
gtm-os-kit/
- 01CLAUDE.md: the Company OS entry point
- 02blueprint/company/: company, team, stack, voice
- 03blueprint/wiki/: playbooks, onboarding, processes
- 04blueprint/hooks/: safety, logging, notifications
- 05gtm-skills/: five reusable starter skills
- 06plugin/: planning, work, review, and compound commands
Guardrails
What the system deliberately protects.
- Safety hooks can block dangerous tool calls.
- Secrets and credentials stay outside committed context files.
- Plain Markdown avoids proprietary knowledge formats.
- Git history makes changes reviewable and reversible.
Quick start
From repository to first useful run.
- 01Clone the kit and copy the blueprint into your project.
- 02Open the project in Claude Code.
- 03Ask Claude to interview you section by section.
- 04Review the populated business context.
- 05Add the skills and hooks your team needs first.
Adapt the system
Want a version built around your market, tools, and sales process?
Keep exploring
Related playbooks
Claude Code SkillsOpen source
GTM Flywheel
Fifteen structured Claude Code skills that turn ICP research, signal scoring, outbound copy, campaign analytics, and sales intelligence into one compounding GTM system.
ICP Research
Signal Scoring
Cold Email
A versioned set of operating skills with scoring models, decision trees, templates, and quality checks that Claude Code can apply consistently to your own data.
Sales EnablementOpen source
Microsite Pipeline
Turns one sales lead into a researched, personalized eight-page sales microsite and PDF using sourced company data.
Lead
Enrich
Synthesize
A repeatable local pipeline that researches a company, generates TAM, ICP, and sales-signal insights, then renders an on-brand HTML page and PDF without fabricating missing data.