We know it works because we use it to build itself
Every feature of Eigthseat goes through the board, the seats and the gates, the same ones you'll use. If the product is bad, our own roadmap slows down.
How it works for us
The founder writes a ticket. The seats plan it, build it on a branch and open a pull request. Quality runs the tests and the pull request's CI. The founder reads the summary and the diff, then merges.
Early on there was nothing to run the tickets, so we built a small bridge first: eigthseat mcp lets a Claude Code session take the next job from the board and report back. From that point the build plan lived on the board, and the product started working on itself.
Branches named eigthseat/EIG-… in our repository are those tickets, and the history is there to read.
Tickets the team has shipped on our own repo
EIG-68The helper runs checks and opens pull requestsEIG-69Move a ticket back to BacklogEIG-70Pick the model by ticket complexityEIG-71Deploys build the image on the serverEIG-72Hard rule: no emoji in design, UI or copyEIG-74New tickets start in BacklogEIG-89The price, terms, privacy and refund pages on this siteEIG-91QA findings reach the Engineer on rework
A sample, not the full list. The pages you're reading sit on the same pipeline.
What still needs a human
The foundations were built by hand, before there was a board to put tickets on. The plan, the design and the architecture decisions are the founder's.
The founder reads and merges every pull request, and sends work back when it isn't right. Quality's retry cap and the gates exist because the seats do get things wrong. We'd rather show you that than hide it.
Try the same team on your project
30 days free, then $9 a month.