When Your AI Vendor Consolidates Products Into One Platform: What to Check

ServiceNow just consolidated three previously separate AI product lines — Now Assist, Moveworks, and AI Experience — into a single unified system called Otto. Vendor announcements like this are typically framed as unambiguous good news: simpler experience, more capability, one system instead of three. For an existing customer of any of the consolidated products, though, the reality is more nuanced, and worth checking directly rather than accepting the announcement's framing at face value.

Why Consolidation Announcements Deserve Real Scrutiny

Product consolidation is a common pattern as an AI vendor's portfolio matures, especially following acquisitions (Moveworks, in ServiceNow's case, was itself an acquired company) — but consolidation can mean genuinely improved integration, or it can mean one product's roadmap and feature set being quietly deprioritized in favor of another, with existing customers migrated onto whichever underlying system the vendor decided to standardize on. Both outcomes get announced with similar positive language; only one is unambiguously good for every existing customer of every consolidated product.

The Actual Checklist for Existing Customers

• Ask directly which of the consolidated products' specific features are being retained, deprecated, or merged into the new unified system — a general "combines the intelligence of" description in a press release doesn't answer this at the feature level you actually need
• Confirm what happens to any custom configuration, integrations, or workflows you built on the specific product you were using — migration to a unified platform is rarely a zero-effort transition for a mature deployment
• Get a specific timeline for when the standalone products will actually be retired versus how long they'll remain supported in parallel with the new unified system
• Ask for the underlying architecture decision: is the unified system built on one of the original products' foundation (meaning that product's approach effectively "won"), or is it a genuinely new system requiring adaptation from every prior product's customers equally
• Request reference customers who have already completed migration to the unified system, specifically ones who were using the same original product you're on

Why This Matters More for Acquired Products Specifically

When one of the consolidated products was originally acquired from a separate company (as Moveworks was), the consolidation is also effectively the final integration step of that acquisition — the point where the acquired product's original architecture, roadmap, and team autonomy typically get folded fully into the acquiring company's systems and priorities. This is worth watching specifically if you adopted the acquired product for capabilities distinct from the vendor's core platform; those distinguishing capabilities are the ones most at risk of being deprioritized in a consolidation, even when the acquisition itself was framed as additive at the time.

Turning This Into a Standing Vendor Management Practice

Any time a vendor you depend on announces a product consolidation, treat it as a required check-in moment, not just an announcement to read and move past. Schedule a direct conversation with your account team specifically about migration timeline, feature parity, and support continuity — and document the answers, since verbal assurances during a sales or support conversation are worth confirming in writing before you commit further investment in whichever system you end up on.