Skip to Content

How to Choose an IT Provider for Your Machine Shop

September 4, 2025 by
Jay Stoltzfus
Jay Stoltzfus

It's 7:15 on a Wednesday. The file server that holds every print, every Mastercam program, and the folder your quotes come out of went unreachable sometime during second shift. You called your IT company at 6:40. You got a voicemail box. The guy who runs the press brake is standing in your doorway, and first shift is burning payroll while you decide whether to send anybody home.

Nobody teaches a shop owner how to choose an IT provider, so most owners do it the way they buy a used forklift: get three prices, pick the middle one, hope it runs. Which means that Wednesday morning isn't really about the server. It's about a decision you made two years ago in your office, in about twenty minutes.

Your IT company ends up wired into everything. The server the floor pulls prints from. The email your POs arrive in. The system you quote out of. The backups that decide whether a ransomware hit is a rough week or the end of a 40-year business. Those are the eight mistakes we see most often in shops around Chester and Lancaster County, and every one of them is avoidable before you sign anything.

Why the Wrong IT Provider Costs You Production, Not Just Money

An office that loses IT for a morning has a slow morning. A shop that loses IT for a morning has people standing around, a spindle not turning, and a ship date that just moved.

That's the piece most IT companies never internalize. They came up supporting insurance agencies and accountants, where the worst case is a laggy inbox. They don't picture a job traveler that can't get printed, a CMM program that can't be pulled, or a customer calling Thursday about a part that was promised Wednesday.

Here's the plain-English version we walk through with owners: eight ways this goes wrong, and the exact question to ask so it doesn't.

8 Mistakes Shops Make When Choosing an IT Provider

1. Buying the newest thing instead of fixing the broken thing

Every IT salesperson has a version of the same pitch. Cloud this, AI that, a platform that will transform how you run the business. Meanwhile the actual problem is a nine-year-old server that drops connections at 2pm and a wireless signal that dies past the second bay.

New isn't the same as right. A brand-new system that doesn't fit how your shop runs is an expensive distraction, and you'll be the one training people on it.

Ask this: How does this help us get parts out the door? Make them connect every recommendation to something concrete: fewer stoppages, faster quoting, a floor that doesn't wait on IT. If they can only answer in buzzwords, you're their revenue plan, not their client.

2. Never asking what happens at 6:40 in the morning

Response time is the only metric that matters on the morning something is down. Yet most owners never ask what "support" actually means in practice.

Plenty of providers advertise 24/7 and mean you can leave a voicemail at any hour. That's not coverage, that's an answering machine with a marketing budget. And if you run second or third shift, a provider whose real hours are 9 to 5 is going to leave you dark for most of your production week.

Ask this: What's your guaranteed response time for a server down, in writing, by severity level? Who picks up at 5am? How fast can a human be standing in my building? Ask for a recent example of an after-hours call and how it went.

3. Treating security as something you'll get to later

Shops get hit. Not because anyone wants your parts, but because attackers scan for weak spots and small manufacturers usually have them. When it lands, it doesn't feel like a data breach. It feels like every file on the network having a strange extension and the floor going quiet.

A provider with weak security habits doesn't just fail to protect you. Their remote access tools become another door into your network. Slow patching, no monitoring, and backups nobody has ever test-restored are how a bad Tuesday turns into a two-week shutdown.

Ask this: What's on every machine, and does it just match known virus signatures or does it watch behavior? (If that distinction is fuzzy, here's the difference between antivirus and EDR.) Are backups stored off site, and when did you last actually restore one to prove it works?

4. Shopping on the monthly price alone

The cheapest quote is almost never the cheapest year. Low headline pricing usually means the cheap number covers monitoring and not much else, and everything you actually call about gets invoiced separately.

Then there's the version where the price really is low and the service really is bad, and you end up paying a second company to clean up after the first one. Owners tell us about this constantly. It's also how IT costs quietly spiral without anyone deciding to spend more.

Ask this: What's included, what's billed extra, and what does the price do when I add five people? A flat monthly number per device is easy to budget and easy to check. Hourly billing quietly trains your people not to call when something is wrong, which is exactly backwards.

5. Hiring for the shop you have, not the shop you'll be in three years

If you're planning a second building, another CNC with its own controller PC, or five more seats of CAD, your IT needs in three years won't look like today's.

Some providers are built for five-person offices and start dropping the ball at twenty. Others are built for 300-seat companies and will quote you an enterprise stack you don't need at a price you can't justify. Both mismatches end in a migration you didn't plan for.

Ask this: Tell me about a client you supported through growth. What broke and what did you change? Then tell them your actual plans. A provider who gets quiet when you describe adding a building is telling you something.

6. Accepting an agreement that doesn't actually promise anything

A vague service agreement is worse than none, because it feels like protection right up to the morning you need it. Undefined response times, exclusions broad enough to cover anything, credits that refund a fraction of one month while you lost three days of production.

Read the exclusions before the features. That's where the real agreement lives.

Ask this: Are response times defined by severity, in hours, with a number next to each? What's excluded? And what happens if you miss it? You're not looking to collect penalties. You're looking to see whether they'll write down what they've been telling you.

