A systems integrator client called me last quarter, halfway through a nine-month manufacturing modernization program, asking the same question I hear on a loop: where did the pitch team go. She had approved the engagement based on a named partner, a named domain lead, and a named integration architect. Two months in, the partner was signing status reports she suspected he was not reading.
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.
Reading the pitch for planned substitution
The pitch team is senior. The SOW lists team members by title, not name. There is no named resource commitment clause offered and no explanation for its absence.
For systems integrator clients evaluating vendors delivering Agentic AI at production scale, the pitch-team-vs-delivery-team pattern above is the diagnostic. Firms that name their experts in the contract and stake fees on production outcomes cannot afford substitution.
Matt Leta, Managing Partner, Future Works.
