3 ms·

The reason we suggest logging in with your work email is so that you can share shortcuts and completions for internal CLI tools with your team. We should proba

The reason we suggest logging in with your work email is so that you can share shortcuts and completions for internal CLI tools with your team. We should probably add this explanation to the login page because I can see how this would be confusing.

GordonS 5y ago
> The reason we suggest logging in with your work email is so that you can share shortcuts and completions for internal CLI tools with your team. 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!)
- mschrage 5y ago
  No worries. We determine who is on your 'team' based on email domain excluding webmail domains, like gmail.com and hey.com. 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!
  - GordonS 5y ago
    Ah, then it finally clicks. I really think you need to make this a lot clearer though. As others have already pointed out, if you're going to require this information, I think you need to ask for it up-front - don't ask for it at the end of the installer. 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.
f6v 5y ago
Off-topic, but given that this hasn't gone too well, I'd love to read a follow-up from you. Like, how you change your product after getting the feedback here.

GordonS 5y ago

> The reason we suggest logging in with your work email is so that you can share shortcuts and completions for internal CLI tools with your team. 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!)

mschrage 5y ago
No worries. We determine who is on your 'team' based on email domain excluding webmail domains, like gmail.com and hey.com. 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!
- GordonS 5y ago
  Ah, then it finally clicks. I really think you need to make this a lot clearer though. As others have already pointed out, if you're going to require this information, I think you need to ask for it up-front - don't ask for it at the end of the installer. 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.

f6v 5y ago

Off-topic, but given that this hasn't gone too well, I'd love to read a follow-up from you. Like, how you change your product after getting the feedback here.