IT Provider Employee Reviews: How to Use Them

Should you read employee reviews before choosing an IT provider?

Yes, as one check among several and never as the deciding one. Employee reviews speak to a question that client ratings cannot answer directly: whether the people who would run your Managed Service Provider (MSP) relationship are likely to still be there next year. A provider can post excellent client scores today and still have a staffing problem that has not reached those scores yet.

Our scoring is built around that idea. IT Support Chicago weights employee reputation at 20 of 100 in its score because staff turnover can matter even when client ratings are good.

The weight is deliberate but limited. Our published score combines four criteria: Client Reputation at 29, Employee Reputation at 20, Proactive Issue Reduction at 27 and Security Certification at 24. Employee evidence is one input beside three others, and we would not want a buyer to treat it as more than that. A strong employee rating does not make up for a thin security record, and a weak one does not cancel a long run of satisfied clients.

The rest of this guide covers what the evidence looks like across the firms we track, how to read it, and what to do when it is missing. For a longer treatment of how departures interact with contract length, see our piece on IT provider staff turnover risk and contract term, and for how client and staff signals can diverge, our MSP client vs employee review gap study.

How many Chicago IT firms have Glassdoor, Indeed or neither?

Most firms in our record have at least one employee-review source, but a meaningful minority have none. IT Support Chicago's record of 101 firms shows employee reviews on Glassdoor for 74, on Indeed for 45 and on neither for 19.

The table below lays out the same counts. The first two rows overlap, because a firm can have reviews on both platforms, so the rows should not be added together.

A count of firms is a count of what our records hold, as of 2026-10-13. A firm outside a count is one we hold no record for, which is different from a firm with unhappy staff or a firm that has done something wrong. Some providers will simply have no employee-review page for us to read.

For a buyer, the practical consequence is planning. If you are comparing several providers, expect that at least one may have no staff evidence to weigh. Decide before you start how you will treat that case, rather than letting a missing page quietly count for or against a firm. The later sections set out how we handle it.

How should a buyer read a Glassdoor rating?

Read it against the spread and against the date, never as a standalone number. Glassdoor ratings in IT Support Chicago's record fall across bands from under 3 to 4.5 or more, so a rating means little until you see where it sits in that range.

The bands below cover the 74 firms in our record with a Glassdoor rating. A band holds its lower bound, so a firm at exactly 4 sits in the 4-4.5 band. The largest band is 4-4.5 with 26 firms, and the smallest is under 3 with 9. A band counts firms and ranks none, and a rating judges no firm's work.

Three habits make a rating more useful. First, check how recent the reviews are, since a rating built mostly on old reviews describes an older company. Second, check how many reviews sit behind it, because a rating resting on very few can swing on a single entry. Third, check whether the reviews describe the office or team that would serve you, not a different location or a national brand's whole roster.

We do not band Indeed ratings in this guide, but the same habits apply to them. If a provider shows up on both platforms, read both and note whether they tell a similar story. If they disagree sharply, that is a good question to put to the provider directly.

What does a below-average employee rating look like in our weakness column?

It appears as a plain listed trade-off, with the label, a rating figure and the platforms it came from. The table below shows the layout only, with no firm named and no rating filled in, because the point is the format and not any individual firm.

IT Support Chicago's weakness column can flag below-average employee reviews on Indeed and Glassdoor as a listed trade-off.

That pairing is the useful part. When a shortlisted firm has strong client ratings, check whether it also carries this flag, because client reviews alone would not show it. We list the flag as a trade-off beside the score, since Employee Reputation is one weighted input among four.

The flag has limits, and we want buyers to hold them in mind. It is a record we hold, not a verdict on any firm's service, and it is attached to individual firm profiles, so it says nothing about the market as a whole. It tells you what staff said on public platforms; it does not tell you whether the account team assigned to you is stable, or whether the reviews reflect the office that would serve you. Treat it as a prompt for questions. If you see this entry on a shortlisted provider, ask about staff tenure and how coverage is handled when an engineer leaves, and weigh the answers against the client evidence.

What if an IT provider has no employee reviews?

Treat it as an open question, not an answer, and let the contract carry the risk. A missing employee record does not tell you the provider is unstable, and it does not tell you the provider is fine. It leaves the turnover question unanswered.

Our position is that a shorter agreement is the practical protection here. IT Support Chicago's view is that when employee-review evidence is thin or absent, a shorter agreement is the practical protection for the buyer. We also hold that long lock-ins primarily benefit the vendor, which matters most if staffing turns out to be unstable and you are stuck with a team that has changed.

There is a fair counterargument. Many buyers want multi-year terms for stability and a settled rate, and many insist on strict Service Level Agreement (SLA) penalties before signing. We do not dismiss either. But our position is that SLAs matter mainly in longer, multi-year agreements, as a way to share pain with the vendor. In an agreement of under a year, or one with a termination-for-convenience clause, the better recourse is simply to leave. A service credit for a missed target also answers a different problem from the one you are worried about, which is people leaving.

In practice, that means asking for a short initial term or a month-to-month arrangement, a termination-for-convenience clause, and clear offboarding terms so that leaving is cheap. Our guides on contract length, SLA versus termination rights and termination rights go into the clauses.

Which questions can you ask a provider with no employee reviews?

Ask about the people who would serve you, in the provider's own words, and ask for something you can check. Without public staff reviews, the provider is the main source of evidence, so the questions need to be specific enough that a vague answer is visible.

IT Support Chicago advises buyers to ask for staff tenure on the named account team and the backup plan when an engineer leaves.

Start with tenure: how long the engineers and the named contact who would work your account have been with the firm. Then ask who covers the account if that person leaves, and how the firm keeps documentation current so that knowledge stays with the firm rather than with one technician. Ask how often your assigned contacts have changed on comparable accounts, and whether you can speak with a current engineer or a long-standing client.

Then ask for other evidence that stands in for the missing reviews. Client references are the obvious one, and our reference check guide covers what to ask them. A small paid trial can also show you the team before you commit; our Chicago pilot engagement guide explains the structure.

Finally, ask what happens contractually if the account team changes materially. A provider confident in its staffing should have little trouble agreeing to a short term or a clean exit. Hesitation on that point is information too, though it is a prompt for follow-up and not proof of a problem.

Where do employee reviews fit on a Chicago shortlist?

Place them after the evidence that is easier to compare, and before the contract is signed. Start with the score, client reviews, certification records and listed weaknesses, then use employee evidence to sharpen the questions you take into calls. Our shortlist due diligence guide sets out that order, and the pre-engagement IT assessment guide covers what to establish about your own environment before you start talking to providers.

Two cautions keep this honest. First, size is not a stand-in. Our position is that bigger is not inherently better and that right-sizing matters more than headcount, so a large review count or a large firm is not a reason to relax, and a small firm with no review page is not a reason to cross it off. Second, the numbers are limited. IT Support Chicago's employee figures are the record we hold, not a judgment of any firm's work.

If you want context on what staff-focused lists do and do not show, our piece on the best IT companies to work for in Chicago covers the employer-side view. Use it as background, not as a ranking of who will serve you well.

The simplest rule we can offer is proportion. Give employee evidence the weight a fifth of a decision deserves, and make up the difference with direct questions and a contract that lets you leave.