When is the right time to implement an ERP?

For a growing manufacturer, the right time to implement an ERP is when growth starts creating coordination problems the team can no longer solve cleanly with spreadsheets, memory, and manual follow-up.

This article looks at the size signals that usually make the ERP question legitimate, then focuses on the operational signs that matter more than headcount. By the end, you should be able to tell whether ERP is premature, worth preparing for, or already late.

The short answer

For an industrial SME, the ERP question usually becomes serious when several of these signals appear:

• The company has more than 30 employees.
• Revenue is around $1.5M to $3M, depending on margins, production complexity, and growth rate.
• Revenue is growing at least 20% year over year, or headcount is increasing fast enough that onboarding and coordination are becoming harder.
• The company has clear growth goals for the next 12 to 24 months.
• Customer management is becoming harder, with more delivery delays, order changes, complaints, or manual follow-up.
• Production key performance indicators (KPIs) are unclear, late, or rebuilt by hand.
• Stock figures are close enough for accounting, but not reliable enough for daily decisions.
• New hires depend too much on what one experienced person remembers.

A manufacturer can reach the ERP question before 30 employees if the process is complex enough. A direct-to-consumer food brand with strict batch traceability, short shelf lives, subcontractors, and demand spikes may need structure earlier than a larger company with simple repeat production.

The reverse is also true. A 40-person company can sometimes wait if the business is stable, the product catalog is simple, and growth ambitions are modest.

The number matters less than the trend. If the company is growing fast and wants to keep growing, ERP becomes a serious topic earlier.

Growth is a positive trigger, not only a crisis response

Many SMEs wait until ERP becomes unavoidable; stock is wrong, orders are late, or production planning is rebuilt every morning. Finance asks for numbers the operations team cannot produce without three days of spreadsheet work. The ERP project starts because the business is already hurting.

That works, but it is an expensive way to learn. The healthier trigger is ambition. If the company wants to grow fast and well, ERP should enter the conversation before the current system collapses. Not because software creates strategy, but because a growing manufacturer needs a way to make its strategy operational.

Growth creates more of everything: more orders, more suppliers, more product variants, more stock locations, more quality checks, more customer promises, more people touching the same flow. Without a shared system, each increase adds coordination work.

At first, the team absorbs it. Then the work starts to land on a few people who quietly hold the business together. That is where ERP becomes less about administration and more about protecting the company's ability to grow.

L'Atelier du Ferment faced that exact moment as volumes doubled every year across four workshops. Production tracking, shelf-life management, cold storage constraints, purchasing, and batch traceability became too heavy to manage through Excel, Access, and paper. Bonx connected operations to Sidely and Pennylane, helped structure manufacturing and procurement, and supported full batch traceability as the company prepared for a factory three times larger.

The real trigger: operational truth starts fragmenting

The clearest sign that it is time to implement an ERP is not a revenue line. It is the moment your company no longer has one shared version of operational truth.

Sales has one view of the order. Production has another. Purchasing is working from a planning file. The warehouse trusts a stock export only after checking the shelf. Finance sees the result after the fact and asks why the margin moved. Customer service has to ask three people before answering a delivery question.

None of this means the team is disorganized. Often, it means the opposite. The team has been organized enough to keep the business running despite weak tools.

But when operational truth fragments, every decision gets slower:

• Can we accept this rush order?
• Do we have the material?
• Which batch should we use?
• What is blocking production?
• Which orders are at risk this week?
• Can we promise this delivery date?
• Are we making money on this product line?

If answering normal operational questions requires asking around, checking multiple files, or relying on the same person every time, the company has outgrown its informal system. That is an ERP trigger.

The spreadsheet ceiling

Spreadsheets are not the enemy. For many SMEs, they are the first operating system of the business. A good spreadsheet can carry planning, stock, purchasing, production follow-up, and reporting for longer than software vendors like to admit.

The problem is that spreadsheets age badly when operations become shared. A spreadsheet works while one person owns the logic, understands the exceptions, and updates it on time. It becomes fragile when five people need to use it, 12 people depend on it, and the company makes daily decisions from it.

Version control slips. Formulas break. Someone duplicates the file to test a change. Critical context moves into comments, messages, or someone's memory. The warning sign is not that spreadsheets exist. It is that the business is making daily decisions from tools that were never meant to carry that much operational risk.

Textile customization atelier LCS replaced paper work orders with real-time production tracking across five workshops. A single order could move through heat transfer, screen printing, embroidery, digital finishing, and sewing. With Bonx, manufacturing orders are generated automatically from confirmed quotes, each order is linked to a QR code scanned at every production stage, and LCS cut production errors by 95% while reducing paper usage by 90%.

Too early, preparing, or ready?

ERP is probably too early if production is stable, order volume is manageable, product variation is low, and the team can answer operational questions quickly from current tools. It may also be too early if leadership is not aligned on what the business is trying to become; ERP is not a substitute for strategic clarity.

