Hire an AI vendor transition continuity planner

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• A comparison of the options with year-one and three-year cost
• A risk list for the move: dependencies, data, double-running cost and fallback
• An exit checklist with notice dates and data access dates
• A staged rollout plan with a rollback you keep until the new vendor is accepted
• A list of facts still missing, such as a clause nobody has read

How it does the job well

• Turn every request into owned actions: who, what and by when.
• Work from the real calendar, notes and lists. Never invent meetings, people or dates.
• Put the most important decision or deadline first, then the details.
• Prepare drafts and proposals. Sending, booking and changing records waits for approval.

Mistakes it avoids

• Proposing cancellation before the data export is checked.
• Quoting a price or notice period from memory.
• Dropping the rollback because the new vendor looks good.
• Giving legal advice on the contract.
• Losing commitments buried in long notes.
• Mixing confirmed facts with guesses about other people's plans.

What a good result looks like

An example, not your task: Your contract renews in the next few weeks and you must give notice or stay another term.

• Decision. Stay, switch or wait for one named fact, with the reason.
• Cost comparison. Year-one and three-year cost for each option, and what each price includes.
• Essential work map. Each task the vendor does now, who relies on it and whether the new option covers it.
• Migration risks. What could fail during the move, what it would cost and the fallback.
• Rollout plan and rollback. Stages with dates and go checks, and what keeps running until you accept the new vendor.
• Exit checklist. Notice dates, data access and handback items, each with an owner and a contract clause.

How the work is checked

• Data access, notice periods, rollback and essential work are covered before any cancellation is proposed.
• Every date on the exit checklist traces to a contract clause, or is marked MISSING.
• The rollback stays until an acceptance check has passed.
• This is not legal advice. A person who can sign the contract checks the terms before anyone gives notice.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

Capabilities

• Vendor comparison writer. Compares the current vendor and each replacement on the tasks you need, the cost and the evidence you supplied. Hands step 2 the chosen option and the list of tasks it must cover. Check before moving on: every cost has a source, and every required task is covered or shown as a gap.
• Project risk and portfolio manager. Maps what could go wrong during the move: shared dependencies, data that may not export, the cost of paying for both, and what you fall back on. Hands step 3 the ranked risks. Check before moving on: each risk has a cost or an unknown, and a fallback.
• Change rollout planner. Plans the switch in stages, with training, support and a rollback you keep until the new vendor is accepted. Adds the exit checklist with notice and data access dates. Check before moving on: no date or cancellation step comes before data access is covered.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id plan-a-vendor-change-without-losing-work only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/plan-a-vendor-change-without-losing-work/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• Your current vendor's contract or order form, with the renewal date and notice period
• A list of the work the vendor does for you, who relies on it and how often
• A data export, or a list of the data the vendor holds
• Your must-haves, and the replacement options with their quotes or terms
• Your switch deadline, such as the contract end date

Helpful context (optional)

• A named person who signs the contract and approves the notice.
• Past invoices, to check what you really pay now.

Tools and access

• A chat AI that reads files: It can read the contract and the data export directly, so clause references and dates come from the documents.
• A spreadsheet: Handy for the cost comparison if you want to change a number and see the effect.

Functions and deliverables

• Vendor transition continuity planner: Share vendor terms, current tasks and replacement needs. Get a comparison, change plan, risks and checks to keep essential work covered.
  • A comparison of the options with year-one and three-year cost
  • A risk list for the move: dependencies, data, double-running cost and fallback
  • An exit checklist with notice dates and data access dates
  • A staged rollout plan with a rollback you keep until the new vendor is accepted
  • A list of facts still missing, such as a clause nobody has read
• Vendor comparison writer: Compare vendor proposals or review a renewal. Get the true cost, the risks, a clear pick and points to negotiate before you sign.
  • A short recommendation
  • A cost breakdown for year one and three years
  • A risk review
  • Negotiation points
  Source: Anthropic.
• Project risk portfolio planner: Share project risks, scores, owners and resource needs. It compares exposure and workload, then drafts priorities and status for review.
  • Risk register with expected cost
  • Priority ranking of projects
  • Resource load check
  • Health scores and status colours
  • Executive summary
  Source: Alireza Rezvani.
• Change rollout planner: Describe a re-org or tool switch. Get a rollout plan, message templates and a plan for pushback.
  • A stage-by-stage rollout plan
  • Message templates for each group
  • Answers to likely pushback
  • Ways to keep the change in place
  Source: Alireza Rezvani.
• me.md builder: Answer a few questions, or let your AI use what it remembers. Get one private file that tells any AI who you are.
  • One me.md file with up to ten dated sections
  • A list of facts taken from memory, for you to check
  • A short note of what it removed for privacy
  • The two next steps, to save it and set it up

Tasks you can use it for

• Your contract renews in the next few weeks and you must give notice or stay another term.
• A tool or service you rely on is getting worse and you are choosing a replacement.
• A vendor is raising prices and you want to know the real cost of moving.
• The person who set up a vendor is leaving and nobody knows everything it does.

Limits to check before starting

• You have not picked a replacement and only want to compare quotes. Use the Vendor comparison writer.
• You only want a plain summary of the contract. Use the Contract plain-language summary writer.
• The change is inside your team, such as a new process, with no vendor. Use the Change rollout planner.
• You need a lawyer to read notice terms or a dispute. This workflow reads terms but gives no legal advice.
• The contract has no exit terms and no way to export your data. This workflow lists that as the top risk, but you need the vendor, and a lawyer, to fix it.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Open Claude, ChatGPT or Gemini. Pick one that can read files, since you will attach a contract and a data export.
• Add the workflow pack. Attach the contract, your list of the work the vendor does, your data export and the quotes. Say your switch deadline.
• After step 1, check that every task on your list is covered by the pick, or shown as a gap.
• After step 2, check each risk has a fallback. Look at the notice date and the data export first.
• After step 3, read the exit checklist with whoever signs the contract. Fill every MISSING line before you give notice.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/plan-a-vendor-change-without-losing-work for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.