Tana is an agentic meeting platform built for teams. You hold your meetings in it, and as you talk the AI turns the conversation into finished work, a filed bug, a logged decision, a drafted recap, that you review before anything lands.
You are starting with a clean slate, and that is fine: you do not need to fill it first, because the conversation is the input. The single best way to see what Tana does, and the move that matters most, is to run a meeting with a colleague.
Run your first meeting, with someone
You need no setup and no existing notes. From the Today view, open the create menu (the pencil icon in the sidebar) and choose Meeting to get a call link. Invite a teammate from your organization, or send the guest link to anyone outside it, they join with just a name, no account. Then click Join Meeting.
Have a real conversation, a planning chat, a bug triage, a quick design look. You are not taking notes. When something concrete comes up, hit the + in the call toolbar, pick how far back to look, and choose what it is, a bug, a decision, a task, and Tana drafts it from that part of the talk. When the call ends, it writes the summary and pulls out anything you missed.
You review each outcome, edit what is off, and accept what you want. Because the meeting is shared, everyone in it has that work right away. That is the whole point: a conversation becomes finished work your team can act on, with no write-up.
Try it on your own first
Want a quick taste before you pull anyone in? Start a chat from Today and ask the AI to make something from scratch:
- "Draft a one-page PRD for a referral feature."
- "Turn these rough notes into a project plan." (paste the notes)
- "Outline a technical spec for a rate limiter."
Everything it produces is yours to review and keep. Chat gets far more powerful as you go, once you have meetings and have connected tools like GitHub or Linear, it draws on everything your team has done and acts in the tools you already use.
What is worth knowing early
- The AI proposes, you decide. Everything you would act on, outcomes, docs, edits, lands as a proposal you review and approve first. The one thing it writes for you automatically is the meeting summary. That control is what makes it safe to let the AI do real work.
- Everything you create stays in your Library, findable from the start. No setup, and nothing gets lost.
- Add structure only when it earns its keep. Once you are making many of a kind, bugs, clients, decisions, give them a type so they share fields and land on a board. When a body of work needs its own people, put it in a space, and where something lives is also who can see it.
- It compounds. Every meeting and chat feeds your shared context, so a few weeks in you can ask "what did we decide about this, and why" and get an answer grounded in your team's actual work.
Get your team in
This is the step that changes everything. Tana is built for working together, and almost nothing about it is as good alone: shared meetings, shared outcomes, a context that the whole team builds and draws on. Invite the people you actually work with, and the next meeting you run together already produces work everyone has, while the AI gets sharper about your decisions, your roadmap, and your code with every conversation.
When you are ready for the daily rhythm, How to work in Tana goes deeper.