← Back to Field Notes

October 6, 2025 · The Bloomfield Team

How to Choose the Right ERP for a Small Manufacturer

Panorama Consulting Group's 2024 ERP report found that 37% of manufacturing ERP implementations exceeded their budget. Average implementation time ran 16 months. For companies under $50 million in revenue, the numbers skew worse because the internal resources available to manage the project are thinner and the cost of disruption during cutover is proportionally higher.

The mistake happens before the first demo. Most shops start by listing features they want, scheduling vendor presentations, and comparing price quotes. That process selects for the best salesperson, not the best system. Here is a different approach that starts with how your shop actually works.

Start With Your Processes, Not the Vendor's Demo

Before talking to any ERP vendor, document how work moves through your shop today. From the moment an RFQ arrives to the moment a part ships and an invoice goes out. Who touches it. What systems they use. Where they wait for information. Where they enter the same data twice.

This exercise takes two to three days if you do it seriously. Walk the floor with a notebook. Sit with the estimator, the scheduler, the production supervisor, the quality manager, the shipping coordinator. Map each handoff. The output is a process flow that shows how your operation actually runs, which is almost never how anyone thinks it runs.

An ERP should fit your critical processes. The vendor who can show you their system running your actual workflow, using your terminology, with your job types, is the one worth evaluating further. The vendor who shows a polished demo with sample data and tells you the system can be configured to match your needs is the one who will cost you six figures in customization later.

The Seven Questions That Matter

When evaluating ERP systems for a small manufacturing operation, these questions separate the contenders from the pretenders.

1. How does your system handle job-based costing? Make-to-order shops need real-time job cost visibility. If the ERP cannot show actual vs. estimated costs at the job level, with material, labor, and overhead broken out, it was built for a different kind of manufacturer.

2. What does your quoting module actually do? Many ERPs claim to handle quoting. In practice, the module is a basic form that stores a price. If your estimators need to pull historical job data, compare similar parts, and build cost estimates from actual production records, test this workflow in detail during the evaluation.

3. How does scheduling work on a real shop floor? Ask the vendor to demonstrate scheduling with your actual constraints. Multiple operations per part. Shared resources across work centers. Rush orders that rearrange the queue. If the scheduling module cannot handle the way your shop actually sequences work, your team will build a parallel system in spreadsheets within three months of go-live.

4. What data can I get out of the system without a consultant? Reporting is where many ERP implementations fail. The data goes in, but extracting it in a useful format requires custom reports that cost $2,000 to $5,000 each. Ask to see the standard reports. Ask how custom reports are built. Ask what it costs.

5. How does this integrate with my existing systems? Your CAD/CAM package, your quality system, your CRM, your accounting software. Open APIs matter. A system that locks your data behind proprietary walls will cost you in integration work for years.

6. What does the implementation actually look like for a shop my size? Get a detailed implementation plan with hours, milestones, and responsibilities. Ask for references from manufacturers within 20% of your employee count and revenue. A vendor who thrives in the 500-employee range may not understand the constraints of a 35-person operation.

7. What happens after go-live? Support response times. Update frequency. The size of the user community. Whether your vendor will still exist in five years. Small ERP vendors get acquired, merged, or sunset regularly. Ask about the company's ownership structure and growth trajectory.

Common Systems and Who They Fit

JobBOSS2 and E2 Shop System serve the 10 to 75 employee job shop market. They are built for make-to-order environments and understand the quoting-to-shipping workflow that custom manufacturers need. Their limitations show up when shops grow past 100 employees or need advanced planning and scheduling capabilities.

Epicor Kinetic targets the 50 to 500 employee range and offers deeper functionality in production planning, quality management, and supply chain. The implementation cost and complexity increase accordingly. Budget $150,000 to $400,000 for a mid-size manufacturing implementation including software, services, and the internal time your team will invest.

Global Shop Solutions, ProShop, and IQMS (now DELMIAworks) each serve specific niches within the small to mid-size manufacturing space. The right choice depends on your specific process type, industry vertical, and growth trajectory. For a deeper look at how ERP systems connect to the broader technology discussion, see our guide to ERP and AI integration.

What the ERP Will Not Do

An ERP is a system of record. It stores transactions, tracks jobs, manages inventory, and generates financial reports. What it does not do well is connect scattered data sources, surface insights from historical patterns, or deliver context to your team at the moment they need it.

A shop that implements the right ERP still needs to think about how quoting data, production data, quality data, and customer data come together to inform decisions. The ERP handles the first layer. The intelligence layer, where your data becomes operational knowledge, requires different tools built on top of that foundation.

Choose the ERP that fits your processes and your team's ability to adopt it. Then build the decision-support layer that turns transaction data into competitive advantage.