What should be in an AI vendor exit plan?

I

Imani Brooks

Operations and legal teams

6d

I am trying to get a realistic read on what should be in an AI vendor exit plan.

Cover data export, workflow replacement, contract terms, and customer impact.

What has actually worked (or failed) for your team? Specific examples, pricing traps, or vendor claims that did not hold up are especially useful.

1,377views6replies
R

Reid Callahan

Customer success lead

5d

Source quality beat model size for us. Clean knowledge + tool scopes fixed more hallucinations than switching models.

A

Aria Voss

Strategy & architecture

4d

Start with one bounded workflow that has a clear success metric. We tried to automate three use cases at once and none of them got good enough to ship.

K

Kenji Okada

Engineering manager

3d

The vendor demo is not the product. Ask to see the same workflow run on your data, not their sample data. That is where connector gaps and permission issues show up.

N

Noor Al-Hassan

Strategy & architecture

2d

Measure rework, not just throughput. An agent that resolves 80% of cases but creates 30% more manual cleanup is not saving time.

E

Elio Marchetti

Product manager

2d

We learned the hard way that 'human in the loop' is not a checkbox. If the approval UI is buried or slow, reviewers will batch-approve without reading.

S

Sage Whitfield

Product manager

19h

Security questions should be part of the first demo, not a procurement afterthought. Ask about retention, sub processors, prompt-injection testing, and audit logs before you waste time on a trial.