[synicalx]

I'm very curious, why base everything on Slack? There's no denying it's super popular (and my preferred choice for collab) but the majority of businesses don't use it, and it indirectly adds cost to your product; if I want to use (and pay for) Rootly I also have to pay for Slack (which is expensive).

And to echo everyone else here; not having up front pricing is a big red flag. You've done well to attract the large customers you have at the moment, but you're going to struggle to draw in the long tail. Engineering teams don't want to talk to your sales people and they shouldn't need to - if AWS can tell me what I'll be paying right down to the second for something, I'm sure you can tell me how much your tool will cost me to use each month without needing to call me.

EDIT:

I should also clarify, I actually quite like this tool from what I've seen of it. Looking at how we handle incidents I could see something like this addressing a lot of our pain points.

[jjtang1]

The messaging for "managing incidents on Slack" is a lot easier to understand and digest we found than something like "all-in-one incident management platform".

We have an entire Web platform that performs the same functions as Slack but also can configure custom Workflows, integrations, view metrics, service catalog, and more.

And thank you for the feedback on pricing, we have a bit of work to do here to make it easier to understand the financial cost before investing time to chat with us!