Choosing an IT Consulting Partner: 12 Criteria That Matter

Business people negotiating at boardroom behind closed doors

Choosing an IT consulting partner comes down to evidence: comparable client outcomes you can verify, a named delivery team you have actually met, independent advisory judgment, a pricing model matched to the shape of the work, and governance you can audit. These 12 criteria give enterprise buyers a structured way to evaluate, score, and shortlist candidates before a contract is signed.

Most enterprise technology leaders start the selection process in the wrong place. They collect proposals, compare slide decks, and pick the firm with the lowest rate or the most recognizable name. Six months later they are managing a program that is off-track, over budget, and staffed with consultants they never met during the sales process.

The research on large program outcomes is consistent. A McKinsey study conducted with the University of Oxford, covering more than 5,400 IT projects with initial budgets above $15 million, found that large IT projects run 45 percent over budget and 7 percent over schedule on average, while delivering 56 percent less value than predicted. Roughly 17 percent go badly enough to threaten the existence of the company. The Standish Group’s CHAOS Report has told a directionally similar story for three decades, though its definitions of success have been fairly criticized for measuring estimate accuracy rather than delivered value.

Those outcomes do not begin at kickoff. They begin in the selection process, where the wrong questions get asked and the wrong evidence gets accepted.

PARTNER EVALUATIONThe 12 criteria at a glanceOne question to ask and one red flag to watch for at every step of an IT consulting partner evaluation.#CRITERIONASK THISRED FLAG1Comparableclient experienceHow many engagements of our sizeand industry have you delivered in thelast three years?References are writtentestimonials rather than peopleyou can call2VerifiableoutcomesWhat was the baseline, the result, themeasurement method, and thetimeline?Case studies describe deliverableswith no quantified business impact3Industry anddomain depthWho on your team has operated insideour regulatory or operationalenvironment?Domain knowledge lives entirely inthe sales team4IncentivedisclosureWhat partner tiers, referral fees, orrevenue-share agreements do youhold, and how are they disclosed?Evasiveness, or a single-vendorpractice presented as neutraladvice5Fit-first advisorydisciplineDescribe an engagement where yourecommended against a platform theclient wantedNo example exists, or the answerpivots to methodology6Delivery modelstructureWho leads delivery, where do they sit,and will you name the team before wesign?Refusal to name the team, orsenior staff who disappear aftersignature7TechnicalcompetencyWhich references map to projects thatactually exercised these certifications?Certification counts presented asdelivery evidence8Performanceunder pressureTell us about an engagement thatwent off-track and what you didHesitation, or a redirect to asuccess story9Pricing modelalignmentWhich commercial model fits thisengagement, and why that one?The same model is proposedregardless of scope maturity10Security andgovernanceCan we see your SOC 2 Type II report,subprocessor list, and incidentresponse plan?Policy documents offered in placeof operational evidence11SLAs andaccountabilityHow are disputes over deliverablequality or milestone completionresolved?Vague answers, or measurementdeferred to the end of theengagement12RelationshipmodelWhat do your longest-tenured clientssay about year three compared toyear one?Clients described as categoriesand verticals rather than by nameAIM CONSULTING

Why do most enterprise partner evaluations ask the wrong questions?

Most enterprise RFPs are built around inputs: team size, certifications, hourly rates, years in business. None of those tell you whether a firm can deliver a measurable business outcome on your program. What predicts outcomes is delivery evidence from comparable engagements, references you can call, and a clear answer to what happens when things go sideways.

There is also a framing problem underneath it. You are not buying a service. You are choosing who holds accountability for a business outcome. That distinction changes how you read a proposal. A firm that leads with methodology slides and partner logos is showing you what it wants you to see. A firm that leads with baseline-to-outcome case studies, named references, and a specific staffing plan is showing you how it works.

How do you evaluate track record and enterprise-scale experience?

