Product
Solutions
Resources
Pricing
Self-host
Plane
View demo
Sales
Contact sales
Login
Get started free
Get started free
See Plane in action
How teams and agents use Work, Wiki, and AI
Watch the demo
6 min 16 sec
Try Plane Business for 14 days
Talk to a human →
Jump to a chapter
01
Introduction
0:00
02
Work
0:26
03
Types and workflows
1:15
04
Wiki
1:58
05
Plane AI
2:50
06
Agents
3:19
07
Initiatives and dashboards
4:11
08
Integrations
4:55
09
Moving to Plane
5:20
10
Recap
5:50
01
Introduction
0:00
0:02
Plane brings Work, Wiki, and AI into one workspace, for teams and agents.
0:09
It's quick for the people doing the work, and structured enough for the company that depends on it.
0:18
Let's follow one feature from spec to release, across product, design, and engineering.
02
Work
0:26
0:26
Everything in Work starts with a work item. Give it an owner, a priority, and a date, and it's on the board in seconds.
0:37
Most things are a shortcut away. Press Command K to search across projects, create something new, or change a state without reaching for the mouse.
0:48
The same work reads the way each person needs it: a board for the team, a table for the planner, a timeline for whoever owns the date.
1:00
A cycle holds what the team means to ship in the next two weeks, and shows how far along it is.
1:08
Larger work breaks into epics and sub-work items, with dependencies drawn on the timeline.
03
Types and workflows
1:15
1:15
When your process needs more structure, you add it yourself.
1:20
Each project names its own states, so engineering and design can each work in stages that fit them.
1:28
Create a work item type, like a bug, and give it the properties that kind of work needs.
1:35
A workflow sets which moves between states are allowed, and who can make them.
1:43
Requests from outside the team arrive through Intake, by form or by email, and wait there until someone accepts them.
1:53
All of it is built in, and each project sets its own.
04
Wiki
1:58
1:58
Work makes more sense with the thinking behind it. In Plane, that thinking sits beside the work.
2:06
Wiki holds guidance for the whole company, like the checks every release has to pass. Each project keeps its own pages for specs and decisions.
2:17
This spec holds a decision for the release: a saved cart is kept for thirty days. People write together in real time, and discuss a passage right where it sits.
2:29
When a decision means more work, select that line and turn it into a work item. Give it an owner, add it to the cycle, and link the spec.
2:43
Whoever picks it up can open the spec and see the decision behind it.
05
Plane AI
2:50
2:50
Because work and knowledge share one workspace, Plane AI can draw on both.
2:57
Ask what's still open for the release, and it answers from your work items and pages.
3:05
Then ask it to act. In Build mode, it shows every change it plans to make. Read each card, keep the ones you want, and nothing changes until you confirm.
06
Agents
3:19
3:19
Agents go a step further. Each has its own instructions and its own place in the workspace, so you can mention one in a comment or assign it a work item, as you would a teammate.
3:31
Here, the review agent is asked to check a work item against the rule in the spec. It replies in the thread: how long the cart is kept is missing.
3:43
The product lead checks that against the spec, and adds the rule to the work item. The agent found the gap, a person decided what to do about it, and the engineer now has a written requirement with the decision one click away.
3:59
Agents can also start on their own, when a work item changes or on a schedule. You choose which projects each one can reach, and how many credits it can use a month.
07
Initiatives and dashboards
4:11
4:11
As more teams join, the question changes from what is my team doing, to how is the whole release going.
4:20
An initiative connects the projects behind one goal, and shows their progress together.
4:26
Project updates say where each project stands, in the lead's own words. Here, design is waiting to hear how long a cart is kept. Open its work item, add the confirmed wording, and link the spec. The designer now has the decision they need.
4:45
Dashboards chart work from any set of projects, and recompute each time you open them. The numbers come from the work.
08
Integrations
4:55
4:56
Plane connects to the tools your teams already use.
5:00
Map pull request stages to states, and a merged pull request moves its work item to done.
5:09
In Slack, turn a message into a work item, or mention Plane in a thread to ask how the cycle is going.
09
Moving to Plane
5:20
5:21
You don't have to start from an empty workspace. Plane's importers bring your work items across, with their states, priorities, and comments.
5:30
Start with one team and a project they're already working on. Bring its spec, assign the next work items, and try a real handoff. Run it beside what you have today, and decide what else to move once you've seen how it fits.
5:46
Use Plane on our cloud, or host it yourself.
10
Recap
5:50
5:50
Work, Wiki, and AI, in one workspace.
5:55
Quick for the people doing the work. Structured for the company that depends on it. And ready for agents to work alongside them.
6:04
Try Plane Business on our cloud, free for fourteen days, with your team. No card needed.
Try Plane Business for 14 days
Talk to a human →
Read the transcript
Share this demo
