ERP Discovery for Small Businesses — Complete Guide

If you run a small manufacturing or distribution operation and you've been researching ERP systems, you've probably come across the concept of an "ERP discovery phase", and assumed it was something designed for companies much larger than yours. A months-long, consultant-heavy exercise that costs more than the software itself before anyone has written a line of configuration. Something for the enterprise crowd.

That assumption stops a lot of legitimate ERP projects before they start. And it's wrong.

ERP discovery for a 35-person job shop looks nothing like discovery for a 3,000-person manufacturer. The questions being answered are the same, how does your business actually work, what needs to change, what does the system need to do — but the scale, the timeline, and the cost are entirely different. Done right, discovery at the small business level can be completed in a matter of weeks, sometimes with minimal external cost, and it's the single most reliable way to make sure your implementation actually delivers what you need.

This article explains what ERP discovery involves at the small business scale, what it realistically costs, and how to figure out the right level of engagement for your situation.

Why Small Businesses Approach ERP Discovery Differently

Large enterprise discovery is a structured, multi-month exercise involving dozens of stakeholders, formal methodology frameworks, and significant consulting fees. For a small manufacturer or distributor, that model doesn't fit, and it doesn't need to.

But the purpose of discovery is identical regardless of company size: understand how the business actually operates before you try to change it. Skip that step, and you end up configuring a system around assumptions that turn out to be wrong, migrating data that wasn't ready to be migrated, and going live on a platform that doesn't match how your team actually works.

What makes discovery different at the small business scale is the context it happens in. The owner is often also the operations manager, the head of purchasing, and the person who knows where everything is. Processes run on institutional knowledge and informal routines rather than documented workflows. Budget and timeline tolerance is tighter. And the stakes are more personal — a failed ERP project at a 40-person shop isn't a line item writedown. It's a serious business event.

These factors don't make discovery less important for small businesses. They make getting it right more important, because there's less margin to absorb a project that goes sideways.

What Does ERP Discovery Actually Involve for a Small Business?

At its core, discovery for a small business is about answering four questions before implementation begins.

How does work actually flow today? 

This means tracing the path of a typical order from the moment it comes in to the moment it's invoiced: who touches it, in what system, in what sequence, and where it gets handed off between people or departments. Not how the process is supposed to work. How it actually works, including the workarounds and the things that only work because a specific person knows where to look. For a small manufacturer, this might take a single focused session. The goal is a snapshot of the worfklow in its current step.

What's broken, manual, or fragile?

 Every small business running on a patchwork of systems and spreadsheets has a list of these, even if it's never been written down. The quote that takes three hours because the estimator has to pull from four places. The inventory count that's always wrong by the time it reaches purchasing. The customer who calls because nobody can tell them when their order is shipping. These pain points are what the ERP is being asked to solve, and they need to be named explicitly before configuration begins, not discovered halfway through implementation.

What needs to work on day one versus what can wait? 

Small businesses often try to automate everything at once when they implement an ERP. It's an understandable impulse, and it's one of the most reliable ways to extend a project timeline and exhaust the team in the process.

Discovery forces a prioritization conversation: which processes are causing the most pain right now, which ones can run as-is for another six months, and what does a successful go-live actually look like? Getting alignment on that question before configuration starts is worth more than almost any other step.

What does your data look like and what condition is it in? 

Customer records, inventory lists, open orders, supplier data, historical job costs — whatever needs to move from your current systems into the new one. How complete is it? How consistent? Are there duplicates, blanks, or formatting inconsistencies that will cause problems in a new system? Data problems discovered during discovery cost a few days to address. Discovered on go-live day, they cost weeks of delays and erode confidence in the new system before it's had a fair chance.

For most small businesses, working through these four areas can be accomplished in two to three focused sessions with the right framework. It doesn't have to be a lengthy consulting engagement.

The 5 Questions Every Small Business Should Answer Before ERP Implementation

Discovery is ultimately about answering a specific set of questions before any software is touched. Here are the five that matter most:

1. What processes are we trying to fix, and in what order of priority? Not everything at once. Which pain points are costing the most time or margin right now?

   
   

2. What does our current data look like, and what needs to be cleaned before migration? An honest assessment here prevents the most common go-live disasters.

   
   

3. Who needs to be involved, and who has final decision-making authority? ERP touches every part of the business. Knowing who's in the room — and who isn't — before configuration begins prevents mid-project surprises.

   
   

4. What does success look like at 90 days post go-live? A concrete answer to this question keeps the project focused and gives everyone a shared target.

   
   

5. What is our realistic internal capacity to support this project alongside running the business? ERP implementations require time from the people who know the business best, the same people who are usually already stretched. Being honest about availability shapes the timeline and the level of external support needed.

   
   

If you can't answer all five of these confidently today, that's not a problem. It's exactly what discovery is for.

What Does ERP Discovery Cost for a Small Business?

