My opinion is that what is missing in this flow is: how the end user (for example, head of human resources – if it is a small organization or someone in the human resources team or someone else if it is an MNC with many users) will want use that account
I believe that the accounts of the parents are better in this case, since this decoupling process that your organization has with what the client's organization may be following and the people who may be authorized to control the entries.
In addition, this eliminates the burden of trying to customize flows for each new large customer you can get …
A usability problem with the initial seat nomination is: if someone opted for the 51-100 package, entering emails from 100 people can be an incredibly painful task …
Then go for
1. & # 39; Lazy seat allocation: at the time of the final customer's choice and comfort & # 39;
2. Subscription in advance and immediately without the need to identify everyone on the list by the company's emails
3. In this case, you must implement a control panel so that people can use the seats in a few days, etc.
(FYI: Adobe has a similar seat assignment for Creative Cloud but its UI is quite formal, little too formal)