What Boutique ServiceNow Consulting Settles in a Two-Hour Scoping Call That Takes a Big 4 Six Weeks

A head of IT at a 600-person logistics firm sent me a scoping document last month. Forty-one pages. It had been produced by one of the Big 4 after what they called a “discovery and assessment engagement.” Six weeks, three onsite workshops, nineteen stakeholder interviews, a kickoff deck, an interim readout, a final readout, and a signed statement of work for the next phase. The invoice for the discovery was €84,000.

He asked me to look at it before he signed the implementation SOW. I read the whole thing on a Sunday afternoon. The actual content, once you stripped out the appendices, the methodology slides, the “future state vision,” the governance structure diagrams, and the eleven-page stakeholder RACI, fit on about two pages of substance. His current ITSM instance was over-customized. He needed a rebuild of incident, problem, and change on a cleaner data model, with a reasonable integration to his monitoring tool and a sane service catalog for his internal users. That was it.

I called him back on the Monday. We spent two hours on the phone. By the end of that call I had a scoped build plan, a sequencing recommendation, a rough cost band, and a shortlist of the three technical decisions that were going to matter most. He said, “That is more useful than everything I just paid for.” That is not a compliment I particularly enjoy giving to myself, because it means someone wasted a lot of money.

I am going to walk through why this gap exists, because it is not an accident and it is not a matter of individual competence. It is structural. And it is one of the clearest reasons to think carefully about whether boutique ServiceNow consulting might fit your work better than the Big 4 default.

Why a Big 4 scoping phase takes six weeks

The economics of a Big 4 engagement require that discovery becomes its own billable phase. A partner on an account cannot bill the firm’s margins by handing you a free call. The firm’s cost structure, its utilization targets, its practice overheads, and the fact that most of its ServiceNow bench is made of consultants who have been in role for under two years, all push toward a scoping engagement that is long enough and expensive enough to justify a dedicated project team.

That team then has to produce artifacts that look proportional to its cost. So you get the forty-one page document. You get the current state assessment, which maps your existing processes to a maturity model that was built for enterprises three times your size. You get the future state vision, which is a generic blueprint lightly edited to mention your industry. You get a benefits realization framework. You get a governance model with three steering committees. None of it is wrong. Most of it is irrelevant to the actual decision you need to make, which is: given your constraints, what should we build, in what order, and what is likely to go sideways?

The six weeks are not evil. They are the shape the engagement has to take for the firm’s commercial model to work. But the output is calibrated to justify the cost of the output, not to answer the question you came in with.

What boutique ServiceNow consulting does differently in two hours

A boutique engagement is run by someone who has done this work directly, usually fifty or more times across their career, and who does not need a team of five analysts to arrive at a view. On the kind of scoping call I run with mid-market buyers, the structure is roughly this.

The first twenty minutes are about the business. What are you trying to deliver? Who is the pain for? What has already been tried, and why did it not work? What is the political terrain? Who is sponsoring, and what does success look like for them specifically? Not the methodology framing of success, the actual one, the one they will be judged on in twelve months.

The next forty minutes are about the instance. If you can get me into your sub-prod for a screenshare, better. If not, I ask targeted questions. Which modules are live. Which are turned on but unused. Which plugins. How much custom scripting. How many update sets are stuck in dev. How often changes get rejected. What the current CMDB looks like. Whether anybody owns it. What integrations are running, and whether they are IntegrationHub, scripted REST, MID server pulls, or something older.

The following forty minutes are the honest part. I tell you what I think we should do first, and why. I tell you what will break if we do things in a different order. I give you a rough cost band for the next three to six months of work. I flag the two or three decisions that are going to drive 80% of the project outcome, and I give you my view on each one. If I think your situation does not warrant hiring me, I tell you that too. Those twenty minutes decide more than any kickoff deck.

The last twenty minutes are housekeeping. What are the right next steps. Who else needs to be in the follow-up. What the proposal will look like. When you will have it.

That is a scoping engagement. It takes two hours because the person running it has already done the pattern recognition that a Big 4 scoping team is doing in real time, in parallel, and with four tiers of internal review.

Why the best ServiceNow consulting partner for a mid size company is usually one who can scope on a call

The reason this matters is not just the cost of the scoping phase. It is what the scoping phase tells you about who will actually run your project.

