* I can concoct exceptions of course: worker who wants to try it for work but doesn’t have their own company card being one. But if you’re targeting cloud users, “doing whatever AWS does to gate accounts” is perfectly reasonable.
* I can concoct exceptions of course: worker who wants to try it for work but doesn’t have their own company card being one. But if you’re targeting cloud users, “doing whatever AWS does to gate accounts” is perfectly reasonable.
This is extremely weird. It's a B2B - I won't ever use my own credit card just to try some service, heck - I won't provide my credit card to an unknown entity that may lack PIC compliance, either. Asking for the company/budget/contract review/etc. for trial, etc. is a massive hassle as well.
>doing whatever AWS does to gate accounts” is perfectly reasonable.
Not really, Amazon is beyond well known and massive, and it has all the policies in place. This a small unknown startup.
If you were a really hot prospect, super-interested in using elest.io for a big project but didn’t want to give a CC because <reasons>, I’m sure you’d find a way to contact them by email and try to work something out. And they’d find a way to vet you or just turn on a free account for you.* The casual “no way I’m giving my CC” people aren’t high-likelihood future paying customers.
Gate with a CC, make sure there’s a way to send an email/free text form and move on with building the company.
* “no way I’m sending an email either for a free trial just because I won’t give a CC.” “OK, you’re not a prospective customer. It’s a numbers game.”
I refuse to give my credit card details to google because I suspect I know what they will use it for, tracking, sneakily taking payments by dark patterns in apps or if my phone gets stolen.
Just because AWS can get away with something doesn't mean you can.