A platform team finds a useful system for shared company knowledge and approvals. The demonstration uses a different agent from the one employees know. The buying discussion quickly turns into a migration project: retrain people, recreate instructions, reconnect tools, and compare every feature of the new assistant.

Ask whether replacing the agent is necessary to get the benefit. If the current agent already does the work well, the purchase worth making is better company knowledge, reusable methods, controlled tool access, or evidence of actions, evaluated separately from a new interface or reasoning model.

The MCP enterprise practitioner discussion includes configuration portability concerns. A shared protocol makes connections possible and leaves real differences in setup, authentication, and behavior, so test the actual clients and tasks.

Identify the asset that should outlive the agent#

List what the company has built around the workflow: source connections, reviewed procedures, account knowledge, evaluation cases, finished artifacts, and decision history. Some belong in source systems, and others need a durable place where an authorized agent can retrieve them.

Then separate those assets from agent-specific behavior. A prompt shaped for one tool interface needs adaptation; a general procedure with clear inputs, outputs, and tests travels easily. A successful transcript is history, not a portable method.

The economic question is how much setup and correction a new agent must repeat. If every switch means rebuilding account context and rediscovering the same exceptions, switching stays expensive even when the subscription cancels instantly.

Item	Portability question
Company facts	Can another authorized agent retrieve current information?
Methods	Are scope, inputs, and expected results explicit?
Tests	Can the next agent be checked on the same work?
Tools	Do permission and approval rules apply on the new path?
Artifacts	Can people continue using completed work?
History	Can past decisions be explained after the switch?

Compare three purchase paths#

Run the same business task through keeping the current agent, replacing it, and supporting both. Count integration effort, training, review quality, execution cost, and the work of maintaining two paths. Supporting choice has value and also creates operational obligations.

Take an account-briefing process. The current agent drafts well but lacks access to reviewed company methods. Connecting that knowledge removes repeated instruction without changing the drafting tool. A replacement agent is better only if it improves accepted results or reduces review effort, and the test shows which.

A mixed arrangement fits when different teams have different jobs, and it does not require every tool to expose every sensitive action to every agent. Define what each path can access and which actions it can request. Company controls follow the authorized operation; verify their coverage.

Test substitution on an ordinary task#

Choose a completed task complex enough to expose dependencies. Give a second agent the approved method, permitted sources, and required output under the same acceptance rubric. Record what had to be rewritten, reconnected, or explained by the original operator.

Do not require identical prose; check accuracy, source use, permissions, cost, review effort, and accepted outcome. If the new agent uses a different tool sequence and meets the same conditions, the method is portable.

Also test a refusal or approval case. An agent that reads shared knowledge but bypasses the expected action gate has not shown a complete substitution. The integration has to preserve authority as well as retrieve the right paragraph.

Price the option to change#

The value of choice is partly immediate and partly future. Immediate value is less retraining and preserved productivity; future value is the ability to evaluate a better agent without rebuilding the company’s methods. Put a dollar figure on that option only with explicit assumptions. Better, measure a replacement rehearsal: engineering hours, operator hours, lost functionality, and repeated review. That gives procurement evidence about vendor dependence and shows leadership whether another path is worth its cost.

Deixic’s existing-agent page is the starting point for this purchase path. The product overview describes the company knowledge and methods a team keeps; Dex is an optional agent for teams that need one. Procurement covers the integration and commercial arrangement.