Earlier quoted context omitted.
"We haven't figured out pricing" sounds like a big turnoff for anyone seriously considering this who wants self service. Just pick something that's a no brainier for people to try, change it later if you have to. Your biggest risk right now is people walk without giving the product real consideration. Lack of clarity on pricing will do that for a lot of people, even though you are offering a free trial.
Thanks for the advice. One challenge for us will be how to price-in token based costs, e.g. downstream GPT services. There was an interesting post earlier today on HN related to this https://news.ycombinator.com/item?id=43186032 which recommended progressive pricing, which I thought was really interesting. On the other hand, the marginal cost of these services is being aggressively driven down by the big players so i…
Show HN: Emdash – Slack/Zoom alternative for distributed team collaboration
51–60 of 69 posts
Re: Show HN: Emdash – Slack/Zoom alternative for distributed team collaboration
#52This looks great. What is the reason for adding the https://sso.tax ? Why did you make SSO an enterprise feature? Is it due to some (technical) reason that would require a monetary compensation to be profitable? SSO has security benefits (on top of the maintainability aspect) which would also benefit small businesses.
Re: Show HN: Emdash – Slack/Zoom alternative for distributed team collaboration
#53Earlier quoted context omitted.
SSO tax seems like a very reasonable price differentiation method to me. Most of the price increases on sso.tax are quite reasonable for a company that needs SSO (most companies I've worked in don't bother until they are above 100 employees, despite what that site says).
> SSO tax seems like a very reasonable price differentiation method to me Security is not a differentiation method. It's table stakes for any technical product. That's what the above linked website explains.
Security as table stakes, sure. SSO, certainly not.
It's an additional cost, last I checked it was between 10$ and 20$ per user per month if you take the cheapest option and outsource it.
This whole notion of "Unless you meet this security standard that 99% of products don't meet, your product hasn't met table stakes" is nonsense and needs to die.
SSO will get cheaper in the future; for now it's hard for a product development team to justify getting 0$ in revenue just because of some purity test by irrelevant folk on the internet.
Re: Show HN: Emdash – Slack/Zoom alternative for distributed team collaboration
#54This looks great. What is the reason for adding the https://sso.tax ? Why did you make SSO an enterprise feature? Is it due to some (technical) reason that would require a monetary compensation to be profitable? SSO has security benefits (on top of the maintainability aspect) which would also benefit small businesses.
SSO tax seems like a very reasonable price differentiation method to me. Most of the price increases on sso.tax are quite reasonable for a company that needs SSO (most companies I've worked in don't bother until they are above 100 employees, despite what that site says).
Companies don't "bother with" SSO because using SSO is expensive, since every product charges more for the privilege. Otherwise there's no reason why a 2-person company shouldn't be using SSO from the get go.
Re: Show HN: Emdash – Slack/Zoom alternative for distributed team collaboration
#55Earlier quoted context omitted.
Thanks for the advice. One challenge for us will be how to price-in token based costs, e.g. downstream GPT services. There was an interesting post earlier today on HN related to this https://news.ycombinator.com/item?id=43186032 which recommended progressive pricing, which I thought was really interesting. On the other hand, the marginal cost of these services is being aggressively driven down by the big players so i…
Have you thought about carving out the token expense? I.e. giving users the option of using their own api key vs you being the middle man for that expense?
Re: Show HN: Emdash – Slack/Zoom alternative for distributed team collaboration
#56Earlier quoted context omitted.
> SSO tax seems like a very reasonable price differentiation method to me Security is not a differentiation method. It's table stakes for any technical product. That's what the above linked website explains.
> Security is not a differentiation method. It's table stakes for any technical product. Security as table stakes, sure. SSO, certainly not. It's an additional cost, last I checked it was between 10$ and 20$ per user per month if you take the cheapest option and outsource it . This whole notion of "Unless you meet this security standard that 99% of products don't meet, your product hasn't met table stakes" is nonsens…
Re: Show HN: Emdash – Slack/Zoom alternative for distributed team collaboration
#57Re: Show HN: Emdash – Slack/Zoom alternative for distributed team collaboration
#58Re: Show HN: Emdash – Slack/Zoom alternative for distributed team collaboration
#59Re: Show HN: Emdash – Slack/Zoom alternative for distributed team collaboration
#60do conversations support nested threads? one frustrating limitation of slack is that a convo in a channel can be put into a thread, but that thread can't have nested threads, which makes it more difficult to follow long, multi-person conversations