How Operators Use Peer Patterns to Accelerate ERP ROI

Over the last two weeks, I hosted live client roundtables with two ERP communities: Business Central and Acumatica. Different platforms. Different industries. The same underlying patterns.

This is the value of roundtables when they are run the right way. They get past product talk and reveal what operators are actually dealing with day to day.

After listening to these conversations, I am convinced most teams are not stuck because their ERP is missing features. They are stuck because the work that matters most lives in the exceptions.

What makes these roundtables different

We run these sessions as working conversations, not presentations. The goal is straightforward.

• Surface what is breaking in real workflows
• Compare patterns across peers
• Turn patterns into practical decisions
• Leave with a short list of actions that will move the needle

In the Acumatica roundtable, we asked clients where planning is breaking down and said it plainly: “It rarely fails because the math is broken. We know it usually fails when operating disciplines aren’t aligned.”

That line resonated because it applies everywhere. It shows up in MRP, warehouse execution, finance approvals, and integrations.

So let’s talk about what we heard, and why it matters even if you are not a Crestwood client, and even if you are not on these ERP platforms yet.

Three patterns that showed up across both communities

1) Exceptions are normal. Unowned exceptions create chaos.

Every growing company has exceptions. For instance:

• A receiving issue that needs a decision
• A pick that fails because inventory is not where the system says it is
• A customer request that breaks the standard workflow
• A planning override because lead times drifted
• A one-time approval that turns into a workaround

Exceptions are not the problem. Unowned exceptions are the problem.

When exceptions live in spreadsheets, side emails, and tribal knowledge, the business gets reactive. Close becomes fragile. Operations get noisy. Leadership loses confidence in the numbers because the numbers are constantly being corrected outside the system.

The result is predictable. More rework. More handoffs. More time spent reconciling what happened. Less time improving what happens next. This is why roundtables matter. When peers share where exceptions live, you quickly see whether your pain is unique or systemic. It is almost always systemic.

If you want ERP ROI, stop asking, “What feature are we missing?” and start asking:

• Where do exceptions live today?
• Who owns them?
• How often do we review why they happen?

2) “Simple” works until it doesn’t. Then it becomes expensive.

In the Business Central roundtable, we discussed how warehouse management is designed as a tiered model.

Business Central supports multiple levels, starting with basic inventory by location, then basic warehousing with bins, then advanced warehousing with separate warehouse documents, and finally directed picks and put-aways where the system dictates sequences and bin logic.

That tiered approach is not trivia. It is a decision model leaders can use.

Because every team hits a point where “simple” starts creating hidden cost.

• More touches per order
• More searching
• More pick exceptions
• More rework
• More expediting
• More dependence on a few people who know how it really works

We framed the mindset as crawl, walk, run. Build the foundation first, then add complexity as the business demands it. Recognize there is a tipping point where you should consider outside solutions and add-ons.

This tipping point idea is bigger than warehousing. It is how scale works.

At small volume, you can survive on memory and informal processes. At scale, those habits turn into a tax.

The cost of staying too simple is often higher than the cost of leveling up. You see it clearly once you start measuring touches, exceptions, and rework loops.

3) Data decays as you grow. Planning inputs have an expiration date.

In the Acumatica roundtable, Robert said something I want every operator to remember:

“As you grow, the data will become bad… not necessarily because it was always bad, but more like food expiring. Food goes bad. Data does go bad if we don’t keep it up to date.”

That is an accurate description of why replenishment, MRP, and DRP break in growing organizations.

Planning systems do not fail because the planning logic is flawed. They fail because inputs drift.

• Lead times are not maintained
• Min/max and reorder points get outdated
• Demand signals change with seasonality and growth
• New SKUs are added without policy discipline
• Teams override the system as a habit, then trust erodes

Once trust erodes, spreadsheets show up.

Shaun made a point we hear constantly. When teams rely on Excel, they extract data, manipulate it, and eventually it becomes cumbersome and unscalable as demand and inventory grow. You can do it for a while. Then it breaks.

Robert also reframed inventory in a way executives understand instantly. Inventory is cash. That changes the conversation from “keep shelves stocked” to “optimize capital.”

Planning quality is not just a supply chain concern. It is a working capital concern. Treat planning data like financial close. Assign ownership, review it on a cadence, measure drift.

The Customer Learning Flywheel

Roundtables create better outcomes than typical user groups because they become a repeatable operating system.

Here is the flywheel we use, and you can copy it whether you are a CFO, COO, or ERP owner.

• Collect signal: Use surveys, roundtables, support trends, and recurring questions. Do not guess.
• Curate the agenda:  Pick one to two topics only. Depth beats breadth.
• Teach a maturity model: Crawl, walk, run. Tiered capability. Tipping points. Decision rules.
• Decide native vs extend: Not all add-ons are equal. Not all problems need technology. Use a scorecard:
  • Is the workflow clear?
  • Is volume high enough to justify automation?
  • What is the risk if it fails?
  • Who owns the data?
  • Who supports it end to end?

Support ownership is part of solution design. Commit to one action and one metric. Roundtables are only valuable if they change behavior. Pick one workflow, one owner, one metric.

The 30-day reset plan

If you want to turn these patterns into action, here is a simple 30-day approach that works whether you are implementing, migrating, or optimizing.

Step 1: Pick one workflow where exceptions live

• Examples: receiving and put-away, picking and shipping, replenishment policy, demand forecasting inputs, approvals and handoffs.

Step 2: Map where work escapes the system

• List the top 10 exceptions and where they get handled today. Spreadsheet, email, chat, informal side process.

Step 3: Assign ownership

• Not “the team.” A name. Ownership turns chaos into accountability.

Step 4: Pick one metric that exposes drift

• Examples: touches per order, pick exception rate, expedite frequency, overrides in planning, stockout frequency, inventory aging, time spent reconciling.

Robert offered a practical tool most leaders skip. Run a time study. Put a timer on the desk. Measure the real cost of the workaround.

Step 5: Run a monthly reset meeting

• Thirty minutes. Review exceptions, not everything. Decide what changes. Assign actions. Repeat.

That is how ERP ROI compounds.

If you are not on an ERP yet

Most migration projects focus on features, modules, and timelines. Do not miss the real requirement: exception handling. Before you migrate, define:

• What workflows must be standardized before go-live
• How approvals and exceptions will be handled
• Who owns critical data fields and how they will be maintained
• What cadence will keep the system aligned as the business grows

If you skip this, you will go live and recreate old habits inside new software.

If you are already live on an ERP

Stop trying to fix everything at once. Stabilize one workflow at a time. Pick the area with the highest rework, the most overrides, or the most manual reconciliation. Make it owned. Measure it. Reset it monthly.

That is how you turn ERP from a system of record into a system that supports execution.

Why this matters

Roundtables are not marketing. They are how operators learn faster.

Peer patterns create clarity. Clarity improves decisions. Better decisions create ROI.

If you want help turning these ideas into a practical roadmap, connect with a Crestwood Customer Success Manager. We will help you identify the next workflow to stabilize, what to fix inside the ERP, and where an extension might actually be worth it.