41–50 of 135 posts
Why is the pricing per user? Is that what your costs are most dependent on? I bet not. I'd argue $5/user is just teaser pricing on its way to PagerDuty's $21+/user. Regardless, cool project—happy to see more competition.
I found PagerDuty to be grossly underwhelming when our team moved to it. I'd focus on stupid-easy integration & some reasonable calendar management to differentiate. PagerDuty Calendar/Holiday/Workday management and cross-regional scheduling were very poorly implemented. The amount of manual schedule adjustment when someone actually wanted to take their 1 week vacation was insane. We ended up with overrides on top of…
For instance at Google, taking vacation in workday puts an OOO event on your Google calendar. Then the oncall scheduler takes that into account along with your oncall history when it schedules new rotations. You only have to get someone to cover if you are taking time off in the near future, and any surplus or deficit will be fixed by the scheduler going forward. It's kind of wild that an expensive product with tons…
So as cynical as my statement may seem- " It's almost like they wanted it to be easier to just not take time off?" .. user ergonomics just doesn't enter into the conversation at all, because the users are internal devs.. who cares.
I also worked at an org that gave each of 50+ large customers a dedicated slack channel with.. wait for it.. the entire internal 200+ member engineering org in channel with them. You can imagine the mayhem as each customer figured out how to get attention (@here/@channel/@theguythatfixedthislasttime) and "hack the phone tree" as I used to call it.
This also meant the every one of our 200+ engineers was a member of 50+ customer channels which were filled with all levels of noise that 95% of the time had nothing to do with their app/team/function, and could/should be ignored.
Why is the pricing per user? Is that what your costs are most dependent on? I bet not. I'd argue $5/user is just teaser pricing on its way to PagerDuty's $21+/user. Regardless, cool project—happy to see more competition.
If you ever start a business selling anything at all, the very first thing you will need to realize is that you never base prices on how much something costs. You base prices on what people are willing to pay.
Sms is a very good fallback channel for push notifications, especially when you don't have good internet coverage for an unexpected reason. I also personally hate phone calls, but I find it more effective to wake people up at night.
Earlier quoted context omitted.
This a deal breaker for me. I understand your intention here and from a pure alerting perspective you're correct, but I have use cases for other forms of notification.
Too bad. :( Would've loved to help you out. Would you mind elaborating on your usecases and why it's axactly a deal breaker?
Why is the pricing per user? Is that what your costs are most dependent on? I bet not. I'd argue $5/user is just teaser pricing on its way to PagerDuty's $21+/user. Regardless, cool project—happy to see more competition.
Since when does anyone set or scale their price on their costs?
Same with increase interest rates
It's certainly widely believed that "price = cost + %profit" rather than "price = level at which maximum profit will be achieved after factoring in market segregation"
Earlier quoted context omitted.
I think the design is you use the automatic escalation if the page isn't acknowledged.
Yes, it will auto-escalate to your team mates, if you don't acknowledge.
Typically there was a fall-back escalation, and then it would go straight up the management chain, which seemed idiotic.
Pagerduty's SLA for availability is 99.9% (3 nines) which is up to 43.8 minutes per month.
If you build your Pagerduty clone on AWS, your theoretical maximum availability is 99.99%.