ClickUp vs Asana vs Jira for teams under 20 (2026)

We are a two-person operations consultancy in Toronto. We do not resell any of these tools, and we have set up, lived in, and torn out all three for clients. This sheet covers verified June 2026 pricing, where each tool is annoying in daily use, what a migration costs you, and when the honest answer is none of the above.

What they cost in June 2026, verified

We pulled these numbers from the three vendors' pricing pages in June 2026 and cross-checked them against four independent pricing trackers. All prices are USD per user per month. All three bill Canadian teams in USD, so add the exchange rate before you budget in CAD.

ClickUp

• Free Forever: $0, unlimited members and unlimited tasks, but 60 MB of total file storage for the whole workspace. That is a few PDFs and one client logo pack.
• Unlimited: $7 billed annually. Trackers list $10 on monthly billing.
• Business: $12 billed annually. ClickUp does not display the monthly rate on its pricing page; you discover it at checkout. Third-party trackers listed it between $13 and $19 in June 2026.
• Brain AI add-on: $9 per user per month on top of any paid plan. The larger "Everything AI" bundle is $28.
• Automation: capped per plan per month. The pricing page lists 5,000 runs a month on Business, and ClickUp has changed plan limits mid-cycle before, so do not architect anything that assumes the cap is permanent.

Asana

• Personal: $0, but capped at 2 users for accounts created after November 12, 2025. Older accounts keep a legacy 10-seat free tier. The 10-person free Asana you remember no longer exists for new signups.
• Starter: $10.99 billed annually, $13.49 monthly.
• Advanced: $24.99 billed annually, $30.49 monthly.
• Seat rule: past 5 seats, you buy in bundles of 5 (bundles of 10 past 30 seats). A 12-person team pays for 15 seats. A 17-person team pays for 20.

Jira

• Free: $0 for up to 10 users. 2 GB storage and 100 automation runs a month.
• Standard: $7.91 on monthly billing. Annual billing is sold in user-count bands rather than a flat per-seat rate, and works out somewhat cheaper depending on which band you land in.
• Premium: $14.54 on monthly billing. Adds cross-team planning, approvals, unlimited storage, and a 99.9% uptime SLA.
• Automation: Standard pools 1,700 rule runs a month across your entire site. Premium moves to 1,000 runs per user per month.

One structural point in Jira's favour: Atlassian charges for active users. Deactivate someone who left and you stop paying for them, no seat bundle to shrink.

Side by side for a 12-person team

List prices hide the real comparison, so here is the math for a 12-person team on annual billing, using the plan each tool realistically requires once you outgrow the entry tier.

	ClickUp	Asana	Jira
Free tier truth	Unlimited users, 60 MB storage total	2 users (new accounts)	10 users, 100 automation runs/mo
Entry paid plan	Unlimited, $7	Starter, $10.99	Standard, $7.91
Plan you will likely need	Business, $12	Advanced, $24.99	Standard, $7.91
12 people, realistic plan, per month	$144 (12 seats)	$374.85 (15 seats, bundle rule)	about $95
Automation ceiling	Capped per plan, caps have moved	Capped on Starter, raised on Advanced	1,700 runs/mo pooled on Standard
Native time tracking	Yes, from Unlimited	Advanced only	No, marketplace apps at extra cost
Built for	Everything, configured by you	Adoption and clarity	Software delivery

Read that fourth row twice. For the same 12 people, Asana on the plan most service teams realistically need costs about 2.6 times ClickUp and nearly 4 times Jira.

Verdict by team profile

Client-services teams: ClickUp

Agencies, studios, bookkeeping firms, consultancies. You need time tracking against client work, guest access so clients can see status without a seat, templated project structures per engagement, and forms for intake. ClickUp has all four on the $7 Unlimited plan. Asana gates native time tracking, approvals, and branching forms behind Advanced at $24.99. Jira treats clients as an afterthought and time tracking as someone else's paid app. ClickUp's price-to-feature ratio for client work is not close. The cost is setup discipline, which we cover below.

Product and software teams: Jira

