SaaS I happily pay for: - CloudFlare - Roam - Slack - Linear - Geekbot SaaS I’m okay with paying for: - Figma - Gsuite - Gusto - Stripe - Netlify SaaS I’d rather not pay for, but have no choice: - AWS (SaaS in a sense I suppose - I actually don’t “pay” yet, working my way through credits) - Heroku (terribly expensive and does not provide startup credits that they say they do) - Wistia (the platform is clunky, but the…
SaaS We Happily Pay For
181–190 of 229 posts
Re: SaaS We Happily Pay For
#182No Atlassian products!
Re: SaaS We Happily Pay For
#183Earlier quoted context omitted.
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.
"Netflix is $10/m, so why would I buy Mailbrew" 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.
If you cost $100/hour, it only takes 6 minutes of saved time per month to pay back for it. Plus lost opportunity if a potential customer doesn't schedule the call with you. Reducing the friction to talk to customers is pretty big in my books.
The question is if the value you get out of the service is higher than what you pay for.
Re: SaaS We Happily Pay For
#184Earlier quoted context omitted.
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
#185Re: SaaS We Happily Pay For
#186Shhh... 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…
This comment sounds like the Infamous Dropbox Comment: https://news.ycombinator.com/item?id=9224 Time, energy, attention, creative limit is important for a tiny startups like this.
It does seem frivolous to me to pay money to automatically close tasks when a linked pull request is merged.
And paying $720 annually to host some frontends? Depending on what they mean by "frontend", this might actually be exactly $720 more than they ought to be spending on this.
Re: SaaS We Happily Pay For
#187I tried Linear, the interface is bit too bland to my taste. I am going to give it another try since there are so many good words about it in comments.
Re: SaaS We Happily Pay For
#188Earlier quoted context omitted.
> Most importantly it gets you SSO on basic plans for any SaaS. Is that because most SaaS offers "sign in with google"? Or is there something else involved?
Yep, saves a lot of annoyance having to keep track of a bunch of logins across SaaSs especially when you need to revoke access when someone leaves, so instead of having to go to all the various services individually to deactivate the accounts, you can just deactivate their Google account or revoke its access to those services.
Re: SaaS We Happily Pay For
#189Re: SaaS We Happily Pay For
#190Linear looks fascinating. We’re using Zenhub now and it’s slow and misused in our org (one giant project board instead of separate boards per repo / project). Curious if anyone here is / has used linear and could compare their experience with it to Monday, Asana or Zenhub?