Criteria 1 through 3 establish whether a firm has done work that resembles yours, and whether it can prove it.

Ask for case studies from engagements with companies of similar size, industry, and technical complexity. A firm that exclusively serves Fortune 100 clients operates at a scale and pace that may not fit a mid-market enterprise, and the inverse is equally true. Require client references you can contact directly rather than curated written testimonials. Live reference calls surface staffing, communication, and delivery issues that written materials rarely mention.

Ask this: How many engagements have you completed for organizations of our size and industry in the last three years? Can you provide two or three references we can contact directly, and what were the measurable outcomes of each?

Red flag: The firm offers testimonials but resists live reference calls, or the references it offers are from engagements more than three years old.

Require before-and-after metrics: cost reduction, deployment frequency, downtime, cycle time. A credible firm can show you the baseline, the result, the measurement method, and the timeline over which it was achieved. Watch for case studies that describe deliverables (“we built a data pipeline”) without any quantified business impact. That is a project summary, not a case study.

Ask this: For your three most comparable engagements, what was the starting baseline, what changed, how was it measured, and who at the client validated the number?

Red flag: Outcomes are described in adjectives rather than numbers, or the measurement method cannot be explained.

Generalist IT consulting handles architecture and program management well. Domain depth matters when you operate in a regulated industry, a complex supply chain, or a data-intensive environment where the constraints are not primarily technical. Ask how many comparable engagements the firm has led in your specific industry in the last three years, not how long it has been in business.

Ask this: Which named people on the proposed team have worked inside our industry’s regulatory or operational constraints, and on what engagements?

Red flag: Industry knowledge is concentrated in the sales team and absent from the delivery roster.

How do you tell whether a firm’s recommendations are independent?

Criteria 4 and 5 address the question buyers ask least often and regret most: whose interest does the recommendation serve?

Almost every credible consulting firm holds technology partnerships, and those partnerships often bring real benefits: earlier access to product roadmaps, certified engineers, escalation paths into vendor support. Partnerships are not the problem. Undisclosed incentives are.

Ask directly what partner tiers, referral fees, or revenue-share arrangements the firm holds, and ask how those are disclosed during a platform recommendation. A firm with genuine advisory discipline will answer plainly, name the arrangements, and explain how it separates the advisory decision from the implementation revenue. A firm with a single-vendor practice presenting itself as neutral is a different proposition, and worth knowing about before the architecture is decided.

Ask this: What partner tiers or revenue-share agreements do you hold, how do you disclose them when recommending a platform, and who inside your firm can override a recommendation that favors a partner?

Red flag: The question produces evasiveness, or the firm’s entire portfolio sits inside one vendor ecosystem while it markets itself as platform-agnostic.

The right firm starts with your business problem, maps it to a solution set, and selects tools last. Ask it to describe a past engagement where it recommended against a platform the client wanted to use, and why. That single question separates firms with advisory discipline from firms that will confirm whatever you already believe. If no example exists, you have your answer.

Ask this: Tell us about a time you told a client not to buy something, or recommended a smaller scope than they asked for. What happened to the relationship afterward?

Red flag: No such example, or the example ends with the client agreeing immediately and buying more.

How do you verify delivery capability rather than strategy?

Criteria 6 through 8 are where proposals and reality most often diverge.

Nearly every enterprise consultancy now delivers through a distributed model that combines onshore, nearshore, and offshore teams. The structure itself is not a warning sign. What matters is where accountability sits, whether working hours overlap enough for real collaboration, and whether the people named in the proposal are the people who show up.

Ask for the delivery organization chart: who leads the engagement, where that person sits, who they escalate to, and how quality oversight works across locations. Request names and résumés of the actual team, not just the partners presenting in the sales meeting. Then put a substitution clause in the contract requiring your approval for changes to named senior roles.

Ask this: Show us the delivery org chart with names, locations, and time zone overlap. Who is accountable for quality, and what happens to that accountability if the engagement expands?

