Incumbent IT Provider Review: A Chicago Renewal Guide

What does an incumbent IT provider review actually check?

It checks external evidence about the Managed Service Provider (MSP) you already pay, and nothing else. Three items carry most of the weight at renewal: how the firm's public client standing sits against the spread we record across the firms we track, whether our records hold a weakness entry worth an explanation, and what documentation sits behind each certification the firm lists. All three are readable before you walk into the renewal meeting, and all three are readable without the incumbent's cooperation.

What the check does not reach matters just as much. It says nothing about how your own tickets were handled last quarter, whether the engineer who knows your environment is still on the account, or whether the roadmap you were sold in year one was ever executed. Those answers live in your ticket history, your own staff, and your account reviews, and no external dataset substitutes for them.

IT Support Chicago tracks 100 active vendors, with an average vendor score of 19.0% across a range of 0.8%-80.6%. That range is worth sitting with before you benchmark anyone: scores in our system are attainment against published criteria, not a grade for the service a particular buyer received. Use the external read to build an agenda, then spend the meeting on the parts of the relationship only you can see.

Why a short agreement is what makes the review worth running

Our position at IT Support Chicago is that shorter agreements keep renewal a genuine decision point rather than a formality. If the term you are re-signing runs for years, or renews automatically unless you object inside a narrow window, the evidence you gather has nowhere to go: you can raise it, but the incumbent knows the alternative to agreeing with you is nothing at all. Long lock-ins, in our view, primarily benefit the vendor, and we do not treat a multi-year default as neutral.

The common counter-argument is that a longer term buys stability and a better rate. We would rather buyers price that trade honestly: the thing being exchanged for the rate is the ability to act on what a review finds. If the incumbent wants the longer term, that is the moment to ask what the buyer gets in exchange beyond a number on a quote — and to read the termination and auto-renewal language before the discount.

We hold a related position on Service Level Agreements (SLAs). Our view is that SLAs matter in multi-year agreements as a mechanism to share pain with the vendor. For agreements under a year, or where you hold termination for convenience, we regard simply ending the agreement as the better recourse, and SLA credits as a smaller lever than they look. We would not tell any buyer that strict SLA guarantees are essential in every engagement; we would tell them to check which recourse they actually hold. Our guides on contract length work through the trade in more detail.

How does your incumbent's public client standing compare with the firms we track?

Compare it against a distribution, not against a single impression. In IT Support Chicago's published score, Client Reputation carries weight 29 of 100, with attainment at median 25.5 and mean 38.8. The middle half of the firms we scored on it falls between 14.3 and 67.4, and every one of the tracked firms received a score on this criterion. That spread is the context a buyer needs before deciding whether an incumbent's public standing is holding up or merely unremarkable.

Two things follow. First, a wide gap between median and mean tells you the distribution is lopsided, so a mid-pack result is not a scandal and a strong one is not proof of anything about your account. Second, this is a corpus pattern: it describes the firms we track collectively and cannot be converted into a statement about any individual provider, including yours.

Raw star averages carry less information at renewal than buyers expect. Across the vendor set the average client rating is 4.75 / 5.0, drawn from 8,144 reviews in total. The criterion itself is scored with a Bayesian model across multiple review platforms, adjusted for volume, recency, and platform credibility. One weakness type we log against tracked firms is client reviews appearing on a single platform only — not a finding about service, but a reasonable thing to raise in a renewal conversation and to test by looking for the incumbent's reviews somewhere other than the platform it points you to.

Reading a staffing-mix flag when an agreement comes up for renewal

Apollo workforce data is where we recorded a weakness entry reading heavily reactive support model at 86% reactive roles. That is the kind of staffing-mix flag we log against a tracked firm, and it is a good example of evidence that is worth a question rather than a conclusion. Job titles classified from workforce data are a proxy: they capture how a firm staffs, not how well any individual engineer works your queue.

The criterion behind the flag is Proactive Issue Reduction, which carries weight 27 of 100 in our published score and is calculated as attainment = (1 − reactive_share) × 100 from proactive titles such as architects, security engineers and consultants versus reactive titles such as help desk, Network Operations Center and support staff. Across the firms we scored on it, attainment sits at median 12.0 and mean 15.8, with the middle half between 0.0 and 25.0. We scored it for 54 of 100 firms; for the rest, our records are silent, and silence is not evidence of a poor mix.

