fenbs vs Basecamp: two opinions about simple
Basecamp and fenbs both refuse to become Jira. Basecamp does it with to-do lists, message boards and a calm philosophy; fenbs does it with one board, roles, and an AI assistant that can work it.
Last checked
The short answer
Basecamp organises a project as a set of tools — to-do lists, a message board, a schedule, docs and files, a chat room — and has been arguing for calm, simple work for twenty years. fenbs agrees with the argument and picks one tool: a board. If your work is mostly communication with some tasks, Basecamp. If your work is mostly a list of things to build and fix, and you want an AI assistant working it with you, fenbs.
Where Basecamp is better
- Communication. Message boards, group chat, check-in questions and a schedule live next to the to-dos.
- Docs and files as first-class parts of a project.
- Many projects for a company, with people in and out of each.
- A long track record and a strong point of view about calm work.
Where fenbs is better
- The board itself. To-do lists say what; a board says where each thing is. Four lanes, fixed.
- Three kinds of task with colours that mean kind, so a list of bugs looks like a list of bugs.
- AI assistants as members. Claude, ChatGPT, Cursor and Claude Code connect over MCP, hold your role, and every change is signed. Basecamp does not have a seat for one.
- Roles that narrow per person, so a client can report and comment and nothing else.
- Stable references — BU-014 — you can quote anywhere.
How to decide in ten minutes
Paste this week's real list into a fenbs board with Add many, connect the AI assistant you already use over MCP, and work from it for a few days. If the board is still true at the end of the week, it is doing the job. If you kept reaching for something Basecamp has and fenbs does not, that is your answer too, and it is a good one.