7. Forgetting that your people actually have to use this

The best setup in the world fails if the office manager keeps a sticky note with the password on the monitor and the guy who runs the saw can't get into the shop-floor terminal without help.

Skip the training and you get the predictable results: nobody adopts it, tickets pile up, people invent workarounds that punch holes in the security you just paid for. Multifactor authentication is the classic one. Rolled out with ten minutes of walking people through it, it's a non-event. Dropped on a Monday with no warning, it's a mutiny by 9am.

Ask this: How do you handle rollouts and onboarding? Who trains my people, in person or on video, and what happens when someone new starts? Ask specifically what training looks like for the folks on the floor, not just the office.

8. Skipping references and shop experience

You wouldn't hire a machinist off a résumé alone. Yet plenty of owners sign an IT agreement having spoken to exactly zero of that company's clients.

Industry experience matters more than most people expect. A provider who has supported manufacturers knows a CAD file server is not a normal file server, that shift change is a bad time for a reboot, and that a shop's cyber insurance renewal has technical questions on it. A provider whose whole book is professional offices will learn that on your dime.

Ask this: Can I talk to a manufacturer you support right now? Then ask that owner the real questions: how fast do they respond when something is down, do they bring you problems before you find them, and would you hire them again. Also ask whether the provider will get on the phone with your ERP vendor when something breaks between the two systems, because that handoff is where shops usually get stranded.

Red Flags That Should End the Meeting

Some answers should end the conversation on the spot:

  • They won't give you references, or claim their clients are "too busy" to talk.
  • There's pressure to sign this week, or a discount that expires before you can think.
  • Security answers stay vague no matter how directly you ask.
  • No clear escalation path for an emergency. Just "call the main line."
  • Pricing is dramatically below everyone else with no explanation of what's missing.
  • They've never supported a manufacturer and can't describe one thing about how a shop differs from an office.

The Quiet Bonus: Renewals and Customer Questionnaires Get Easier

Here's what nobody mentions during the sales process. The same things that make a provider good at keeping your floor running are exactly what your cyber insurance carrier and your biggest customer are now asking about.

Multifactor authentication, endpoint detection, tested offsite backups, documented patching. Choose well and renewal season is a form you hand off and forget about, and an OEM security questionnaire is an afternoon instead of a crisis. Choose badly and you're checking boxes you can't actually back up, which is how claims get denied. If your renewal is coming, it's worth knowing what carriers are actually asking for now before you answer anything.

IT Provider FAQs for Small Manufacturers

What should a small manufacturer look for in an IT provider?

Look for response commitments in writing, real security controls, flat predictable pricing, and experience with shops rather than offices. The provider should understand that a file server outage stops production, not just email. Ask how fast they get on site, who answers at 5am, and whether they'll document your systems so you're never dependent on one person's memory.

What questions should I ask an IT provider before signing?

Ask five things: what's your guaranteed response time by severity, what's included versus billed extra, how do you handle backups and test restores, who comes on site and how fast, and can I talk to a manufacturing client you support today. Get the answers in the agreement, not in an email from a salesperson.

How much should IT support cost for a 20-person machine shop?

Most shops are best served by a flat monthly price per device rather than hourly billing, because hourly billing punishes you for calling when something is wrong. Ask for the per-device number, what it includes, and what triggers an extra invoice. A clear number you can multiply by your device count beats a low headline rate with surprises attached.

Do I still need an IT provider if we already have an IT guy?

Often yes, because one person can't cover second shift, vacations, and a resignation. The bigger risk is documentation. If your systems live in one person's head, their two-week notice becomes your emergency. Many shops keep their internal person and add a provider for monitoring, backups, security, and coverage when that person is unavailable.

Will an IT provider help with our cyber insurance renewal?

A good one will fill out the technical sections and close the gaps before you submit. Carriers now ask about multifactor authentication, endpoint detection, offsite backups, and patching, and answering yes without the controls in place can void a claim. Ask a provider directly whether they've completed carrier applications for other clients.

Is it worth switching IT providers mid-contract?

It can be, if the current provider is missing response commitments or leaving you exposed. Read your termination clause first, then confirm who owns your passwords, backups, licenses, and documentation. A professional transition takes a few weeks of overlap and shouldn't require any production downtime. Get the offboarding terms in writing before you give notice.

Not Sure Your Current IT Company Is the Right Fit?

Starlux IT is based in Parkesburg and works with small manufacturers across Chester and Lancaster County: Coatesville, Downingtown, Gap, and the shops in between. Our techs are local and get on site the same day, because a floor that's down can't wait on a helpdesk three time zones away. We know what a SolidWorks and Mastercam file server needs to stay fast and recoverable, and we bill a flat monthly rate per device so nobody hesitates to pick up the phone. Here's what a managed IT plan for a shop covers if you want the details.

If you're evaluating providers right now, take 30 minutes with us. No pressure, no pitch deck. We'll look at what you have, show you the gaps, and you'll walk away knowing exactly where you stand and what to ask everyone else you're talking to, whether you hire us or not.

Book your free 30 minutes →

Jay Stoltzfus
Jay Stoltzfus September 4, 2025
Share this post
Archive