IT Guidance for Automotive Clients in the Pacific Northwest

I spend most of my time with dealerships that run between 80 and 350 units per month. Which means I spend most of my time explaining why general IT advice doesn't apply to them. The network setup that works fine for a law firm or a manufacturer's rep office will cost you deals at a dealership. And the IT provider who doesn't understand that will cost you more.

The DMS runs the building. CDK, Reynolds, Dealertrack — pick your vendor. That system controls desking, service ROs, parts inventory, F&I deal jackets, accounting, everything. It also dictates your network architecture. You don't get to choose cloud-first if your DMS vendor requires an on-prem server stack with specific port access and vendor VPN rights. I've watched shops try to modernize around the DMS and hit the same wall every time. The vendor controls the infrastructure requirements. You work backward from there.

Most dealerships I talk to have some version of this story. The IT person who set things up three years ago is gone. The documentation they left is incomplete or wrong. The parts counter has a weird printer setup that only one person knows how to fix. The service advisors have a desking workflow that depends on a specific drive mapping that wasn't in any manual. And when something breaks during peak hours, the current IT provider says it's a CDK issue and CDK says it's a network issue and nobody is fixing the fact that your service lane can't open ROs.

Let me tell you what downtime actually costs at a dealership. A Subaru store near Tacoma had their F&I system go offline at 2pm on a Saturday. Peak deal-closing hours. They had four deals in the pipeline, all waiting on F&I to run credit and print contracts. The problem turned out to be a failed switch in the sales tower, but it took 40 minutes to isolate because the IT provider on call didn't know which switch served F&I and which served parts. Two of those four deals walked. Not because the customers were impatient, but because the GSM had to tell them to come back Monday and one of them bought a car Sunday morning at a different store. That's what downtime looks like in automotive. It's not measured in hours of inconvenience. It's measured in deals that don't close.

The Pacific Northwest presents specific challenges. Earthquake prep isn't optional here. Your disaster recovery plan needs to account for both the building going offline and the regional fiber routes going down. I've seen DR plans that assume cloud failover, which is great unless your internet connection is also dead. If your DMS is on-prem and your backup strategy requires live internet to function, you have a problem. You need local backups, tested restore procedures, and a documented path to getting the service drive operational again even if the sales tower is rubble.

FTC Safeguards changed the compliance landscape for dealerships starting last year. If you're holding customer financial data — and you are, in every deal jacket — you now have specific requirements around encryption, access controls, incident response, and annual risk assessments. A lot of dealerships found out about this when their lender or OEM started asking questions during audits. Your IT provider should be helping you document your security posture, not finding out about Safeguards at the same time you do. This isn't theoretical. I've watched dealerships delay deals because they couldn't immediately prove their F&I data handling met current requirements.

The vendor access problem is real and ongoing. Your DMS vendor needs VPN access. Your phone system vendor needs remote management. Your camera system vendor wants cloud upload. Your service lane display boards need internet. Your parts cataloging system needs OEM connectivity. Each one of those is a potential security hole and a potential point of failure. You need someone who understands how to segment that traffic, monitor those connections, and know when vendor access becomes vendor liability.

Here's what works: an IT provider who has actually spent time on a service drive during peak hours. Who knows what the GSM's morning desking routine looks like. Who understands that the parts counter going offline doesn't just inconvenience the parts manager — it stalls every service RO that needs a part lookup. Who can walk into your building and identify which systems are business-critical and which ones can wait until Monday.

Ryan Collier has worked in IT since around 1996. The team at TCG has cumulative experience over 100 years. What that actually means for you: we've seen the failure modes. We know what breaks and when and how much it costs when it does.

If you're running a dealership in Washington or Oregon and your current IT situation feels like a black box with occasional failures, let's talk. We can start with a simple infrastructure assessment — what you have, what's documented, what's vulnerable. No obligation. Just clarity about what your actual IT posture looks like and what it would take to make it defensible.

Visit craftworkgrp.com/contact or call us directly. We'll schedule a walkthrough of your facility and give you a written assessment within a week.