CRM for machine shops: what it does and how to choose one

A CRM for a machine shop is the system that keeps RFQs, quote follow-up, customer history, contacts, and repeat-order signals in one place so work doesn’t disappear into inboxes or spreadsheets. In plain English, it helps you track who asked for what, what you quoted, what changed, and who needs a nudge next. It is not the system that runs production; that job belongs in ERP or MRP.

What a machine shop CRM actually is

A machine shop CRM is a contact-and-follow-up system built around quoting work, not around selling subscriptions or office services. It helps you remember who the customer is, which parts or part families they buy, what RFQs came in, what you quoted, what revision you’re on, and when to check back.

For example, say one buyer sends a steady mix of phone calls, emails, and drawing updates for several part families. A good machine shop CRM keeps that history tied to the account, so the estimator or sales lead can see the latest thread without digging through a shared inbox or asking around the office.

It also helps with repeat business. If a customer reorders six months later, the shop should be able to see the old quote, the last revision, the contact who handled it, and the notes that explain how the job was won. That is the kind of memory a spreadsheet usually loses unless someone is extremely disciplined.

CRM vs ERP vs job shop software

CRM handles relationships and sales follow-up. ERP or MRP handles jobs, materials, routings, purchasing, inventory, scheduling, shipping, and the production side of the house. Quoting often sits between them: some shops quote inside the CRM, some inside the ERP, and some use a separate estimator tool that feeds both.

A simple way to draw the line is this: if the record is about winning work or keeping the customer informed before the job exists, it belongs in CRM. If the record is about making the part after the order is won, it belongs in ERP or MRP. A common mistake is forcing production status updates into CRM, which creates duplicate entry and annoys the team. The CRM should not become a second job traveler.

If a vendor says it is all one platform, check carefully where each record actually lives and who has to type the same thing twice. Generic sales CRM software can work for a simple shop, but it usually starts to feel awkward when RFQs, quote revisions, and ERP handoff are part of the daily routine. That is the boundary to watch: CRM should support the quote process, not replace the production system.

The workflow from RFQ to repeat order

A real shop workflow usually starts with an RFQ arriving by email, phone, or portal. The CRM should create or update the customer record, attach the contact, and log the request so the estimator can see the print, due date, material notes, tolerance concerns, and any special handling.

From there, the quote is prepared. If the buyer asks for a revision, the CRM should keep the old version, not overwrite it. That matters because machine-shop work often changes across revisions, and the history can explain why a price moved or why a lead time changed.

If the quote turns into an order, the handoff to ERP or MRP should be clean. The CRM’s job is to preserve the sales history and the promise that was made; the ERP’s job is to turn that promise into a job traveler, material plan, and production record. After delivery, the CRM should help you see when the next reorder is likely, who the buyer is now, and which part families tend to come back.

A shop often notices the value of this only after a buyer leaves and nobody can quickly tell who used to order which parts, on what cadence, and under which revision history. That is where a machine shop CRM earns its keep.

The fields and automations that matter most

The useful records are usually simple:

• customer record: company name, locations, credit or terms notes if you keep them there, and account owner
• contact record: buyer, engineer, quality contact, shipping contact, and who handles which part family
• RFQ record: source, due date, linked customer, part family, drawing or spec reference, and status
• quote record: quoted price, lead time, version, assumptions, and what changed from the last version
• revision record: drawing revision, customer revision notes, and which quote version matched it
• follow-up record: next step, promised callback date, and who owns it
• job link: the ERP or MRP job number once the order is won

The best automations are the boring ones: remind the estimator when a quote ages past your normal window, flag RFQs with no reply, and surface repeat-order candidates based on old quotes or closed jobs. Keep the judgment calls human. A machine shop CRM should nudge people, not pretend it knows when a buyer is likely to award a difficult job.

What belongs in CRM versus ERP/MRP is pretty consistent. CRM should hold the conversation, the quote trail, the revision trail, and the next action. ERP or MRP should hold the traveler, routing, materials, work center load, inventory, and shipping. If the CRM starts duplicating production status screens, it is probably too heavy for a quoting-heavy shop.

What to automate and what to keep human comes down to this: automate reminders, status flags, stale-quote alerts, and repeat-order prompts. Keep pricing judgment, exception handling, customer promises, and award decisions human. In practice, the shop gets into trouble when software starts making assumptions about lead time or award probability that only an estimator can judge from the print and the buyer relationship.

How to judge a CRM before you book demos

Start with fit, not features. A good job shop CRM should be simple enough that an estimator can update it between calls without slowing down the quote process. If the demo feels like a generic sales tool built for software companies, that is a warning sign.

Use this checklist:

• Can it track RFQs, quote versions, and follow-up without awkward workarounds?
• Can it keep customer history tied to multiple part families and multiple contacts?
• Can it show the next action fast, without five clicks?
• Can you move data in from spreadsheets or the old system without a months-long cleanup project?
• Does it report on quote aging, open RFQs, win/loss, and repeat business in a way the shop will actually use?
• Does it leave production, inventory, and scheduling in ERP or MRP where they belong?
• Can it handle the handoff from RFQ to quote to order to re-order without forcing duplicate entry?
• Does it let you keep revision history instead of overwriting it?

Watch for common mistakes when moving off spreadsheets or an old system. The first is trying to clean every old record before go-live; that can stall the project forever. The second is importing fields no one uses just because they exist in the old file. The third is making the CRM so rigid that people go back to email and side spreadsheets the first time the workflow gets messy. The fourth is expecting the system to fix an unclear quoting process. Software cannot repair a process nobody has agreed on.

Ask to see the daily workflow, not just a polished dashboard. Watch what happens when an RFQ becomes a revision, then an order, then a reorder six months later. If the system makes that path clumsy, it will not get used. And if it needs a long training project just to log a call, it is probably too heavy for most machine shops.

A practical rule: if the demo spends more time on sales activity scores than on quote history and account history, keep looking. A machine shop CRM should help your team remember and respond, not make them manage software all day.