Implementation Strategy

Jun 15, 2026 Implementation Strategy

How to Pressure-Test a ServiceNow Implementation Timeline Before You Sign the SOW

A procurement lead at a German logistics company forwarded me three SOWs last week and asked which one to sign. The scopes were almost identical. ITSM, a light HRSD wave, around 800 employees, two integrations. The timelines were five months, seven months, and eleven months. The pricing roughly tracked the timeline, which is what made him nervous. He wanted to know whether the five-month vendor was a hero or a liar, and he wanted to know it before he committed his name to the contract. The honest answer is that you cannot tell from the SOW. You can only tell by pressure-testing the plan the vendor will not put on the slide. There are five questions that separate a vendor who has actually delivered a ServiceNow implementation timeline in your size segment from one who is selling you a number that exists only in a sales spreadsheet. None of them are about the platform. All of them are about the parts of the project the vendor would prefer you did not look at too closely. Every mid-market ServiceNow proposal arrives with a Gantt chart. The Gantt chart shows phases stacked on top of each other in a tidy waterfall. Discovery, design, build, test, deploy, hypercare. The phases have...

Jun 2, 2026 Implementation Strategy

ServiceNow Consulting Costs: What Mid-Market Buyers Actually Pay (And Why)

A finance director at a 600-person logistics company sent me three proposals last month and asked which one was the real number. The Big 4 firm had quoted €840,000 for an ITSM and HRSD build. A regional partner had quoted €420,000. A boutique had come in at €260,000. All three SOWs described, on paper, more or less the same scope. He wanted to know whether he was looking at three different qualities of work or three different ways of pricing the same work. The honest answer is that he was looking at one piece of work priced through three completely different commercial models. ServiceNow consulting costs are not opaque because the market is dishonest. They are opaque because nobody in the buying process is comparing like with like. Once you understand what each model is actually charging for, the right number for a mid-market implementation falls into a much narrower range than the proposals would suggest. This is the conversation finance directors deserve to have before they sign, not three months in when the change orders start arriving.

Jun 2, 2026 Implementation Strategy

ServiceNow Consulting Costs: What Mid-Market Buyers Actually Pay (And Why)

A finance director at a 600-person logistics company sent me three proposals last month and asked which one was the real number. The Big 4 firm had quoted €840,000 for an ITSM and HRSD build. A regional partner had quoted €420,000. A boutique had come in at €260,000. All three SOWs described, on paper, more or less the same scope. He wanted to know whether he was looking at three different qualities of work or three different ways of pricing the same work. The honest answer is that he was looking at one piece of work priced through three completely different commercial models. ServiceNow consulting costs are not opaque because the market is dishonest. They are opaque because nobody in the buying process is comparing like with like. Once you understand what each model is actually charging for, the right number for a mid-market implementation falls into a much narrower range than the proposals would suggest. This is the conversation finance directors deserve to have before they sign, not three months in when the change orders start arriving.

May 28, 2026 Implementation Strategy

The Real ServiceNow Implementation Timeline: What Mid-Market Buyers Are Never Told

A CIO at a Hungarian energy company asked me last month how long a ServiceNow implementation actually takes. He had three proposals on his desk. One said four months. One said seven. One said "approximately twelve depending on scope." All three were for what he described as "basic ITSM plus a bit of HR." He wanted me to tell him which one was lying. The honest answer is that all three were lying, but in different directions, and the most useful thing I could do for him was explain the timeline none of them had put on paper. ServiceNow implementations are not late because the platform is hard. They are late because the proposal everyone signs is built around the part of the project that vendors know how to estimate, and the parts that actually consume the calendar are either missing from the SOW or buried inside a line called "client responsibility." This is the conversation that needs to happen before a contract is signed, not at week sixteen when the program is already three months behind.

May 28, 2026 Implementation Strategy

The Real ServiceNow Implementation Timeline: What Mid-Market Buyers Are Never Told

A CIO at a Hungarian energy company asked me last month how long a ServiceNow implementation actually takes. He had three proposals on his desk. One said four months. One said seven. One said "approximately twelve depending on scope." All three were for what he described as "basic ITSM plus a bit of HR." He wanted me to tell him which one was lying. The honest answer is that all three were lying, but in different directions, and the most useful thing I could do for him was explain the timeline none of them had put on paper. ServiceNow implementations are not late because the platform is hard. They are late because the proposal everyone signs is built around the part of the project that vendors know how to estimate, and the parts that actually consume the calendar are either missing from the SOW or buried inside a line called "client responsibility." This is the conversation that needs to happen before a contract is signed, not at week sixteen when the program is already three months behind.