compare
Most people evaluating Asana as project management software are not starting from nothing. There is a spreadsheet that three people update, a chat channel where work gets handed off, and a nagging sense that something is being dropped every week. The question is not whether Asana is good software. It is whether the way it models work, and the way it charges for people, fits a team of the size you actually have.
Those two things decide more than the feature list does. A tool with every view in the world is useless if the reason work goes untracked is that the people who need to see it are not in the account. So this article works through the structure first, then the plans as listed in September 2026, then the three specific points where small teams find the fit breaking down.
The unit of work is the task. A task has one assignee, one due date, a description, comments, and attachments. The design decision that separates Asana from a plain board tool is that a task can live in more than one project at the same time. The same task can appear in a marketing project and in a quarterly launch project without being duplicated. Update it once and both views change.
That multi-homing is genuinely useful when a piece of work belongs to two conversations. It also means the mental model has to be learned. A card on a board belongs to that board and nowhere else. An Asana task is a record that projects point at. People who expect the first model are surprised when removing a task from one project leaves it alive in another. It is worth deciding, before anyone else is invited in, whether a project represents a team, a deliverable or a time period. Teams that answer that question late end up with projects at three different levels of granularity and no way to report across them.
Views are projections of the same task set. List, board and calendar are available on every plan. Timeline and Gantt are projections too, not separate artifacts, so switching between them is not a migration and nothing has to be re-entered.
The most common reason an Asana rollout produces reports nobody trusts is subtasks. A subtask does not automatically belong to the parent task's project. Teams that break work down by creating subtasks under a single parent end up with most of the real effort sitting outside project views, dashboards and workload calculations. Nothing is broken. The work simply is not where the reports look. Deciding early that anything worth reporting on gets promoted to a task in the project, and that subtasks are only checklists, avoids a rebuild six months in.
Asana lists four plans for work management, plus a tier above Enterprise for organizations with heavier compliance needs. Prices below are the ones shown on the pricing page in September 2026, in US dollars, before tax.
| Plan | Annual, per user per month | Monthly, per user per month | Headline limit or addition |
|---|---|---|---|
| Personal | $0 | $0 | 2 users, list, board and calendar views |
| Starter | $10.99 | $13.49 | No seat limit, timeline and Gantt, dashboards, forms |
| Advanced | $24.99 | $30.49 | Portfolios, goals, resource management, time tracking |
| Enterprise | Contact sales | Contact sales | Data residency, audit logs, dedicated workspaces |
Personal includes unlimited tasks and projects, unlimited storage with a 100 MB cap per file, status updates, time tracking through integrations, and more than 100 free integrations. Starter adds unlimited automations, custom fields, custom templates and unlimited free guests. Advanced adds approvals and proofing, form branching, native time tracking that compares estimated against actual, and connections to Salesforce, Tableau and Power BI.
Sales tax is applied on top based on the billing address, so the budget figure should include it. The listed annual saving is up to 18 percent, which matches the gap between the annual and monthly rates.
This is the single most important line on the pricing page for a small team. Personal is capped at two users. It is not a small team plan. A team of five cannot rehearse a real workflow on it, because three of them cannot get in.
That is a design choice rather than a flaw, and it is worth comparing against how other products in the category draw the line, because the shape of the cap decides what you can test before paying:
| Product | What the free plan caps |
|---|---|
| Asana Personal | 2 users |
| Trello Free | 10 collaborators and 10 boards per Workspace, 10 MB per file |
| Jira Free | 10 users, 2 GB storage, 150 automation steps per month |
| Linear Free | 2 teams and 250 issues, with no member cap |
| monday.com Free | 2 seats, 3 boards, 3 Docs |
A cap on objects lets a whole team rehearse and hit the wall honestly. A cap on people blocks the rehearsal entirely. Tools that include every board type free for up to five people and ten boards sit at the other end of that spectrum: the features are all present and the counting happens on headcount and board count instead.
Asana does not bill per person in a straight line. Its pricing FAQ sets out the increments: between 2 and 5 total users, seats are added one at a time. Up to 30 total users, seats are added in blocks of 5. Up to 100 users, blocks of 10. Up to 500, blocks of 25. Above that, blocks of 50.
Applied to the listed Starter price, before tax, that produces these steps:
| Team size | Seats billed | Starter, billed annually |
|---|---|---|
| 5 people | 5 | $659.40 per year |
| 6 people | 10 | $1,318.80 per year |
| 10 people | 10 | $1,318.80 per year |
| 11 people | 15 | $1,978.20 per year |
| 16 people | 20 | $2,637.60 per year |
The sixth person doubles the bill. The team grew by twenty percent and the cost grew by one hundred percent. Nothing is hidden here, but it is easy to miss when comparing headline per seat rates across products.
There is a legitimate way to blunt it. Starter and above include unlimited free guests, and guests do not consume a paid seat. A client who reviews work and leaves comments, or a contractor who only touches one project, can be a guest. Someone who belongs to the organization should be a member. Counting honestly before signing up, and asking which of the eleven people genuinely need a member seat, often moves a team back down a block.
Starter and Advanced both include Asana AI in a metered form: 5 requests per user per month, capped at 50 requests per account per month. For a ten person team, that is 50 requests for the entire account, which is a handful of summaries and a couple of generated drafts.
Beyond the allowance there are two purchase routes. Prepaid usage packs are listed at $0.50 per request and stay valid for the billing cycle. Pay as you go billing is listed at $0.60 per request, billed monthly, with a spend cap that can be set in the product. A request is counted as one successful unit of work, and failed, timed out or cancelled tasks are not charged. Usage alerts fire as the allowance is consumed.
The practical advice is to set the spend cap on the first day rather than discovering the figure on the first invoice. AI usage is the one line on an Asana bill that is not predictable from headcount, and a team that starts routing real work through it will see it move.
A fair reading of the trade has to include the other direction. Three things in Asana are genuinely hard to replace with a simpler board tool.
The first is rules that survive people. Unlimited automations on Starter mean an intake form can create a task, assign it by the answer to a dropdown, set a due date, and move it between sections as its status field changes, without anyone remembering to do any of it. A small team can run on convention instead, and many do, but convention breaks the week someone is on leave.
The second is the reporting spine. Custom fields plus dashboards plus, on Advanced, portfolios and goals give a chain from a single task up to a quarterly objective. That chain is what lets a manager answer a question about strategy with data rather than opinion. Most lighter tools stop at the board.
The third is the integration surface. More than 100 integrations are listed on the free plan, and Advanced adds connections to Salesforce, Tableau and Power BI. For a team whose reporting already lives in a business intelligence tool, that matters more than any view.
None of these are reasons to stay if the bill is being driven by seat blocks for people who only read. They are reasons not to switch on price alone.
Capacity questions. The recurring question in a weekly meeting is who has room for the next thing. Resource management, which shows who is overloaded and lets work be rebalanced, is an Advanced feature. On Starter the answer comes from a spreadsheet someone maintains on Monday mornings, and that spreadsheet is accurate until the person who owns it gets busy. The cost of it being out of date is invisible right up to the moment a deadline slips, which is why teams tend to upgrade for this reason rather than plan for it. Native time tracking that compares estimated against actual hours is also Advanced, so on Starter the estimates never get corrected by reality and the next round of planning repeats the same optimism.
Reporting across projects rather than inside one. Starter dashboards report on a single project well. Rolling five client projects into one view of what is late is what portfolios are for, and portfolios start at Advanced. The jump from Starter to Advanced is more than double per seat, so this is the decision that most often turns a manageable bill into an uncomfortable one.
The conversation lives somewhere else. Tasks have comment threads, but there is no team chat channel inside Asana, so day to day discussion happens in Slack or Teams. The reasoning behind a decision ends up in one place and the task in another, and reconnecting them depends on someone remembering to paste. Discipline works for a while and then decays. This is where a tool that keeps a chat channel beside the boards removes a copying step rather than adding a feature. The Pinateca vs Asana comparison lays out how the two split that ground, including what Asana does that a smaller board tool does not attempt.
Two terms are worth reading before an annual commitment. There is no on premises edition, and the FAQ states there are no plans for one, so self hosting is not an option for teams with that requirement. Refunds are not offered: cancelling keeps paid features until the end of the period, after which access to paid features and the data tied to them is lost.
Count how many of the people in the account need a member seat and how many could work as guests, then look up which seat block that lands in. If the answer is that the block, not the work, is driving the bill, compare the alternatives on how they count rather than on features, starting with Pricing and the wider set of All comparisons.
No. The Personal plan is capped at two users, so a team of five needs a paid plan. At the listed Starter rate of $10.99 per user per month billed annually, five seats come to $659.40 a year before tax, or $67.45 a month if billed monthly at $13.49.
Seats are sold in blocks. Between 2 and 5 total users they are added one at a time, but up to 30 total users they are added in blocks of 5. A team going from five people to six therefore moves from 5 billed seats to 10, which doubles the subscription.
No. Personal includes list, board and calendar views. Timeline and Gantt views begin at Starter, along with reporting dashboards, forms and custom fields. Teams that plan work against dates tend to hit that boundary in the first week.
Starter and above include unlimited free guests, and guests do not consume a paid seat. Someone who belongs to the organization should be a member and does count. Moving review only participants to guest status is the most reliable way to keep a team inside a lower seat block.
Asana states that refunds are not offered and that paid features remain available until the end of the current subscription period. After expiry, access to paid features and the data associated with those features is lost, so anything that needs to survive should be exported before the period ends.