If you go to that Linear one’s site on an iPhone and zoom in really fast on their image of the todo list client, it immediately restarts your phone.
SaaS We Happily Pay For
131–140 of 229 posts
Re: SaaS We Happily Pay For
#132Earlier quoted context omitted.
Wow, surely there must be better way to test Stripe integration than just making excuses for paying for stuff you don't need?
What are they really losing there? the stripe fee? they are paying themselves 10 dollars minus the fee... surely it's worth the 60¢/month it costs for absolute certainty that your integrations work for real?
Re: SaaS We Happily Pay For
#133Earlier quoted context omitted.
Right. $27/month per user for email filtering and meeting scheduling seems absolutely crazy. While I applied the idea of supporting other small startups, lots of the items in this list seem frivolous!
> $27/month per user How does this even matter from a budget perspective? You are already paying probably in the $10-20k / month range for per-employee salary. Seems a lot like complaining about a dripping faucet while you have a water main break.
If you're in the west coast US. This company appears to be italian, so the reality is more like €3k/month, and as they're a startup it might be even less. The other option is looking at it that they're spending 10% of their recurring revenue on SAAS products, which as a 3 person team seems crazy.
Re: SaaS We Happily Pay For
#134"Collaborative email on top of G Suite. The main thing we pay for is a comment box below each email thread. It allows us to quickly discuss emails without forwarding or copy/pasting in Slack. It also allows us to edit drafts collaboratively and have multiple team inboxes for invoices, support, and other stuff." Thanks for the mention Francesco. I'm Philippe, one of the co-founders of Missive [1], don't hesitate if yo…
Re: SaaS We Happily Pay For
#135SavvyCal looks interesting, but for a "lean operation" can you really justify paying $12 per month per user for a service to schedule meetings? All of GSuite starts at $6/mo, and already does this.
Heard this one before. "Netflix is $10/m, so why would I buy Mailbrew (the product we make) for the same price?" Apparently hundreds of people are happy to pay for quality indie software that solves their problems. We are among them.
No, that's not the argument being made though.
The argument is 'why is a team of 3 paying 3x$10 to 'schedule meetings'. There's only 3 people, i.e. a reasonable questioning of the value being made.
Honestly, $10 is not that much, but why on earth would it be needed is a fair question.
Re: SaaS We Happily Pay For
#136Earlier quoted context omitted.
This isn’t really “testing”. It’s just signing up for their own service. They aren’t making stripe transactions and then reversing them. If stripe bans you from buying your own service, they may want to rethink that policy.
I think this is credit card company policy and not specifically Stripe. IIRC, there is some language regarding using your own credit card because it could potentially be used to give yourself a loan. Credit cards have a much higher APR and lower limits for a cash advance. Processing your own cards could be used as an avoidance.
Re: SaaS We Happily Pay For
#137I also had kind of a strange reaction to it, which I tried to figure out, and I'll explain it in case it's at all representative of other reactions being posted here.
I think it's just kind of intimidating to read a list of SaaS someone else uses. After reading the whole list, in the back of my head I'm imagining the burden of learning all of these all at once, of managing a dozen new passwords and payments I'm not currently managing, etc, and I'm not imagining an improvement to my own workflow because my work doesn't match yours.
It's easy to imagine getting zero or negative value out of any SaaS if it's not solving a problem I personally have.
But on the other hand it's hard to imagine getting less than 12/mo for any service that is doing something for me. And it's hard to imagine that a 3 person team mistakenly believes they like some service they're using.
So I'll skip the judgment about how you're spending money on improving your work environment and say thanks for the post.
Re: SaaS We Happily Pay For
#138If you go to that Linear one’s site on an iPhone and zoom in really fast on their image of the todo list client, it immediately restarts your phone.
Also happens if you open it slowly, but you have to zoom in quite a bit.
The inner image is just an image but there is a component around that. I am not a front end person and don’t have a theory but I’m also curious now.
Re: SaaS We Happily Pay For
#139Earlier quoted context omitted.
I know of no payment service provider that offers support for testing that is good for fairly normal 2020 software development processes. The standard seems to be offering one separate sandbox environment along with your production one, which you can use to experiment without literally making charges/refunds/etc, and possibly a set of specific credentials you can use to simulate various outcomes such as a declined ca…
In my experience, some (maybe not Stripe) payment vendors sandbox environments acts slightly different, and these minor issues can break things in production. A payment provider I worked with didn't have a proper way of "storing" cards. But you could create a subscription and bill it whenever you wanted. We didn't want to risk that the subscription stopped working, so we hard coded the subscription to be valid until…
I don’t know anything about payments or the EU regulations but it feels kind of stupid to not specify the maximum amount of time allowed? Is it just bad documentation or does that date/interval have to be secret for some reason?
Re: SaaS We Happily Pay For
#140Earlier quoted context omitted.
I know of no payment service provider that offers support for testing that is good for fairly normal 2020 software development processes. The standard seems to be offering one separate sandbox environment along with your production one, which you can use to experiment without literally making charges/refunds/etc, and possibly a set of specific credentials you can use to simulate various outcomes such as a declined ca…
In my experience, some (maybe not Stripe) payment vendors sandbox environments acts slightly different, and these minor issues can break things in production. A payment provider I worked with didn't have a proper way of "storing" cards. But you could create a subscription and bill it whenever you wanted. We didn't want to risk that the subscription stopped working, so we hard coded the subscription to be valid until…