The Real ServiceNow Implementation Timeline: What Vendors Won’t Print in the SOW
A CIO at a European industrial group forwarded me a slide last week. Big four brand on the cover, twelve neat swimlanes, "Go-Live: Q1 2027" in bold across the bottom. Nine months, ITSM plus HRSD plus a CMDB refresh, three geographies, forty-two integrations, twelve thousand employees. He asked me one question: is this real. I told him what I tell everyone who shows me a plan like that. The dates are real. The scope is not. Something in that triangle is going to slip, and if nobody names which side before the kickoff, the project will name it for them at month seven. This is the conversation nobody wants to have during a pitch. Vendors sell aggressive dates because aggressive dates win RFPs. Buyers accept aggressive dates because they need a business case that clears the CFO. Nine months sounds decisive. Fourteen months sounds like the vendor is padding. So everybody signs, and then everybody spends the second half of the project renegotiating what "live" actually means. The honest number for a full mid-to-large ServiceNow implementation is not nine months. It's twelve to eighteen, and the shape of those months matters more than the total.
