This looks nice, but requiring an email during setup, with no explanation or discernible reason - and demanding a work email at that - seems very creepy.
This decision alone removes my trust in your product and your company, sorry.
This decision alone removes my trust in your product and your company, sorry.
We should probably add this explanation to the login page because I can see how this would be confusing.
I guess I'm still missing something, as I don't get why the domain of my email address is relevant for who I share things with? My (hopefully constructive!) feedback is that by asking specifically for a business mail, you send certain signals to the end user.
Are you honestly saying that emails won't be used for sales purposes? (that might sounds a bit adversarial, but it's a genuine, non-judgemental question!)
If there are a bunch of people at the same company using Fig, we'd probably reach out to understand what you find valuable and how we could make it better - we don't have a paid offering yet, but want to figure out what teams are willing to pay for!
Something else I would add is that there are almost 300,000 people "in my team" using my business email domain (yep, it's a big company). I think better wording here would be "organization", rather than "team". But...
...I'm personally pretty unsure about this whole-company team/organization thing overall - for example, I work at a consultancy/outsourcer, and we can't just share whatever we want beteen divisions or teams. You've raised a lot of money (congrats :), and at some point you and your investors are going to want to make some money; so you can either charge individuals (which you've ruled out), or charge companies. Assuming the latter, and assuming you're going after larger companies with a lot of devs/sysadmins, I think your approach/presentation needs to be better tailored to that audience. If you're set on this "team" approach, I personally think it would be better to have it more like Slack (and many others), where someone has "ownership" rights for the team, and can manage its membership.
Thinking some more, I'm guessing your plan is something like: get as many individual devs/sysadmins on board for free, so they want it at work. If that's right, you need 2 better approaches/presentations: let individuals get it without barriers (like asking for business email...), and have a clearly separate paid plan.