Asana Personal 2 seats: when indies should buy Starter
Use official Personal caps—2 seats, no Timeline/Forms/custom fields—to decide when a two-person shipping board needs Starter at $10.99/user/mo annually.
When a solo founder or two-person partnership jams shipping, client follow-ups, and ops into one board, the search often becomes whether Asana Personal’s two seats are enough. This page does not re-run a Trello vs Asana vs Todoist bake-off. It freezes Personal’s official limits as of 2026-09-29 on asana.com/pricing and spells out when Starter is the rational next buy. Re-open the pricing page before you pay; numbers move.
What Personal includes
Asana labels the free forever tier Personal for one or two people managing personal projects. Official cards list 2 users, unlimited tasks and projects, list, board, and calendar views, unlimited storage with a 100MB max per file, status updates, and 100+ free integrations. The comparison table keeps Timeline and Gantt, Forms, custom fields, unlimited automations, unlimited free guests, private teams, and the admin console on Starter and above. Starter shows $10.99 per user per month billed annually and $13.49 billed monthly. Checkout still governs seat minimums, so do not order from memory. For most indie pairs, the seat wall hits first; Forms and custom fields hit second; Timeline becomes the third wall when you must present externally.
Personal already covers daily sprint hygiene. What pushes payment is usually identity and structure, not task count. A third person who must edit tasks for weeks will outgrow comments and links. Weekly client intake makes Forms attractive. Field-based priority filters make tag-only lists feel brittle. Treat those frictions as observable signals instead of accepting slogans about free forever.
A two-seat skeleton that still ships
Keep the workspace at two formal members—you and a partner. Clients and contractors collaborate through comments, linked files, and status updates instead of consuming a third seat. Split projects along Product, Clients, Admin, and Learning. Product holds the current mainline release. Clients holds paid accounts and trial follow-ups with customer-name tags. Admin holds tax, domains, invoices, and legal. Learning holds courses and experiments that get archived when done. Use My Tasks for today’s executable queue so you are not clicking across four projects all morning.
List, board, and calendar already cover sprint work. Board shows work in progress, list is better for bulk edits, and calendar catches ship dates and renewals. When you need a client intake form or field filters every week, Personal becomes the bottleneck and Starter’s Forms plus custom fields become the product you are actually buying. Dependencies and start times also sit on paid tiers. If your release train often waits on design before QA, decide whether paid dependencies beat a comment convention.
Write permission habits down. Who creates projects, who closes tasks, who posts the weekly status update. Personal’s access model is project-leaning; do not expect a rich role system to save seats. When a partner is away, use status updates for blockers instead of temporarily seating a contractor.