At renewal, the useful move is to ask the incumbent how its proactive-to-reactive mix has changed over the term you just completed — what roles were added, what recurring ticket categories were engineered out, and what the plan is for the next term. Treat one recorded flag as an opening question. Our proactive staffing ratio guide sets out how we classify the titles and where the method runs out of road.

What does re-checking certifications at renewal actually re-check?

It re-checks our records, and only our records. Our legend defines a (claimed) mark as an entry IT Support Chicago holds no third-party documentation for. A check mark means the opposite: we hold a named third-party issuer's document, evidence hosted off the firm's own domain, or a public registry entry. Both marks describe our own records, never how secure a firm is, and a (claimed) entry must never be read, or written up, as certified, audited or accredited.

That distinction matters more at renewal than at first purchase, because a certification named in a proposal three years ago may have lapsed, changed scope, or simply never been documented anywhere we could reach. When we publish a status we use one of two phrasings — third-party documented, or the firm's own claim — and we would encourage buyers to hold the same discipline in their own notes.

The practical ask is short: request the current attestation or certificate directly from the incumbent, check the issuer and the observation period, and confirm the scope covers the services you buy. A System and Organization Controls (SOC) 2 Type II report covers control operation over a multi-month window, while SOC 2 Type I covers control design at a point in time. In our records, Payment Card Industry Data Security Standard (PCI DSS) entries are the most common certification listing, appearing for 20 vendors. Security Certification carries weight 24 of 100 in our score, with attainment at median 10.0 across the firms scored on it. Our certification verification checklist covers what to ask for document by document.

The four published criteria, and where the tracked firms sit

Our published score combines four criteria scored from public evidence, each with its own weight and its own coverage. Reading them side by side keeps a renewal review honest, because a single headline number hides which parts of a firm's profile our records actually reached. Six further criteria apply only inside a signed-in custom evaluation and carry no weight in the published score.

Coverage is the column buyers skip and should not. In IT Support Chicago's score, Proactive Issue Reduction carries weight 27 of 100 and is scored for 54 of 100 firms. Where a criterion is unscored for a firm, our records are silent about it — that is a gap in what we could gather, never a finding against the provider.

Questions to put to the incumbent before you sign again

Bring the external evidence, then spend the meeting on scope and terms. Our view at IT Support Chicago is that a per-user price without scope context is misleading, so the first question is not what the rate is but what the rate now covers compared with the term that is ending. Ask what moved into the base bundle, what moved out to project billing, and which exclusions were added quietly at the last uplift.

Second, ask about the people. Employee Reputation carries weight 20 of 100 in our score because turnover is a risk even when clients are satisfied today, and a renewal is the right moment to ask who is assigned to your account and how long they have held it. Third, ask about headcount honestly: we do not accept that a larger firm delivers better service by default, and right-sizing — depth in the systems you actually run — is the question worth asking instead.

Fourth, ask what changes in your recourse. Confirm the notice period, whether the agreement renews automatically, whether termination for convenience survives, and what happens to your documentation, licences and administrative credentials if you leave. A performance review of your provider that ends without a clear answer on exit terms has not finished. If you serve a regulated vertical, check that the scope still matches your obligations; our Chicago law firm guide shows how we read vertical claims against our data.

What this review cannot tell you

Our score is built from public evidence, and IT Support Chicago never observes ticket handling inside a buyer's own environment. That single limitation frames everything above. Response quality, escalation behaviour, whether the virtual Chief Information Officer (vCIO) sessions produced anything actionable, and how the provider handled the one bad week that mattered — none of it appears in a public dataset, and no vendor ranking will supply it.

The second limitation is asymmetry. An incumbent with no weakness entries in our records is unflagged, not validated: we may simply hold no data on the dimensions where a problem would surface. Where a criterion is unscored, treat the absence as a gap in our intake and go looking for the evidence yourself. Delivery models and industries in our records are what firms publish on their own websites, as read by our crawler — claims we recorded, never capabilities we assessed.

The third is temporal. Everything we publish is a snapshot as of a collection date, and a renewal decision is about the term ahead. Workforce mixes change, review platforms accumulate, and certification documentation is obtained or lapses. Use our records to shape the agenda, use your own ticket data and internal stakeholders to judge delivery, and keep the term short enough that the next renewal is still a decision you get to make.