The Branching Company
Source control for the slides, skills, and docs you ship.
For the forward-deployed engineers, consultants, and agencies who ship a different deck, prompt, and SOP to every client—where a shared drive and a Git repo aren't enough.
Surfaces
Wherever the artifact lives.
Branching lives there too.
Install the Chrome extension. Branching reads what you're working on—deck, skill, or doc—and shows you a tree of every variant you've ever shipped, who it went to, and what changed.
PowerPoint
Branch a deck. Diff every slide. Roll back without losing work.
Google Slides
Fork the master for one client. Merge the polish back later.
Gamma
Diff every regenerate before it overwrites your hand-tuned slide.
Canva
Track who edited the brand template, when, and what they changed.
Skills
skills.mdDiff prompt, tools, and model in one view. Run evals before you ship.
Docs & SOPs
Refund tiers, intake flows, pricing rules. One source of truth across every agent that reads them.
The Problem
Git was built for code.
You ship everything else.
You send the same deck twelve different ways.
A consultancy customizes the same pitch deck for twelve prospects: a logo swap, a price slide tuned in a Slack thread three months ago, a benchmarks chart updated in one variant and forgotten in the other eleven. The deck Acme saw is not the deck Globex saw, and nobody on the team can tell you exactly why anymore.
An agent just edited your skill. You can't see what changed.
An MCP-connected agent rewrote your refund-policy skill on Monday morning, and the diff—what prompt got tightened, which tool got swapped, what threshold moved—exists nowhere a human can read. You find out it changed when a customer asks why their refund was denied, three days and forty support tickets later.
Git asks you to merge a deck like it's a function.
A skill is a markdown file plus a system prompt plus an MCP server config plus an eval suite plus a model choice; a deck is a thousand binary nudges and a brand kit; an SOP is a tree of policies other artifacts depend on. Git asks you to merge any of them like a code change and pretends a binary diff is a useful review.
Your refund policy says three different things.
Three tiers—auto-refund under $5, auto-deny on prior abuse, manual review otherwise—written into one master SOP and forked across four agents. Last quarter someone bumped the master ceiling to $10, didn't tell the others, and finance flagged the line when two clients got the new threshold and two didn't.
Version every artifact.
Not just the code beneath it.
Visualize
Every artifact, every variant, every client on one graph: the deck Acme saw, the skill the support agent runs, the SOP that fired on Tuesday's refund. You see what your next change touches before you ship it, and what an agent already changed before a customer reports it.
Branch
Fork a deck for one client, fork a skill to test a tighter prompt, fork an entire policy tree to try a refund threshold against last quarter's tickets—keep what works and throw away the rest without losing it. The graph remembers everything you tried, the customer who asked for it, and which variant won.
Ship
Promote a deck from staging to one client to all clients with the same review-and-approve flow you'd want for production code—tag every release, diff slides, prompts, tools, and policies side by side, roll back instantly. Nothing reaches a customer without passing the gate.
Verify
Catch the drift before the customer does: run the new refund policy against the agents that handle intake and support, and if they answer differently for the same case, you see it in the graph before the change goes live. Every policy you ship is checked against every artifact that reads it.