There has been a run of acquisition news across the developer tooling world this summer, and this week one of them landed on something I actually use, every day, without thinking about it. I am being deliberately light on the specifics, partly because the details are still settling and partly because the specifics are not really the point. The pattern is the point, and I have lived through enough versions of it now to recognise the shape before the press release has finished loading.
You know the rhythm. The blog post goes up. It is warm and reassuring and uses the word "journey" at least once. Nothing will change. The team is staying. The product you love is in safe hands and will now be "even better resourced." Everyone tweets that they are excited. And then, somewhere between six months and two years later, you find out what the deal actually bought, and it is almost never the thing the blog post said.
the three outcomes, and how to read which one you're getting
In my experience an acquisition of a tool you depend on resolves into one of a few outcomes, and you can usually tell which one within a quarter if you know what to watch.
The first is genuine investment. Rare, but real. The acquirer wanted the product and the team, leaves them largely alone, and pours in resources that a smaller company never had. The tell is that the public roadmap keeps moving and the original engineers keep shipping and keep talking. When this happens it is wonderful and you should enjoy it, because it is the least common of the three.
The second is the acqui-hire wearing a product's clothes. They wanted the people, not the thing. The product is kept on life support whilst the engineers are quietly redeployed onto the parent's actual priorities. The tell here is a roadmap that goes still. No new features, just security patches and the occasional dependency bump, and a support queue that gets slower and politer. The thing is not dead, but it has stopped growing, and a tool that has stopped growing in a moving ecosystem is dying slowly.
The third, and the one that empties my heart, is the absorb-and-rebrand. They wanted the market position, the customer list, or the technology to fold into a larger suite. The standalone product gets a sunset date, a migration path to the Enterprise Platform you did not ask for, and a pricing model that assumes you have a procurement department. The tell is the appearance of the word "platform" where there used to be the name of a thing that did one job well.
what i actually do about it
I have stopped reacting to the announcement and started watching the behaviour. The announcement is theatre. The behaviour is data. So my response on day one is, deliberately, to do almost nothing, which is harder than it sounds when a chunk of your daily workflow has just changed owners.
What I do do is take stock honestly:
- How locked in am I, really? Could I export my data in a format another tool can read, today, before anyone has a reason to make that harder? If the answer is no, that is the first thing to fix, regardless of how the acquisition plays out.
- Is there an open alternative I have been ignoring because the proprietary one was simply better? Acquisitions are an excellent prompt to re-evaluate the open option, which has often quietly caught up whilst I was not paying attention.
- What is my actual switching cost? Not the imagined, catastrophic one, the real one. Half the tools I feel trapped by, I am not. I have just never priced the exit.
Then I wait, and I watch the roadmap, the changelog, and crucially whether the people who built the thing are still publicly working on it or have gone conspicuously quiet. The engineers leaving is the loudest signal there is, and it usually arrives a long time before any official change to the product.
The other thing I have started doing is reading the new owner's existing portfolio, because that tells you more than any announcement. If they have a history of buying tools and shepherding them well, that is a genuinely good sign and you can relax a little. If their back catalogue is a graveyard of products that were "joining the family" and then quietly disappeared into a suite nobody asked for, you have your answer regardless of how warm this particular blog post is. Companies acquire in patterns, and the pattern is on public record if you go and look. I had not thought to do that for years, and it is the single most useful five minutes you can spend the day a deal is announced.
the uncomfortable bit
Here is the part I have made peace with, slowly. None of this is anyone's betrayal. The people who build a great tool are allowed to sell it. They worked hard, they took a risk, and a life-changing cheque is a perfectly reasonable thing to accept. My disappointment is real but it is not a grievance. I built a dependency on something I did not own and could not control, and that was my choice and my risk, made because the tool was good and the trade was worth it at the time.
What I have learned is to make that trade with my eyes open. When I adopt a closed tool now, I ask up front: what is my exit, and how much does it cost? If I cannot answer, I either find the answer or I do not adopt it for anything load-bearing. It is not cynicism. It is just pricing in a risk that was always there, that I used to pretend was not, until a few too many warm blog posts taught me otherwise.
For now, this particular tool still works exactly as it did last week. I will keep using it, I will keep watching, and I have already spent twenty minutes confirming I can get my data out cleanly if I need to. That twenty minutes is the entire lesson. The day to plan your exit is the day you do not need one, and an acquisition is simply the universe sending a reminder that you should have done it already.