This is the question most consultants avoid answering directly. Here's a straightforward breakdown:

Self-directed discovery carries low or no external cost. The investment is primarily internal time, typically 15–30 hours spread across the owner and one or two key staff members. This works well for businesses with a technically confident internal lead and relatively straightforward processes. Some consultants provide the framework and check-in support as part of a broader engagement at no separate charge.

Guided discovery typically runs $2,000–$8,000 depending on the depth of engagement and the consultant involved. It's often structured as a standalone phase before a full implementation contract is signed, which gives the business a clear picture of scope and cost before making a larger commitment.

Full managed discovery runs $8,000–$20,000 or more for complex situations, such as multiple sites, heavily manual or undocumented processes, significant data cleanup required. At the true small business scale, this level of engagement is rarely necessary.

The right way to think about this cost is relative to the alternative. An ERP implementation that goes sideways at a 40-person shop, because requirements were assumed rather than documented, or because data problems weren't caught until go-live, can easily cost $50,000 to $100,000 in wasted fees, rework, and lost productivity. Discovery is a modest investment against a significant risk.

One other thing worth knowing: some consultants offer discovery as a standalone engagement with a fixed fee, separate from the implementation contract. That structure protects you, it means you get a clear, documented scope before you're committed to a full project budget.

Should a Small Business Do ERP Discovery Themselves?

Sometimes, yes. A good consultant will help you figure out which situation you're in rather than defaulting to the most expensive option.

Self-directed discovery makes sense when the owner or a senior operations person has the time and capacity to lead it, the business has relatively straightforward and well-understood processes, and the implementation is lower complexity. For a single-site manufacturer with a clean product line and an engaged internal team, a structured self-assessment can be entirely sufficient.

Guided or full discovery makes more sense when processes are largely undocumented or heavily dependent on one person's knowledge, when there are multiple stakeholders with different priorities who need to get aligned, when the business has attempted an ERP project before without success, or when internal capacity to drive a structured project alongside day-to-day operations simply isn't there.

The important point is that having options at different levels doesn't mean choosing between doing discovery properly and doing it affordably. For small businesses, the right-sized engagement exists, it just takes a consultant willing to structure their practice around offering it.

What to Look for in an ERP Discovery Partner as a Small Business

Not every ERP consultant is set up to serve small businesses well. Four things matter more at this scale than at the enterprise level:

Experience with businesses your size. A consultant whose typical client is a 500-person company will bring processes, timelines, and expectations that don't translate to a 35-person shop. Ask specifically about their experience with businesses in your size range, and ask for references you can actually call.

Flexible engagement models. A consultant who only offers full-service discovery at a single price point is built for a different market than yours. Look for tiered or right-sized options that reflect what a small business actually needs.

Willingness to tell you what you don't need. The most reliable signal that a consultant is working in your interest is their willingness to say "you don't need a full engagement for this situation." That kind of honesty is rare and worth paying attention to.

Industry-specific context. If you're a manufacturer or distributor, a consultant who understands your operational environment, job costing, production orders, inventory management, distribution workflows, will ask better questions during discovery and catch things a generalist won't. Domain knowledge isn't a bonus at the discovery stage. It's what makes the requirements meaningful.

How A BC Consulting Runs ERP Discovery for Small Businesses

A BC Consulting's approach to discovery was built specifically for small and mid-sized manufacturers and distributors.

Our tiered model gives small businesses three genuine options based on internal capacity and project complexity:

Self-directed: A BC provides the structured framework, templates, and guided questions; the business drives the process internally, with consultant check-ins at key stages. Designed for businesses with an engaged internal lead and the capacity to own the process.

Guided: A BC works alongside the internal team through process mapping, requirements definition, and data assessment, bringing structure and expertise without taking over the project. The right fit for most small manufacturers and distributors.

Full-service: A BC manages the entire discovery engagement for businesses that don't have the internal bandwidth or want experienced guidance throughout. Appropriate for more complex situations or businesses that have been through a difficult implementation before.

All three paths produce the same output: a documented requirements blueprint and project roadmap that makes the implementation predictable, the scope defensible, and the investment well-understood before it's made.

A BC's team has spent enough time in manufacturing and distribution operations to understand the difference between how a business looks on paper and how it actually runs. That context shapes the questions they ask during discovery, and the quality of the blueprint they produce.

If you're a small manufacturer or distributor thinking through ERP and not sure where to start, a discovery conversation is the right first step.

The Bottom Line

ERP discovery isn't an enterprise luxury. For small manufacturers and distributors, a right-sized discovery process, whether self-directed, guided, or fully managed, is what separates an implementation that delivers from one that drains. The questions it answers are the same regardless of company size. At the small business scale, the difference is simply how efficiently you go about answering them. The tools and the frameworks exist to do this well without months of consulting time or an enterprise budget. The businesses that take that step are consistently the ones whose implementations go the way they hoped.