Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Launch HN: Rootly (YC S21) – Manage Incidents in Slack

news.ycombinator.com

Post reply on HN
Print view View original

61–70 of 96 posts

Re: Launch HN: Rootly (YC S21) – Manage Incidents in Slack

#61

Post by jjtang1 »

renewiltord wrote: post #59
jjtang1 wrote: post #55

Earlier quoted context omitted.

Thank you! You're not alone, I've ran into quite a few cases where working from a thread will suffice (big and small companies). We are still team dedicated incident channel but there are a few things that threads do better. For example, the number of incident channels that get spun up can get out of hand. Threads are a lot cleaner for that. So we built a workflow that'll let you specify an auto archive behaviour. We…

Great stuff. Good luck with your product. I imagine we'll need it later but for the moment, I think we're too small to be worth your time. Would have loved to have run into you guys when/if you were looking for seed investment though

Appreciate the kind words and agree on fit.

Happy to compare notes and stay in touch if you'd like to connect of course jj@rootly.com.

Re: Launch HN: Rootly (YC S21) – Manage Incidents in Slack

#63

Post by altdataseller »

hijinks wrote: post #35
dneri wrote: post #32

Congrats on the launch, I would use this for my smaller team. Why have a pricing page with no pricing on it though?

because they want to look at crunchbase and find out how much funding you got then charge you based off that. I wish companies would boycott companies doing contact us for pricing

Well, then they would charge me pennies because the startup I work for has $0 funding :)

Re: Launch HN: Rootly (YC S21) – Manage Incidents in Slack

#64

Post by altdataseller »

midislack wrote: post #15

I’ve always wondered about building a startup on another startup’s back. What happens if they cut you off? Is getting bought up by Slack the end goal here? Seems like a big risk, one whim at Slack and you’re toast.

The risk is lower when you're not actually competing directly with that platform. For instance, if you're building a Twitter client reliant on the Twitter API, that's a bigger risk since you're directly competing with Twitter.

Unless Rootly is grossly doing something negligent, the chances are extremely low that Slack will not allow Rootly to build a Slack app.

Re: Launch HN: Rootly (YC S21) – Manage Incidents in Slack

#66

Post by jjtang1 »

MarketingJason wrote: post #65

Agree with many of the sentiments on here about pricing. I actually came across Rootly a couple months ago when looking for this sort of solution and the lack of transparency on cost led me to immediately dismiss it as an option

Oof, thank you for the feedback. We certainly don't want that happening. We'll look into adding greater transparency that works for our model so you can make a better informed decision upfront.

Re: Launch HN: Rootly (YC S21) – Manage Incidents in Slack

#67

Post by jjtang1 »

altdataseller wrote: post #62

PagerDuty has a product called RunDeck, which sounds familiar to your offering. Do you view them as competition?

Indirectly, their automations are less incident management/process focused but more on remediation (e.g. run A to restart db). Whereas ours are more focused around e.g. updating status page automatically, inviting responders, posting reminders, syncing with Jira, etc.

Re: Launch HN: Rootly (YC S21) – Manage Incidents in Slack

#68

Post by jjtang1 »

altdataseller wrote: post #64
midislack wrote: post #15

I’ve always wondered about building a startup on another startup’s back. What happens if they cut you off? Is getting bought up by Slack the end goal here? Seems like a big risk, one whim at Slack and you’re toast.

The risk is lower when you're not actually competing directly with that platform. For instance, if you're building a Twitter client reliant on the Twitter API, that's a bigger risk since you're directly competing with Twitter. Unless Rootly is grossly doing something negligent, the chances are extremely low that Slack will not allow Rootly to build a Slack app.

Yup that is a very good point. We make Slack even stickier for their customers and ours alike.

Re: Launch HN: Rootly (YC S21) – Manage Incidents in Slack

#69

Post by jjtang1 »

drevil-v2 wrote: post #57

I will echo the other comments on no upfront pricing. Even though this could be potentially useful for my team, I won't "contact" you for pricing. I am sick of having to deal with salespeople who want to know a ton of info about your business so they can gouge every last cent out of you and then some. I would gladly pay a little extra just to have clear pricing and sign up with a credit card. I have got an engineerin…

Appreciate the feedback here. We'll look into what we can do to help you make a more informed decision around the financial cost structure and how that works before deciding to try us.

Re: Launch HN: Rootly (YC S21) – Manage Incidents in Slack

#70

Post by Mandatum »

Aren't you concerned with IR or ITSM tools (ala ServiceNow) just copying your patterns and adding it to their existing Slack Apps? Slack already has public demos with pretty much the same pattern you've adopted.

Have you got a bigger end-goal, because this is trivial to copy well. You need a moat, or you need to seek acquisition quick.

Post reply on HN