Implementation Strategy

Oct 13, 2026 Implementation Strategy

ServiceNow Consulting Costs: Fixed-Fee vs Time-and-Materials, and Which One Actually Protects Your Budget

A finance director at a logistics group in Rotterdam called me in February. Their ServiceNow ITSM rollout had been running for eleven months on a time-and-materials contract with one of the big consultancies. The original estimate was 420 billable days. They had just signed off invoice number thirty-four, and the running total was 710 days. Nothing was live yet. The project manager kept using the phrase "complexity emerged during discovery," which is consultant Esperanto for "we didn't scope it and now we're charging you to fix our scoping." She asked me one question. "Would a fixed-fee contract have stopped this?" The honest answer is that it would have stopped most of it, and the parts it would not have stopped would at least have been someone else's problem. That is the whole argument for how ServiceNow consulting costs should be structured in a mid-market engagement. Not that fixed-fee is cheaper on paper, because sometimes it is not. The point is that fixed-fee shifts the scope risk off your P&L and onto the vendor's, and that is the risk that actually blows budgets.

Oct 7, 2026 Implementation Strategy

The Two Weeks That Decide Your ServiceNow Implementation Timeline

A head of IT at a 600-person industrial supplier called me after their partner's third timeline slip. The signed statement of work said twenty-two weeks to live incident, request, change, and a thin CMDB. By week nineteen, the delivery lead was asking for an eight-week extension and quoting discovery findings as the reason. His board had already approved the extension when he phoned me, so he was not asking for help negotiating. He wanted to know what he could do differently on the next phase so it did not happen again. His question is the right one, and the honest answer is that almost every ServiceNow implementation timeline is decided before the official kickoff meeting. The two weeks before the project is announced to the business are where most of the slip is manufactured, and nobody budgets for them. I say this at the risk of annoying every account executive at every system integrator. They sell a start date. Clients buy a start date. Everybody wants the kickoff slide in the second week of the quarter. What actually drives whether a project lands on time has very little to do with the kickoff and almost everything to do with the preparation that either happened or did not...

$ServiceNow Consulting Costs: The Honest Math Nobody at a Big 4 Will Show You$

Sep 23, 2026 Implementation Strategy

ServiceNow Consulting Costs: The Honest Math Nobody at a Big 4 Will Show You

A COO of a European logistics company forwarded me a proposal last month. Two hundred and eighty pages. A well-known Big 4 firm quoted €1.4M for what she described as "a fairly standard ITSM implementation with HRSD in a second phase." She had already paid €90K for the assessment that produced the proposal. Her question to me was simple: is this what ServiceNow actually costs, or am I being played? The answer is uncomfortable for the industry. She was being played, but not in the way she thought. The €1.4M number was not made up. It reflected real hours, real rates, real overhead. The problem was that roughly 40% of those hours would be spent on things that added no value to her instance, and she had no way to know which 40%. This is the conversation about servicenow consulting costs that partners avoid, because the moment you actually break the numbers apart, the pricing model that funds most of the industry stops making sense for anyone who is not a Fortune 500.

Sep 21, 2026 Implementation Strategy

The Real ServiceNow Implementation Timeline: Why Six Months Rarely Means Six Months

A COO signs a Statement of Work in January. The SI has quoted a 24-week ServiceNow implementation timeline, ITSM Pro plus a light ITOM footprint, go-live in early July. She circulates the plan internally. Marketing pencils in a launch webinar. Finance builds the licence spend into the Q3 forecast. HR schedules the change-comms rollout. By late April the delivery lead sends the first quietly worded status note. Discovery took longer than planned because the CMDB source data was worse than anyone admitted. Two integrations were re-scoped when the SAP team said their middleware team is booked until September. Change requests are stacking up. The July date is now "at risk". By June it has slid to October. By October it is November with a phased approach. The webinar is cancelled. None of this is unusual. It is the average ServiceNow implementation timeline for a mid-market rollout done properly. The problem is that almost nobody quotes it that way at the sales stage, so every project starts with a plan that was already fiction on the day it was signed.

Sep 5, 2026 Implementation Strategy

ServiceNow Consulting Costs: What a Mid-Market Buyer Actually Pays and Why the Number Keeps Moving

A CFO at a 600-person distribution business emailed me in July with a spreadsheet. Two proposals for the same ITSM foundation project, both from tier-one partners. One was €480k, the other €1.1M. The scopes looked, on the surface, almost identical. Same modules, same integrations, same go-live window. She wanted to know whether the cheaper firm was cutting corners or the expensive one was gouging. The honest answer was neither. What she was looking at was two different ways of pricing the same uncertainty, and neither number was going to be the number she actually paid. That is roughly the tenth version of that conversation I have had this year. Buyers ask what ServiceNow consulting costs should be and the market gives them a range wide enough to drive a truck through. Some of that spread is real. A lot of it is theatre. This post is the honest breakdown of where the money actually goes, why the sticker price and the final invoice almost never match, and what a mid-market company can do to stop being surprised.

