Operations Advisory
ERP, Systems, and Workflow Transformation
Get the system and the process aligned, in either order.
A new ERP or system implementation rarely fails because of the software. It fails when it gets layered onto a process no one has redesigned, or configured around requirements no one actually validated. This capability covers system selection, implementation governance, and the workflow redesign that has to happen alongside it.
Understanding the Business
Growth gets harder when the economics of the work become difficult to see.
This is not a finance exercise.
Financial statements matter, but running a business requires understanding what sits underneath them: where revenue is created, where money is spent, how cost accumulates, who is authorized to commit resources, how work moves from an order to delivery, and where margin can quietly disappear along the way.
As companies grow, that visibility often becomes fragmented.
Pricing may live in one place. Purchasing in another. Labor and material costs may be reconstructed after the fact. Operating teams maintain their own spreadsheets. Customer commitments sit outside the financial system. Managers know the P&L but cannot easily explain what operationally created the result.
That is where revenue leakage, cost leakage, weak pricing decisions, and unpleasant month-end surprises begin to appear.
The question is not simply, "Are the financial statements accurate?"
It is, "Can the systems underneath them explain how this business is performing?"
A healthy business system should make it easier to understand:
Where do we make money?
What does the work actually cost?
Where are we losing margin?
Who can authorize spending and commitments?
Can we trace the operating activity that produced the financial result?
If those answers require several people, multiple spreadsheets, and a long reconciliation exercise, the business may have outgrown the way it is being managed.
Financial results are the output. Business systems should let you see what created them.
The System Around the System
A powerful platform cannot help much if the business still operates around it.
Many companies already own capable systems.
They also carry paper for signatures.
Maintain critical spreadsheets outside the ERP.
Re-enter the same information into multiple platforms.
Pay for modules nobody uses.
Build custom workarounds around processes the core system could already handle.
Discover that different functions have different versions of the same customer, cost, inventory, or performance data.
The useful question is therefore not, "Do we have an ERP?"
It is, "How much of the business actually runs through it?"
A business-systems review looks across the whole environment:
The core financial and ERP platform.
CRM and customer information.
Planning, purchasing, inventory, and operations.
Quality and compliance systems.
Payroll, workforce, and training systems where relevant.
Reporting and business intelligence.
Integrations, spreadsheets, paper processes, and bolt-on applications.
Data ownership, approvals, authorities, and segregation of responsibilities.
The objective is not to eliminate every specialized tool. It is to understand whether the pieces form a coherent system or whether the organization has gradually built a collection of disconnected solutions around its core.
In the core system
A connected platform
A spreadsheet, paper, or an inbox
This is one common pattern, not a diagnosis. The real exercise is mapping where your own activities actually live.
ERP Selection & Transformation
When the core system needs to change, make the decision deliberately.
The wrong implementation can cost far more than choosing the right system carefully.
There comes a point where spreadsheets, entry-level accounting platforms, disconnected applications, or an aging ERP can no longer support the business the company has become.
Taking the next step can be intimidating. The market is crowded with platforms, implementation partners, new software, AI claims, custom solutions, and vendors who naturally believe their product is the answer.
The objective is not to buy the most sophisticated system. It is to choose the right-sized core architecture for the business you are building.
That starts by defining the operating requirements before evaluating the software.
What needs to be controlled?
What information needs to move between functions?
What does leadership need to see?
What processes should remain standard?
Where is specialization genuinely required?
There is also an important discipline in accepting that most businesses are less unique than they believe. Modern ERP platforms have been shaped by thousands of companies across industries. Standard processes often represent years of accumulated operating knowledge.
Customization should therefore earn its way into the system. Every unnecessary modification creates another item to maintain, test, upgrade, integrate, and eventually replace. Saving money or preserving an old process during implementation can become considerably more expensive later.
Where possible, favor:
Custom
Standard
Bolted On
Integrated
Locally Obsolete
Cloud-Supported
Vendor Features
Business Requirements
Short-Term Convenience
Long-Term Architecture
Lasting Progress can support the process from the business side: defining requirements, evaluating the current environment, helping down-select platforms and partners, challenging unnecessary customization, supporting implementation governance and go-live, and helping ensure the system is built around how the company needs to operate.
The role is not to replace the software implementer. It is to help the business remain an informed customer throughout the process.
Closing Thought
The best ERP is not the one with the longest feature list. It is the one that becomes the reliable core of how the business operates, understands its economics, and makes decisions as it grows.
From Insights
Related thinking from Lasting Progress Insights.
Start with a conversation, not a proposal.
You do not need to have the problem perfectly defined. An initial conversation can clarify what is happening, what may require immediate attention, and whether Lasting Progress is the right fit.