task-ops
There are two reasons to search for ClickUp kanban, and they are not related. The first is an evaluation: is the board any good, and what does it cost. The second comes from inside, six months after adoption, when somebody notices that the same project has a Board view, a List view, two saved filters, a Table someone built in March, and no agreed answer to the question of which one is the board.
The first question has a short factual answer. The second is the one that decides whether the tool is working, and it is rarely discussed on pricing pages.
The ClickUp pricing page lists Kanban boards, unlimited tasks, unlimited free plan members, collaborative docs, calendar view, sprint management, in-app video recording and unlimited custom views on the Free Forever plan, with 60MB of file storage. Paid plans are Unlimited at 7 dollars per user per month billed yearly or 10 billed monthly, Business at 12 billed yearly or 19 billed monthly, and Enterprise on request.
The board itself is not the thing the plans differ on. Board view is present from the free plan, and the card carries subtasks, assignees, custom statuses and comments. What the plans differ on is the other views, and the ones a project team reaches for when the board alone stops answering the question.
| Free Forever | Unlimited | Business | |
|---|---|---|---|
| Gantt | Trial | Unlimited | Unlimited |
| Timeline | Trial | Trial | Unlimited timeline views |
| Workload | Trial | Trial | Portfolio workload management |
| Custom fields | Trial | Unlimited | Unlimited |
| Guest permission control | Guests must be given full access | Guests with permission control | Guests with permission control |
| Activity history | 1 day | 7 days | Unlimited activity views |
| Chat message history | 30 days | Unlimited | Unlimited |
| Whiteboards | 3 | 10 | Private whiteboards |
| Spaces | 5 | Unlimited | Unlimited |
| Lists per Space | 40 | 200 | 400 |
| Automations per month | Limits apply | Limits apply | 5K |
Two rows deserve attention before any trial starts. The scheduling views a project team wants are marked Trial on the free plan, and Timeline and Workload are still marked Trial on Unlimited. So a team evaluating on free will see Gantt working during the trial period and should not plan around it as a permanent free feature.
The guest row is the other one. On the free plan, the pricing page states that guests must be given full access with no permissions, and permission control for guests starts at Unlimited. For an agency that invites clients into the workspace, that is not a nice to have, it is the reason the free plan cannot be used with outside people.
60MB of file storage on the free plan is enough for text and small images and not enough for a design review. Teams hit it without warning because nobody watches a storage figure until an upload fails. Unlimited storage begins on the Unlimited plan.
One day of activity history is the limit that matters more, and it is easy to skim past. When a client asks who changed a due date on Monday and the question arrives on Wednesday, the free plan cannot answer it. Seven days on Unlimited covers a normal working week. Unlimited activity views begin on Business. Chat message history follows the same pattern at 30 days on free.
None of these are unreasonable for a plan that costs nothing. They simply mean the free plan is a place to evaluate rather than a place to run a client project from, and knowing that in week one is cheaper than discovering it in month four.
Unlimited custom views sounds like generosity, and in a single person's workspace it is. In a team it introduces a failure mode that no plan limit protects against.
A view is a saved question. Board grouped by status answers what stage is this in. Table grouped by assignee answers who is loaded. Calendar answers what is due. Each is legitimate, and each one added is another place a card can be looked at without being understood.
The trouble starts when two views of the same list are configured with different filters. A card that is filtered out of the Board view still exists. Somebody looking at the board concludes the work is finished, because on their screen it is. The card is visible on a view that only one other person opens. Nobody has done anything wrong, and the information is nevertheless gone.
Three symptoms tend to appear together:
This is not a criticism of flexibility. It is what flexibility costs when nobody decided the default. The teams that do well with a configurable tool are the ones that treat a new shared view as a change to a shared agreement rather than as a personal preference.
Four conventions cover most of it, and none of them require a paid plan.
One canonical board per team, and say which one it is. Pin it, name it Board, and make it the view that opens by default. Everything else is supplementary. The cost of not deciding this is paid every day in small confusions.
Personal views stay private. Most tools allow a view to be private to its creator, and a filter built for one afternoon's work belongs there. Shared views are for questions the whole team asks repeatedly, and that is a much shorter list than it first appears.
A shared view needs an owner and a reason in its name. Blocked over 3 days is a name that explains itself. Copy of Board 2 is how a workspace becomes unreadable. If nobody can say why a shared view exists, deleting it is safe, and the shape of the workspace is improved by the deletion.
Limit work in progress on the board, not in a document. A kanban board earns its keep when the in progress column has a ceiling that is visible. The ClickUp pricing page lists setting limits on each stage as part of the board feature set, and a board without a limit is a list drawn sideways.
Reviewing shared views once a quarter and deleting the ones nobody opened takes twenty minutes and is the highest value maintenance any workspace gets.
Custom statuses are listed as part of the customisation set, and they are where board design either helps or quietly hurts. The columns on a kanban board are a description of how the team actually works, so adding one is a claim that a real stage exists.
The failure is the column that never empties. A stage called Waiting, or Review, or On hold accumulates cards that nobody owns, because the status describes a condition rather than a person's next action. Six weeks later that column holds eleven cards and the board has stopped being a picture of flow.
Two habits prevent it. Give every column a rule for leaving it, written down somewhere the team can see, such as review cards move within two working days or go back to in progress. And keep the column count low enough that the whole board fits on one screen without horizontal scrolling, because a stage nobody can see is a stage nobody enforces.
Sprint management is on the free plan, which suits teams working in fixed intervals, and sprint points and reporting begin on Business. For a team not running sprints, the equivalent discipline is a fixed weekly review of the board where every card in the middle columns is either moved or explained. That review is what keeps statuses honest, and no configuration substitutes for it.
Spaces, Folders and Lists are how work is organised, and the free plan caps Spaces at 5 with 40 Lists per Space. Those numbers are generous in the abstract and constraining in a specific way: they encourage deep nesting, and deep nesting is where cards go to be forgotten.
The practical guidance is to keep the structure shallower than the tool allows. One Space per team or per client, one List per project, and Folders used only when there are genuinely too many Lists to scan. Every additional level is another decision someone has to make correctly when filing a task, and another place a search has to be aimed.
It is worth setting this up before importing existing work rather than after, because reorganising a hierarchy that already has views, automations and dashboards pointing at it is considerably more work than building it right the first time.
There is an honest trade at the centre of all this. A tool that can be shaped into anything has to be shaped by somebody, and that somebody usually becomes the person who maintains the workspace. For a team with an operations person who enjoys that work, the flexibility is the reason to choose it, and the automations and dashboards on Business pay for themselves.
For a team of six with no such person, the configuration effort never ends and the workspace drifts. The alternative shape is a tool where the views are fixed and the cards are shared between them, so that a board, a schedule and a calendar are the same work seen three ways rather than three things to keep in step. Tools that ship kanban, Gantt, calendar and resource views over one set of cards are making that trade deliberately: less to configure, and less to keep aligned.
Cost follows the same logic. Comparing 12 dollars per user per month for Business against a plan whose scheduling views are included from the start is not a like for like comparison of software volume. It is a comparison of how much of the tool is being paid for and how much is being administered. A side by side look at the mainstream options is the fastest way to see where each one draws that line.
Open the project that prompted the search and count the shared views on it. If there are more than three, pick the one that is authoritative, rename it so that is obvious, make every other shared view private or delete it, and tell the team which one to open. That costs half an hour and fixes most of what feels wrong about a busy workspace. If the count was already low and the missing piece is a timeline the whole team can see without a paid upgrade, a free plan that does not hold the scheduling views back is worth an hour of comparison.
Yes. The pricing page lists Kanban boards, unlimited tasks, unlimited custom views and calendar view on Free Forever, along with 60MB of file storage. The views that are restricted on the free plan are the scheduling ones, with Gantt, Timeline and Workload marked as Trial.
At list prices, Unlimited is 7 dollars per user per month billed yearly, so ten people is 70 dollars a month, and Business is 12 dollars per user per month billed yearly, so 120 dollars a month. Billed monthly rather than yearly, the same plans are 10 and 19 dollars per user. Enterprise pricing is quoted on request.
Three shared views is a reasonable ceiling for most teams: one board, one schedule, and one list or table for taking stock. Anything beyond that should be private to the person who made it. The number itself matters less than having one view that everybody agrees is authoritative.
They can be invited, but the pricing page states that guests on the free plan must be given full access with no permission control, and guest permission control starts on the Unlimited plan. For client work where an outside party should see one project and nothing else, that puts the free plan out of scope.
Almost always because two views of the same list have different filters. Someone searches a view that excludes the card, does not find it, and creates it again. Reducing the number of shared views and agreeing which one is authoritative removes the cause rather than the symptom.