Live data from Hacker News

Twilio set to acquire Segment for $3.2B

forbes.com

11–20 of 101 posts

Re: Twilio set to acquire Segment for $3.2B

#13

This seems cheap, segment was doing great especially with sass the way it is now.

Segment (and any other SaaS that wants to own the event firehose) has pricing issues as the customer scales. As a customer you are charged on data volume[0], but your data grows at the rate = (Users x Engagement X Features X Data Sources). That rate can easily be the square of your revenue growth.

This pricing issue makes it easy for Segment's fast-growing customers to justify an in house replacement. This puts huge down-pressure on their "revenue retention" rate and makes it hard to raise more VC or go public.

[0] - Segment technically prices on user volume but in reality it's a mix of users + objects depending on what your sources are

Re: Twilio set to acquire Segment for $3.2B

#15
post #13

This seems cheap, segment was doing great especially with sass the way it is now.

Segment (and any other SaaS that wants to own the event firehose) has pricing issues as the customer scales. As a customer you are charged on data volume[0], but your data grows at the rate = (Users x Engagement X Features X Data Sources). That rate can easily be the square of your revenue growth. This pricing issue makes it easy for Segment's fast-growing customers to justify an in house replacement. This puts huge…

So what’s the end state solution? The tools change and/or mature slower than a fast company will grow. Where are you going from here?

Are you eventually running your own cluster? Or, are you paying per Gb per second how GCP bills with decoupled compute / memory / storage? Or maybe with a little bit more overhead with the orchestration cost on top of consumption with how azure bills for ADF.

Just from reading blog posts, Spotify’s move was interesting, regarding their annual “songs you liked” at the holidays, where they sort of ran a hybrid.

Sorry to digress but what is the end state. Is there just a number where it makes sense to hire people and build and/or shift vendors? And if yes, what vendor is “after” stich? Astronomer maybe. Sorry if that’s basic.

Re: Twilio set to acquire Segment for $3.2B

#16
This is the same Segment that started out as a single Javascript file that a couple guys threw together before rebranding right? I mean, they're so much more now (or so it seems) but feels like it was just yesterday... and I'm only 26!

Re: Twilio set to acquire Segment for $3.2B

#19
post #2

Twilio feels like a great fit for Segment, all the best to the team and the next steps. Show HN: Analytics.js (2012) https://news.ycombinator.com/item?id=4912076 via @rauchg https://twitter.com/rauchg/status/1314709848030756864

It's kinda nuts. They have some videos on startup school. They basically just threw spaghetti for months building random products for markets they barely understood until they landed on analytics and it just snowballed. This isn't even a brilliant idea. They entered a crowded market with a solution that was just a bit better than everyone else and now have a $3B exit.

Re: Twilio set to acquire Segment for $3.2B

#20
post #13

Earlier quoted context omitted.

Segment (and any other SaaS that wants to own the event firehose) has pricing issues as the customer scales. As a customer you are charged on data volume[0], but your data grows at the rate = (Users x Engagement X Features X Data Sources). That rate can easily be the square of your revenue growth. This pricing issue makes it easy for Segment's fast-growing customers to justify an in house replacement. This puts huge…

So what’s the end state solution? The tools change and/or mature slower than a fast company will grow. Where are you going from here? Are you eventually running your own cluster? Or, are you paying per Gb per second how GCP bills with decoupled compute / memory / storage? Or maybe with a little bit more overhead with the orchestration cost on top of consumption with how azure bills for ADF. Just from reading blog pos…

Solution seems obvious, volume discounts in one shape or another.

SaaS companies pricing is often geared towards startups that "can't afford" to control costs, i.e. developer time spent on minimizing cost has a higher monetary and opportunity cost than ignoring those costs in the short term, even if they're piling up at $50/mo for every auxiliary service.

But that strategy does not account for those same startups after they grow enough to take a breath and start optimizing costs.

Post reply on HN