91–96 of 96 posts
Congrats on your launch! Seems like you've had to build a lot of integrations with other platforms, any tips or tools that made that easier?
We built out our own Workflows engine that makes our life significantly easier. This way different customers can use the same integrations N number of ways without us needing to bake in a default configuration. Otherwise we'd be playing catch up all the time.
Earlier quoted context omitted.
From our experience we still see them in a number of deals. I think their focus has shifted more towards SLOs and Microsoft Teams though, areas where we aren't investing in right now.
Cool, thanks for this view. I'm also intrigued by the text in this launch announcement: > Our focus in the early days was build a hyper opinionated product to help them follow what we believe are the best practices. Now our product direction is focused on configuration and flexibility, how can we plug Rootly into your already existing way of working and automate it. This has helped our larger enterprise customers be…
Ironically having good tooling is the least important element in a successful incident response program (but it does help).
Motivated people and a good process far supersedes tooling. And yes so certainly see room for this. We are doing this already as part of our partnership model.
Part 1 is getting you setup and using Rootly. Part 2 is helping you successfully drive adoption now and 365 days onwards. We'll run workshops and AMAs with guest speakers on topics completely unrelated to Rootly when we are able to identify needs (we bare the cost). For example we did a session with a F500 organization on on-call compensation and another startup on communicating incidents to leadership.
The biggest mistake for a tool in this space is to think of this as only a PLG/SaaS based offering.
Congrats on the launch, I would use this for my smaller team. Why have a pricing page with no pricing on it though?
Thank you for the kind words and feedback. If you email jj@rootly.com we can get you some pricing ASAP. It'll be dependent on number of users and level of support/onboarding/custom feature development required. But if you're a small team, Rootly is powerful and ready to go out of the box with defaults and you might not require some of the custom stuff. To answer your question directly, we customize each package for e…
For the vast majority of your users, I would expect the amount of installation-engineering required to be zero. For every big business on an Enterprise plan of a SaaS like e.g. Cloudflare, there are 10 or 20 accounts for customers just as big(!) who are on their Business plan — which is basically the same feature-set, but without any of the high-touch custom stuff. Because they don't need any of it, in order to get all the value they need from the SaaS.
In other words, it feels like you have an Enterprise plan, but no Business plan. It's pretty easy to construct one — just assume any high-touch stuff doesn't happen. What's the base cost, per user?
Earlier quoted context omitted.
We have seen Slack start investing in this area with their own Workflow Builder they announced last year. One of the big use cases they highlighted was incident response. We haven't ran into any customers trying to leverage that just yet though as still a lot of heavy lifting required. IMO what makes Slack so power is their app ecosystem. We aren't too worried about them shutting that down or competing with us. We se…
I'm not familiar with Workflow Builder. Does it have a separate data retention scheme? Slack seems to have a big problem in that information quickly ages out, the search is pretty bad, and, in some cases, the data is actually ephemeral and will just disappear. Incident response is one of the categories that I want to preserve. Does Rootly address any of these problems? OK, I see at the end of the demo that there is a…
Only on free plans. Corporations that have customers with SLAs that they're doing incident-response for probably aren't using Slack's free plan.
But even if they are, the data's also not actually purged from their systems. It's still in the Slack-workspace archive export, if/when you do one of those. They just hide it from you. Paying for a plan un-hides it.
Earlier quoted context omitted.
I'll just ask, flag if this is out of place, I see lots of complaining about pricing - how many of those people are in a position where they would actually be buying this? Isn't it an enterprise product targeted to executive level buyers, and customized to the business? Just because some users or hands-on folks at smaller companies are angry they can't get a price doesn't mean there is a problem. It's probably a feat…
I'm im position of buying this kind of product (CTO of 50eng), I could be interested by this kind of tool (we're alerting a lot through slack, and I'm searching a way to better track my incidents), but i'll never take 1 hour to "present my company" and "discuss a pricing" for a such "little" product. For a product that costs tens of thousands of $ I understand, for a product that would cost hundreds, red flag, I don'…
Congrats on the launch. How is this different than FireHydrant?
The CEO of FireHydrant had a less charitable answer last year: https://twitter.com/bobbytables/status/1403090735038189573
https://twitter.com/evnsio/status/1442908782405701634
Standing on the shoulders of giants huh