[teej]

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

[evrydayhustling]

This goes against my intuition in several ways, so I'm curious if there are examples to discuss.

- Scaled deployments have Segment connecting many systems run by many teams, so the cost of coordinating a replacement can go up just as fast as Segment's.

- High growth companies have fires everywhere, including other infrastructure, so it's not obvious that Segment makes it to the top of the list.

- I expect the bulk of Segment revenue is not from companies with "high growth" by HN standards but scaled enterprises with high complexity and lower growth. These can dominate net rev retention even if there are smaller companies growing faster.

Again, no data to support the above, just a different narrative. Anyone have facts?

[texasbigdata]

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.

[nikitaga]

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.

[teej]

The end state is you DIY. Segment isn’t doing anything secret/magic, it’s just well executed and super convenient.

The “how” question has changed every 3 years in the last 10 that I’ve done data work. That trend is driven primarily by data scale and partially that analytics and ML access patterns have evolved a lot.

[bleonard]

We are building Grouparoo (https://www.grouparoo.com) because we think you should be able to do this yourself and own/control the data - without the incentive structure being messed up from the cost pressure.

[texasbigdata]

Do y’all have pricing info?

This post [0], and the open job requisitions suggest you’re using a bit of cash to do this. What is your business model?

0: https://mobile.twitter.com/grouparoo/status/1292844163617239...