How ZeroWidth works
ZeroWidth reads the decisions your team already writes down, checks each decision against your numbers, and tells your agents what worked.
Your first week
- Day 1Connect
Start ZeroWidth on a computer or a server, and connect your team's AI agents. From then on, agents report new decisions as they're made.
- Days 2 and 3Bring in what already happened
ZeroWidth shows what reading your past chats and documents would cost, before reading anything. Nothing is read until you say yes, and never past a spending limit you set.
- Days 4 and 5Review the decisions ZeroWidth kept
Read the decisions ZeroWidth found. A decision read wrongly is corrected with a retraction, so nothing is ever quietly edited.
- From then onA check before every decision
When a similar decision comes up, ZeroWidth shows what happened last time.
ZeroWidth reads decisions from your team's tools, and shares the results with your team and your agents.
ZeroWidth reads decisions from
- Chats with Claude and ChatGPT
From the export file each app gives you.
- Slack and Notion
From a workspace export.
- Google Docs and Word
Documents and their comment threads, with who wrote each part.
- GitHub, Jira and Linear
Commits, issues and pull requests, and how each one ended.
- Meetings
Transcripts, with who said what.
- Email
Only the labels your team chooses to share.
- Coding agents and other AI agents
Claude Code sessions, and any agent reporting decisions as they're made.
- Your numbers
From Stripe and the other tools your team already uses, or from a CSV file.
ZeroWidth shares what worked with
- Your AI agents, before they act
Agents look up past decisions over MCP.
- Your team, in the ZeroWidth console
Every decision, the part of the business it touched, and how it turned out.
- Your own tools, through an API
The same record the console reads.
- A file you can export at any time
All of your decisions as one file, with or without the original text.
ZeroWidth checks each decision against your numbers.
After a decision, ZeroWidth compares your numbers with how they usually move.
Acme's daily signups
- The goal and the guardEach decision gets the number it should move and which way, plus anything that must not get worse, like signups during a price rise.
- BeforeEach number's history sets what the weeks ahead would look like with no change.
- AfterWhen the time is up, what happened is compared with that. Nothing is judged early.
- The usual swingA change counts only when a number moves more than it does in ordinary weeks.
- Worked. A number moved the right way, and none moved the wrong way.
- Mixed. One number moved the right way and another moved the wrong way.
- Didn't work. No number moved the right way, and at least one moved the wrong way.
- No clear change. No number moved more than usual.
- Too early to call. The deadline hasn't passed yet, or too few numbers have come in.
- Can't tell. Nothing fair to compare with, such as no numbers from before the decision.
ZeroWidth works with any AI agent
ZeroWidth uses MCP, the standard way AI agents connect to tools. Claude Code, Claude Desktop and other agents check past decisions before they act, and tell ZeroWidth about new decisions.
Connect Claude Code
With ZeroWidth running on your computer. On a company server, agents connect over your network with a token. Hosted ZeroWidth will give each team one address.
Terminal
$ claude mcp add --transport http zerowidth http://127.0.0.1:4380/mcp
Agents look up decisions, report decisions and answer questions
- Look up past decisionsOn a topic, a part of the product or a number.
- See the best and worstOver any stretch of time.
- Report a decisionAs the decision is made, with the goal behind the decision.
- Answer open questionsWhen ZeroWidth can't tell what happened, the agent can say.
Put your team's decisions to use.
Have a signup code? Start with your code