How to Compare IT Companies in Chicago: A 10-Point Buyer’s Scorecard

Three proposals land on your desk in the same week. All three promise 24/7 support, all three mention cybersecurity, and the monthly prices sit within a few hundred dollars of each other. On paper, they look interchangeable. Six months after you sign, the differences show up: how long a down server stays down, whether anyone noticed a suspicious login at 2 a.m., and how hard it is to leave if things go badly.

This guide is for owners, office managers, and managing partners evaluating managed IT services in the Chicago area. It gives you ten criteria to compare providers on, the questions to ask for each, what a strong answer sounds like, and a scoring table you can copy into a spreadsheet. If you’re still building a shortlist, start with our overview of IT companies in Chicago, then come back here to evaluate the finalists side by side.

Proposals Hide the Differences That Matter Most

Most IT proposals are written to look alike. They list the same categories (help desk, monitoring, security, backup) because that is what buyers expect to see. The real differences live in the details a proposal rarely spells out: what “response” means, which security tools are included versus quoted later, and what happens to your passwords and documentation when the contract ends.

The stakes are higher than a typical vendor decision. Your IT provider holds administrative access to nearly everything your business runs on. The 2025 Verizon Data Breach Investigations Report found that third-party involvement in breaches doubled to 30% in a single year, and the IBM Cost of a Data Breach Report 2025 put the average cost of a breach for U.S. organizations at a record $10.22 million. Choosing a provider is a security decision as much as a service decision.

The 10 Criteria, and How to Pressure-Test Each One

Ask every finalist the same questions, in writing, so you’re comparing like with like. Vague answers are information too.

1. Response Time Guarantees: “Fast” Means Nothing Until It’s in the SLA

Every provider says they’re responsive. What matters is whether that promise is defined, measured, and contractual.

Ask:

• What are your guaranteed response times by priority level, and are they in the contract?
• Do you distinguish between response time and resolution time?
• Can you show me last quarter’s actual response metrics for clients my size?

A good answer sounds like: “Critical issues affecting the whole office get a technician working on them within a defined window, around the clock. Lower-priority requests have their own tiers. We report actual performance against those targets every month, and the targets are written into your service agreement.”

Red flag: “We’re usually pretty quick” with no tiers, no reporting, and nothing in writing. Also confirm who answers the phone. A strong IT help desk puts you in touch with a technician, not a ticket-taking answering service.

2. Onsite Coverage Area: Remote Support Has Limits

Most issues get fixed remotely, but failed network switches, new office buildouts, and hardware swaps still need someone on site.

Ask:

• Where do your onsite technicians dispatch from, and how long does it typically take them to reach our office?
• Is onsite work included, or billed separately?
• Do you cover all of our locations, including satellite offices?

A good answer sounds like: “Our techs dispatch from [a named location], your office is within our regular service area, and onsite visits for covered issues are included in your agreement.”

Red flag: A provider who can’t tell you where their nearest technician is based, or who subcontracts onsite work to a third party without disclosing it.

3. Security Stack: Ask Who Is Watching, Not Just What Is Installed

Antivirus and a firewall are the floor. A modern cybersecurity program layers several controls and, critically, puts humans behind the alerts.

Ask:

• Which security tools are included in the base price, and which are add-ons?
• Who monitors security alerts overnight and on weekends: a person in a security operations center, or an automated email?
• How do you enforce MFA and Conditional Access in Microsoft 365?
• How do you secure your own remote management tools and technician accounts?

That last question matters because of the third-party risk data above. Your provider’s access is a door into your environment.

A good answer sounds like: “Every client gets endpoint detection and response monitored by a 24/7 SOC, email filtering, MFA on every account, network security at the firewall, security awareness training, and backups with scheduled restore tests. Our own technicians use phishing-resistant MFA and least-privilege access.”

Red flag: Security described only in product names, with no mention of who responds when something fires. Bonus points for providers who offer periodic penetration testing to validate their own work.

4. Industry Experience: Your Software and Regulations Should Sound Familiar

A provider who already knows your line-of-business applications and compliance obligations will onboard faster and make fewer mistakes.

Ask:

• How many clients in our industry do you support today?
• Which of our core applications have you managed before?
• What compliance requirements apply to us, and how does your service address them?

A good answer sounds like: For a law firm, the provider brings up document management platforms like iManage or NetDocuments and the confidentiality duties under ABA Rule 1.6 without being prompted. For healthcare, they confirm they’ll sign a Business Associate Agreement. For manufacturing, they ask about your ERP and plant-floor systems.

Red flag: “We support all industries” with no specifics.

5. Contract Terms: Read the Exit Before the Entrance

The most important clauses are the ones you hope never to use.

Ask:

• What is the term length, and does it auto-renew?
• Can we terminate for cause if SLAs aren’t met?
• What is the notice period, and what offboarding help do you provide?

A good answer sounds like: “Here’s exactly how renewal and termination work. If we miss our commitments, you have a defined path out, and we’ll hand over credentials and documentation as part of a structured transition.”

Red flag: Long auto-renewing terms with steep early-termination fees and no performance-based exit.

6. Pricing Model: The Exclusions Tell You the Real Price