A Big 4 scoping engagement is run by a senior partner, maybe a senior manager, and a scoping team of analysts. None of those senior people will be on your delivery. They will be present at the kickoff, they will show up at the steering committee, and they will not be the ones who open your instance in week four and realize that your current custom table design is going to make the incident consolidation twice as complex. By then you are working with the delivery team, which is a different set of people, and the relationship between what was scoped and what gets built is loose at best.

A boutique scoping call is run by the person who will actually be on your project. If I scope you, I build you. If what I promise in the two-hour call turns out to be wrong, I eat it, because I am still the person on your account three months later when you notice. The incentives are aligned by the shape of the firm.

This is not a feature. It is just what happens when the person who sold the work is the person who delivers it. And it is one of the main reasons the best ServiceNow consulting partner for a mid size company tends to be a specialist practice run by senior practitioners, not an SI with a bench of juniors supervised remotely.

Should I hire a Big Four firm or a specialist SI: what the scoping phase tells you

I want to be fair to the Big 4 here. There are projects where their model is genuinely the right choice. A global rollout across fifteen countries with carve-outs for local tax regimes, a merger integration where you need program management across six workstreams and 200 people, a transformation where the ServiceNow build is one piece of a much larger business change program. Those are projects where the Big 4 cost structure maps to real complexity, and where their program management capacity earns its keep.

If your project is one of those, hire the Big 4. The scoping phase will still be slow and expensive, but you need the artifacts because you will reference them for the next three years and twenty-six people will need to be aligned to them.

If your project is a mid-market ITSM rebuild, an HRSD go-live, a CMDB cleanup, an integration consolidation, or any of the hundred other things that mid-market ServiceNow buyers actually need to do, hire the specialist. The scoping call will give you the clarity. The build will be done by the person who scoped it. The deliverable will be a working instance, not a document deck.

The honest version of “should I hire a Big Four firm or a specialist SI” starts with: what does your scoping conversation feel like? If the Big 4 is sending you a scoping proposal and the boutique is giving you a call, you have two different products on your desk, not one product at two prices.

What top small ServiceNow partners vs Big 4 Accenture Deloitte sell differently

The confusion in the market is that both sides sell the same thing on their website. Both have a page that says “ServiceNow consulting.” Both list implementation, advisory, managed services. The difference is not visible until the first meeting.

A top small ServiceNow partner will tell you, within an hour of talking to you, what they think you should do. They will push back on parts of your current plan. They will probably correct your terminology somewhere. They will not treat the discovery conversation as a sales call.

A Big 4 will treat the discovery conversation as a sales call, because the next step is a proposal to run discovery. The incentives force this. The first paid phase is almost always discovery, and discovery is where the margin lives on a Big 4 contract, because that is the phase that is easiest to pad with junior consultants and process overhead.

Watch for this signal. If the first call is scoping work, you are talking to a practice that gets paid to deliver. If the first call is a qualifier for a longer discovery proposal, you are talking to a practice that gets paid to sell discovery.

Where to start, practically

If you are evaluating a ServiceNow partner right now and you want to pressure-test which side of this line they are on, do these four things.

Ask the firm for a two-hour technical scoping call before you sign anything. Ask that the senior person who would be on your delivery is the one on the call. If they will not do that, you have your answer about who will actually be in the chair when the project is running.

In that call, bring your three hardest open questions. Not the strategic ones. The specific ones. How should I design the CI relationships for my CMDB given that I have both AWS and on-prem? What should I do about the thirty-seven custom tables my previous partner built? How do I sequence HRSD onto an instance that already has ITSM live? Watch how they handle the questions. A seasoned practitioner will have an opinion in minutes. A sales-led engagement will defer every answer to the discovery phase.

Ask what the proposal will contain. If the answer is a document with executive summary, methodology, team org chart, benefits framework, and governance, you are getting Big 4 output. If the answer is a scope note, a sequencing plan, a cost band, and a resource plan, you are getting a boutique proposal.

Finally, if you have already paid for a Big 4 discovery document and you are not sure what to do next, get a second opinion on it from a boutique practitioner before you sign the implementation SOW. Our 10-day Instance Health Report is one way to do that; a scoping call against your existing document is another. Either way, do not let the forty-one page deck tell you what to build. Let someone who will build it tell you.

The scoping call is the single best proxy for what the rest of the engagement will feel like. Pay attention to it. See more of how we work at milicmedia.com/services/.

Mladen Milic runs Milic Media Kft, a boutique ServiceNow consultancy delivering implementation, health audits and HRSD work across the EU. Reach him at mladen@milicmedia.com.