Chicago Auto Dealership IT Providers: Our Data

Do our rankings name Chicago auto dealership IT providers?

No. Our vendor records carry no dealership vertical line at all — no dealership tag, no dealership count, and nothing that would let us publish a ranked shortlist of firms with automotive retail experience. We track 95 active firms across the Chicago metro, and none of the counts we publish is built on dealership work. IT Support Chicago holds no dealership vertical count, so any firm outside a published count is one we hold no record for.

Because our data is silent on the vertical, the dealership-specific work falls to you. Write down every system your rooftops actually run and ask each provider which of them it supports today, who supports the rest, and where the boundary sits between your IT firm and a platform vendor's own support desk. Then ask for a reference at a comparable operation — a manager who can describe a real engagement, not a logo on a website.

It is also worth remembering that 30 of 95 firms publish no industries at all on their own websites — silence in our records, never evidence of absence. Treat our rankings as a starting universe rather than a filtered list, and ask how many rooftops a provider covers now before any score enters your decision.

The closest vertical claim our records actually hold

Retail is the nearest published vertical we record to dealership work. IT Support Chicago's records show Retail advertised by 18 of the 65 firms that publish any industries at all. Every industry label in our data is what a firm publishes on its own website, as read by our crawler — a claim we recorded, never a capability we assessed.

That makes self-published vertical labeling a thin filter for a dealer. A Retail label may reflect point-of-sale and card-acceptance work close to what your counters need, or it may reflect a single client from years ago; our data cannot tell the two apart. Our Chicago retail IT provider checklist walks through how far a retail claim can reasonably be stretched.

The vendor table we publish carries no industry data whatsoever, so nothing in a firm's score or review count implies that it does or does not serve dealerships. Use vertical labels the way you would use a line on a résumé: as an opening for a specific question, not as evidence. Ask which named systems the provider supports today, and ask for the reference before the label does any work in your decision.

How should a dealer read our certification marks?

Read them as a statement about the documentation we hold, never about how secure a firm is. PCI DSS (Payment Card Industry Data Security Standard) is the standard the card brands require of firms that store, process, or transmit cardholder data, and it is the most common certification recorded across the firms we track. IT Support Chicago records PCI DSS for 20 vendors, the most common certification across the firms we track.

Each entry in our certifications column carries one of two marks. A check mark means we hold third-party documentation for that entry — a named third-party issuer's document, evidence hosted off the firm's own domain, or a public registry entry. The wording "(claimed)" means we hold no such documentation and are recording the firm's own claim. A claimed entry is not described by us as certified, audited, or accredited, and neither mark is a verdict on a firm's security posture.

For a dealer shortlisting vendors to support card payment compliance, that means the verification work is yours to do, on your own timeline. Ask for the document itself, who issued it, what scope it covers, when it was issued, and which parts of your own payment environment fall inside that scope. Our certification verification checklist sets out the same sequence in more detail. A provider's certificate and your store's obligations are separate questions; ask your acquirer or qualified assessor which is which.

Should a multi-rooftop group default to the largest provider?

No. IT Support Chicago's position is that a dealer group should right-size its provider to coverage needs rather than assume larger delivers better. Headcount is not a service guarantee, and we advise buyers not to treat it as one.

The argument for size deserves a fair hearing. Buyers who favor the biggest firm usually point to bench depth, after-hours rotation, and the ability to cover several sites at once — all real concerns for a group running rooftops from the city out to the collar counties. Our data carries no headcount field, so none of those are readable from company size; they are readable from a provider's answers. Ask which named engineers would be assigned to your account, how a weekend outage gets handled at each rooftop, whether metro travel is in scope or billed separately, and what happens when the assigned engineer is away.

Ask the same questions of a smaller firm rather than assuming the trade-off runs only one way: who covers the account during turnover, and how coverage is documented when a single engineer knows your sites best. Employee Reputation carries weight 20 of 100 in our published score precisely because turnover is a risk even when clients are happy today. Our size and fit guide covers how to match coverage to rooftop count without treating headcount as a proxy for quality.

What our score cannot tell you about dealership fit

Our published score combines four criteria scored from public evidence, and the largest single input is public review sentiment. IT Support Chicago weights Client Reputation 29 of 100, with a median of 32.7 and a mean of 44.1 across tracked firms. It is scored for 95 of 95 firms, so it is the one dimension every ranked provider carries — and it says nothing about whether any of those reviewers runs a dealership.

The gap between that median and mean shows how unevenly review evidence is distributed across the firms we track. A high Client Reputation figure reflects volume, recency, and platform credibility in public reviews, not vertical experience. Across all vendors we record 6,083 client reviews and an average client rating of 4.79 / 5.0, and none of that aggregate is broken out by industry. Coverage varies elsewhere too: Proactive Issue Reduction, weight 27 of 100, is scored for only 52 of 95 firms, so an unscored firm is one we lack workforce data for rather than a reactive one.

Our records also note weaknesses alongside scores — client reviews on a single platform only, recent ratings trending down against an all-time average, or a workforce weighted toward reactive support roles. Read those before you read a ranking position, and read our scoring methodology before you read either. We would rather a dealer discount a score honestly than over-read it, because no part of it was built from dealership evidence.

Running the evaluation yourself: scope, price, and term

A dealership technology vendor evaluation should start with written scope, not with a shortlist. Write down rooftop count, device and user counts by department, coverage hours including weekend operations, where cardholder data moves, and which systems are supported by a platform vendor rather than by your IT firm. Vendor research for an auto dealer group is mostly this document; the quotes get comparable only once it exists.

On price, our position is that a per-user monthly rate compared without scope context is misleading. One provider's per-user figure may cover a different set of services than another's, and travel, after-hours work, and on-site visits may sit inside or outside it. Put each quote next to your scope document line by line before you put the rates next to each other, and ask each provider in writing what falls outside the fee.

On term, our position is that shorter agreements are generally better for the buyer, and that long lock-ins primarily benefit the vendor. The common counterargument — that a multi-year deal locks in your rate and gives the provider room to invest — is worth weighing honestly, but it also removes your cheapest form of recourse. IT Support Chicago advises shorter agreements, since long lock-ins primarily benefit the vendor rather than the dealership buying the service.

Service Level Agreements (SLAs) follow from that. Our position is that SLAs earn their keep mainly in multi-year agreements, as a mechanism for sharing pain with the vendor. If your term is under a year, or carries termination for convenience, our view is that the stronger remedy is simply leaving — so read the termination rights guide before you negotiate credit language.