Red flag: The firm will not name the team before signature, cannot explain how oversight works across locations, or resists a substitution clause.

Relevant certifications include AWS and Azure Solutions Architect credentials for cloud work, CISSP or CISM for security programs, and PMP for delivery-heavy engagements. Certifications validate baseline knowledge. They do not validate implementation experience. Require references tied specifically to projects that exercised the certifications the firm is highlighting in its proposal.

Ask this: For each certification you have listed, which client engagement demonstrated it, and can we speak to that client?

Red flag: Certification counts presented as a proxy for delivery capability, with no engagement mapped to them.

Ask for an example of an engagement that went off-track and how the firm handled it. This question is more revealing than any success story. Look for documented escalation paths, delivery oversight independent of the engagement team, and a track record of managing scope change without the program imploding. A firm with real delivery experience answers without hesitation. A strategy-only shop pivots back to methodology.

Ask this: Describe an engagement that went off-track. What was the trigger, who raised it, how long did it take to stabilize, and what did the client say afterward?

Red flag: No example is offered, or the story has no cost to the firm in it.

What should the contract, pricing, and governance look like?

Criteria 9 through 11 determine what recourse you have when the relationship is tested.

Time and materials works when scope is still evolving. Fixed price works when requirements are locked and deliverables are well defined. Outcome-based pricing aligns incentives when business results can be measured cleanly, which is rarer than it sounds. Large transformation programs frequently combine models: a fixed-fee discovery phase that de-risks the early commitment, followed by time and materials with milestone-based billing.

A credible firm recommends the model that fits the engagement rather than the one that protects its revenue. Require a clear statement of work, acceptance criteria, a change-control process, and milestone-based payment terms where applicable.

Ask this: Which pricing model do you recommend for this engagement, and what would have to be true for you to recommend a different one?

Red flag: The same commercial model is proposed regardless of how mature the scope is.

Request a current SOC 2 Type II report and ISO 27001 certification, one or both depending on your engagement’s data and regulatory requirements, for any firm accessing your systems or data. For regulated industries, verify HIPAA safeguards or GDPR-aligned data handling as applicable. Ask for a subprocessor list, a recent penetration test summary, and an incident response plan.

Policies alone do not prove compliance. Ask for operational evidence: access review records, audit trails, signed approvals, and remediation trackers. If the firm uses offshore or nearshore delivery, confirm how data residency and access controls work across each location.

Ask this: Can we review your most recent SOC 2 Type II report, your subprocessor list, and evidence of your last access review?

Red flag: Policy documents are offered in place of audit artifacts, or data handling across delivery locations cannot be explained precisely.

Ongoing engagements, managed services, and retainers should include defined SLAs: response times, escalation paths, and performance thresholds. Establish how the engagement will be measured and reported throughout, not only at the end. Ask specifically how disputes about deliverable quality or milestone completion get resolved, and what happens commercially if a milestone is missed.

Ask this: How are quality and milestone disputes resolved, who arbitrates, and what is the commercial consequence of a missed milestone?

Red flag: Vague answers, or reluctance to define consequences. A firm that resists this conversation is a firm that does not want to be measured.

How do you assess long-term partnership fit?

A firm that treats every engagement as a one-time project will not invest in understanding your business deeply enough to be useful past the first scope. Ask about its longest active client relationships, and what those clients say about year two and year three value compared to year one. That is the real indicator of whether a firm is building something with you or executing a scope and moving on.

You can usually tell the difference by how a firm talks about clients during the sales process. Familiarity and specificity point one way. Categories and verticals point the other. Pay attention to whether the firm is asking more questions than it is answering.

Consider running a short paid discovery engagement before committing to a full program. It gives both sides a low-stakes way to test communication, responsiveness, and how the firm handles uncertainty, and it produces an artifact you own regardless of what you decide next.

