The Hidden ServiceNow Consulting Costs That Blow Up Mid-Market Budgets
A CIO at a Central European insurance group called me in April with a very short question. Her ServiceNow programme had been signed off at €1.2 million eighteen months earlier. The current actual spend was €2.1 million. The platform was live in ITSM only, roughly half the original scope, and her CFO wanted an explanation before he approved another cent. She wanted to know whether her partner had ripped her off, whether her team had failed her, or whether this was just what a ServiceNow build looks like in the real world. The honest answer, which took me three days of reading her contracts and change notes to give her, is that it was all three at once, and none of the individual causes were dramatic enough to notice while the project was running. That is the pattern I see in almost every conversation about ServiceNow consulting costs. The headline day rate and the signed statement of work almost never predict the final invoice, because the money that kills the budget is not on either document. It shows up quietly in change notes, environment fees, extension weeks, and the specific overtime the buyer pays their own people to compensate for the partner's assumptions.
