Asana lists Personal at $0, Starter at $10.99 per user per month annually or $13.49 monthly, and Advanced at $24.99 annually or $30.49 monthly. Model the full paid-member count, seat increments, guest-domain rules, portfolio and workload needs, timesheet add-ons, services, and renewal—not just the displayed per-user rate.
Official public sources checked 15 September 2026. Prices below are USD list-price references, not a quote. Country, currency, tax, reseller, promotion, contract, legacy subscription, quantity, and renewal date can change the payable amount.
Published plan-price snapshot
| Plan | Billing basis | Published rate | What to verify |
|---|---|---|---|
| Personal | No charge | $0 | For individuals and small teams within published limits |
| Starter | Annual | $10.99 | Per user per month |
| Starter | Monthly | $13.49 | Per user per month |
| Advanced | Annual | $24.99 | Per user per month |
| Advanced | Monthly | $30.49 | Per user per month |
| Timesheets and Budgets add-on | Annual | $5.99 | Per user per month, where available |
A price row answers only the starting arithmetic. Before approval, preserve the dated vendor page or quote, record the currency and billing term, and identify every population that will be charged. If the vendor page and order form differ, the signed order form and governing contract control the purchase.
How Asana billing changes total cost
- Paid membership, guest treatment, organization email domains, and seat increments affect invoice quantity. Confirm the exact rule for the proposed workspace structure.
- Portfolio, workload, goals, advanced reporting, approvals, forms, automation, security, and admin needs can change the required tier.
- The Timesheets and Budgets add-on has separate pricing where available; AI, services, support, integrations, and change management may add cost.
- Annual and monthly rates differ. Model expansion, inactive-member removal, renewal timing, and any promotional term.
Illustrative annual license baselines
The examples use the second paid public plan shown above where available. They are reproducible arithmetic, not a forecast or recommendation.
| Population | Assumption | Annual baseline | Excluded |
|---|---|---|---|
| 25 paid users | Starter · Monthly | $4,047/year | License baseline only; excludes tax, add-ons, implementation, migration, support, internal labor, and discounts. |
| 100 paid users | Starter · Monthly | $16,188/year | License baseline only; excludes tax, add-ons, implementation, migration, support, internal labor, and discounts. |
| 250 paid users | Starter · Monthly | $40,470/year | License baseline only; excludes tax, add-ons, implementation, migration, support, internal labor, and discounts. |
Cost drivers the quote must expose
- Paid members, guests, teams, organization domains, and purchased seat increments
- Starter versus Advanced requirements for portfolios, workload, goals, reporting, and governance
- Timesheets, budgets, AI, integrations, implementation, and support
- Migration of projects, tasks, attachments, automations, forms, and histories
- Adoption, administration, seat governance, renewal, and export/exit work
Build base, expected, and stress cases. A useful model separates recurring licenses and consumption from one-time vendor services, internal implementation effort, dependent tools, and exit work. Record unknown values as a range with an owner and decision deadline rather than silently entering zero.
Questions to put in writing
- Which collaborators count as paid members, guests, or members of another organization domain?
- What seat increment will the proposed count be billed at?
- Which workflows require Advanced rather than Starter?
- Are timesheets, budget controls, AI, services, or premium integrations separate?
- What can be exported with relationships and history if the buyer later leaves?
Renewal and exit checks
Record the initial term, renewal term, auto-renewal status, notice deadline and delivery method, protected pricing, uplift rule, minimum quantity, reduction window, reassignment rights, usage true-up, data-export method, post-termination access, deletion schedule, and retained-data exceptions. Test the export before the renewal decision if the product will hold business-critical records.
Official sources used
PR97 summarizes public vendor information for comparison. It has not inspected your tenant, order form, reseller proposal, or negotiated contract. Recheck the linked official source and written quote on the day of decision.
Normalize the quote in one worksheet
Capture plan, billable unit, allowances, services, internal cost, renewal, and exit assumptions beside their evidence.
Asana approval record
The approval should state which operating roles require this service, why the selected edition is necessary, and which evidence proves the mandatory workflow. For Asana, record the exact quote, plan, billable population, included allowance, add-on, service scope, implementation owner, and first renewal deadline beside the decision.
Commercial facts to reconcile
- Paid membership, guest treatment, organization email domains, and seat increments affect invoice quantity. Confirm the exact rule for the proposed workspace structure.
- Portfolio, workload, goals, advanced reporting, approvals, forms, automation, security, and admin needs can change the required tier.
- The Timesheets and Budgets add-on has separate pricing where available; AI, services, support, integrations, and change management may add cost.
- Paid members, guests, teams, organization domains, and purchased seat increments
- Starter versus Advanced requirements for portfolios, workload, goals, reporting, and governance
- Timesheets, budgets, AI, integrations, implementation, and support
- Migration of projects, tasks, attachments, automations, forms, and histories
Reviewer questions
- Which collaborators count as paid members, guests, or members of another organization domain?
- What seat increment will the proposed count be billed at?
- Which workflows require Advanced rather than Starter?
After launch, compare the first invoice with provisioned access and expected usage. Review adoption by required role and workflow at 30, 60, and 90 days. Before notice is due, test a current export and decide whether to retain, resize, renegotiate, replace, or cancel. Keep this evidence with the order form so future reviewers can reproduce both the cost and the reason for the purchase.