GTM OS

GTM OS gives founders and commercial teams one shared folder for how they sell, market, and work with customers. It installs brand, market, strategy, accounts, playbooks, team context, and active work, so people and supported agents can reuse the same go-to-market context in every session.

What folder structure does GTM OS install?

gtm-os/                           # One shared home for your go-to-market├── README.md                     # The GTM index and starting point├── foundations/                  # Stable context behind commercial decisions│   ├── brand/                    # Messaging, positioning, and voice│   ├── market/                   # Audience and market context│   ├── product-marketing/        # Product truth and sales narrative│   └── strategy/                 # The go-to-market strategy├── accounts/                     # Customer briefs and relationship health├── playbooks/                    # How the team approaches recurring GTM work├── templates/                    # Reusable formats for launches and campaigns├── team/                         # Teammate profiles and working styles├── work/                         # Campaigns, projects, content, and research in flight├── .agents/commands/             # Onboarding, account, review, and upkeep workflows├── lessons.md                    # What agents should do differently next time└── log.md                        # A concise history of meaningful work

• Stable foundations keep brand, market, product, and strategy close to the work they shape.
• Playbooks and templates turn the team's best methods into reusable starting points.
• Shared instructions, lessons, and history help different agents work from the same rules and past decisions.
• Built-in workflows cover onboarding, accounts, teammates, reviews, and upkeep.

How do you bring in the GTM context you already have?

Say "set me up," then give GTM OS the best context you already have:

• Use a connected source such as Palette's Context Library to bring in company, customer, team, and active-work context.
• Drop positioning documents, sales decks, research, account exports, and other material into _inbox/.
• Use a built-in copy-and-paste prompt to bring useful context over from ChatGPT, Claude, Notion, or another tool.
• Answer one short round of questions about your company, market, brand, and team.

Your agent sorts that material into foundations, accounts, playbooks, team context, and active work, then confirms any gaps before replacing the template. Palette Desktop creates a checkpoint before installation, so you can restore the folder if you want to start over.

How does GTM OS work with different AI agents?

GTM OS keeps your brand, market, product story, accounts, playbooks, and active work in ordinary Markdown files that Claude Code, Codex, Gemini, and other supported agents can read. Shared instructions help each agent work from the same GTM context instead of relying on a separate prompt for each tool.

The same context supports sales, marketing, and customer work. One agent can prepare an account call, another can draft a launch, and both can use the same positioning, voice, customer history, and team decisions.

What can you ask once GTM OS is set up?

Once the GTM context is in place, any supported agent can use it for the sales, marketing, or customer work in front of you:

• "Help me bring our positioning, brand voice, and campaign history over from Notion."
• "Prepare me for the Acme call using our account history and sales approach."
• "Turn this product update into launch messaging for our audience and voice."

company-os/├── accounts/       # customers, relationship health├── gtm/            # brand, playbooks, active work├── product/        # strategy, specs, feedback├── engineering/    # architecture, decisions, runbooks├── ops/            # finance, hiring, admin└── people/         # teammate context

accounts/├── accounts.md     # roster, owners, next steps├── approach.md     # your sales approach├── _template/      # source for new accounts└── <company>/      # one folder per account    ├── health.md   # risks, relationship health    └── meetings/   # notes and follow-ups

content/├── content.md      # drafts and published work├── playbook.md     # how your team creates content├── voice.md        # tone, language, self-check└── drafts/         # work in progress    ├── README.md   # the structure for each draft    └── <piece>.md  # one channel-aware draft