In the land of computers being acquired tends to mean the acquired co. shutters their business, and everything they worked on ceases to be available to the customers who made them a company worth acquiring. I seriously applaud your allowing customers to set up their own servers. It's quite atypical... but it's kind of a dead-end thing unless you open-source the code. "Hooray... We can continue... but things will never improve, bugs will never be fixed, and our needs will eventually exceed the capabilities of the software that no-one is working on anymore."
Wouldn't it be nicer if the acquiring company valued the company being acquired enough to keep it going, or roll its functionality into its own offerings so that customers can continue being served?
The greatest asset of Clutch.io is the technical team and their ability to produce well-crafted code which means getting a return on the acquisition means deploying that team toward important projects at Twitter which could help them grow their userbase, engage existing users and monetize those users.
(Disclaimer - I have not spoken to the team about why they were acquired and what they'll be working on, but my statements are representative of what the majority of these types of acquisitions are like)
Not really, e.g. Oracle acquiring Sun or Vmware acquiring Nicira, not to mention all the $100M+ but "unfashionable" acquires that don't even get airtime on HN.
Anyway, I don't get this sort of complaint. If you really think the service had potential to be profitable, why not go ahead and clone it?
Yes, but usually not with any sort of press release from either company, or any other positioning that makes it sound like the "acquisition" was any indicator of success or strength.
Most startups are high-risk, and so it's blindingly obvious that there are going to be lots of ideas which are able to be implemented, but not scaled into a business. And we've all heard about VC's investing in the "team" more than the product, and how hard it is to find and hire really good engineers. So, a startup as sort of a long-cycle public job interview isn't the worst thing in the world.
Still, it would be nice (given the mindset of most engineers) to see the released framed in a more accurate way "Company X team being absorbed into Company Y", or "Company Y extends employment to entire team of Company X".
Perhaps it's just me, but I think most people see these "acquisition" press releases, and resulting "congratulations" rounds as somewhat of a poor veneer over the reality of what really transpired.
You just only read about tech-specific acquires here because that is the focus of HN.
If I started a company up, had no investment, then decided to go work at bigco on the understanding I could say they acquired my company, then it's all quite meaningless.
It's just a shame to see so many deadpooled companies and products through acquihires spun as "yay success!".
Maybe I'm just getting old ;)
As I say though, congrats on the new job.
A rising tide lifts all boats. We, as workers in this industry, should all be glad that there's now so much hype. There are many important industries that should get more of the community attention, but don't.
As an angel investor, I rarely see "the team just got jobs and we're calling it acquisitions" and more often "we paid off the investors minimally and got good job offers."
This is false.
After all, why work with a company made up of a few 25 year olds testing out a market, who may "pivot" any time, and will shut down their product when some big company wants to hire them? Seems like a justifiable choice to go with an inferior product from a profitable established company which is much less likely to disappear in two years.
Even as a startup guy, I'm hesitant to build on startup products. YC Startups may be even worse in this context as they are frequently picked off and shut down, and the founders are young and not necessarily in the product for the long haul.
It's open source
My co-founder Philipp is talking about this project at next week's Silicon Valley iOS Dev Meetup
A/B testing for mobile and social apps
Everyone take note. This is how you handle an aquihire correctly