Agile Analytics started with one belief: the team running a delivery practice already pays enough for tooling. The reporting layer on top should grow with the team — not invent reasons to charge more as the team gets bigger or pretend that a Scrum Master with two pilots is a different customer than a release manager with twenty teams. The 6.8.x line is where we finished living that belief: every plan ships every feature, the 30-day trial is fully unlocked from day one, and the three tiers (Team, Business, Premium) are sized so the price you pay tracks the value you actually use. This is a longer read about what changed in the move from flat-rate org pricing to per-seat, why we made each call, and what it means for you whether you're piloting with two engineers or rolling out to a hundred teams.
The pricing change in one sentence
We moved from a flat per-org subscription to per-seat tiers — Team at $25/month for 2 seats, Business at $100/month for 6 seats, and Premium at $2,000/year for unlimited seats. A seat is a distinct Azure DevOps user who opens any analytics view, fires any extension event, or completes a license action in the last 30 days. People in the org who never open the extension don't count. The three tiers cover the three shapes of customer we see again and again — and every tier includes every feature, with no view, dashboard, or capability gated by plan.
Why per-seat over flat-rate
Flat-rate org pricing was simple on a spreadsheet but unfair in practice. A team of two paid the same as an engineering organisation of two hundred, and the smaller team usually walked because the math didn't pencil. The fix wasn't to lower the flat-rate price (that just shifts the unfairness toward larger orgs subsidising the trial-stage ones) — it was to admit that two-person pilots and hundred-team rollouts are genuinely different shapes of customer and let the pricing reflect that.
- A two-person Scrum team running a discovery pilot pays for two seats — not a department's worth of analytics tooling.
- A six-person delivery team running Scrum or Kanban pays the Business price — predictable, no surprises when a new engineer joins next sprint.
- An engineering organisation running multiple programs at once gets unlimited seats at Premium — a flat ceiling, not a per-head escalation that punishes growth.
Features never block growth
Every Agile Analytics view exists on every plan. Cycle Time scatterplots with percentile bands, the Vacanti zone overlays, Wheeler's XmR Process Behavior chart, the Cycle Time Heat Map, Sprint Summary, Monte Carlo, Next Sprint Planning, AI Metrics with GitHub Copilot, AIIP thresholds, custom KPIs, webhook notifications — all of them ship at Team, Business, and Premium identically. The trial is 30 days of the same fully-unlocked feature set, not a stripped-down demo that hides the views you'd actually buy for. The reason is straightforward: we want the decision to upgrade to be about how many of your people benefit from the extension, not which feature the sales team is willing to unlock today. If a view exists in the product, it works for you on day one and it keeps working on day one thousand.
Day one to many years — the upgrade path
The shape of an Agile Analytics customer changes over time. The most common pattern looks like this: one Scrum Master starts a 30-day trial on a single team, decides the views answer their stand-up and review questions better than the queries they were running before, and converts to the Team tier. A sprint or two later, the engineering manager next door asks for an account — that's seat three, and the Team tier becomes Business. Twelve months later, the same company is running three programs, four scrum teams, and a coaching practice — that's Premium. We designed the tiers so each upgrade is a small, obvious step (2 seats → 6 seats → unlimited), the analytics layer is the same one you've been using all along, and there is no migration, no reconfiguration, and no "re-platform" conversation. The license key you activate at the Team tier is the same license key after you upgrade.
What the soft seat banner is — and is not
From v6.7.0 onward, when an org's distinct active users in the last 30 days exceed the seat allowance for its tier, a soft banner appears at the top of the License panel in Configuration. The banner shows used vs. limit and links to the pricing page. It is intentionally a soft signal, not a hard wall.
- The license stays fully active. Every view continues to work. No telemetry is suppressed. No data is hidden.
- There is no count-down clock, no "upgrade in N days or lose access" pressure. The banner exists so the admin sees what the rest of the team already sees — that the value of the extension has spread past the original seat count — and can choose when to upgrade.
- Existing Founding, Annual, and Monthly subscribers don't see the banner regardless of seat count. Those plans are grandfathered byte-for-byte and renewals preserve the legacy treatment.
For customers who paid before per-seat existed
If you bought Founding, Annual, or Monthly before the per-seat tiers existed, your current price stays exactly the same on every renewal. The new tiers apply only to new subscriptions and to intentional upgrades — they don't backfill onto your existing plan. Your settings, license key, and dashboards are unchanged across this transition. If your team grows beyond the seat count of your tier in the future, we'll surface a soft in-extension notice — no surprise billing, no auto-upgrade. The decision to move tiers is yours.
What "on your side from day one" actually means
A lot of B2B software is priced to maximise the moment of conversion — every feature gated, every trial timed, every upgrade choreographed to extract maximum spend. Agile Analytics is priced for the opposite shape of relationship: we want to be the analytics layer your team uses for years, not the one a finance department gets a CFO ask to cut next quarter. That decision shows up in concrete places — the trial is fully featured, every plan ships every view, the upgrade path is mechanical (2 → 6 → unlimited), the legacy pricing is preserved on renewals, and a 30-day money-back guarantee covers the post-purchase window so the buy decision doesn't have to be perfect. If the product fits your team's flow questions, the pricing should never be the reason you leave.
When to upgrade
A few practical signals that say it's time to move tiers — not because we want you to, but because the value has already crossed the line.
- Team → Business: A third engineer started opening the dashboards on a sprint cadence. The seat banner is showing. The team is past the 2-seat allowance most of the month, not just one busy week.
- Business → Premium: The extension is being opened by a second delivery team or a release coordinator, the seat count has moved past 6 multiple sprints in a row, and the per-seat math at Business is now within sight of the Premium flat rate.
- Anywhere → Premium: The conversation in the org has shifted from "one team's metrics" to "the engineering practice's metrics." That's the inflection where unlimited seats start paying for themselves — and where coaching/release/PMO functions also need access without you tracking seat counts every month.
How to upgrade
From inside the extension, open Configuration → License and the upgrade CTA threads through to the pricing page with your org details pre-filled. Picking a new tier uses the same Stripe checkout flow as a new purchase — your existing license key is preserved and the seat allowance changes on the next renewal. From the website, the new tiers are at /pricing — the same page the in-extension Buy buttons link to. Either path, you keep your existing settings and your existing license; we don't reset your configuration on an upgrade.
The short version
Every plan ships every feature. The trial is fully unlocked from day one. The three tiers cover real customer shapes — pilot, full team, organisation — and the seat counts (2, 6, unlimited) are sized for those shapes. Features never block growth. Legacy subscribers keep their pricing on renewal. The seat banner is a soft signal, never a wall. And the 30-day money-back guarantee is there because we want the buy decision to be easy and the relationship to be long.