Industry guide
Should a manufacturer buy manufacturing software or build a custom system?
Buy a manufacturing ERP such as Epicor Kinetic when you need finance, inventory and production in one system and your plant runs close to how the product expects. Build a custom system when the gap is one specific job, such as quoting, scheduling or shop floor tracking, because a product charges for the whole suite every year and the custom system is built once around that job.
| What you are comparing | A product | A custom build |
|---|---|---|
| Cost over five years | A subscription every year, plus implementation, data migration, training and the consulting needed to change it. Many manufacturing ERP vendors publish no price, so the five-year figure has to come from a quote. | A one-time build scoped in writing, then running costs such as hosting and the database. No licenses, so the total does not rise as the plant adds people. |
| Per-seat fees | It depends on the vendor. Business Central, Odoo and SAP publish per-user prices. Plex sells one subscription with unlimited users, and Acumatica prices by resources and not by seats. | None. Every operator, planner, estimator and manager can have a login at no added fee. |
| Fit to your process | You adopt the way the product models a quote, a job and a schedule, and configure the rest. Rules it cannot hold end up in spreadsheets beside it. | Built from your own travelers, costing rules and scheduling logic, including the parts that are particular to your plant. |
| Time to launch | An ERP rollout is a project with configuration, data migration and training before the plant can rely on it. A narrower tool can be in use sooner. | Starts with discovery and a written scope. Working screens are shown during the build, and the schedule is set in that scope. |
| What it replaces | Often the whole ERP, including the finance system, even when the problem was only on the production side. | Only the part that is not working. The ERP and the ledger you trust stay in place and the new system connects to them. |
| Who maintains it | The vendor maintains the product. A reseller or consultant usually maintains your configuration and any custom code. | Any competent developer, since Black Badger writes the code to be read and extended and sets up every account in your name. |
| Changes after launch | Limited to what the product and your plan expose. Larger changes go through the reseller or wait for the vendor. | Anything can change, because you own the code. Changes are scoped and built as the plant needs them. |
When buying manufacturing software is the right answer
Buy when you need a system of record for money, material and orders. Accounting, purchasing and inventory valuation work the same way in most companies, and an ERP has those solved. There is no reason to build them again.
Buy as well when your plant is close to what a product was designed for. A discrete make-to-order shop looking at an ERP specialized for that work, or a company in a sector that has its own industry suite, starts with a close fit.
When building a custom manufacturing system is the right answer
Build when one job in the plant has outgrown every product you have tried. The signs are an estimator with a workbook nobody else understands, a planner who rebuilds the schedule by hand each morning and operators writing counts on paper for later entry.
Those jobs are where a manufacturer differs from its competitors, which is why a product built for every plant fits them poorly. A system built from your own rules fits because it started there.
Build beside the ERP and leave the ERP in place
The most common design we build is not a replacement. The ERP stays as the record of customers, items, orders and the ledger. The custom system does the one job the ERP does badly and passes its results back.
That keeps the build small and the risk low. It also means the comparison is rarely a whole ERP against a whole custom system. It is usually an extra module, a second product or a consultant-led reconfiguration against a focused build.
How to compare the cost of manufacturing software with a custom build
Compare five years instead of the first-year quote. On the product side add the subscription, modules, implementation, training and the consulting you expect to pay for changes. Where the vendor publishes no price, ask for all of it in one quote.
The custom number is a one-time build plus running costs. Black Badger does not publish a price, because the figure depends on what the system has to do and which systems it must agree with. A written scope gives you the number to set beside the product total.
What a custom build involves, and how to ask about one
Questions buyers ask
Is custom software risky for a manufacturer?
Custom software used to be risky for a manufacturer because it depended on one developer. Black Badger answers that by creating every account in your name and writing code another developer can read and carry on. The risk that remains is scoping the wrong thing, which is what discovery is for.
Can a custom system connect to NetSuite, Odoo or another ERP?
Yes, a custom system can connect to an ERP. Most of what we build for manufacturers reads from and writes to an ERP that stays in place. The connection is named in the written scope, along with which system is the record for each kind of data.
Is a custom build cheaper than an ERP module?
A custom build is not always cheaper than an ERP module in the first year. The module adds a fee that repeats and often grows with users. A build is paid for once and then has running costs. The comparison usually turns toward the build as the years and the headcount add up.