Most workflow tools are priced per seat. The logic is easy: more people means more seats. The logic is wrong for a delivery monitoring layer, because the value scales with the number of PMs being watched for, not the number of developers receiving briefs.
A PM with twelve developers is not twelve times more valuable to support than a PM with one. The briefs go out, the check-ins run, the bounces are read — the work Pyloq does is per PM. Charging per developer charges the team for hiring, and charges them for the part of the product that is not the part they are paying for.
Per PM is not a generous model. It is the only honest one. The thing you pay for is the value created — the loop being watched — not the size of the room the briefs are read into.
A workspace is not capped at one PM. An account can hold several — each with their own projects, their own check-in schedule, their own developers being briefed. The workspace owner sees across all of them on one screen. The bill grows when the coverage grows: a second PM added is a second loop watched, and that is what you pay for.
That is the only scaling that makes sense. The size of the developer pool, the number of tickets, the volume of messages — none of those are what Pyloq is doing for you. The PM is the unit of value. The PM is the unit of price.