For ERP sellers
The best manufacturing ERP prospects are plants where something just forced the question: new owners, a legacy system nearing end of life, a first controller, a new site, or an acquired incumbent vendor. Reach them before the scoring sheet is written.
Book a demoLast updated September 27, 2026
The short answer
Plants rarely replace an ERP out of dislike. They replace it when something forces the question: new owners, a legacy system at end of life, a first controller, a new site, or a renewal after their vendor is acquired. Deals commonly take 120 to 270 days and turn on a scoring sheet written early. Clean finds those plants while the decision is still open.
Plenty of plant owners dislike their ERP and are not shopping for a new one. Dislike is a constant, and a constant is not a buying moment. The system holds the item master, routings, bills of material and years of job cost history, and everyone knows its workarounds.
So the ERP stays the system of record and a spreadsheet becomes the system of work: the schedule, the hot list, the real cost of a job. That spreadsheet proves the pain. It does not prove timing.
What moves a plant is an outside push: a legacy vendor putting a date on the end of support, or a second site that single-site inventory and costing can't handle. For ERP, that push often arrives as one of six moments. The full set of 14 is in manufacturing buying signals.
Our view: start with ownership change, whether it comes as a private equity deal, a merger or an owner handing the business on. New owners often want numbers the old system cannot produce.
Private equity adds a second wave. Add-ons were about 38% of completed US middle-market private equity buyouts in Q1 2026, up from 31% the quarter before (all industries, per Schneider Downs). Know which deal you are in: a platform deal is an opening, while an add-on may simply be moved onto the platform's system.
ERP buying moments and what they tend to open (typical patterns, not guarantees)
| Buying moment | What changes at the plant | Why it opens an ERP deal |
|---|---|---|
| Ownership change | A private equity deal, a merger or owner succession | After a private equity deal, new owners commonly revisit ERP, banking, insurance and benefits within about a year |
| Systems change | The legacy ERP nears end of life or a migration starts | The plant must move anyway, so the question is which system |
| First controller | A first hire in a finance function the plant never had | Rule of thumb: around 100 to 200 employees. The new controller did not pick the current system |
| New site | A second plant or warehouse is bought, built or leased | Two sites strain single-site inventory, costing and reporting |
| Capacity expansion | A new line, shift or major equipment | More jobs and routings outgrow the spreadsheet schedule |
| Incumbent vendor acquired | The plant's ERP vendor changes owners | One negotiation advisor reports 15 to 40% list-price increases after PE buyouts of mid-market software. Not every acquirer reprices |
Headcount sets the signer. The full approval map, including when a capital expenditure request kicks in, is in how manufacturing plants buy.
Every extra person costs time. In Focus Digital's 2026 cross-industry benchmark, deals with one decision maker averaged 28 days and deals with 9 to 12 averaged 182. An owner-led ERP decision and a committee decision are different sales at the same price.
Our view: in ERP the controller matters more than in almost any other plant category. One implementation firm's test for a mid-market project is whether someone inside can own the chart of accounts decision and be available weekly for eight months. At a mid-size plant that person is often the controller, so a plant without one is rarely ready.
Who decides, by plant size (typical patterns, not rules)
| Plant size | Who decides | What the evaluation looks like |
|---|---|---|
| About 50 employees | The owner, often alone | A demo, a reference call, a gut decision |
| About 200 employees | President or GM, after the controller builds the payback | A shortlist, scripted demos, a scoring sheet |
| 1,000+ employees | A committee across operations, IT, finance and corporate | A formal RFP, an IT security review, legal redlines |
Clean's compilation of published prices and third-party estimates puts a manufacturing ERP at roughly $56,000 to $235,000 in year one, from a small deployment to a mid-market system at 50 users. Treat it as directional. For traditional ERPs, implementation services often run 1 to 2 times the first-year subscription. Clean's rough range for the cycle is 120 to 270 days from first touch to purchase order, with bigger plants taking longer. Focus Digital's benchmark (all industries) puts $50,000 to $100,000 deals at about 120 days and $100,000 to $250,000 deals at about 170.
Expect the incumbent to defend on price. Large ERP vendors commonly discount harder at quarter end, so if your deal sits in legal as their quarter closes, have the controller's payback case ready. Test your numbers in the manufacturing pipeline value calculator and see how other categories compare in manufacturing software sales cycles and deal sizes.
Mid-size and larger plants typically buy ERP through a scored bake-off: a shortlist, scripted demos, a weighted sheet. The sheet often gets written early, around vendors the plant already knows. A vendor who first shows up when the RFP goes out is being scored on weights someone set before it arrived.
Timing beats a better demo here. Reach the plant soon after the moment and open with the change itself: the reporting pack the new owners want, the support end date on the old system, the second site's inventory. More on the first touch is in how to sell to manufacturers.
Implementation partners get one extra opening, which one implementation firm calls a common mid-market case: the stalled first attempt. The legacy vendor announces end of support with a one to three year runway, a first partner runs discovery and loses momentum, and the plant still has to finish before support ends. The next firm in is selling a rescue.
Contact databases and intent data tools mostly miss these moments. Intent data measures reading, and no plant reads its way into a new owner. Which ERP runs a plant's back office almost never appears on its public website either, so tools that scan for installed technology only ever see the marketing site.
Clean researches manufacturing accounts plant by plant: the account is the site where jobs get routed and costed, not only the parent's head office. More than 4,000 early signs sit in Clean's database, catalogued across 14 buying moments in a plant's life, and about 190 of them matter to ERP sellers. For each plant, those signs are laid out on a dated timeline, and a temporal graph network weighs their order and spacing. A change of owners, then a new head of finance, then a second site says more about an ERP decision than any one of the three alone, and Clean maps more than 140 typical chains like that one.
Each plant Clean puts in front of an ERP team carries a dated reason to reach out. Attached to it: the evidence, any other explanation that could fit, and the fact that would prove the reason wrong. Unconfirmed facts stay marked unknown; Clean doesn't guess at them. Repair shops, contractors and one-person operations never reach your list; they are filtered out first. Clean works out who to reach and why, often before the plant has said anything publicly, and your team does the reaching out.
Clean's September 2026 research on the seller side covered more than 500 companies whose software, AI and automation products go into US plants. The mechanics are in how Clean works. Book a demo and you'll leave the call with a live list of plants built for your ERP.
Most plants live with an ERP they do not love until something forces the question, such as new owners, an end-of-life legacy system or a first controller. Reach the plant soon after that moment, open with the specific change, and get on the shortlist before the scoring sheet is written.
Common triggers are an ownership change, a legacy system nearing end of life, a first dedicated controller, a new site, a capacity expansion, and a renewal after the ERP vendor is acquired. Dissatisfaction alone rarely does it, because the data, training and workarounds tied to the current system make switching a project nobody volunteers for.
Plan on roughly 120 to 270 days from first touch to purchase order, a rough range compiled by Clean. Plant size drives most of the spread: an owner-led 50-person shop can decide in a few months, while a plant of 1,000 or more runs a formal RFP, an IT security review and legal redlines.
Directionally, about $56,000 to $235,000 in year one, based on published prices and third-party estimates compiled by Clean. The low end is a small deployment and the high end is a mid-market system at around 50 users. For traditional ERPs, implementation services often run 1 to 2 times the first-year subscription, so plants compare total cost.
At around 50 employees the owner typically decides alone. Around 200, a president or general manager signs after the controller builds the payback case. At 1,000 or more, a committee spanning operations, IT, finance and corporate runs the evaluation. Wherever there is a controller, that person owns the chart of accounts work that makes or breaks the project.
Next
Clean