Asana Renewal Negotiation: What Buyers Should Know
Work management tools spread team by team, and the seat count follows the spread rather than the usage.
I spent years on the vendor side of enterprise software, and work management platforms like Asana tend to follow a recognisable pattern: one team adopts it, other teams get added over time, and the licence count grows with the rollout rather than with active usage. By renewal, the contracted seat total reflects who was invited, not who is working in the tool.
Seats added per rollout wave, against teams still active
Invited during a company-wide rollout, working somewhere else since.
The licence count follows the rollout. Adoption does not.
What typically shapes a renewal like this
Per-seat pricing where every invited member counts, tier structures that gate features teams asked for once, and adoption that varies widely by department, with some teams living in the tool daily and others logging in occasionally at best.
Questions worth asking before your renewal
- How many licensed members have been active in the last 30 to 90 days, broken down by team
- Which teams adopted the tool and then quietly moved their work elsewhere
- Are we on a tier for features that one team requested, and is that team still using them
- Do we have guest or external collaborator accounts that are being billed as full members
- Is another tool in the business doing the same job for a different department
Common levers buyers use
The fastest correction is usually per-team activity data. It separates the departments that genuinely depend on the platform from the ones that were rolled in and drifted away, and it turns a general request for a discount into a specific, evidenced seat reduction.