Ask this: Which client has been with you longest, what does the work look like now compared to year one, and can we speak with them?

Red flag: The firm’s longest relationships are all recent, or the relationship narrative is about renewals rather than expanded value.

How do you score candidates against these criteria?

The criteria are only useful if they produce a comparable result across firms. This is the weighting AIM recommends as a starting point. Adjust it to the shape of your program.

Score each criterion 0 to 3, where 0 means no evidence provided, 1 means asserted but unproven, 2 means demonstrated with evidence, and 3 means demonstrated with evidence a third party confirmed.

SCORING FRAMEWORKRecommended weightingScore each criterion 0 to 3, where 0 is no evidence provided and 3 is evidence a third party confirmed. Any zero is adisqualifier.GROUPCRITERIAWEIGHTWHY THIS WEIGHTEvidence and track record1, 2, 325%Past comparable outcomes are the strongestavailable predictorAdvisory independence4, 515%Determines whether the architecture decisionserves youDelivery capability6, 7, 830%Where proposals and reality diverge most oftenCommercial and governance9, 10, 1120%Determines your recourse when the relationship istestedPartnership fit1210%Compounds over multi-year programsAIM CONSULTING

Three rules make the scorecard work:

  • Any zero is a disqualifier. A firm that cannot produce evidence on a single criterion should not be rescued by a strong total. Zeros mean the evidence does not exist, not that it scored low.
  • Score the evidence, not the answer. Confident answers are easy. Score what the firm actually showed you.
  • Weight delivery above strategy. Strategy is verifiable in a room. Delivery is not, which is why it needs the most scrutiny before signature.

As a working guide: above 70 percent belongs on the shortlist, 55 to 70 percent warrants a second round with specific evidence requests, and below 55 percent should not proceed to contract conversations.

Use this checklist before the conversation, not after

The right IT consulting partner does not win because it had the best proposal or the biggest name. It wins because it can show you the evidence: comparable client outcomes, a team you have met, transparent incentives, a pricing model that fits the engagement type, clean governance documentation, and a track record of long relationships rather than repeated first engagements.

Run every candidate through these 12 criteria before contract conversations begin. Ask for specifics rather than summaries. Request references and actually call them. If a firm cannot answer these questions with confidence, that answer tells you what you need to know.

Ready to choose an IT partner based on evidence, not just promises?

We invite you to hold us to the same high standards outlined in this framework.

Start a conversation with AIM Consulting today to discuss your next major transformation program.

Frequently asked questions

What is the difference between an IT consulting firm and an IT staffing firm?

A staffing firm supplies individual resources against roles you define and manage. A consulting firm takes accountability for an outcome, brings its own delivery leadership and methods, and is measured on results rather than hours filled. The distinction matters most when a program goes off-track, because only one of the two models carries responsibility for fixing it.

How long should an IT consulting partner selection process take?

For a major transformation program, six to twelve weeks is typical: two to three weeks to define requirements and build the candidate list, three to four weeks for proposals and evaluation, and two to four weeks for reference calls, security review, and contracting. Compressing reference and security due diligence is the most common and most costly shortcut.

Should you run a formal RFP?

An RFP is useful when requirements are well defined and you need comparable responses across many candidates. When the problem is still being framed, a short paid discovery engagement with two or three firms usually produces better information than an RFP, because it shows you how each firm thinks rather than how well it writes.

Is it better to hire a large global firm or a mid-size consultancy?

Large firms bring scale, geographic reach, and deep bench strength, usually at higher rates and with less senior attention per engagement. Mid-size firms typically offer more senior involvement and more flexibility, with a smaller bench. The right answer depends on program size and how much partner-level attention your program actually requires.

What is a paid discovery engagement?

A short, fixed-fee engagement, typically two to six weeks, in which a firm assesses your current state and produces a recommendation, roadmap, or architecture you own outright. It lets both sides test working style before a large commitment, and it produces something useful even if you select a different partner.