Your product was born multiplayer

"Invite your team" is normally a year of engineering: presence, sessions, conflict handling, permission tiers. Most small products never get there.

If your product runs each customer in their own container, every surface you embed is already a URL: and on Hoody, a URL two people open is a thing two people are in. The embedded editor your customer works in is the same editor their colleague opens from the invite email; separate instance numbers give each person their own window onto one shared filesystem. Permission layers decide who can write and who can only look.

You didn't schedule the collaboration epic. You exposed a property the environment had from day one.