Every ERP proposal I have reviewed — as the vendor, and more often now as the person a client calls in to referee someone else's — puts senior names on the cover page. Almost none of them say, in writing, who will actually be sitting in the room when requirements get gathered, who will be on the call during the data migration that runs long, or who shows up during the week go-live turns ugly. That gap between the names on the proposal and the names on the project is the least diligenced risk in an ERP purchase, and it is also the easiest one to close, if you know what to ask before you sign.

Why the gap doesn't show up in the sales process

The person who sells the engagement is rarely the person who delivers it, and that is true across the industry, not a knock on any one firm. Sales teams are measured on signed contracts. Delivery teams are measured, eventually, on margin. Those two incentives point in the same direction: staff the proposal with your most credible people, staff the project with whoever is available when the contract signs. By the time a client notices the switch, the relationship has moved from the partner level to a project manager relaying updates from a team they never met.

This is not a bad-faith move on most firms' part. It is just how capacity gets managed when your most senior people are also your best salespeople. The incentive problem is structural, which is exactly why it will not fix itself and has to be addressed before the contract is signed, not discovered after.

Four questions that actually tell you something

Most RFP processes ask about methodology, certifications, and reference clients — all reasonable, and none of it tells you who is actually doing the work. Four questions do:

  • Who, by name, will be on this project full-time from kickoff through 30 days post go-live, and what else are they staffed on during that window?
  • What proportion of the hours on this statement of work will be delivered by someone named in this proposal, versus someone not yet assigned?
  • If the lead named here rotates off, what happens contractually — notice period, replacement approval, any rate adjustment?
  • Can I speak with a client this exact team delivered, start to finish, without a mid-project substitution?

None of these are hostile questions, and a good firm will not treat them as one. A firm that staffs the way it sells answers all four directly. A firm that doesn't will reach for generalities — "our bench," "a dedicated pod," "the same quality regardless of who's assigned" — language that usually means the honest answer is no.

Put it in the contract, not just the pitch

A verbal assurance about staffing is worth exactly as much as the paper it isn't written on. The statement of work should name the lead, state the minimum percentage of their time committed to the engagement, and specify what happens if that person leaves — the firm's problem to solve, with your approval rights over the replacement, not a change order you discover after the fact. If a vendor resists naming anyone in the contract, that reluctance is itself an answer to the question you were asking.

What you are actually protecting against

None of this is about distrust of junior staff, who are often sharper than the senior people presenting the proposal. It is about continuity of judgment on the decisions that never show up in a project plan — which requirement is actually non-negotiable, which data exception is a one-off versus a pattern, which executive needs a direct conversation instead of a status email. Those calls get made correctly when the person making them has been with the project since scoping, not when they are handed a backlog on week six.

I have led more than 50 NetSuite implementations personally, start to finish, specifically because I believe continuity is the variable that actually predicts outcomes. It is a meaningful part of why the engagements I run land with retention and ROI numbers that are easy to state because they are consistent, not aspirational. The firms worth hiring are the ones willing to put that same commitment in writing before you ever have to ask.