Performalise is priced per team, from $450 per team per month billed annually, with every capability on every plan and no per-user charge. This page explains why, what a team means, and who the product is not for.

Why per team

The unit Performalise coaches is the team, so the unit it charges is the team. Per-seat pricing would make every stakeholder, coach and Scrum Master who looks at the signal a cost, and the signal works when more people see it, not fewer. Per-team pricing also keeps the incentive honest: a quieter coach for a maturing team is success, not a reason to charge for more seats (constitution, value 9).

What a team means

Any group that runs sprints or iterations together, typically a Jira project, an Azure DevOps team or a shared backlog. Pricing is sized around teams of up to ten people on average across the account; if some teams run larger, that is fine as long as the average holds. One licence per team covers every team member plus any coaches, Scrum Masters or stakeholders who access that team's data.

The plans

  1. Perform: $530 per team per month, or $450 billed annually. Every capability.
  2. Scale: $940 per team per month, or $800 billed annually. For organisations that need the portfolio altitude, more integrations and priority support.
  3. Enterprise: custom. Organisations with 15 or more teams qualify for volume pricing; multi-year commitments unlock further savings.

Upgrades take effect immediately. Downgrades apply at the next billing cycle, with no lock-in penalty. Current prices and the plan comparison are on the pricing page; if this page and that one ever differ, the pricing page wins.

What changes the price

The number of teams and whether you bill annually. Nothing else: not head-count, not the number of coaches or stakeholders, not which of the nine capabilities you use.

Who Performalise is not for

We would rather tell you now than after a sprint. Performalise is not the right fit if:

  1. You want individual productivity scores. We measure patterns, not people. There are no per-person leaderboards, and we will not build them.
  2. Your teams do not work in Jira, Azure DevOps or Linear. Those are the front doors today. Other trackers are also supported, just talk to us.
  3. You want a dashboard and no coach. The signal only becomes value when the AI Coach Hans or Lotte act on it inside the team. If nobody wants coaching, you would be paying for reports, which would be sad.
  4. You want velocity as a productivity target. Velocity is a planning signal for the team that owns it. We will not turn it into a KPI or compare it across teams.
  5. You measure success in output. Story points closed, tickets shipped, commits per week. We tie work to outcomes: usage, retention, OKR movement. If output is the scoreboard, the signal will keep disagreeing with it.
  6. You want OKRs pushed down into tickets. We translate an OKR into a sprint goal the team commits to. We will not cascade OKRs as task lists.
  7. You want a date, not a range. Forecasts arrive as ranges (±4-6 weeks across a portfolio) with the confidence behind them. If a single promised date is required, we will disappoint you honestly rather than precisely.

Frequently asked questions

Is there a per-user charge?

No. One licence per team covers every team member plus the coaches, Scrum Masters and stakeholders who access that team's data.

What if some of our teams are bigger than ten people?

Pricing is sized around an average of up to ten people per team across the account. Larger teams are fine as long as the average holds.

Is every capability on every plan?

Yes. The nine capabilities are on Perform, Scale and Enterprise. The plans differ in altitude (portfolio view), integrations and support, not in which capabilities you get.

Part of How Performalise works, the public record of how the product is built to behave. Last reviewed 27 August 2026. Corrections: josef@performalise.com.