Insight · Teaming

What a prime should ask a ServiceNow subcontractor

Nine questions that actually separate sub-vendors, written from the position of a firm that would rather be asked them.

A prime shortlisting a ServiceNow subcontractor is making a bet with their own client relationship as collateral. If the subcontractor underdelivers, the prime absorbs it — in remediation cost, in schedule, and in the harder-to-price currency of how the client talks about them afterwards.

Most subcontractor qualification calls do not test for this. They test for availability, rate and a CV. Those are necessary and they are not sufficient, because every firm on the list will pass all three. What follows are the questions that separate them, written from the position of somebody who would rather be asked them.

Questions about the work

"Walk me through something on this platform you got wrong."

The single most useful question available, and the hardest to prepare for. A practitioner who has genuinely delivered has a specific answer with a mechanism in it — an identification rule that merged CIs it should not have, a scoped application decision that cost three upgrades. Somebody who has mostly been near delivery gives a process answer about communication or stakeholder alignment.

You are not testing for humility. You are testing whether the failure is described at the level of the platform or the level of the project.

"What would you refuse to do on this scope?"

Every scope has a wrong request buried in it — the customisation that will not survive an upgrade, the integration pattern that will not scale, the timeline that assumes the CMDB is better than it is. A subcontractor who cannot name one either has not read the scope or intends to build whatever is asked and invoice for it.

"What has to be true before this scope is deliverable?"

Dependencies the client controls: environment access, a data owner who can make decisions, a test instance that reflects production. A subcontractor who has delivered knows these are where schedules die and will name them unprompted. One who names none will discover them on your programme, at your cost.

Questions about representation

"Are you currently representing anyone else on this opportunity?"

Duplicate submission is the most common way a sub-vendor damages a prime, and it is usually not malicious — it is a firm working several channels without tracking them. Ask directly, ask for it in writing, and make right-to-represent exclusive per opportunity in the MSA.

"Is the person on this CV the person who will do the work?"

Ask it plainly and get the answer in the contract. Substitution after award is the second most common failure mode, and the version that hurts most is the one where the substitution is technically compliant — same title, same years, different capability entirely.

"What is your bench, honestly?"

A small firm's honest answer is that there is no bench, and that is fine — it is what you are buying. What matters is whether they say so. A two-person firm claiming surge capacity is telling you something about how they will describe schedule risk later.

Questions about what happens when it goes wrong

"Who do I call at 6pm on a Friday, and what do they have authority to do?"

In a small firm the answer should be a name and "everything". If the answer routes through an account manager who then has to reach a delivery manager, you have bought a layer, not a capability.

"How will you tell me the date is going to slip?"

The question is about mechanism and timing, not intention. Everybody intends to raise risks early. The useful answer describes what triggers the conversation — a specific slip threshold, a weekly checkpoint with a named artefact — rather than a promise of transparency.

"What does your handover look like?"

You will eventually be asked by the client to continue without the subcontractor, or to replace them. What exists at that point — documented decisions, a maintainable configuration, update sets with legible naming — determines whether that is an inconvenience or a second project.

The question to ask yourself

Before any of the above: what are you actually buying? Capacity at a rate, or judgment on a scope? They are different purchases with different failure modes, and the qualification that suits one is close to useless for the other.

If it is capacity, optimise for reliability and administrative friction — onboarding speed, invoicing, substitution terms. If it is judgment, the CV matters far less than how the person reasons about the platform in a twenty-minute conversation, and you should spend the twenty minutes.

Most disappointing subcontractor engagements begin with a prime buying judgment through a process designed to buy capacity.