How to pick a CRM that fits the way a manufacturer sells
A manufacturer's CRM has to handle quote requests, engineering review, distributors and reps. It also has to work with an ERP that already owns pricing and orders. Here's what to look for, how the usual options compare, and when we'd tell you HubSpot is the wrong pick.
Free, 30 minutes, and you'll leave with at least one clear next step.
What does a manufacturer need from a CRM?
A manufacturer needs a CRM that tracks every quote from request to order, shows each account's order history from the ERP, and handles sales that run through distributors and reps. Email and marketing tools help. Those three jobs decide whether your team keeps using it.
Most CRMs are sold on a simple sale, where one buyer fills in a form and a rep closes the deal. A plant rarely sells that way. One order can involve an end customer, a specifying engineer, a distributor and a rep firm. The quote may sit with engineering for a week, and the price and lead time come from the ERP.
Test each CRM with a quote from last month that went through engineering and a distributor. Ask the vendor to show you where every piece of it would live.
Questions to put to every CRM on your shortlist
- Can one deal show the end customer, the distributor and the rep firm, each with a named role?
- Can quote revisions stay on one deal, with the reason each one changed?
- Is there a stage for engineering review, and can you report on how long quotes sit there?
- Which ERP connectors exist, who builds them, and which records do they actually move?
- Can outside reps who never log in still send leads and updates?
- What happens to a won quote? Does someone retype it into the ERP?
- Which features need the top plan, and what does each extra seat cost? Check current pricing on the vendor's site.
How HubSpot compares with the CRMs manufacturers usually shortlist
HubSpot
Sales, marketing and service on one database, and reps tend to pick it up fast. Quotes, approvals and line items run in its CPQ tools. Custom objects for projects or equipment need Enterprise. NetSuite and Business Central have HubSpot-made connectors, and most other ERPs need middleware or a custom build.
HubSpotSalesforce, including Manufacturing Cloud
Very flexible, with an industry edition that adds sales agreements and account-level forecasts for repeat, contract-based orders. That flexibility usually comes with a longer setup and an in-house admin or a partner on call. It makes the most sense for large, multi-division companies with complex forecasting.
HubSpot vs SalesforceMicrosoft Dynamics 365 Sales
A natural fit if your company already runs on Microsoft and Business Central or Finance and Operations. Setup and reporting lean on Microsoft partners, and marketing tools are a separate product.
The CRM inside your ERP
NetSuite, Epicor, Acumatica and others include CRM features. They have one big advantage, since orders and prices are already there. Marketing, email and the day-to-day rep experience are usually thinner, so many teams end up using them only for order entry.
Zoho CRM and Pipedrive
Quick to start. They suit a small sales team with simple quoting. Teams with distributor networks, engineering review or a heavy ERP link often outgrow them and face a second migration a few years later.
HubSpot vs ZohoWhere the CRM stops and the ERP starts
The biggest choice in a manufacturing CRM project is deciding which system is right when the two disagree. This is the split we start from. Anything that changes what gets built, shipped or billed stays in the ERP.
CRM governs
- Quote requests (RFQs) and web inquiries
- Quote revisions and approvals
- Distributor and rep firm links
- Specifying engineers and buyers
- Trade show leads
- Lost quote reasons
Shared, synced one way
- ERP customer number ERP to CRM
- Order history and last order date ERP to CRM
- Credit hold flag ERP to CRM
- Won quote becomes a sales order request CRM to ERP
ERP governs
- Bills of materials and routings
- Standard costs and price lists
- Production schedule
- Inventory and lead times
- Sales orders and invoices
- Credit holds
Does HubSpot connect to the ERP a manufacturer already runs?
Yes, for most ERPs, though the route differs. HubSpot makes its own connectors for NetSuite and Microsoft Dynamics 365 Business Central. Epicor, SAP Business One, Sage, Acumatica, Plex and older systems usually connect through a third-party connector, middleware or a small custom build.
The connector matters less than the plan behind it. Before anything is built, we write down which fields sync, in which direction and how often, and both sales and accounting sign it. Records get matched on the ERP customer number, never on company names. Our guide on connecting HubSpot to an ERP walks through the whole process, and our NetSuite integration page covers that connector in detail.
A custom power systems manufacturer came to us after an earlier move from Salesforce left gaps and mismatched fields. We cleaned up the data and reorganized its HubSpot and ERP sync so customers and orders match in both. Reminders, assignment and follow-up now run on their own instead of by hand.
When is HubSpot the wrong CRM for a manufacturer?
HubSpot is the wrong pick when your sales mostly happen inside the ERP, or when you need a product configurator with deep engineering rules. In those cases we'll say so on the first call.
Your sales team mostly enters orders. If three inside reps key in repeat orders from long-time accounts and you do almost no marketing, the CRM in your ERP may be enough. Adding HubSpot gives them a second screen to keep up.
You sell configured products with hundreds of rules. HubSpot's quotes and CPQ tools handle line items, discounts and approvals well. A product that needs a rules engine to check which options fit together usually needs a dedicated configurator, which can then pass the finished quote to the CRM.
You run many divisions with their own data models. A very large company with separate business units, its own admins and complex territory forecasts may get more from Salesforce, even after the extra setup. Our HubSpot vs Salesforce comparison covers where that line falls.
Your main problem is on the shop floor. If the trouble is scheduling or capacity, a CRM won't fix it. Our Friction Point Analysis finds where the time goes first.
Manufacturers who run HubSpot with us
A power systems manufacturer left Salesforce and now sells from one system tied to its ERP
Read the case studyA commercial oven maker put its forgotten leads back in front of sales in just over 45 days
Read the case studyWhat goes wrong after manufacturers buy a CRM?
The software is rarely the problem. Most failed CRM projects we review were set up in a hurry, with too many fields and no rules about who owns what.
A commercial oven manufacturer we work with had a HubSpot account full of stale deals. Its sales leader guessed the open deal list looked about four times bigger than it was. Our audit turned up leads that had never been called. We rebuilt three pipelines and made key deal fields required. Those leads were back with sales in just over 45 days.
Our guide on what to set up first in HubSpot lays out the order that avoids most of this.
How we help you choose and set up
-
Trace a few recent quotes
We follow recent quotes from request to invoice across your CRM, inbox and ERP, and show where each one stalled. You get this even if you decide HubSpot isn't right for you.
-
Agree the record split
Sales and accounting sign off on which system owns each field, which records sync and in which direction.
-
Set up and connect
Pipelines, quote stages, distributor and rep roles, the ERP link and the first three reports, tested on live accounts.
-
Train and adjust
Short training sessions for reps and managers, then a few weeks of fixes once people are using it day to day.
CRM for manufacturers questions
What's the difference between a CRM and an ERP for a manufacturer?
The ERP runs what gets built, shipped and billed, such as bills of materials, inventory, orders and invoices. The CRM runs the selling before that, such as quote requests, follow-up and lost-quote reasons. Most manufacturers need both, connected so reps can see order history.
Do we need a separate CRM if our ERP already has one?
Not always. If your team mostly enters repeat orders and does little marketing, the ERP's CRM may be enough. If you chase new accounts, follow up on quotes and run email or ads, a separate CRM connected to the ERP is usually the better fit.
Can a CRM track quotes that need engineering review?
Yes. In HubSpot we add an engineering review stage to the deal pipeline, assign the engineer a task and report on how long quotes sit there. That report often shows the biggest delay in the whole sale.
What should a manufacturer budget for a CRM?
Plan for three costs: licenses, setup and the ERP connection. License prices change, so check current pricing on each vendor's site. Setup and integration depend on your data and your ERP. We scope ours after the first call.
Can we switch CRMs without losing quote history?
Yes, if the move is planned. Companies, contacts, deals and notes can all come across, with duplicates merged first. Our Salesforce to HubSpot checklist lists what to export and check before you switch.
Related
More in HubSpot
Bring us one quote and we'll show you where it would live
On a 30-minute call we'll look at how you quote today and tell you plainly whether HubSpot, your ERP's CRM or something else fits better.