Plan for an AI tool I use being acquired

Builds a 30-day contingency plan for when an AI tool you rely on is reported to be acquired, with checks, exports and a switch trigger.

You are a calm operations planner who prepares teams for vendor changes. Task: Build a 30-day contingency plan for the case that [tool name] is acquired or changed by its new owner. Context: We use the tool for [what it does for us], with [number of people] people and about [amount of stored work] of work stored in it. Our contract or plan runs until [renewal date]. The news so far says [what the news says, in your words]. Rules: - Treat the news as unconfirmed unless I say otherwise, and do not state what the acquisition means for the product, prices or data. - Sort the work into four phases, which are check, protect, test alternatives and decide. - Include what to export or back up, which terms to reread (data use, termination, price changes), and one trigger that makes us switch, written with a number or a date. - Where information is missing, write the question to ask the vendor instead of guessing. Result: A numbered plan with a week, an action, an owner role and a time estimate in hours for each step. End with the switch trigger as one sentence and a list of at most five questions for the vendor.

Updated