Per-user, per-device, all-inclusive, and hourly block models can all work. Problems come from what sits outside the monthly fee.

Ask:

• What is included, and what is billed separately? Specifically: onsite visits, after-hours work, new-user setup, projects, and software licensing.
• How do prices change as we add staff?
• What did a typical client our size spend beyond the monthly fee last year?

A good answer sounds like: “Here is a written list of inclusions and exclusions. Day-to-day support is unlimited, and projects are quoted separately in advance.” Providers who publish their managed IT pricing openly make this comparison much easier.

Red flag: A low headline number with per-ticket or hourly charges for routine requests. That structure discourages your staff from asking for help early.

7. References: Talk to a New Client and a Long-Term One

Ask:

• Can you connect me with two or three clients similar to us in size or industry?
• Can one of them be a client who onboarded in the last year?
• What is your client retention rate?

A recent client remembers onboarding clearly. A five-year client tells you whether service holds up after the honeymoon period.

A good answer sounds like: References arrive within a day or two, and the provider points you to public client testimonials and reviews as well.

Red flag: Hesitation, or references who only talk about pleasant account managers rather than outcomes.

8. Onboarding Process: The First 30 Days Predict the Next Three Years

Ask:

• Walk me through your onboarding plan and timeline.
• What do you typically find when you audit a new client’s environment?
• How do you communicate the transition to our staff?

A good answer sounds like: A documented onboarding process with a defined timeline, and a candid list of common findings: excessive admin permissions, accounts belonging to former employees, missing patches, outdated software, and backups no one has tested.

Red flag: “We’ll just install our agent and get going.” Skipping discovery means problems carry over into the new relationship.

9. Strategic Planning: Someone Should Own Your Roadmap

Day-to-day support keeps you running. Planning keeps you from being surprised by end-of-life hardware, licensing changes, and budget spikes.

Ask:

• Will we have a dedicated account manager separate from the help desk?
• How often do you meet with us to review performance and plans?
• Do you help build an annual IT budget?

A good answer sounds like: “Your account manager runs quarterly business reviews covering environment health, risk trends, and a forward-looking roadmap.” Look for genuine IT strategy and consulting, not a sales pitch disguised as a meeting.

10. Documentation and Ownership: You Should Own the Keys

Ask:

• Where is our network documentation stored, and can we access it?
• Who holds the global admin credentials for our Microsoft 365 tenant, domain, and firewall?
• If we leave, what do we receive and how quickly?

A good answer sounds like: “You own your documentation and credentials. You’ll always have break-glass access, and we provide a full handover on exit.”

Red flag: Any suggestion that documentation is proprietary to the provider.

A Scoring Table You Can Copy

Score each provider from 1 to 5 on each criterion, multiply by the weight, and total the column. The weights add up to 20, so a perfect score is 100. Adjust the weights to fit your priorities; a healthcare practice might raise industry experience, while a multi-site distributor might raise onsite coverage.

Scoring guide: 1 = vague or evasive, 3 = adequate but not documented, 5 = specific, documented, and in the contract.

Have two or three people from your team score independently, then compare. Where your scores disagree, you’ve found the follow-up questions for your next call.

Downtown vs. Suburban Providers: Geography Changes the Math

Chicagoland is big, and where a provider’s technicians are based affects what “onsite support” means in practice.

Downtown offices in the Loop, River North, or West Loop come with their own logistics. Many high-rise buildings require vendors to provide a certificate of insurance, reserve freight elevators, or check in with building management before work starts. A provider experienced with downtown Chicago IT support will already have these routines down. Ask how they handle building access and after-hours work in managed properties.

Suburban offices in places like Schaumburg, Naperville, Aurora, Hoffman Estates, or St. Charles face a different issue: distance. A provider dispatching from the city may be an hour or more away on the Kennedy or the Eisenhower during rush hour. Suburban businesses also tend to have warehouses, shop floors, or multiple sites that need hands-on work more often.

The practical test is simple. Map every location you have, then ask each provider for the realistic drive time from their dispatch point to each one during business hours. If you have both a downtown office and a suburban site, confirm the provider covers both with the same service levels rather than treating one as an exception.

Make the Decision With Evidence, Not Impressions

Sales meetings reward charisma. A scorecard rewards specifics. Send the same written questions to every finalist, score the answers honestly, and give extra weight to anything a provider is willing to put in the contract.

If you’d like a clearer picture of where your current environment stands before you compare providers, a cybersecurity risk assessment gives you a baseline to measure every proposal against. You can also book a 15-minute call with our team, or reach us at (312) 922-8600 in Chicago or (847) 888-1900 in the suburbs. We’re happy to answer every question on this scorecard.

Aaron Kane

CEO of CTI Technology

Aaron Kane is the CEO of CTI Technology, headquartered in Elgin, IL, with a team across Chicagoland — helping businesses navigate technology with confidence. With expertise in IT strategy, infrastructure, cloud solutions, and voice technologies, Aaron focuses on helping organizations improve efficiency, strengthen operations, and make smarter technology decisions. Under his leadership, CTI Technology has continued to grow while maintaining a strong focus on service and long-term client relationships.

Connect with Aaron on Linkedin