THE SHORT ANSWER
Send Marco Di Santo's five questions from his November 10, 2026 post (an agent in production and how long it has run, the cost in its worst month, who fixes it after go-live and how fast, what it got wrong in the first weeks, and a call with the process owner rather than the sponsor), and mark each answer Shown, Described, or Missing as he says. Then ask for one artifact the sales side does not hold: the day-60 page the vendor's forward deployed engineer wrote for one account that went live two quarters ago. The page I use has four lines, the promise, the signal (the customer's own eval rows on a schedule, with the go-live pass rate as the floor), the watch list (what the customer switched off), and the keys (the named person at the customer who can change a prompt without calling the vendor), with a recall rule of three triggers and two business days underneath. It answers questions 1, 3, 4, and 5 with names and dates; question 2 sits on the per-outcome line. A vendor with agents in production has one per account. In my own pricing migration, 12 accounts sat on plan on the dashboard with usage under the minimum and two were lost; the page would have shown a blank keys line two quarters earlier.
