Monthly cost per seat
Use your own seat-cost assumption instead of hardcoding public pricing, then update it when your contract, billing tier, or renewal assumptions change.
Unitlane guide
Set billing assumptions for estimates
Use manual assumptions instead of hardcoded Atlassian prices.
Marketplace trialClear boundariesNo unsupported guarantees
What it does
Billing assumptions power estimated monthly and annualized impact.
Billing model
Mark monthly, annual, or unknown billing so estimated impact is framed honestly and reviewers do not confuse planning numbers with invoices.
Renewal date
Anchor cleanup planning around the next cycle without promising current-cycle savings, especially when contract timing and billing rules are outside the app.
What it does not claim
It does not calculate official invoices or guarantee billing reductions.
Actual billing depends on plan.
Billing impact depends on plan, contract terms, timing, and customer assumptions, so estimates should be reviewed before finance decisions.
Timing and contract matter.
Billing impact depends on plan, contract terms, timing, and customer assumptions, so estimates should be reviewed before finance decisions.
Treat impact as an estimate.
Billing impact depends on plan, contract terms, timing, and customer assumptions, so estimates should be reviewed before finance decisions.
Best next step
Continue to License Guard for Jira License Cleanup for the current screenshots, evaluation path, trust boundaries, and Marketplace trial link behind this workflow.