What IT Looks Like for Automotive Businesses in the Pacific Northwest

I've spent enough time in dealer offices to know that IT conversations often start with the wrong question. "What's your uptime guarantee?" or "How fast do you respond to tickets?" Those matter. But they miss what actually breaks at a dealership and what that breakage costs.

A Subaru store in Tacoma had their service lane go dark last February. The DMS wouldn't load on advisor workstations. Parts lookups timed out. Techs stood around because ROs couldn't be opened or closed. The service manager called at 9:47am and said they'd lost about two hours of peak winter service traffic. The actual problem was a failed network switch in the parts department that nobody had documented as critical infrastructure. The switch carried VLAN traffic for both service-side operations and a routing path that the DMS vendor required. None of that technical detail matters to the customer who was told to come back tomorrow and chose a different shop instead.

Downtime at a dealership isn't measured in hours. It's measured in deals you no longer get to write.

The DMS Vendor Controls More Than You Do

Here's what the cloud-first consultants miss about automotive IT. Your DMS vendor — CDK, Reynolds, Dealertrack, whoever — controls a large portion of your operational reality. They require specific on-prem server configurations, specific network architecture, specific vendor access protocols. The desking software your GSM fires up at 7am to set the sales floor is fragile and undocumented and usually only fully understood by one person in the building. F&I now has FTC Safeguards exposure that shows up in deal jackets as a compliance question. If your IT partner's first move is "lift everything to the cloud," they haven't spent enough time on a service drive to understand what they're proposing.

We've worked with dealerships where the previous IT provider treated the environment like a generic office. Standard firewall rules, standard patching schedules, standard backup windows. Then a CDK update pushed after-hours hit a configuration the firewall didn't expect, and the F&I manager couldn't pull credit reports the next morning. Or Reynolds scheduled maintenance during a time that conflicted with the nightly parts inventory sync, and the parts counter opened without accurate stock counts. These aren't hypothetical. They happened in the last eighteen months within 40 miles of Seattle.

The automotive vertical has specific operational rhythms. Saturday service is peak. End-of-month is when the sales floor runs hottest. A backup window that works for an accounting firm will torch a dealership's Saturday morning. Your IT provider needs to know that before they design the environment, not after they break it.

What Actually Matters in Automotive IT

Network segmentation that matches dealership operations. Sales, service, parts, F&I — each has different uptime requirements and different vendor dependencies. When one segment has a problem, it shouldn't pull down the others. We've seen single points of failure take out an entire dealership because nobody mapped the traffic flows. Vendor relationship management. CDK doesn't return your calls the same way they return ours. Reynolds has escalation paths that only open when another vendor is on the line with a specific support contract. Dealertrack has requirements buried in implementation docs that your sales rep didn't mention. You need an IT partner who already knows those paths and has those relationships warm. FTC Safeguards Act compliance. This went live in December 2022 and a lot of dealerships are still catching up. You're required to have written information security policies, designated security personnel, risk assessments, vendor management protocols, and incident response plans. The FTC can fine you directly. Your IT provider should be helping you document and maintain that posture, not discovering the requirement when you ask. After-hours support that understands dealership hours. A ticket opened at 6pm on a Saturday during peak service isn't the same as a ticket opened Tuesday afternoon. Response time matters differently depending on where you are in the month and what part of the dealership is affected.

What We Actually Do

Ryan Collier has worked in IT since around 1996. Our team has cumulative experience north of 100 years. We've built environments for dealerships where the previous provider thought "managed IT" meant ticket response and patch management. We've inherited networks where nobody had documented which VLANs carried DMS traffic or where the vendor access paths terminated. We've worked through CDK transitions, Reynolds upgrades, and Safeguards audits.

What we count as success: deals closed without IT friction, service lanes that stay live during peak hours, F&I managers who don't call because credit pulls are timing out, parts counters with accurate inventory at open.

If your current IT story doesn't account for desking software fragility, DMS vendor requirements, or what a dark service lane costs you in February, we should talk. Call TCG at the number on craftworkgrp.com or use the contact form. We'll start with what your dealership actually needs, not what fits a standard managed services template.