Small: three editors, one bill, no seat mathematics
At €39 per month the plan includes three editors - typically the designer, a developer and whoever writes the guidelines. That composition is the point. Per-editor pricing quietly turns every extra contributor into a purchasing decision, so in practice the developer never gets an account and the documentation stays the designer's homework. With a flat plan, inviting the fourth person is an invitation, not a discussion: €10 per month, done. And everyone who only reads - the rest of the team, the stakeholders, the new joiner - is free and unlimited on every plan, including the free one.
Growing: the ladder has no trap in it
Nine editors on Starter costs €39 plus six times €10: exactly €99, the price of the Team plan. From the tenth editor onwards Team is simply cheaper, and it brings unlimited hubs, adoption analytics, per-hub permissions and 180 days of page history with it. Extra editors beyond the included ten cost €8. There is no team size at which you are punished for having grown, no moment where the next step is "contact sales", and switching plans is a button in your billing screen with the difference settled on the next invoice.
Grown: thirty editors, and the honest ceiling above that
A thirty-editor team runs fine here: €99 plus twenty times €8 is €259 per month, still without a sales conversation, still with unlimited readers. But we would rather name the ceiling than let you find it: we do not offer SAML single sign-on, approval workflows or release management. If your organisation is heading toward those requirements - security reviews, sign-off chains, procurement gates - our Zeroheight comparison says openly that their Enterprise plan is the better home. Pentrical is built for the middle of the market, and staying good at that means not pretending to be an enterprise suite.
What the whole-team model actually changes
When editing stops being scarce, the documentation stops being one person's backlog. The accessibility specialist fixes a wrong paragraph before lunch instead of filing a ticket. The developer corrects a measurement the moment it looks off - and because measurements, colours and tokens come straight from Figma on every sync, mostly there is nothing to correct. Once you are on Team, adoption analytics closes the loop: which components exist in Figma, which are documented, which does anybody actually read, and what did people search for without finding. That last list is your documentation backlog, written by your own team.