No ERP Does Everything. Here Is What Works Instead.

TL;DR. Your ERP is good at what it was designed for: accounting, job costing, AP/AR, and compliance reporting. It was never designed to run your quoting workflow, capture your best estimator's knowledge, coordinate field crews in real time, or route insurance claims intelligently. Mid-market companies that try to force these workflows into their ERP spend more on workarounds than they would on purpose-built tools. The winning pattern: keep your ERP as the financial system of record, then build (or buy) specialized tools for the workflows that actually differentiate your business.

You are not imagining it. Your ERP really cannot do what you need it to do.

Not because it is a bad system. Procore, Sage, Epicor, QuickBooks Enterprise, Applied Epic: these are solid platforms that do exactly what they were built for. The problem is that "what they were built for" and "what your operations actually need" are two different things. According to Panorama Consulting Group, 74% of ERP projects go over budget, and the average project runs 189% above initial estimates. Most of that overspend comes from trying to make the system handle workflows it was never architected to support.

If you run a $30M to $100M business in construction, distribution, manufacturing, insurance, or field services, this post is for you. Here is an honest breakdown of where your ERP earns its keep and where you need something else.

What ERPs Actually Do Well

Credit where it is due. A well-implemented ERP is the backbone of your financial operations. These platforms were designed from the ground up for:

Accounting and financial reporting. General ledger, accounts payable, accounts receivable, financial statements. This is the core of every ERP, and most mid-market platforms handle it competently. Sage does it. Epicor does it. QuickBooks Enterprise does it for smaller operations growing into the mid-market.

Job costing and project accounting. For construction companies and manufacturers, tracking costs against jobs or projects is table stakes. Procore, Sage 300 CRE, and Epicor all provide solid job costing modules. A $50M general contractor can track labor, materials, and subcontractor costs against individual projects reasonably well inside these systems.

Compliance and audit trails. Tax reporting, regulatory compliance, document retention. ERPs are built for auditability. Insurance companies running Applied Epic get policy lifecycle tracking. Manufacturers on Epicor get traceability. These are genuine strengths.

Procurement and AP workflows. Purchase orders, vendor management, invoice matching. Standard procurement cycles work well inside most ERPs because the process is largely the same across industries and companies.

The pattern: anything that follows a standardized, transaction-based workflow with predictable inputs and outputs is fair game for your ERP. The system of record for financial data is exactly what these platforms were built to be.

Where Every Mid-Market ERP Falls Short

Here is where the frustration starts. You paid $150K (or $500K, or more) for your ERP implementation, and you still have people working in spreadsheets, texting photos of whiteboards, and emailing PDFs back and forth. That is not a failure of adoption. It is a failure of fit.

Quoting and Estimating

A $60M HVAC contractor's quoting process involves equipment specs, labor rates that change by region and union jurisdiction, material pricing that fluctuates weekly, and historical data from similar jobs. A $45M insurance administrator's underwriting workflow pulls from actuarial tables, agent notes, carrier guidelines, and risk models. Both call it "quoting." Neither one looks anything like a standard ERP transaction.

ERPs treat quoting as a form you fill out. The actual quoting process at most mid-market companies is a judgment call informed by years of experience, dozens of variables, and institutional knowledge that lives in someone's head. No ERP module captures that.

"We spent $80K customizing our quoting module. After six months, the estimators were still running their own spreadsheets because the system could not handle our change order logic."

Knowledge Management and Institutional Memory

Your best estimator is 58. She retires in three years. Everything she knows about pricing, vendor reliability, and site-specific risks lives in her head and in a filing cabinet nobody else understands. Your ERP has a document management module. It stores files. It does not capture, organize, or make searchable the operational knowledge that keeps your business running.

This is the problem we see most often across industries. A $70M distributor whose warehouse manager knows which suppliers actually deliver on time. A $40M manufacturer whose senior machinist can look at a part spec and know the setup time within five minutes. That knowledge has enormous value, and your ERP has no architecture for it.

Field Coordination and Real-Time Operations

A $35M field-service company dispatches 40 technicians daily. The dispatcher needs to know who is available, who is qualified for which equipment, which jobs are running long, and which customer called in an emergency 10 minutes ago. This is a real-time, dynamic optimization problem.

Your ERP is a batch-processing system. It records what happened after it happened. By the time a field service call shows up in Sage or QuickBooks, the dispatcher has already solved (or failed to solve) the problem using a whiteboard, a group text, and a color-coded spreadsheet. The World Economic Forum notes that mid-market companies are finally reaching the point where AI-powered tools can handle this kind of real-time coordination, but the entry point is purpose-built tools, not ERP modules.

Claims Routing and Processing

Insurance companies running Applied Epic or Vertafore have strong policy management. But claims intake, routing, triage, and processing involve unstructured data (adjuster notes, photos, customer emails, repair estimates) that does not fit into a policy record. A $60M final expense insurance provider processing thousands of claims monthly needs intelligent routing that considers claim type, adjuster workload, complexity, and regulatory requirements. The ERP sees a claim as a financial transaction. The operation sees it as a 15-step workflow with human judgment at every stage.

