← Back to Field Notes

January 20, 2025 · The Bloomfield Team

Why Shops Still Run on Spreadsheets

An IndustryWeek survey found that 72% of manufacturers with fewer than 100 employees use spreadsheets as a primary tool for at least one critical business function: quoting, scheduling, inventory tracking, or production planning. Most of these shops also have an ERP system. They pay for it monthly. They use it for invoicing, purchase orders, and work order management. Then they open Excel to do the work that actually runs the business.

The standard explanation is that these shops are resistant to technology. That reading misses the point entirely. Shops run on spreadsheets because spreadsheets do something that most manufacturing software fails to do: they conform to the way the user thinks about the problem.

The Flexibility Problem

An estimator building a quote in a spreadsheet has complete control over the structure. They can add a line for a material surcharge that no standard quoting module anticipated. They can build a conditional formula that accounts for their specific shop rate structure, with different rates for five-axis work versus three-axis work versus manual lathe operations. They can add a column for notes that captures the reasoning behind a price, visible right next to the number.

The same estimator working inside an ERP quoting module faces a fixed set of fields. The system was designed to handle the general case. Manufacturing quoting is never the general case. Every shop has pricing logic that reflects their specific equipment, their specific customer relationships, and their specific cost structure. When the software cannot accommodate that logic, the estimator builds a spreadsheet that can.

This is a rational response to a real limitation. The problem is what happens at scale.

What Spreadsheets Cost at Scale

A single spreadsheet on a single person's desktop is a useful tool. Thirty spreadsheets across five people's desktops, each containing a different slice of the operation's data, each with its own formula logic, each updated on its own schedule, becomes a fragility the operation depends on without realizing it.

The estimator's quoting spreadsheet contains five years of pricing history that no other system can access. The scheduler's capacity planning sheet has machine availability data that the ERP's scheduling module does not reflect accurately. The quality manager's tracking sheet has nonconformance patterns by part family that the quality system's reports cannot produce. The owner's financial model pulls from three different spreadsheets to calculate true job profitability because the ERP's standard reports do not account for actual overhead allocation.

Each spreadsheet is a shadow system. Each one fills a real gap. Together, they form a fragile web of operational knowledge that breaks when someone changes a formula, when a file gets overwritten, or when the person who built it leaves the company. The gap between what the ERP delivers and what the operation needs is where spreadsheets live and where risk accumulates.

Why ERP Implementations Fail to Close the Gap

Most ERP systems for small and mid-size manufacturers were built to manage transactions: purchase orders, work orders, invoices, inventory movements. They do this well. What they do poorly is support analysis and decision-making. Querying historical job data to find comparable quotes requires either custom reports that someone has to build and maintain or SQL access that nobody on the team is comfortable using.

The implementation process typically consumes six to eighteen months and $50,000 to $250,000 for a 30-to-50-person shop. At the end of that process, the system handles transactions. The spreadsheets that handle decisions remain because the ERP never addressed the decision-making gap that created them in the first place.

The answer is not a bigger ERP or a more expensive implementation. The answer is a layer that sits on top of the ERP and the spreadsheets, connecting the data from both into tools that support the specific decisions your team makes every day. That is what custom AI tools for manufacturers are designed to do.

The Path Forward

Spreadsheets are not the enemy. They are a signal. Every spreadsheet in your operation represents a decision that your existing systems do not support well enough. Cataloging those spreadsheets, understanding what decisions they serve, and identifying which ones carry the most risk if they break or become outdated is the first step toward building something better.

The shops that successfully move beyond spreadsheet dependence do it incrementally. They pick the highest-value spreadsheet, the one that carries the most risk or supports the most consequential decisions, and they build a proper system around that specific use case. The estimator's quoting spreadsheet becomes a connected quoting tool that pulls historical data from the ERP automatically. The scheduler's capacity sheet becomes a real-time view of machine availability. Each replacement eliminates risk, preserves the logic that made the spreadsheet valuable in the first place, and connects previously isolated data to the rest of the operation.

Your spreadsheets are telling you where your systems fall short. The question is whether you listen to what they are saying or keep adding tabs.