If your team ships software, Jira Standard is the boring correct answer. Sprints, backlog grooming, story points, velocity reports, release versions, and the development panel that shows linked branches and pull requests from GitHub or Bitbucket. ClickUp imitates sprints competently. Asana does not really try. And under 10 users, Jira is free with no time limit, which makes it the only one of the three a small product team can run seriously at $0. Skip Premium until someone can name the specific feature they are missing. Under 20 people, they usually cannot.

Mixed ops teams: Asana, with a budget warning

Marketing plus ops plus a couple of founders, no sprints, no client billing. Your real risk is not missing features. It is that half the team quietly stops updating the tool by week six. Asana has the lowest abandonment risk of the three because the daily surfaces, My Tasks and Inbox, are genuinely good, and a new hire is productive in an afternoon without training. Buy Starter at $10.99 and stay there as long as you can. The moment three different people ask for portfolios, time tracking, and approvals in the same month, you are looking at a bill that more than doubles, and that is the point to re-run this comparison rather than auto-upgrade.

ClickUp: cheapest real plan, messiest by default

ClickUp's pitch is everything in one place: tasks, docs, whiteboards, chat, goals, forms, time tracking. At $7 it underprices both rivals while bundling features they charge extra for. For a team under 20 that wants one tool instead of four, the value is real.

Where it is annoying daily

• The hierarchy. Workspace, Space, Folder, List, task, subtask, checklist item. Every team puts the same kind of work at a different level, and six months in you have three Spaces that all mean "Clients" and nobody remembers why.
• ClickApps. Dozens of toggles that change which fields and features exist in your workspace. Powerful, but it means your ClickUp and the ClickUp in the tutorial video are different products.
• Notification noise. Default settings notify on nearly everything. Unless an admin prunes watcher rules and notification settings in week one, the team learns to ignore all of it, and then the tool is decorative.
• Performance. Large workspaces with heavy custom fields get sluggish, especially in Everything view. Not fatal under 20 people, but noticeable.
• The upsell. The interface sells Brain AI in empty states and toolbars, and the monthly price for Business is not on the pricing page.

The honest framing: ClickUp is cheap because you are the implementation team. Assign one owner, decide the hierarchy on paper before you build it, and turn off every ClickApp you cannot name a use for. Skip that and the workspace grows cluttered fast.

Asana: the nicest daily experience until the invoice

Asana is the most pleasant of the three to use day to day. My Tasks is the best personal queue in the category, Inbox makes handoffs visible, and the design restraint that costs Asana feature-comparison points is exactly what keeps non-technical teammates updating it. Tools only work if people use them, and Asana gets used.

Where it is annoying daily

• The pricing cliff. Starter is missing the precise features a growing team reaches for next: native time tracking, approvals, portfolios, goals, forms with branching logic. Every one of them sits on Advanced at $24.99, which is 2.3 times Starter. You never upgrade for one feature. You upgrade because three requests pile up, and your bill more than doubles in a single decision.
• Phantom seats. The bundle rule means a 12-person team pays for 15 seats. On Advanced, that is about $75 a month for three people who do not exist.
• Silent rule caps. Starter caps monthly automation actions. When you hit the cap, your rules stop running until the next cycle, and Asana does not make this loud. The first symptom is usually a handoff that never happened.
• The free tier is gone in practice. Two users is a couple, not a team. New teams cannot trial Asana properly without paying.
• Thin reporting below Advanced. If a founder wants a cross-project status view, that is portfolios, which is Advanced money.

Jira: built for software, ceremonial for everyone else

For shipping code, Jira earns its reputation. The sprint and backlog tooling is the deepest here, the GitHub and Bitbucket integration shows real development state on every work item, and the free tier is the most generous of the three for a team under 10.

Where it is annoying daily

• Ceremony. Nothing is just a task. It is a work item (Atlassian retired the word "issue") with a type, a project, a workflow, and a status someone configured. Adding a status to a workflow is an admin job, not a click on the board.
• Scheme sprawl. Workflow schemes, permission schemes, screen schemes, notification schemes. This is governance built for 500-person companies, and a 15-person team carries the complexity without needing the control.
• Non-engineers avoid it. In mixed companies, marketing and ops end up asking a developer to file things for them, which defeats the entire point of a shared tracker.
• The marketplace tax. Things you assumed were included are paid apps: time tracking, advanced forms, richer roadmaps. Marketplace apps bill per user, on top of your Jira bill.
• The pooled automation cap. 1,700 runs a month across the whole site on Standard. A 15-person team that automates handoffs and notifications can burn that before month end, and then rules stop until the meter resets.

