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, all billed annually — Team at $300/year for 2 seats, Business at $1,200/year for 6 seats, and Premium at $2,000/year for unlimited seats. A seat is an assigned place on your plan: your extension admin assigns people in Configuration → Access Control, and only assigned people hold seats. 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.
How seats actually work — assigned places, honest edges
A seat is an assigned place on your plan. Your extension admin assigns people in Configuration → Access Control; assigned users — admins included — each hold one seat, and seats can be swapped at any time by removing someone and assigning someone else. When every seat is taken, the next assignment is simply refused until a seat is freed or the plan is upgraded. That is the whole enforcement model: the cap works at the moment of assignment, so there is never a surprise bill and never a mid-sprint lockout of someone who already holds a seat.
- Nobody who holds a seat ever loses access because a plan is "over" — over-cap is impossible by construction; the cap refuses the next assignment instead.
- People without a seat are not locked out of the product's front door: they see the Dashboard, every other view stays visible in the navigation, and asking the admin for a seat is one click. Visibility is deliberate — hiding the product never helped anyone make a case for a seat.
- Existing Founding, Annual, and Monthly subscribers have no seat limits at all. 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, and your plan has no seat limits at all: seat assignment simply does not apply to legacy plans. The decision to move tiers is always 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 and extended on request, every plan ships every view, the upgrade path is mechanical (2 → 6 → unlimited), and the legacy pricing is preserved on renewals. The 30-day trial IS the guarantee: you evaluate the complete product before a single payment, so the buy decision never has to be a leap. 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 wants in — seat requests are landing in Access Control and both seats are taken sprint after sprint, not just one busy week.
- Business → Premium: a second delivery team or a release coordinator is asking for seats, all 6 are assigned 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
Email support with the tier you want and we move your existing subscription — your licence key is preserved, your settings are untouched, the new seat allowance applies as soon as the plan changes, and Stripe prorates the difference. Don't start a second checkout for an upgrade: a fresh checkout creates a separate subscription rather than changing the one you have, which is why the path runs through support today. Pricing details live at /pricing, the same page the in-extension buttons link to.
The short version
Every plan ships every feature. The trial is fully unlocked from day one — and the trial is the guarantee: you evaluate the whole product before paying anything. The three tiers cover real customer shapes — pilot, full team, organisation — and the seat counts (2, 6, unlimited) are sized for those shapes. Seats are assigned places: the cap refuses the next assignment rather than ever surprising you with a bill, nobody holding a seat is ever cut off, and people without one keep the Dashboard and a one-click way to ask. Features never block growth, and legacy subscribers keep their pricing on renewal.