If you run a mid-sized distribution, manufacturing, or logistics business, you’ve probably been told you need a custom ERP. Maybe by a consultant. Maybe by an agency that quoted you a six-figure rebuild. Maybe by a peer who just finished one. The truth is most companies who think they need a custom ERP actually need something simpler. The ERP isn’t the problem. The way the ERP talks to the rest of the stack is. Here’s how we tell the difference on consultations, and how you can run the same check yourself.
What is custom ERP software?
A custom ERP is software written from scratch to match how a single business actually runs. It replaces an off-the-shelf system like SAP, NetSuite, or Acumatica with a system that has every screen, every field, and every workflow shaped for the company that paid for it. The trade-off is cost and time. A custom rebuild typically takes nine to eighteen months and runs into six or seven figures. The off-the-shelf alternative installs in weeks and costs a fraction. Custom is the right call only when the off-the-shelf options can’t model the business without breaking.
When do you actually need custom?
In about four out of five consultations, we recommend against custom software. Here are the five questions that tell us when custom is the right move and when it isn’t.
1. Is the friction inside the ERP, or between the ERP and other tools?
If your team is copying data between the ERP and a separate CRM, separate inventory tool, separate accounting software, or a master Excel sheet, the friction is between systems. That’s an integration problem, not an ERP problem. Most companies we talk to have between four and eight tools that don’t talk to each other. The ERP gets blamed because it’s the biggest system, but the actual fix is connecting the existing tools.
2. Has anyone tried configuring the off-the-shelf ERP, or did they assume it couldn’t be done?
NetSuite, SAP Business One, and Acumatica are highly configurable. Most teams that say “off-the-shelf doesn’t fit our business” haven’t fully explored the configuration depth. If a configured off-the-shelf ERP would model 80% of your business, you don’t need custom. You need a configuration partner.
3. Are you building processes the off-the-shelf system can’t model, or just processes you’ve always done a certain way?
There’s a difference between “we operate in a way no off-the-shelf can handle” and “we operate in a way we’ve always done.” Sometimes the latter is genuinely a competitive advantage. Sometimes it’s an inherited workflow nobody has questioned in fifteen years. The consultation separates these two cases.
4. Is the system you’re replacing a Visual Basic, FoxPro, or Access database from before 2010?
If yes, you may need custom even if the workflows are standard. The technology itself is the problem. We’ve written about Visual FoxPro modernization and Visual Basic legacy rebuilds because both technologies have aged out and the developer pool is shrinking. In these cases the question isn’t whether you need a new system, it’s how to migrate without taking the business offline.
5. Do you have one person who holds the entire system together, and what happens if they leave?
Single-developer dependency is a key-person risk. If your CTO, your IT lead, or your one Visual FoxPro developer is the only person who can read the codebase, you have a continuity problem regardless of which technology the system runs on. Custom rebuilds solve this by producing documented, modern code that any senior developer can pick up.
The ERP isn’t the problem. The way the ERP talks to the rest of the stack is.
What does custom ERP cost?
Custom ERP costs have changed dramatically in the last two years.
Historically, going to a traditional software agency for a full ERP replacement ran $300,000 to $800,000 over twelve to eighteen months. That was the wall most mid-sized businesses ran into. The custom path was reserved for companies with deep budgets.
The wall has come down. With AI-assisted development, custom builds now land in the same range as configuring an off-the-shelf system through a value-added reseller. VAR-led off-the-shelf configuration typically runs $30,000 to $250,000 for setup, plus per-user licensing on top. Custom builds with AI-assisted development can land in that same $30,000 to $250,000 range.
What we’re seeing across the industry: businesses that would have defaulted to configured off-the-shelf five years ago are now considering custom, because the cost gap that made custom impossible has closed. The question is no longer “can we afford custom?” but “does our business actually need it?”
Common pitfalls to avoid
- Hiring a developer with no team behind them. A single experienced developer can absolutely build a custom ERP. The trap isn’t a single primary developer, it’s a single developer with no senior backstop, no code review, and no documentation discipline. That’s how you end up with the same key-person risk you started trying to escape. The right software firm gives you a primary developer plus the senior expertise behind them, the architecture review, and the documentation that means the code outlives any one person on the project.
- Letting scope creep during the build. Every “while we’re at it, can you also…” adds three weeks. The successful builds we’ve run scope tightly to phase one, ship that, then scope phase two from a position of working software instead of vapor.
- Skipping the data audit. Before any rebuild, secure the existing data. Our most common find on consultations is a database that hasn’t been backed up in years. Fix that before writing new code.
- Building before talking to the people who’ll use it. Department heads who own the screens know what’s broken better than anyone. Skip them and you’ll rebuild the same problems on a modern stack.
Common questions
How long does a custom ERP build typically take?
Most builds we run ship a working first phase in four to six months and complete the full rollout in twelve to eighteen months. Faster than that usually means scope is too narrow. Slower usually means scope is too wide.
What’s the difference between custom and configured ERP?
Configured ERP starts from an off-the-shelf platform (NetSuite, SAP, Acumatica) and adapts it to the business through configuration screens and light customization. Custom ERP is built from scratch with no underlying platform. Configured is faster and cheaper. Custom fits better when the business doesn’t match what the platforms assume.
Can we keep using our current ERP during the rebuild?
Yes. The rebuilds we run use a dual-system approach: the new system runs alongside the old one until the team is ready to switch over. There’s no flag day where everything has to work at once.
Who owns the code we pay for?
You do. Day one. Every Pilot West engagement transfers code ownership at the start, not at delivery. If you decide to bring the work in-house or change vendors, the code goes with you.
Custom ERP isn’t always the right answer. Most of the time it isn’t. If you’re trying to figure out whether it’s right for your business, our Custom Enterprise Software page covers the full picture, or you can book a free thirty-minute consultation and we’ll work through it together.
