Rollout pathSign-up, founder review, install, and activation stay in one controlled handoff.
The public pricing surface should remove ambiguity. Teams know when founder review happens, where download access appears, and how support fits into activation and rollout.
After sign-upSigned-in accounts continue from the account approval surface.Once the account exists, founder approval and download eligibility move into the authenticated account surface and desktop access follows the same signed-in account state.
Support lanePricing questions, founder approval, and activation issues share one path.Commercial and technical support stay tightly coupled so teams can move from founder approval into live desktop access without context switching.