Manufacturing guide
Plants buy through an approval ladder set by size: the owner signs at small shops, a president or GM signs after the controller checks payback at mid-size plants, and bigger purchases need a capital expenditure request. An outside date often sets the timing.
Book a demoLast updated October 5, 2026
The short answer
Manufacturing plants buy through an approval ladder set by size. The owner signs at a small shop. At a mid-size plant the controller checks payback and a president or GM signs. Bigger purchases go through a capital expenditure request, and software adds IT review. The date often comes from outside: a customer, an auditor or a breakdown. Clean researches those moments plant by plant.
The generic B2B buying process (problem, research, shortlist, decision) holds for plants too. It hides the part that decides your forecast: who can say yes, and up to what amount. In plants, that moves with headcount.
At a 50-person shop the owner usually raises the purchase and signs it, often personally. Around 200 employees a president or GM typically signs after the controller checks the payback. At 1,000 or more, expect a buying committee across operations, IT, finance and corporate, plus IT security review for most software. Some 300-person family companies still buy like the 50-person shop, so ask.
The request usually starts with the plant manager or someone who reports to them. This page covers what happens next.
A typical pattern, not a measured rule. Every company differs.
| Question | About 50 employees | About 200 employees | 1,000+ employees, multi-site |
|---|---|---|---|
| Who raises it | The owner | Plant manager, quality or maintenance manager | Site leader or a corporate function |
| Who signs | The owner, often personally | President or GM, after the controller checks payback | A committee across operations, IT, finance and corporate |
| Written approval policy | Usually none | A threshold ladder, often only on paper | A formal delegation of authority |
| IT involvement | An outside IT provider, if anyone | One IT generalist, often with an outside provider | Security review for most software |
| What often kills the deal | The owner changes course | The payback math | Security review or a corporate standard |
In many mid-size plants the finance gate is a controller, not a CFO. The controller typically owns three things: the payback math, the vendor setup paperwork (tax forms, insurance certificates, supplier onboarding) and cash timing against the bank line. As a rough rule of thumb, a controller shows up somewhere around 100 to 200 employees, and a CFO gets added above them as the company grows.
Sellers rarely meet the controller because the champion carries the case upstairs. Fix that without going around your champion: ask early what the controller will want to see, then build that page together. Payback in months on line one, total cost on line two, assumptions underneath. The plant manager reads the feature list. The controller reads the payback line.
Timing note: controllers are often buried in the month-end close for the first few workdays, a bad week to chase a signature.
Companies rarely publish their delegation of authority. One published approval template for a 100 to 300 employee company gives a useful shape. It is one template and not manufacturing-specific, so use it to ask sharper questions, not to assume a number.
Two details matter more than the dollar amounts. The controller rung, $10,000 to $25,000, sits roughly where many smaller plant software contracts land (see manufacturing software sales cycles and deal sizes). And software goes to IT review regardless of cost.
Capital climbs fewer, higher rungs. A plant manager's own capital authority commonly tops out somewhere between $25,000 and $100,000. Above that, the purchase leaves the plant as a formal request to an operations leader, the CFO or the owner. So ask your champion straight out: what is the most you can approve without a capital request?
One published approval template for a 100 to 300 employee company. Not a survey and not manufacturing-specific.
| Purchase amount | Who approves |
|---|---|
| Under $500 | Auto-approved |
| $500 to $2,500 | Department manager |
| $2,500 to $10,000 | Director or VP |
| $10,000 to $25,000 | Controller |
| Over $25,000 | CFO |
| Any software or subscription | IT security review, regardless of cost |
Before anyone weighs in, the capitalization threshold decides which path a purchase takes. One published capex guide puts the typical line at $5,000 to $10,000, though each company sets its own. Below it, the money comes from an operating budget the plant manager already runs. Above it, the purchase becomes a depreciated asset and usually needs a form.
The tax code's de minimis safe harbor lets a business that elects it expense items up to $2,500 per invoice or item, or $5,000 with an applicable financial statement such as audited financials. (Not tax advice.)
For software sellers this cuts two ways. Subscriptions usually land in an operating budget. The sensors, installation and integration around them often don't, so a machine monitoring or automation deal can split into an expense line and a capital request with different approvers and clocks. Ask how the plant will book each piece before you quote.
A capital expenditure request, also called a capex request or a capital appropriation request (AFE in oil and gas), is the document that moves a purchase above the plant's own authority. At many mid-size plants it is a spreadsheet or a short form, and these are the parts your champion will be asked to fill in.
Two things commonly sink one: soft savings finance can't tie to a line on the P&L, and a capacity case for work the plant hasn't won yet. One practitioner put his company's rule for capacity projects plainly: have the business in hand before you spend.
Payback in months is the sentence a plant manager can repeat upstairs. One industrial woodworking machinery dealer's published guide puts common hurdles at a 15% to 25% ROI or a payback of three years or less. Some practitioners describe the bar for cost-reduction projects as closer to two years. Treat both as typical, and ask your champion which bucket your deal falls into.
Build payback from numbers the plant already tracks: scrap and rework dollars, unplanned downtime hours, overtime, quote turnaround, first-pass yield. Your case study averages won't survive the controller. If your champion has no baseline, make measuring one the first job of the pilot.
Match the story to the owner's horizon. According to one 2026 research brief, close to two in three US manufacturing businesses are owned by someone aged 55 or older. Our view: an owner planning an exit soon will hear a three-year payback very differently from a newly installed second-generation president.
Your champion has probably written a capital request for a machine. Software may be new to them. This order tends to work:
Not every purchase climbs the ladder. Safety fixes and breakdowns often get a fast-track path outside the normal budget cycle, especially when a safety deadline is involved. That authority commonly sits with an operations or facilities leader. When a press is down, nobody waits for the next capital review. The sellers who live in that moment are mostly in EHS software and maintenance software.
Deadlines a customer sets compress approvals the same way. A new program with a first article inspection date, a supplier scorecard sliding toward red, or an IATF 16949 audit on the calendar all make the cost of waiting visible. If your product fixes something with a date attached, put the date in your first sentence.
If it doesn't, don't invent urgency. Plant equipment and qualified suppliers stay in place for years, and switching means requalification and downtime. A this-week-only offer tells the buyer you don't know how plants buy.
Software is the one category where a small price doesn't guarantee a short path. In the template above, software goes to IT review regardless of cost. At 1,000-plus employees, expect it. At 200 employees the reviewer might be one IT generalist with an outside provider. At 50 it might be the owner's outside IT firm, or nobody.
The questions rarely change: where the data lives, who at your company can reach it, how you connect to the ERP and the machine controls, and what happens to the data if you go away. Plant buyers often resist subscriptions over lock-in as much as over price, so answer the exit question first.
Defense suppliers add a hard gate. If the plant handles controlled unclassified information for defense customers, expect detailed questions on data location, access and your own security, often framed around CMMC, before anyone books a demo. See CMMC compliance prospects for how that market buys.
Once a company runs several plants, a VP of operations or COO typically sits between the CEO and the plant managers. Plant managers keep authority over their building, but capital allocation and standards move up a level. At 1,000-plus employees, expect corporate quality, EHS and procurement directors who set the standard each site has to buy to.
That structure produces a common late-stage loss: a site pilot that works, then dies because corporate has a standard or a program of its own. Sell to both levels on purpose, and ask your plant manager early who at corporate owns the category. Plant-level targeting gets you in the door at the right site. Corporate gets you the rollout.
At 50 employees a formal pilot is rare. The owner watches the product work on a real part, then decides. At 200, a pilot often means one line or one cell with a metric agreed up front. At 1,000, it is a one-plant proof that has to survive a corporate review before anyone talks about rollout.
Pilots are also where plant deals stall. The research on pilot purgatory, and how to run a pilot that gets decided, is in how to sell to manufacturers. The short version: a pilot with no owner and no decision date rarely turns into a purchase order.
A few habits keep a pilot alive. Charge for it, even a small amount, so someone inside the plant owns the result. Get the controller to agree to the success metric in writing. Book the decision meeting before the pilot starts. Bring in the people whose daily work changes from week one.
In our research, plants tend to buy when a customer, a regulator or a broken machine sets the date, more often than when a budget opens. Industrial Equipment News surveyed more than 250 manufacturing executives and managers in 2025, and their answers lean the same way. Asked what most often starts a significant purchase, 59% pointed to aging assets, 53% to regulatory compliance and 52% to capacity expansion, all ahead of cost savings at 39%.
Money is rarely the stated problem. In a late-2025 national survey of manufacturers, access to capital was the least-cited challenge, named by under 5% of respondents. What's scarce is a dated reason and a champion who can write the case. For the month-by-month view, see when manufacturing plants buy.
Clean researches manufacturing accounts plant by plant and sorts what happens at each one into 14 buying moments, running from a new site or capacity expansion through to a certification renewal or a compliance deadline. The aim is to put you in front of the plant while its decision is still open, which is often before the company has announced anything. Each reason Clean gives you is dated and shows its supporting evidence, the alternative readings that might also explain it and the test that would disprove it, so your champion is not asked to take the timing on faith. Whatever Clean can't confirm is left marked unknown. Read the 14 manufacturing buying signals or how Clean works, then book a demo and, on the call, we'll assemble a live list of plants for your product.
When the purchase will be booked as an asset and costs more than the requester can approve alone. Plants commonly treat equipment above about $5,000 to $10,000 as capital, and a plant manager's own authority often tops out between $25,000 and $100,000. Subscriptions usually come from an operating budget, but bundled hardware, installation or a multi-plant rollout can push a deal into one.
A request usually starts with whoever owns the problem, often a plant, maintenance or quality manager. Finance, commonly a controller at mid-size plants, checks the payback math. It then climbs rungs set by dollar amount, up to an operations leader, the CFO or the owner. Software often adds IT security review, while safety fixes and breakdowns frequently get a fast-track path.
Small shops keep it simple: the owner sees the software work and signs. Mid-size plants compare a few options, the controller checks payback and a president or GM signs. Large multi-site companies add IT security review and sometimes a corporate standard that overrides the plant. Subscriptions usually come from an operating budget, while hardware may need a capital request.
There is no single rule. One industrial woodworking machinery dealer's published guide puts common hurdles at a 15% to 25% ROI or a payback of three years or less. Some practitioners describe the bar for cost-reduction projects as closer to two years. Customer-required, safety and compliance projects are judged differently, because someone outside the plant sets the cost of waiting.
It depends on size and amount. At small shops the owner approves almost everything. At mid-size plants department managers approve small purchases, a controller signs in the tens of thousands and a president or GM signs above that. One published template for a 100 to 300 employee company puts the controller at $10,000 to $25,000.
Next
Clean