Who it’s for
Tarsen is built for founders and small teams: the people who open the same board every morning, own every project on it, and have to decide what to do before the day gets away from them. It is not trying to be the system a whole company runs on. Being clear about that up front saves everyone a trial.
It fits well if
- You are working alone across a few projects, or running a team of two to twenty.
- You end most days unsure whether you worked on the right things.
- You want your work planned, not just listed. Mission Mode picks a realistic day from what is actually on the board and the hours you actually have.
- You work from the board daily and care that it is fast. You notice lag, and you would rather press a key than find a menu.
- You want an AI assistant that can see your real work, either inside the app or through your own Claude over MCP.
- You have outgrown a single Trello board but have no interest in Jira.
- You want to be able to take your data out whenever you like, in a format that means something.
Who it works for in practice
| Why | |
|---|---|
| Founders and solo operators | One person, several projects, and a daily plan that decides what to actually do. My Work and Inbox mean you stop holding it all in your head. |
| Small software teams | Card references like TAR-102, priorities, estimates, blocked states with a reason, and sub-cards. Enough structure to run a sprint without a process consultant. |
| Agencies and studios | A project per client, with private and member-only projects so a client’s work is not visible workspace-wide. Labels and saved views to slice by client or stage. |
| Remote teams | Live updates, presence on the board, comments with mentions, and push notifications that reach your phone rather than sitting in an inbox. |
It is probably the wrong tool if
We would rather tell you now than have you find out in week three:
- You need dependency management and a critical path. There is a timeline view showing how cards overlap, but nothing models one card blocking another's schedule.
- You need time tracking and billing. Estimates exist; timers and invoices do not.
- You need custom fields or per-team workflow automation. The card shape is deliberately fixed, and there is no automation engine.
- You need forms, portfolios, resource management or an org-wide reporting layer. That is a different category of product.
- You are a large organisation needing SSO enforcement, SCIM provisioning and audit exports. Single sign-on works through Clerk, but the enterprise administration around it is not built.
If one of these is the only thing stopping you, it is worth asking where it has got to. The list above is kept honest deliberately: finding this out in week three is worse for both of us.
What people usually notice first
- The command palette. ⌘K reaches almost everything, and most of the app can be driven without the mouse.
- Mission Mode. It reads your board, your due dates and your capacity, and proposes a day you could actually finish.
- That it is quiet. No badge on every surface, no daily digest you did not ask for. Notifications are per workspace and per category.
- How little there is to configure before it is useful.
Something missing here? Email support@tarsen.co and we’ll write it.