Live data from Hacker News

SaaS We Happily Pay For

francescodilorenzo.com

151–160 of 229 posts

Re: SaaS We Happily Pay For

#151
post #6

SavvyCal 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.

Easily. It's about reducing the barrier to entry when someone wants to look at your demo. Every extra scheduling email you send is a chance to lose someone in the funnel. $6 extra a month? Irrelevant. Product probably underpriced because the guy can't demonstrate how many calls he's saving them.

Re: SaaS We Happily Pay For

#152
post #132

Earlier quoted context omitted.

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?

Well there's also the income tax and possibly VAT.

Surely that's based on your actual sales, not on your credit card receipts.

Re: SaaS We Happily Pay For

#153
post #52

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.

Also crashes my iPhone 8+ running 14.2. The page is noticeably lagging when just scrolling past that image too.

Re: SaaS We Happily Pay For

#155
post #97

Earlier 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.

This is anecdotal, so take it with a grain: I worked for a credit card processor about a decade ago, and it was routine to have the merchant run a penny transaction on the terminal, and refund it post testing to make sure it works.

They're fairly large processing over $40b in annual transaction volumes, and there wasn't any stress about not doing it again post testing (the only stress was the customer wanting a refund for the transaction costs).

If it is a merchant bank, or network requirement, it's either explicitly for card not present transactions, or not well followed. The important factor was handling of the credit card information (PCI DSS compliance).

Re: SaaS We Happily Pay For

#156

Shhh... you can do almost all of this on Github private repos for free. Tasks and issue management, wiki, kanban board, discussions, ci/actions to trigger other stuff (send notification email for e.g.), storage of docs, revision control, tagging and organization, notebooks (with code too!), static hosting, support tickets, and so much more with Github API/webhooks :) Startup of this size shouldn't be spending a dime…

Why not do everything in Emacs? I'm sure there's a plugin for everything here in Emacs as well!

Use whatever tool to create the product you want to create.

Re: SaaS We Happily Pay For

#159
post #141

I really appreciate this list. It's cool to see how people work, and I'm sure the folks building the services you're using appreciate the kind words. I 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 whol…

The more I read your comment, the less I understood it.

I understand it very well, and relate closely to the author's mixture of feelings. It's overwhelming and intimidating to be reminded that there's a bunch of stuff you ostensibly should be using, or at least researching and evaluating and deciding not to use.

Re: SaaS We Happily Pay For

#160
post #32

"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…

Who designed your logo? I like it.
Post reply on HN