By Donald D. Hook — Former CTO & CIO, Full On Consulting | April 2026 | 10 min read
Selecting an IT consulting firm is one of the highest-stakes procurement decisions a technology organization makes. The wrong choice doesn't just cost money — it costs time, morale, and sometimes the initiative itself.
The firms that are best at winning work are not always the ones best at doing it. These 20 questions are designed to reveal the difference — before you sign.
Team & Resources
Q: Who specifically will be the lead consultant and project manager on our engagement?
Why this matters: Reveals whether the team you meet during the pitch is the team that will actually do the work.
Q: What is the background and experience of those named individuals?
Why this matters: Certifications and years of experience are less important than specific, relevant delivery track record.
Q: What happens if a key team member leaves or is reassigned mid-project?
Why this matters: Resource churn is the single largest cause of IT project delays. How firms answer this reveals their commitment level.
Q: What percentage of the team will be on-site vs. remote?
Why this matters: For complex implementations, on-site presence during critical phases significantly reduces risk.
Track Record & References
Q: Can you provide 3 references from clients with similar scope and industry?
Why this matters: References in your industry at comparable complexity are the strongest validation of capability.
Q: Can you share a case study where a project went off-track and how you recovered it?
Why this matters: Every experienced firm has recovery stories. If they only have success stories, they are either inexperienced or not being honest.
Q: What are the measurable outcomes from your 3 most recent engagements like ours?
Why this matters: Separates firms focused on outcomes from those focused on activity.
Methodology & Delivery
Q: Walk me through your delivery methodology for this type of engagement.
Why this matters: Listen for specificity — how they manage scope, escalate risk, and report status. Vague answers indicate a brand, not a process.
Q: How do you handle scope changes?
Why this matters: Firms without a defined change order process will either let scope expand silently or bill you without warning.
Q: What are your status reporting cadence and format?
Why this matters: Weekly reports and escalation processes should be defined before the contract is signed, not improvised during delivery.
Q: How do you approach change management and user adoption?
Why this matters: Technology without adoption delivers no value. Firms that treat change management as optional create technically successful but organizationally failed implementations.
Pricing & Risk
Q: What is included and explicitly excluded from the scope of this proposal?
Why this matters: Exclusions are where cost overruns hide. Make the firm enumerate what is not included.
Q: What assumptions underlie your timeline and budget estimate?
Why this matters: Unrealistic assumptions are how low bids become expensive projects. Get them in writing.
Q: Do you offer fixed-price or milestone-based pricing options?
Why this matters: Milestone-based payments align firm incentives with delivery. Time-and-materials without milestones shifts all risk to you.
Q: What are the billing and invoicing terms?
Why this matters: Front-loaded payment schedules favor the firm. Milestone-tied payments protect you.
Transition & Exit
Q: What is your knowledge transfer and transition plan at engagement end?
Why this matters: A firm with no transition plan is maximizing dependency. You should leave more capable than when they arrived.
Q: Who owns the IP and documentation created during the engagement?
Why this matters: Custom code, process documentation, and architecture designs should belong to you.
Q: How will you measure success at engagement end?
Why this matters: If a firm cannot articulate specific, measurable success criteria, they will declare victory on their own terms.
Q: What ongoing support do you offer after the engagement closes?
Why this matters: Post-implementation issues are inevitable. Understand what support is available and at what cost.
Looking for an IT Consulting Firm That Can Answer All 20?
Full On Consulting was founded on the belief that clients deserve consultants who are accountable for outcomes — not just hours. We welcome every one of these questions and will answer each one specifically.
Schedule a ConversationView Our ServicesFrequently Asked Questions
What are the most important questions to ask an IT consulting firm?
The most critical questions are: Who specifically will work on my engagement (not just who leads the pitch)? Can you provide 3 references from comparable clients? What happens if a key team member leaves mid-project? How do you manage scope changes? What does success look like and how will you measure it? These questions reveal whether a firm is a true consulting partner or an expensive staffing agency.
How do I know if an IT consulting firm is really experienced?
Ask for case studies with specific, measurable outcomes — not general descriptions. Ask references specific questions: Did the firm deliver on time and on budget? How did they handle problems when they arose? Would you hire them again? Look for consultants who can explain how they handled a project that went sideways — experienced firms have recovery stories. Inexperienced ones only have success stories.
What should I look for in an IT consulting contract?
Key contract provisions to review: named resource commitments with approval rights for changes; a clear change order process that prevents scope creep; milestone-based payment tied to deliverables rather than time; IP ownership clauses for any custom work; a defined transition and knowledge transfer plan at engagement end; and liability provisions that are reasonable relative to the engagement value.
How do I evaluate an IT consulting firm's methodology?
Ask the firm to walk you through their delivery methodology for your specific type of engagement. Listen for specificity: how do they manage scope? How do they escalate risk? How do they report status? Vague answers like 'we use agile' or 'we follow best practices' indicate a firm that is describing a brand rather than a process. Strong consultants can describe specific artifacts, cadence, and governance mechanisms.