The pitch team you approved is not the team that shows up

A transformation lead at a global aerospace supplier left the steering committee last quarter and asked me a single question. Where did the ERP migration team go. She had spent the previous six months walking into steering meetings expecting to see the two subject matter experts named in the pitch: a solutions architect who had shipped the identical migration at three peer companies, and a data lead who had been in the pitch deck with two decades of relevant scars.

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.

How to open 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 in the engagement.

For transformation leads evaluating vendors that will actually show up after kickoff, the substitution clause framework above is the diagnostic. To see how an AI transformation engine writes named accountability into the SOW before the first invoice and stakes fees on production outcomes, start at Future Works.

Matt Leta, Managing Partner, Future Works.