71–80 of 100 posts
Hi folks! Just in 8 months, we grow our Slack bot from zero to $25,000/mo. Moreover, it keeps growing like crazy. Based on our learnings we prepared a step-by-step guide on how we did that. I hope it will be useful to you. Feel free to ask me questions here.
Re: "we grow our Slack bot from zero to $25,000/mo." "Or your mattress is freeee "
Earlier quoted context omitted.
Want me to do a screen sharing of our Baremetrics dashboard? Reach out to me at alex at standuply.com to book a call.
I'm amazed at the hostility here these days :( It's very accommodating of you to offer to share additional metrics. To be honest, my interest isn't intense enough to warrant my time for a screen share, much less yours. I will keep an eye on your blog, though. ETA: I can't seem to find an RSS feed for your blog :( ETA2: It's at https://standuply.com/blog/feed/ , but don't see a link to it anywhere.
Remember when this used to be a friendly startup forum full of people who liked hearing about interesting technology and how it was made?
Earlier quoted context omitted.
That is so true. We were building for Telegram before Slack and was very disappointed business-wise about it. Now we're fully focused on Slack and it helps us in building a great product for the narrow use-case. However, of course, we're looking for ways to expand our market. I'm not sure about Discord (how many of you guys are using it?), but MS Teams, Google Chat, and Stride are the other players that in my opinion…
During an interview I had at Discord recently the lead engineer mentioned they had exceeded 130 million users. Though, there was also a recent bump by almost 70 million people that left Skype and joined Discord in the news recently as well. He told me that Skype is the 800 pound gorilla to beat and that they have around 300 million users or something. They're definitely gunning for them, and Microsoft has changed Sky…
Earlier quoted context omitted.
That is so true. We were building for Telegram before Slack and was very disappointed business-wise about it. Now we're fully focused on Slack and it helps us in building a great product for the narrow use-case. However, of course, we're looking for ways to expand our market. I'm not sure about Discord (how many of you guys are using it?), but MS Teams, Google Chat, and Stride are the other players that in my opinion…
I've used Discord since sept 2015. It's been an interesting journey (my friend develops a bot and has reached 26,000 servers and 3 million users.) It's quite good, but still does not support stereo audio input inside of the client. Canary build has a new experimental audio subsystem so it may be now, haven't tested yet.
Earlier quoted context omitted.
That is so true. We were building for Telegram before Slack and was very disappointed business-wise about it. Now we're fully focused on Slack and it helps us in building a great product for the narrow use-case. However, of course, we're looking for ways to expand our market. I'm not sure about Discord (how many of you guys are using it?), but MS Teams, Google Chat, and Stride are the other players that in my opinion…
During an interview I had at Discord recently the lead engineer mentioned they had exceeded 130 million users. Though, there was also a recent bump by almost 70 million people that left Skype and joined Discord in the news recently as well. He told me that Skype is the 800 pound gorilla to beat and that they have around 300 million users or something. They're definitely gunning for them, and Microsoft has changed Sky…
Earlier quoted context omitted.
We've seen plenty of people going all in building their business on a platform they don't control, then getting mad when the platform they depend on changes how things work. With that said, are you guys also targeting other platforms than Slack? I'm sure MS Teams, Discord, etc provide the same foundations for an even larger reach?
>We've seen plenty of people going all in building their business on a platform they don't control, then getting mad when the platform they depend on changes how things work. I've always wondered about this. When you depend on another, already-monetized platform to build on, your livelihood depends on a variety of factors not in your control. What if they decide to make your functionality part of their core product?…
Choosing Slack doesn't mean it's the only platform you're developing for. You can expand the same value proposition to other platforms with the same business users (I can't say the same regarding other b2c chatbots/platforms, though).
Hi folks! Just in 8 months, we grow our Slack bot from zero to $25,000/mo. Moreover, it keeps growing like crazy. Based on our learnings we prepared a step-by-step guide on how we did that. I hope it will be useful to you. Feel free to ask me questions here.
I'm curious if you could talk about your unit economics: 14,000 teams are using your bot (including some big brand tech companies), but its translating to what feels small, 25k/mo for a 7 person operation.
So I'm more concerned about our growth rate rather than revenue numbers.
As for unit economics, we're very lean burning less than $20k. So we're able to survive and grow Standuply further.
Hi folks! Just in 8 months, we grow our Slack bot from zero to $25,000/mo. Moreover, it keeps growing like crazy. Based on our learnings we prepared a step-by-step guide on how we did that. I hope it will be useful to you. Feel free to ask me questions here.
My company has a Slack bot product and we've found that we are able to drive lots of clicks the "Add to Slack" button but a very low percentage complete the installation. Our assumption is that this is because most users that get to the "Add to Slack" button are not administrators and most users won't go through the (frankly poorly designed) "find an administrator" flow... but of course we have no visibility into wha…
1. You ask for too many permissions. It makes a lot of sense to ask for less because people don't like to share their sensitive information with the product they don't know/trust yet.
2. It may depend on your target audience, but our users in most cases are able to install the bot on their own. So it doesn't hurt our (not yet perfect) onboarding flow.
Earlier quoted context omitted.
Why would a company that relies heavily on bots shut us (or another valuable) bot off?
They decide they want to provide the features you provide directly? See Twitter, Google, Apple, Microsoft etc. It's a very old game at this point and you really should be aware of your risk in being so dependent on what is effectively a closed platform. (i.e. an API does not make a closed platform open) They're providing APIs right now to help fuel their own growth but once that growth levels off, or worse reverses,…