fenbs for founders: the backlog before you have a team
A single board for the product you are building, with your AI assistant as the first team member and a place for early users to report what breaks.
Last checked
The board is the roadmap
Before there is a team there is a list. Features you mean to build, enhancements users asked for, bugs you found at midnight. Three kinds, four lanes, a number on each so a tweet or a support reply can say “that is BU-023, it is In Progress”. Priority is a number from 1 to 10, and Next Up is what you have committed to. That is the whole roadmap, and it fits on a phone.
Your first hire is an assistant
Connect Claude Code or Cursor to the board over MCP and give it a role. It files bugs from failing tests, moves what it ships, comments with what it did, and reads your AI context first so it knows how you want things done. When you hire a person, they join the same board with a role of their own, and the history already shows how the work has been going.
Let users in, a little
The smallest role lets a person add tasks and comment. Give it to the five users who email you most. Their bug reports land on the board with their name, numbered, instead of in a thread you will lose.
How to try it
Do not evaluate a simple tool with a demo project. Paste in the real list you are working from this week using Add many, add the one person who most often tells you about problems with a small role, connect the AI assistant you already use, and work from the board for a week. At the end ask one question: is the board still true? Your own board is free, so the trial costs nothing but the week.