One repo for GTM, ops, sales, finance, and the agents working in them.
and any MCP or CLI agentChatGPTJonas
#go-to-market24 membersClaude APP 2:04 PMDone. Proposed an edit to ops/runbook.md
gtm
launch-plan.md
pricing-onepager.pdfsales
pipeline.csv+12 −3call-notes.mdopsrunbook.md+3 −3financebudget-2026.csvboard-deck.pdfv4 → v5skillsresearch/SKILL.mdClaudeMaraCompanies set up GitHub repos for good reason: one source of truth, real review, agents that ship. But GitHub is built for software engineers. Everyone else hits three walls.
Clone, branch, stage, commit, open a PR, resolve conflicts. That workflow is built for engineers shipping code. Everyone else just needs to make a change and move on.
Git chokes on big binaries. The launch video, the board deck, design files: everything needs LFS, a bolt-on with size limits, extra setup, and its own bills.
Access is per-repo, all or nothing. No view-only, no finance-only folder, no approvals. Anyone who is in can change anything.
gtmEveryone · editsalesEveryone · editfinancesalaries, board decksEveryone · editSuggest a change, the owner accepts or rejects it. Checkpoints instead of commits. No branching to learn.
One history for the 2.1 GB launch video, the board PDF, the pipeline CSV, and the launch plan. Prose diffs as prose, spreadsheets diff row by row, large assets keep every version. No size limits, no LFS setup.
launch-video.mp42.1 GB · v3 · no LFS neededlaunch-plan.md34 edits · +9 −4 todaypipeline.csvrow-level diffs · +12 rowsboard-deck.pdfevery version kept · v5logo-lockup.pngcompare versions side by sideNon-developers want a simple mental model: make a change, it lands in one linear history. Branching and async review are supported for workflows that need them.
Mara's Claude edited gtm/launch-plan.mdjust nowJonas's ChatGPT updated sales/pipeline.csv2 min agoCodex uploaded finance/board-deck.pdf14 min agoMara's Claude edited kb/refunds.md1 hr agoWho can see, who can edit, who approves. Git hosts control who can push, not who can see. There's no “finance can read this folder, sales can't.”
gtmEveryone · editsalesSales team · editEveryone · viewfinanceFinance onlyMara approvesskillsEveryone · viewproposals onlySee which files and skills your agents actually read and use. Know what context matters and what is dead weight.
skills/research/SKILL.md214gtm/icp.md131sales/pipeline.csv89ops/runbook.md56brand/old-deck.pdf0Everything a 5–20 person startup runs on that isn't source code.
skills/The SKILL.md files and prompts your agents run on. Diff each revision; roll back the edit that broke behavior.
gtm/Launch plans, messaging, positioning docs, the pricing one-pager. Agents keep them consistent with each other.
sales/The pipeline CSV, call notes, proposals. An agent updates the pipeline after every call. You review the diff.
ops/Runbooks, vendor lists, onboarding checklists. The files that answer "how do we do this here."
finance/The budget, the model, board decks. Every version kept; every change attributed.
kb/Policies, FAQs, product facts. The answers your team and agents rely on, kept current and trustworthy.
Your source code stays in GitHub. LixRay is for the repos that are not source code.
github.com/acmefrontendbackendsource code
lixray.com/@acme/companygtmsalesopsfinanceskillseverything else