Cutting a Fixed-Fee Write-Off in Half
How timing and executive alignment recovered budget on an under-priced ERP project.
- Engagement
- ERP implementation
- Pricing
- Fixed fee
- Stage
- Early delivery
- Stakeholders
- Finance and operations teams, CEO, CFO, CTO, CIO
The situation
A fixed-fee ERP project was heading for a loss of about $130K before delivery was even well underway.
What was really going wrong
- The fixed fee had been priced well below the real scope and complexity of the work.
- Functional consulting and project management effort had both been underestimated during the initial analysis.
- The client refused to approve more budget at first, because the contract was fixed fee.
How we fixed it
Step 1: Confirm the gap early.
We met the firm's partners and core delivery team to validate the shortfall and quantify the financial risk while there was still time to act.
Step 2: Earn the right to ask.
After the first budget conversation met resistance, we deliberately held off re-raising it until the team had made meaningful, visible delivery progress, so the next conversation would come with credibility.
Step 3: Make the case to executives.
We held several executive-level discussions, two to three times a week at the peak, showing progress, remaining scope and the funding gap side by side. The message was direct:
We need to be fair about the work that needs to be done and the budget that goes with it.
What we refused to allow
The team doing unfunded extra work while the budget was being resolved. New requests were parked until the budget was in place.
Tools we used
Budget-burn versus forecast tracking.
The results
Bar comparison. Projected write-off about $130K. Final write-off about $65K. Difference labelled Cut in half.
Projected write-off: ~$130K
Final write-off: ~$65K
Cut in half
~$65K
projected write-off, reduced from about $130K
Budget approved
Additional budget approved on a fixed-fee contract
Escalations reduced
The lesson
On fixed-fee work, a budget shortfall is a delivery risk, not a finance problem. Raise it early, back it with progress, and don't let the team absorb losses quietly.
