Absorbing Late-Stage Scope Without Moving Go-Live
How a surprise integration three months before go-live was funded instead of absorbed.
- Engagement
- Custom integration
- Pricing
- Time and materials
- Stage
- Mid-project
- Stakeholders
- Enterprise delivery team, executive leadership, C-suite
The situation
Three months into an implementation, and three months before go-live, the client raised a custom integration nobody had scoped.
What was really going wrong
- The integration had never been identified during discovery.
- The client saw it as an oversight that should be covered, not as new scope.
- The existing budget and timeline had no room to absorb the extra work.
How we fixed it
Step 1: Understand the real impact.
We worked through the integration's technical requirements with the delivery team and assessed what it meant for scope, timeline and resourcing.
Step 2: Agree our options internally first.
Before going back to the client, we aligned internally on the realistic options, including adding a resource and what each option would cost.
Step 3: Have the direct conversation.
We met the client several times that week and laid out the gap plainly:
This integration wasn't part of the original scope, and the current budget and timeline don't account for it. If we want to keep the go-live date, we'll need to adjust resourcing and budget accordingly.
The client agreed to add a resource and approve a dedicated integration budget.
What we refused to allow
Starting any integration work before the change was formally approved. Internally:
We are not starting this work until we have a clear agreement in place.
Tools we used
Change request and integration impact assessment.
The results
Stacked bar about $85K protected: about $35K integration build funded and about $50K unpaid extension avoided. Go-live date held.
~$85K protected
- ~$35K integration build funded
- ~$50K unpaid extension avoided
Go-live date held
~$85K
protected: about $35K for the integration build, plus an unpaid one-month extension worth about $50K avoided
Go-live date held
Escalations reduced
The lesson
When new scope appears late, separating accountability from obligation is what stops deadline pressure turning into unpaid work.
