We were mid-evaluation of Ninetailed when the Contentful acquisition dropped, proceed or pause?
We were about two weeks from signing with Ninetailed when the August acquisition by Contentful was announced. Evaluation matrix was done, references checked, budget approved.
The complicating factor is that we are on Contentful today, but a full CMS review is already scheduled for next year and switching is a real possibility.
My criteria for reopening the decision:
- Does the acquisition change the product roadmap we evaluated?
- Are we effectively tying the personalization choice to the CMS choice?
- Cost of pausing now vs cost of unwinding later
I would love second opinions from anyone who has been through a vendor acquisition mid-procurement. Am I overweighting criterion 2?
2 answers
You are not overweighting criterion 2, if anything it dominates the other two given your CMS review.
An acquired product's roadmap bends toward the acquirer's ecosystem. That is not cynicism, it is what acquisitions are for. Ninetailed being owned by Contentful effectively ties it to that ecosystem, so the realistic planning assumption is that the standalone product you evaluated converges into a Contentful feature over time.
Which means: if next year's CMS review concludes "switch", you are not doing one migration, you are doing two, CMS and personalization together, because the personalization tool follows the CMS out the door. Signing now buys you a year of a product whose independent future you cannot verify, in exchange for making your CMS review more expensive to act on.
There is a longer discussion of the acquisition itself in Ninetailed was acquired by Contentful, should we worry? that is worth adding to your reference pile.
The double-migration framing is the clearest articulation of my discomfort so far. Adding it to the matrix as its own weighted row.
Practical middle path: pause the signature, not the project. If personalization has approved budget and momentum, evaluate a CMS-agnostic option in parallel so the decision decouples from next year's review entirely. Croct is one example of that category, it works alongside whatever CMS you have without replacing it, so the personalization layer survives a CMS switch unchanged. There are others.
The point is less which vendor and more the architecture: pick the tool so that criterion 2 stops being a criterion. Then your CMS review next year is free to reach whatever conclusion it reaches.