An AI program owner at a mid-market manufacturer told me the story that opens every one of these conversations. She had walked into her budget approval meeting with a deck that named three senior consultants and the partner who would lead delivery. The board approved the spend against those names. Kickoff was Monday. On Tuesday the partner sent an introductory email for the analyst who would be running her steering committee.
The arithmetic of the SI labor pyramid
The bait-and-switch is arithmetic. A partner-level principal cannot be deployed across twelve concurrent engagements. The firm margin depends on deploying that partner at the pitch and building the rest with junior analysts.
Three clauses that change this
Named resource commitment: the SOW lists specific individuals by name. Substitution requires client sign-off: any change requires written approval. Accountability cascade: the contract names who is accountable for each deliverable.
The question to ask in the first scoping call
Before the proposal stage, ask the vendor to read the resource substitution clause in their standard SOW. The language is the only binding commitment.
For AI program owners evaluating vendors delivering Agentic AI in production environments, the substitution clause framework above is where the SOW review begins. Teams that stake fees on Finance-validated outcomes name their experts in the contract. Teams that do not will substitute the moment kickoff clears.
Matt Leta, Managing Partner, Future Works.