CRM & sales · 28 December 2025 · 5 min read

Building a CRM machinists actually use

Salesforce, Pipedrive, HubSpot are excellent — if you run a software company or a consultancy. Drop one into a machine shop and you have bought a tool shaped for a world that isn't yours.

The pattern is familiar: a job shop buys enterprise CRM, uses it for a few months, then drifts back to Excel. Here is why that happens — and how to avoid it.

What generic CRM gets wrong

An obsession with sales stages

Pipedrive has "Lead", "Qualified", "Proposal", "Won". Salesforce has custom funnel stages. But a machine shop does not really have a sales funnel — it has customers, quotes pending, and delivery dates. Force a shop into a funnel and half the data ends up wrong or misleading. A quote that has been "in the pipeline" for three weeks isn't in the pipeline; it is probably dead.

The wrong activities tracked

Generic CRM logs calls, emails and meetings. Your real activities are: quote sent, quote revised, quote lost (and why), job delivered on time, repeat customer ordered again. You do not care that someone emailed three weeks ago. You care that a quote has sat for 21 days with no follow-up.

No machine or capacity context

When you are quoting, the first question is: can we actually do this, and when? Generic CRM does not know you have a single 5-axis centre, and it does not know that centre is booked solid through March. So you quote work you cannot deliver, or you quote high because you are overbooked and the tool gives you no way to see it.

Suppliers as an afterthought

Your suppliers matter as much as your customers, but generic CRM treats "supplier" as a contact category. A shop needs supplier contacts and pricing, material lead times, historical pricing to spot inflation, and payment terms. None of that fits naturally into a sales-funnel CRM.

What a machine-shop CRM should hold instead

Simple customer records

Store what you actually use: company, contact, phone, email, notes on capability (5-axis work, aluminium specialist), last order date, repeat frequency. That is it. No "lead score", no "lifecycle stage".

Quote tracking, not a sales funnel

Every quote ever sent. Date, value, status (pending, accepted, lost). If lost, why — too dear, too slow, went elsewhere. And a nudge when a quote goes stale, say after a couple of weeks of silence.

Machine allocation

See at a glance which machines are booked when. Add a prospective job, check whether you have capacity, and know your real delivery date before you promise it.

A supplier database

Centralised supplier contacts, pricing and lead times. When you need a lead time for stainless bar stock, you check the system instead of digging through old emails.

An activity log, not email tracking

Log the operational facts — quote sent, quote revised, customer called, job shipped, repeat order received — but not as busy-work. The point is to answer real questions: why did this customer order three times in six months, and what is their pattern? This one keeps coming back with rush jobs — do we charge extra, or say no?

Why this matters for the bottom line

Quote follow-up. The most common reason a winnable quote is lost is that nobody followed it up. A system that simply surfaces stale quotes — rather than hiding them in an inbox — means more of them get chased, and a chased quote stands a far better chance than a forgotten one. We are not going to invent a percentage for you; the mechanism is the point.

Capacity planning. When the person quoting can see the machines are full, they quote higher or turn the work down. When they cannot, they promise dates the floor can't hit. Visibility removes the guess.

Supplier management. How often does someone ring a supplier without checking the lead time first? Centralised supplier info removes those wasted calls.

The implementation trap

Here is where most shops come unstuck: they buy generic CRM, try to shoehorn their reality into it, and give up after a couple of months. The fix is not more training. It is CRM built for the way a shop actually works — complex machines, capacity constraints, supplier relationships, repeat customers. Get that right and adoption is natural, because the software matches what people already do.

That is the thinking behind DASCRM. It is built around quotes, customers and capacity rather than a generic funnel — and because it is part of DMOS, a won deal becomes a job in DASBridge automatically, instead of being re-keyed into a separate system.