If your team is engineers plus one or two others, none of this will bother you much. If half your team is not technical, it will bother you every single day.

Migration and lock-in: what moves with you

All three export tasks to CSV, and that fact is close to meaningless. The export file is the easy 20 percent. Here is what stays behind:

• Leaving ClickUp: Docs and comment threads do not come out in any useful form, and custom exporting is gated to the Business plan. Your automations are rebuilt from scratch.
• Leaving Asana: rules, forms, and project message threads stay. Task history survives as CSV rows, which is archaeology, not continuity.
• Leaving Jira: workflow logic, automation rules, and everything inside marketplace apps stays. Years of comment context effectively stays too.

The deeper lock-in is not data. It is structure and habit: your custom fields, your statuses, your saved views, and the muscle memory of 15 people. That is why teams who hate their PM tool still keep it for years.

Practical notes from doing this for clients (we have built 600+ workflows across stacks like these, and migrations fail the same way every time):

1. Map fields in a spreadsheet before you touch an importer. Old field, new field, what dies. ClickUp ships importers for Asana, Jira, Trello, and Monday, and it is the most aggressive about making the move easy in.
2. Migrate one live project as a pilot, not the whole workspace.
3. Run both tools in parallel for two weeks, maximum. Longer than that and people pick a favourite, and you have two sources of truth again.
4. Turn the old tool read-only on a named date. Read-only, not deleted, because you will need to look something up in month two.

One design choice cuts future switching cost more than anything else: keep automations outside the tool where you can. Rules built inside ClickUp, Asana, or Jira die with the subscription. The same logic in Zapier, Make, or n8n just gets repointed at the new tool. We build it that way deliberately, and it is a big part of our automation practice.

Skip all three if

• You are under six people with three or fewer concurrent projects. A shared doc with three headings, This Week, Blocked, Done, reviewed for 20 minutes every Monday, carries a team that size. It costs nothing, needs no admin, and nobody has to learn it. Every PM tool is overhead until the doc visibly breaks, and you will know when it breaks.
• Your work already lives in your CRM. If your "projects" are really deals, onboardings, or client renewals, run them as pipelines where the customer data already is. Duplicating CRM stages into a PM tool creates two systems that drift apart within the first month. This is the most common setup mistake we see in RevOps engagements.
• The real problem is intake and handoffs. A PM tool makes dropped handoffs visible. It does not stop them from dropping. If work arrives by text message and leaves by memory, fix that first; our operations leak audit walks through how to find where work actually falls.
• You are buying software to fix accountability. No tool makes people update statuses. If a weekly review does not exist, the tool is dead in 90 days and the subscription runs for two years after that.

If you want a second opinion before committing a team of 15 to a tool for the next three years, our advice works like our builds: flat $150 per hour, scope quoted in writing first, and we will tell you if the answer is a doc. Details on how we work.

FAQ

Is ClickUp's free plan enough for a team under 20?

For tasks alone, yes, since members and tasks are unlimited. In practice the 60 MB total storage cap ends it fast: the first project with PDFs, briefs, or design files fills it. Treat Free as a trial and the $7 Unlimited plan as ClickUp's honest floor for a real team.

Why is our Asana bill higher than the advertised price?

Two reasons. Past 5 seats, Asana sells seats in bundles of 5, so a 12-person team pays for 15 seats. And the features most growing teams want, time tracking, approvals, portfolios, branching forms, sit on Advanced at $24.99, not the $10.99 Starter price you saw advertised.

Does a team under 20 need Jira Premium?

Usually no. Standard at $7.91 covers sprints, backlog, reporting, and integrations. Premium mainly buys cross-team planning, approvals, and per-user automation limits. The one trigger to watch is automation volume: Standard pools 1,700 rule runs a month across the whole site, and a heavily automated team can hit it.

How painful is switching tools later?

Tasks move, process does not. CSV exports carry task names, assignees, and dates, but automations, forms, docs, and comment history mostly stay behind, so budget for the rebuild, not the export. You can cut future switching cost now by keeping automation logic in an external tool like Zapier, Make, or n8n instead of inside the PM tool itself.