For small teams
A shared board with clear membership
The problem
What gets in the way
A shared spreadsheet works until two people edit it and nobody knows who owns the row. Chat is worse: decisions disappear. You do not need Jira. You need members and a board.
What changes
After you start using it
- 01
Membership and roles live on the workspace
- 02
Guests can see one project without seeing every project
- 03
Board, list, timeline, calendar, and channels show the work without a second tool
Workflow
Stand up a team workspace
- 01
Create the workspace. Invite people by email. They sign in with Discord or email and password.
- 02
Add a project for the workstream. Set statuses that match how you already talk about work.
- 03
Use guests when someone should see one project and nothing else.
What you use
Capabilities in this job
- 01
Projects
A workspace holds projects. A project holds statuses and tasks. The board is the live view: columns are statuses, cards are tasks. List, timeline, and calendar show those same tasks. A canvas sits on the project for the sketch that is not a task yet. Templates start the next card from work you already shaped. Opening a task uses the inspector so you stay on the view.
- 02
Chats
Public and private channels sit next to the projects. Threads and reactions stay in the channel. A project can have a linked channel so the conversation about that work has a home. Turn chats off if the team already talks somewhere else.
- 03
Automation
Build a workflow for a job you already repeat: a trigger, a branch, a wait, a note to the team. Triggers include a manual run, a webhook, a schedule, and events from the workspace. An AI agent node calls OpenAI or Anthropic with a key you store, and it can use tools including an outbound MCP server. Separately, create a scoped API key, register a webhook, or connect Claude or ChatGPT to the workspace over MCP. There is no Slack, Zapier, or Jira app.
Questions