Customer Communication and Follow-Up

Your ERP knows who your customers are. It does not know that the project manager at your biggest client prefers text updates on Fridays, that the site superintendent wants photo documentation of every delivery, or that the insurance agent needs a call within two hours of a status change. CRM modules exist in most ERPs, but they are bolt-ons that treat customer communication as a database problem rather than a relationship problem.

The Named Platforms: An Honest Assessment

Here is how the major mid-market platforms stack up, industry by industry.

Procore (Construction, $30M to $100M+ GCs and specialty contractors): Strong project management and document control. Decent field collaboration. Job costing and financial integration have improved but still require Sage or another accounting platform for the general ledger. Procore does not handle quoting, estimating, or sub-bid analysis deeply. If you are a $50M GC, Procore is likely part of your stack, not all of it.

Sage 300 CRE / Sage Intacct (Construction and services): Solid accounting and job costing for construction. Sage Intacct is gaining ground for multi-entity mid-market companies across industries. Neither platform handles field coordination, knowledge management, or real-time operations. Sage is your system of record, not your operating system.

Epicor (Manufacturing, $20M to $100M+): Deep manufacturing functionality: MRP, production scheduling, quality management. The platform struggles when manufacturers need to capture tribal knowledge, automate quoting for custom jobs, or integrate with field-service operations. Epicor runs your shop floor scheduling. It does not run your customer-facing workflows.

QuickBooks Enterprise (Growing businesses, $10M to $40M): The system many mid-market companies grew up on and are now growing out of. Research from Panorama Consulting consistently shows that companies hitting the $20M to $30M range start feeling the ceiling. Limited job costing, single-entity architecture, and reporting that requires exporting to Excel. If you are still on QuickBooks Enterprise at $30M, you are probably running the real business in spreadsheets.

Applied Epic / Vertafore (Insurance, $20M to $100M+): Purpose-built for insurance agency and broker operations. Strong policy lifecycle and carrier management. Falls short on claims processing automation, intelligent routing, customer communication workflows, and knowledge management. The policy is managed; the operation around it is not.

The Framework: ERP as Foundation, Not Finish Line

MIT Sloan's research on AI adoption paths identifies a spectrum from "buy" to "boost" to "build." The same logic applies to your ERP.

Keep your ERP for what it does well. Financial reporting, compliance, job costing, procurement. These are solved problems. Do not rip out your ERP. Do not spend $300K trying to customize it into something it is not.

Identify the 2-3 workflows where your ERP fails you. These are almost always the workflows that differentiate your business. The quoting process that wins you bids. The knowledge base that makes your senior people irreplaceable. The field coordination that determines whether you make money or lose it on a given Tuesday.

Build (or buy) purpose-built tools for those workflows. A purpose-built quoting tool that integrates with your ERP costs a fraction of what a failed ERP customization costs. It ships in weeks, not months. And it actually works because it was designed for your specific workflow, not for a generic transaction.

The companies getting this right are not the ones with the biggest IT budgets. They are the ones who stopped asking their ERP to do everything and started treating it as one part of a connected stack.

According to ProNovos research, the most effective approach is to treat your ERP as the financial system of record and add specialized tools for forecasting, analytics, field workflows, and executive reporting. That pattern holds across construction, manufacturing, distribution, insurance, and field services. The ERP handles the books. Purpose-built tools handle the work.

How to Know Which Workflows Need Something Else

Run this test for any workflow you are considering:

Does the workflow follow a predictable, repeatable pattern? If yes, your ERP can probably handle it. Purchase orders, invoice matching, standard billing. If no (if it involves judgment calls, institutional knowledge, or real-time decisions), you need something purpose-built.

Are people working around the system? If your team built a spreadsheet that "translates" ERP data into something useful, that is a signal. The spreadsheet is the real tool. The ERP is just the data source.

What does the workaround cost you? A $50M distributor whose inventory team spends 10 hours a week reconciling ERP data against reality is spending $25K a year on a workaround. A purpose-built inventory optimization tool costs less than that and eliminates the problem.

Can a vendor sell you something off the shelf? For generic workflows, buy SaaS. For workflows that involve your specific business logic, competitive differentiation, or institutional knowledge, build. (We covered this in depth in Build vs. Buy AI: What No One Tells Mid-Market Leaders.)

The Bottom Line

Your ERP is not the problem. The expectation that it should do everything is the problem. The Stanford HAI 2026 AI Index Report shows a 2.4x median ROI on AI investments, but that return comes from targeted, workflow-specific deployments, not from trying to bolt AI onto an ERP that was designed for double-entry bookkeeping.

Keep your ERP. Stop fighting it. Identify the 2-3 workflows where you are losing money to workarounds, and build the right tool for each one.

If that sounds like your situation, book 30 minutes with us. We will look at your current stack, identify the workflows your ERP was never meant to handle, and tell you exactly what to build and what to leave alone. No 47-slide deck. No ERP replacement pitch. Just a straight answer about where purpose-built tools will actually move the needle.

For more on capturing the operational knowledge that lives in your team's heads, read How to Capture Tribal Knowledge Before Key People Leave.