By Donald D. Hook — Former VP & Partner, NTT Data ($40B Global IT Services Firm) | Former CTO & CIO | Full On Consulting | May 2026 | 14 min read
Most companies evaluate IT consulting firms the wrong way. They review the proposal. They check the partner's credentials. They assess the methodology. They negotiate the rate card.
What they almost never evaluate is the team that will actually show up to do the work.
I know this because I spent 16 years inside one of the world's largest IT services firms — NTT Data, a $40B global IT services organization — rising from consultant to Vice President to Partner. I built practices, won Fortune 100 engagements, and scaled teams from 20 to 120 consultants. I know exactly how staffing decisions get made on client engagements. I know the internal conversations that clients never hear. And I know that the gap between who sells an engagement and who delivers it is one of the most expensive blind spots in enterprise IT.
How the Staffing Model Actually Works
Large IT consulting firms operate on a pyramid model. At the top are Partners and Managing Directors — the rainmakers who sell work, manage client relationships, and set firm strategy. Below them are Managers and Senior Consultants. At the base are Consultants and Analysts — often recent graduates or early-career professionals with one to four years of experience.
The economics of the model require this structure. A Partner at a large consulting firm is expected to sell $5M to $15M in engagements per year. They cannot personally deliver all of it. They are not supposed to. Their job is to sell, appear at key moments, and manage the relationship — while the pyramid below them does the work.
The margin is made on the spread between what the junior delivers and what the senior is billed at. A first-year Analyst costs the firm $80,000 to $120,000 in fully loaded compensation. That same analyst is billed to clients at $150 to $350 per hour. The client was sold on the Partner's credentials. The client is paying for the Partner's rates. The client is receiving work product from someone who may have graduated two years ago. This is not an exception to the model. It is the model.
The Eight Steps of the Bait-and-Switch
Step 1
The Pitch
A senior Partner presents to your leadership team. Their credentials are genuine. Their experience is real. Their understanding of your business challenge is impressive. You feel confident that this person — specifically this person — will be leading your engagement.
Step 2
The Proposal
The Partner is listed as Engagement Lead. The team bios look strong. The proposed methodology is thorough. The rate card reflects the seniority of the team described. Everything looks as expected for a firm of this caliber.
Step 3
The Kickoff
The Partner is on the kickoff call. Engaged. Asking the right questions. Establishing credibility with your executives. Your confidence is reinforced.
Step 4
Week Two
The Partner has "other client commitments." A Manager will be handling the day-to-day. You are introduced — competent, professional, six or seven years of experience. You are mildly surprised but not alarmed.
Step 5
Month Two
The Manager introduces the broader team: two Analysts just out of school, one offshore resource managing documentation, and a Senior Consultant splitting time across two other engagements. The Manager mentions they are also supporting another account.
Step 6
The Status Report
Everything is green. The status report is polished. The slides look good. The risks listed are all in the "Low" category. Nobody mentions that testing is running two weeks behind schedule.
Step 7
The Problem
Something goes sideways. A dependency was missed. A technical issue has been unresolved for weeks. The timeline is slipping. Suddenly, the Partner reappears — to manage the relationship, explain the situation, and reset expectations. The problem is framed as a client-side issue or an unforeseen complexity.
Step 8
The Invoice
You are billed at the rates in the original proposal. The invoice does not break down hours by resource level or seniority. Analyst hours are billed at Senior Consultant rates. You approved the rate card at proposal stage. Contractually, there is very little to dispute.
I Saw It Firsthand — From Both Sides
I am not describing this model from the outside. I spent 16 years inside it. As a Vice President and Partner at NTT Data, I participated in the staffing decisions, the utilization reviews, and the rate card negotiations. I know how the internal conversations go. I know what drives resourcing decisions. And I know that clients almost never ask the questions that would expose what is actually happening.
The Big 4 Recovery Story
On a recent program recovery engagement, a Big 4 consulting firm had been engaged to lead the overall implementation. When our team arrived on site, we found a group of junior consultants — fresh hires, brand new to each other, and completely new to the client's environment and technology stack.
They were being billed at $350 an hour.
They were green.
Our team — brought in to support the recovery — found ourselves guiding and upskilling their consultants more than we were serving the client. We were essentially providing on-the-job training for a team the client was already paying $350 an hour for. The client had no idea. The status reports were green.
The eCommerce SOW Story: When a Vendor Tries to Bully the Client
On a separate engagement, a company's board brought me in as Interim CIO to conduct a full IT assessment. One of the first things I did was pull the Statement of Work for a stalled eCommerce project that had been dragging for months with nothing to show for it.
What I found in that SOW told me everything I needed to know. The scope was vague. Deliverables were defined in terms of activities rather than outcomes — "consulting sessions," "design workshops," "documentation reviews" — with no measurable acceptance criteria attached to any of them. The timeline had no dependencies mapped. The payment schedule was front-loaded in the vendor's favor. And the change order provisions were written so broadly that virtually any client request could be billed as out-of-scope.
But the bigger problem was not the SOW itself. It was how the firm was using it.
They had taken deliberate liberties — interpreting ambiguous language in their own favor at every turn, expanding their scope where it benefited them, and contracting it where it created accountability. When the client raised concerns, the firm pushed back hard. They were betting that the client would not know the contract well enough to challenge them — and that the discomfort of confrontation would keep the relationship compliant.
They were wrong.
I went through that SOW line by line. Every deliverable. Every milestone. Every payment term. Every change order clause. I documented where the firm had deviated from what was agreed, where they had billed for work outside scope, and where they had failed to deliver what the contract required. Then I held them to it.
What started as a project status conversation became a formal negotiation. The firm escalated internally when they realized the client now had someone in the room who understood exactly what the contract said and was not going to be moved. By the end, I was no longer negotiating with their project manager or their account executive. I was negotiating directly with the owners of the firm.
I presented my findings and recommendations directly to the client's CEO in person. The outcome: the vendor delivered the majority of the contracted work and we negotiated an off-ramp — they had lost so much money on the engagement that continuing made no business sense for either party. I then identified and onboarded a new vendor to complete and deploy the eCommerce platform.
The lesson: a weak SOW in the hands of an aggressive vendor is not just a contract problem. It is a leverage problem. And the only way to neutralize it is to know the document better than they do — and be willing to take the conversation all the way to the top.
"The most dangerous sentence in any IT consulting proposal is: ‘Our team of experienced consultants will...’ That sentence is always true of the partners. It is not always true of the people who will actually be in your conference room."
— Donald D. Hook, Former VP & Partner, NTT Data
What to Demand Before You Sign
Knowing the model exists is only useful if you know how to protect yourself. Here is what experienced buyers demand before signing an IT consulting contract:
Named resources with verifiable credentials
Require the proposal to name every consultant who will work on your engagement — not just the Partner. Ask for their individual backgrounds, certifications, and relevant experience. Any firm unwilling to do this before contract signature is hiding something.
Contractual resource continuity provisions
Include a clause requiring your written approval for any changes to named key resources. This does not prevent all turnover, but it forces the firm to notify you and get your agreement before substituting a senior resource with a junior one.
Seniority-level billing transparency
Require invoices to break down hours by individual or at minimum by seniority level. This makes the spread between billed rates and actual resource levels visible — and auditable.
Dedicated time commitments
Ask specifically: what percentage of each named resource's time is dedicated exclusively to your engagement? A manager supporting three other accounts simultaneously is not a dedicated resource — regardless of what the proposal implies.
Outcome-based deliverable definitions
Deliverables defined as activities — "consulting sessions," "design workshops," "documentation reviews" — give vendors no accountability for results. Require deliverables to be defined as measurable outcomes with defined acceptance criteria. If a vendor resists this, that tells you everything.
References from comparable engagements
Ask for three client references from engagements of comparable size and scope. Ask those references specifically: did the team delivered match the team sold? Clients who have lived the bait-and-switch will tell you — if you ask directly.
What the Right Model Looks Like
The alternative to the bait-and-switch is not complicated. It requires a firm that has no junior staff to deploy — by design, not by policy — that names specific people on every engagement before the contract is signed, and that is led by practitioners with documented delivery experience, not just sales experience.
Full On Consulting was built on exactly these principles — by someone who spent 16 years inside the model and built his own firm specifically to be the alternative. Every engagement is led by a former CIO, CTO, or senior delivery executive. The person who presents in the sales meeting is the person who runs the engagement. We will tell you yellow before you find out yourself. And we have the track record — $40M+ in documented client savings — to back it up.
Evaluating an IT Consulting Firm for Your Next Initiative?
We are happy to walk through how to structure the engagement, what to put in the contract, and what questions to ask — regardless of whether you engage us. We have been on both sides of the table. That conversation is free.
Our ServicesSchedule a CallFrequently Asked Questions
What is the IT consulting bait-and-switch?
The IT consulting bait-and-switch is a staffing practice used by large consulting firms where senior partners present and sell an engagement — establishing credibility and confidence with the client — but junior consultants with significantly less experience are deployed to actually do the work. The client is billed at rates reflecting the senior partner's credentials while receiving work product from analysts and consultants who may have only 1 to 4 years of experience. This is not an exception to how large firms operate. It is the business model.
How do large consulting firms decide who to staff on client projects?
Staffing decisions at large consulting firms are driven primarily by utilization targets and margin optimization — not by client fit. Partners are expected to sell $5M to $15M in engagements per year and cannot personally deliver all of it. Projects are staffed from an available bench of consultants, with junior resources deployed where the firm can maximize the spread between their cost to the firm and the rate billed to the client. The partner's job is to sell, appear at key client moments, and manage the relationship — while the pyramid below them does the work.
What should I include in an IT consulting contract to prevent junior staffing?
Include these provisions in every IT consulting contract: (1) Named resources — require the proposal to identify every consultant by name with individual credentials; (2) Resource continuity — require your written approval for any changes to key named resources; (3) Billing transparency — require invoices to break down hours by individual or seniority level; (4) Dedicated time commitments — specify what percentage of each named resource's time is dedicated exclusively to your engagement; (5) Acceptance criteria — define deliverables in terms of measurable outcomes, not activities like 'workshops' or 'consulting sessions.'
How much do large IT consulting firms charge for junior consultants?
Large IT consulting firms typically bill junior consultants (Analysts and early-career Consultants) at $150 to $350+ per hour — rates that reflect the senior credentials used to sell the engagement, not the experience level of the person doing the work. A first-year Analyst at a large firm may cost the firm $80,000 to $120,000 in fully loaded annual compensation while being billed to clients at $200 to $300 per hour. The spread between cost and billing rate is where large consulting firms make their margin.
What questions should I ask an IT consulting firm before signing?
Ask these questions in your final evaluation meeting: (1) Who specifically will be on site, and how many hours per week will each person be dedicated exclusively to our account? (2) What other client engagements will each named team member be supporting simultaneously? (3) What is the seniority and experience level of every person who will work on our project? (4) What happens contractually if a key team member leaves or is reassigned? (5) Can you provide three references from engagements of comparable size — and will those references confirm the team delivered matched the team sold? The answers will reveal more than any proposal document.
What is the difference between a boutique IT consulting firm and a large firm?
A boutique IT consulting firm typically has a flat structure with senior practitioners delivering directly to clients — there is no junior pyramid to manage utilization. This means the person you meet in the sales process is the person who runs your engagement, and billing rates reflect the actual seniority of the people doing the work. Large firms offer scale and brand recognition, but their economics require deploying junior resources to generate margin. For mid-market companies that need senior expertise and direct accountability, a boutique senior-only firm often delivers better outcomes at lower total cost than a large firm billing junior rates at senior prices.