Live data from Hacker News

PagerDuty S-1

sec.gov

61–70 of 194 posts

Re: PagerDuty S-1

#61
post #21

Earlier quoted context omitted.

They're spending $30M+ on R&D, so if you feel that way as a customer, that's not good.

On principle alone I wouldn't give them my money ever again. I'd engineer my own lightweight solution before then or use an underdog competitor. I have a sour taste in my mouth for their meteoric rise to success/IPO versus their pathetic investments (or lack therof) in product improvement. It really sucks to use. Reminds me of Engineyard (also abandonware).

We tried using one of their competitors and strongly disliked it, enough to go back to PagerDuty in under a year.

I'm sure there are other options we could have tried, but it seems to do what we need pretty well.

Re: PagerDuty S-1

#62

I run a service that integrates with pager duty on behalf of our users, and man oh man did they make some poor design choices with their API. The most glaring one is their integration keys, which is how you trigger an alert. They’re just v4 uuids with the hyphens removed, or in other words, completely random. This is fine by itself, except they have two versions of their event API, and keys for the v1 API don’t work…

if you've ever logged into pager duty and tried to use it you'd know UX/ergonomics is not their strong suit.

Re: PagerDuty S-1

#63
They just raised a round in September of 2018 at $1.3B so it will be interesting to see where the public market values the company.

2017 revenue: $79.6MM 2018 revenue (est): $117.8MM 2019 revenue (est): $164.9MM 2020 revenue (est): $214.3MM

Safe guess potentially 10x current year (2019) which would be $1.6B.

Considering that they need an IPO pop the shares would be priced about 20-25% lower, bringing them back to that $1.3B private round valuation.

Unless the bankers are very optimistic and it will trade higher in which case they would be looking to price at the $1.6-1.7B range and hope that it pops to $2B at open.

Re: PagerDuty S-1

#64
post #3

Earlier quoted context omitted.

> Support is often viewed as a cost center Support is a cost-center for B2C companies, but one of the most important parts for B2B.

It’s still usually viewed as a cost center by management in either case, and employees in support roles are notoriously underpaid, overworked and at risk of inexplicable layoffs. I would love to see more companies treat support technicians and customer support agents like prized human capital, give them good job security, don’t try to outsource or downsize them, and give them top class compensation to make them very…

Which is why managers in B2B support organization often start moving toward profserv ... which then creates a downward spiral in the value the core product provides.

Re: PagerDuty S-1

#65

PagerDuty feels like abandonware. It hasn't changed in the last 4-5 years.

When I call my insurance or bank, I get a pleasant voice interface.

When PagerDuty calls my carphone (or worse, my motorcycle helmet communicator), I get an inhuman civil defense robot from 1980 that only accepts touch-tone inputs.

Re: PagerDuty S-1

#66
post #46

Earlier quoted context omitted.

Uh, that is a big negative sign for me, because they have an an "employer active" account. In other words, they pay for the privilege to get reviews deleted. > 100% approval rating of our chief executive officer. So I am 99.99% sure that HR was tasked with removing bad reviews ;-)

That's so unfortunate. I remember back when Glassdoor prided themselves on not doing that.

Oh look a penny..

Re: PagerDuty S-1

#67
post #63

They just raised a round in September of 2018 at $1.3B so it will be interesting to see where the public market values the company. 2017 revenue: $79.6MM 2018 revenue (est): $117.8MM 2019 revenue (est): $164.9MM 2020 revenue (est): $214.3MM Safe guess potentially 10x current year (2019) which would be $1.6B. Considering that they need an IPO pop the shares would be priced about 20-25% lower, bringing them back to tha…

You need to dream bigger. Palantir looking to go public at 45X revenues.

https://news.crunchbase.com/news/palantirs-2018-revenue-said...

Re: PagerDuty S-1

#68

Earlier quoted context omitted.

Uh, that is a big negative sign for me, because they have an an "employer active" account. In other words, they pay for the privilege to get reviews deleted. > 100% approval rating of our chief executive officer. So I am 99.99% sure that HR was tasked with removing bad reviews ;-)

Is there any evidence that glassdoor lets employers do this? I think glassdoor actually specifically says that they won't, unless it violates a law somehow. They even specifically state that they "don’t take sides in factual or contractual disputes between employers and reviewers." https://help.glassdoor.com/article/I-m-an-employer-What-can-...

Generally employers figure out who left the bad review and threaten legal action to the person who made the review. It isn't Glassdoor that removes the review but the person who wrote it.

Re: PagerDuty S-1

#69
post #21

Earlier quoted context omitted.

They're spending $30M+ on R&D, so if you feel that way as a customer, that's not good.

On principle alone I wouldn't give them my money ever again. I'd engineer my own lightweight solution before then or use an underdog competitor. I have a sour taste in my mouth for their meteoric rise to success/IPO versus their pathetic investments (or lack therof) in product improvement. It really sucks to use. Reminds me of Engineyard (also abandonware).

I feel that while OP is correct - PagerDuty hasn't changed much - engineering my own on-call system is the last priority of pretty much any business. It's one of the things you don't want to do yourself.

Additionally, PagerDuty works extremely well and I can't think of any additional features we need right now.

Re: PagerDuty S-1

#70

I run a service that integrates with pager duty on behalf of our users, and man oh man did they make some poor design choices with their API. The most glaring one is their integration keys, which is how you trigger an alert. They’re just v4 uuids with the hyphens removed, or in other words, completely random. This is fine by itself, except they have two versions of their event API, and keys for the v1 API don’t work…

What's the big deal in checking if each version works?

Sounds like you just need to ignore the errors you get when testing the API version, e.g. wrap a try/catch block around the request.

If that's your big gripe with the API, you have it pretty good!

Post reply on HN