Practical Technology for Small Businesses

---

The monthly price is the easy part of an IT proposal to compare. What’s harder is figuring out whether two providers are quoting the same work.

Does support include someone coming to your office? Who sets up a new employee’s laptop? If a backup fails, who notices?

You shouldn’t have to learn a page of technical abbreviations to get those answers.

A useful IT support agreement explains which systems and services are covered, how to get help, who handles maintenance and security, and what costs extra. It should also spell out what your business is still responsible for. That clarity matters whether you’re hiring your first IT provider or reviewing an arrangement you’ve had for years. 

Before getting into software names or service tiers, ask the provider to walk through a few situations that could happen at your business. A new employee starts next week and needs a computer, email, and access to your scheduling software. Is that setup included? Someone working from home can’t connect to the files they need. Can they contact support directly, or does the request need to go through your office manager? Your accounting software stops working. Will the IT provider help troubleshoot it and work with the software company, or will you need to make those calls yourself?

These examples give you something concrete to compare. Ask which computers, accounts, applications, and locations the agreement covers, then have any exclusions explained. The answer doesn’t have to be “everything is included.” It does need to be clear before the first invoice arrives.

Look for the support hours, the way employees should request help, and how urgent problems are handled. Ask what happens outside normal business hours, too. Does someone take emergency calls? What qualifies as an emergency, and is there an additional charge?

Pay particular attention to the difference between response time and resolution time. A commitment to respond within a certain period does not necessarily mean the problem will be fixed within that period. The agreement should define what counts as a response and how the provider will keep you informed while work continues. When a proposal mentions “24/7,” ask what that covers. Is it security monitoring, access to a support team, or both?

You’ll also want to know who is handling the routine work that helps protect your systems: software updates, security settings, and reviewing suspicious activity. The Federal Trade Commission’s small-business guidance recommends keeping software updated, using multifactor authentication, and putting security expectations for vendors in writing.

Ask your provider to explain what those responsibilities look like in your agreement.

For example, which software gets updated automatically, and which applications need separate attention? If a security tool flags a problem, who reviews it? Who should an employee contact after opening a suspicious attachment?

Employee departures deserve attention here, too. Decide who notifies the provider, who removes access, and what happens to the departing employee’s files and email.

“Security is included” is a starting point for that conversation, not a complete answer.

Don’t stop at asking whether you have backups.

Find out what is backed up, how often it happens, who checks for failures, and how recovery is tested. A backup arrangement should fit the information your business needs and the way you would have to recover it.

Use something specific: “If we lost our shared customer files today, what would happen next?”

Ask who would restore them, how recent the recovered files could be, and what might affect how long the work takes. Also confirm whether restoration labor is covered or billed separately.

A line in a proposal that says “backup monitoring” doesn’t answer all of those questions. Ask whether backup software, storage, testing, and recovery work are part of the quoted service.

Ask the provider to walk through a few changes you might reasonably make during the year: hiring employees, replacing computers, adding software, or moving offices.

How would each one affect the price?

Find out whether the agreement is priced by employee, device, or another measure. Ask about onboarding charges, software subscriptions, on-site visits, after-hours work, and projects outside the regular service.

There’s nothing inherently wrong with charging separately for a larger project. You just need to know where routine support ends and separately quoted work begins. It’s also worth agreeing on who at your business can approve extra charges. That saves an employee from accidentally authorizing work they assumed was covered.

Before choosing a plan, explain how your business actually operates.

Which application do you need to serve customers? When does your staff start work? Could you manage without email for an hour, but not without access to your appointment schedule?

Those details give the provider a better basis for recommending support than your employee count alone.

Bring your recurring frustrations into the discussion as well. If your office manager spends part of every week sorting out computer problems, describe what they’re dealing with. Ask which of those tasks the proposed agreement would take off their plate.

Finally, read the renewal and cancellation terms, including what happens to your data, accounts, and documentation when the relationship ends.

Before signing, ask the provider to walk through one last question:

“What could happen during a normal month that would leave us with an extra bill or a problem we’d need to handle ourselves?”

The answer should help you understand whether the agreement fits your business.

ICS Technologies serves businesses in Florence, Muscle Shoals, and the surrounding Shoals area. Its ProActive Care offerings include monitoring, software updates, and security services, with coverage depending on the selected package and agreement. I

To discuss support for your business, contact ICS with a few details about your staff, the systems you rely on, and the problems you’d like help addressing.