Why Twilio Acquired Segment
rudderstack.com
rudderstack.com
Realized this when I use Twilio SMS + Video, Sendgrid and Segment together before their acquisitions and now I'm just sort of using Twilio, Twilio Sendgrid and now Twilio Segment.
I wouldnt build a startup on Twilio its costs eventually add up much higher than competitors. "Just because someone spends a lot on marketing doesn’t mean you should be paying for their marketing budget, especially as the core product commoditizes."[0] On the other hand they definitely have a rich API and I suppose they have tremendous uptime to boot. I never had a single issue setting up Twilio or Sendgrid any issues I had were with a web framework or other libraries, or network firewall but never Twilios APIs specifically.
https://www.bandwidth.com/twilio-alternative/
For a fun project though so can't comment on uptime etc. However, if they are powering the VOIP infra behind the other providers, should be good I guess?
If Twilio wants to own the entire developer ecosystem, maybe they will do others like APM first (Datadogs etc)?
In terms of culture, Twilio would be a better fit, given their focus on developer evangelism in user acquisition which is similar to Segment's strategy. In fact, if you look at Sendgrid, which Twilio has acquired 2 years ago, it also adopts a similar strategy.
Unless you try to send multiple requests to it's API at the same time. We've had to build in retry with random backoff into our mail sending helper because SendGrid's API doesn't like multiple requests at once.
Anecdata, but my experience with Sendgrid's support during a production outage was that to get a response from a human being we ultimately had to reach out to somebody on LinkedIn. Everything else via official channels just received automated replies promising responses in x business days. Also FWIW while our production e-mails weren't being sent, the Sendgrid API was happily returning HTTP 200 success responses.
I agree that it definitely was a breeze to integrate with though.
We had one emergency where someone figured out how to mass mail through our app (flawed "invite via email" feature), we were able to immediately reach support through the live chat feature and stop some 200k spam emails from being processed (they were in their queue by the time we noticed). Saved our butts.
Acquiring companies that are adjacent to your core business makes total sense in adding value to your platform, and not acquiring core functionalities allows you to claim that competition is getting stronger.
1. Complimentary businesses: Stripe is a developer interface for collecting payments from customers, Twilio is a developer interface for communicating with (and now understanding / "segmenting") your customers.
2. Similar culture: very high emphasis on great DX and developer evangelism. Shoutout to Stripe's docs for being the best in the biz, and Twilio's are not too shabby either.
3. Unique opportunities: Stripe collects payment for their customers, Twilio collects payment from their customers. If everything was under one roof, you could have a situation where Stripe becomes a de-facto bank account. Revenue comes in to your Stripe account and many of your consumables (paying for Twilio's services) could come directly out of that account, removing the need to egress funds to your bank at all, thus reducing financial transaction overhead (which at scale could be a sizeable gain in efficiency).
Enterprises could have a single point of truth (Segment) and target existing and potential customers via sms (Twilio), email (SendGrid) and digital ads (The Trade Desk).
I am just calling Unbundling of Building
Wrote some thoughts here:
https://twitter.com/ankitpansari_/status/1314915795433000960...
A whole group of software development functions - hosting, payments, storage, analytics, communication are being abstracted by modern services such as AWS, Twilio, Stripe, and Segment.
A software developer can now focus on the core value of the product.
Werner Vogels, the CTO of AWS, coined 'Undifferentiated Heavy Lifting'.
He suggests that businesses should use resources on-demand and pay for what they use, leveraging each other competency.
Shared some slides on my Tweet here - https://twitter.com/ankitpansari_/status/1314915795433000960