Preparation often begins around 15 to 30 employees, or earlier if operations are complex. At this stage, the company may not need a full ERP live next month, but it should stop treating tooling as a side topic.

Good preparation looks practical:

• Map the order-to-delivery flow.
• Identify where information is re-entered.
• List the tools the team already uses.
• Clean product, bill of materials, supplier, stock, and customer data.
• Decide which processes are stable and which ones change often.
• Name an internal project owner who understands operations.
• Define the problems the ERP must solve first.

The goal is not to write a 90-page specification. The goal is to understand the company well enough to choose a system that fits the way it works and the way it wants to grow.

You should move from preparation to implementation when operational friction is no longer occasional. That point usually shows up through repeated symptoms:

• Delivery promises are becoming harder to keep.
• Production planning depends on manual reconstruction.
• Stock accuracy is no longer trusted.
• Purchasing reacts to shortages instead of anticipating them.
• Quality or traceability data is scattered.
• Operators record work on paper, then update tools later.
• Sales, production, and finance disagree about order status.
• Management cannot see performance without manual reporting.
• New hires learn the company through people rather than a clear system.

One or two of these issues may be normal growing pains. Several at once means the company is probably ready.

The timing becomes even clearer if growth is about to accelerate: a new product line, a new factory, a new sales channel, a major retailer, a fundraising round, a large customer contract, or a planned hiring wave. If the business is about to become more complex, implementing ERP after the complexity arrives may be too late.

A smaller company can still need an ERP

The 30-employee and $1.5M to $3M revenue range is useful, but real life is messier.

Féroce implemented Bonx in 42 days before a national TV appearance drove a tenfold order surge. At the time, the company had reached roughly $2M in revenue with only six people, but traceability depended heavily on the founder. Each order had to stay linked to the right batch, QR code, subcontractor flow, stock location, and shelf life. At 20 orders a day, that was manageable. At hundreds or thousands, it was not.

Féroce did not need ERP because it had a large headcount. It needed ERP because the operational promise of the brand could not remain manual at the next stage of growth.

Where Bonx fits

Bonx is an AI-native manufacturing ERP. For growing manufacturers, Bonx is relevant to the ERP timing question because it removes one of the reasons companies wait too long: the belief that ERP has to mean an 18-month project before value appears.

Bonx customers go live in 1 to 3 months, connect operations to tools already in the stack, and cover order management, inventory, purchasing and supplier management, planning, production, quality, and logistics. The goal is to create an operational system that fits how the company works and can keep changing after go-live.

Bonx works as a system of action rather than a passive system of record. Bonx AI agents can act on configured operational rules: generating manufacturing orders, suggesting procurement, prioritizing stock, and surfacing the exceptions humans actually need to decide. At L'Atelier du Ferment, for example, Bonx helps generate manufacturing orders and procurement suggestions based on sales, shelf life, and cold storage capacity.

That changes the timing conversation. If ERP means years of consulting, waiting until the company is desperate can feel rational. If ERP can be deployed in weeks and help the team act on growth instead of only recording it, the better move is to implement when the growth plan is clear and the operational signals are already visible.

The buying rule

Do not implement ERP because you crossed a symbolic employee threshold. Implement ERP when the company has clear growth objectives and the current way of running operations is starting to create risk: missed delivery promises, unreliable stock, unclear production performance, scattered traceability, manual reporting, and too much knowledge sitting in too few heads.

If you are below 30 employees but complexity is rising fast, start preparing. If you are above 30 employees and the business still depends on spreadsheets to answer basic operational questions, the ERP conversation is already legitimate. If revenue is around $1.5M to $3M and growth is serious, waiting for a more official threshold may only make the project harder.

The right time to implement an ERP is not when you have become "big enough." It is when the business is ready to grow beyond what informal coordination can carry.

FAQ on ERP timing

How many employees do you need before implementing an ERP?

For an industrial SME, the ERP question often becomes serious around 30 employees. A smaller company with complex production, traceability, subcontractors, or fast growth may need ERP earlier.

What revenue should a company reach before implementing an ERP?

A useful range is around $1.5M to $3M in annual revenue for many industrial SMEs, depending on margin, complexity, and growth rate.

Can an ERP be implemented too early?

Yes. ERP can be too early if operations are simple, growth plans are unclear, data is poor, and nobody inside the company can own the project.

What are the signs that ERP is already late?

ERP is probably late when stock cannot be trusted, production planning is rebuilt manually, delivery dates are slipping, traceability is scattered, operators work on paper before updating systems, and reporting depends on manual spreadsheet work.

Should a company implement ERP before a growth push?

Often, yes. If the company is preparing for a new factory, a new sales channel, a major customer, a product expansion, or a hiring wave, ERP should be considered before the added complexity lands.