AI-enabled functionality requires defined customer value, data rights, model behaviour, human oversight, security, cost, incident authority and version control. Marketing language should not outrun supported performance or contractual responsibility. Research options remain distinct from dependable production capability.
Acquisitions require product, architecture, people, customer, data, security and financial integration milestones. Synergy is not counted merely because customers or technologies appear adjacent. The board can stop integration capital when retention or technical evidence moves.
For a ₹500 crore-plus technology portfolio, acquisition integration is governed through architectural dependency and customer migration choices, not only synergy targets. Management records which identity, data, billing, entitlement, observability and support systems will remain separate, converge or be retired, together with the customer and incident risk of each transition. Capital is protected for continuity and reversible migration before cross-sell or cost savings enter the base case. This gives the board a practical way to stop one integration stream while preserving the acquired product's customers, talent and standalone cash if the shared-platform thesis weakens.