Sep 3, 2026 Implementation Strategy

The Real ServiceNow Implementation Timeline: What Sales Decks Don’t Tell You

A COO at a 900-person logistics company forwarded me a proposal last month. Fifty pages, three modules, six weeks from kickoff to go-live. Fixed price, "accelerator-driven", "pre-configured for logistics". She wanted to know if the number was real. It was not. What she was looking at was a sales artifact, not a plan. The team that wrote it had never actually delivered a working ITSM instance in six weeks and would not this time either. But it looked clean on a slide, and someone in her CFO's office had already circled the price. That conversation is roughly the fifteenth version of the same conversation I have had this year. Buyers ask "how long does it take to implement ServiceNow" and get back a number that has nothing to do with the work sitting in front of them. So this post is the honest version. If you are budgeting a ServiceNow implementation timeline, or trying to sanity-check one you have been handed, this is what you actually need to plan for and where the weeks go. For a mid-market company doing a genuine ITSM foundation, meaning Incident, Problem, Change, Knowledge, Service Catalog with maybe a dozen real items, a working CMDB with Discovery pointed at production,...

Aug 21, 2026 Implementation Strategy

ServiceNow Consulting Costs: What You Actually Pay For, and Why the Number on the Statement of Work Is Almost Never the Final Bill

A CIO at a mid-market insurer emailed me on a Tuesday morning last month. Subject line: "second opinion." She had a signed SOW from one of the Big 4 for a Now Assist rollout across ITSM and CSM. The headline number was €780,000 over nine months. Reasonable, on paper. Six months in, the run rate was tracking to €1.4 million and the go-live date had slipped twice. She wanted to know two things. Was she being taken for a ride, and what would a boutique shop have quoted for the same scope. I get some version of that email about every three weeks now. The gap between what buyers think they are signing up for and what they end up paying is the biggest source of pain in ServiceNow programmes right now, and it is almost entirely avoidable if you know where to look before you sign. Every ServiceNow implementation has three cost lines. The one on the SOW. The one that hits your budget. And the one your finance director will actually approve when the change request lands on their desk in month five.

Aug 20, 2026 Implementation Strategy

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.

Aug 6, 2026 Implementation Strategy

Comparing ServiceNow Consulting Costs: Boutique, Big SI, and Vendor Pro-Services

A procurement lead at a European retail chain sent me three quotes last month and asked me to explain why they were so different. All three vendors had been briefed against the same document. A Big Four systems integrator quoted €1.4 million for the ITSM and HRSD build. ServiceNow's own professional services team quoted €980k. A boutique firm on my recommendation quoted €520k. She wanted to know whether the boutique had missed something, whether the Big Four had padded, or whether the vendor was quietly the best deal in the room. The honest answer took an afternoon of reading the small print and a call with each partner about how they staff a project. That is the conversation every buyer eventually has. The public rates people quote for ServiceNow consulting costs make the three delivery models look roughly comparable, and then the actual invoice arrives and they are not comparable at all. If you are running a competitive procurement right now, or trying to decide whether the price you are being quoted is fair, you need to understand what you are actually buying inside each of the three quotes. The rate card is the smallest part of it.

Aug 4, 2026 Implementation Strategy

How to Sequence a Multi-Module ServiceNow Implementation Timeline Without Everything Slipping

A CIO at a European medical devices group walked me through his eighteen-month plan last week. ITSM in wave one. HRSD and CMDB in parallel in wave two, four months later. SecOps and a customer portal in wave three, another six months after that. The board had already seen a Gantt chart with three neat rectangles stacked in sequence, each shorter than the one before. The programme sponsor had committed to the dates. The vendor had priced the whole thing at a discount if it landed inside the eighteen-month window. He asked me one question. Was any of it real. The honest answer is that a multi-module ServiceNow implementation timeline almost never survives contact with wave two, and the reason is not the platform. The reason is that the client organisation gets tired somewhere around month five, the vendor rotates the A-team off the account after go-live, and nobody wrote down what the interlock between waves actually costs in decision bandwidth. By the time wave two kicks off, the muscle that carried wave one is exhausted and the assumptions the plan was built on have quietly stopped being true. This post is about how to sequence a multi-year roadmap so that does not happen.