Studios
For mid-sized manufacturers whose ERP was forced into a manufacturing shape it doesn’t naturally take. Where BOMs change weekly, the shop floor and the front office don’t share a language, and your team has built a layer of band-aid solutions just to keep the system functional.
The ERP was set up by someone who’s no longer at the company. Workarounds have piled up. Nobody understands why certain configurations exist, only that breaking them creates problems downstream.
Production schedules live in one place. Work orders live somewhere else. Costing comes together a week late, and only when somebody manually pulls it.
Different scopes, different teams, different processes inside one company. The ERP forces them all into the same workflow, which means none of them fit.
SAP Business ByDesign, older NetSuite tiers, niche manufacturing platforms — many of them are reaching end-of-support. You’re running your business on a clock you don’t control.
When the ERP doesn’t think the way manufacturing actually works, the right move is one of three: a different configured platform, integrations on top of what you have, or a custom rebuild. We’ll tell you which one fits.
In about four out of five consultations we run with manufacturers, we recommend against a custom rebuild. Sometimes the answer is migrating off a sunset platform to a modern configured one. Sometimes it’s integrations that connect the shop floor to the front office. Sometimes the ERP is fine and the actual problem is workflow design.
For the manufacturers where custom is genuinely the right move (multi-business-unit operations no off-the-shelf system models, niche production processes that resist configuration, or legacy systems built by someone who’s no longer reachable), we build incrementally. Production keeps running on the existing system while we ship the modern replacement section by section.
For the deeper service breakdown, see Custom Enterprise Software, ERP Software Integration, or Legacy Software System Modernization depending on which path fits.
Most of the manufacturing work we do isn’t named publicly because the businesses are mid-market and brand recognition isn’t the goal. The patterns are consistent though. A director of finance describing the system as “just a mess, band-aid solutions to things, and we’re always uh, from IT perspective, from GL perspective, everything doesn’t work on it.” A platform vendor announcing they’re sunsetting the version the company runs on. A team that has stopped trusting the reports because the underlying data is wrong.
If that sounds familiar, the path forward is the same as everywhere else: figure out what’s actually broken before deciding what to build.
SAP, NetSuite, and Dynamics are general-purpose ERPs with manufacturing modules. They work for many manufacturers. The trade-off is configuration cost. If your business’s production process, BOM structure, or multi-business-unit complexity doesn’t match what those platforms assume, you spend a lot on customization without ever quite fitting. Custom is the right call when the long-term cost of working around the platform exceeds the cost of building.
Three paths. Migrate to S/4 HANA Cloud (SAP’s recommended path). Migrate to a different configured ERP (NetSuite, Dynamics, Acumatica, Odoo). Or build custom if your operations don’t fit any of those well. The right answer depends on how much customization you’ve done in ByDesign and whether that customization is genuinely necessary or accumulated drift. We’ll work through it on the consultation call.
Yes. Most manufacturing engagements include integrations with shop-floor data capture (MES platforms, barcode scanners, IoT sensors), accounting, CRM, and supply-chain partners. Sometimes integration alone solves the problem and we don’t recommend a rebuild at all.
We ship the highest-impact section in four to six weeks. Full system replacement typically takes twelve to eighteen months depending on complexity. The new system runs alongside the existing one until each piece has migrated. Production never stops.
From day one. Every engagement transfers source code ownership at the start, not at delivery. If you ever decide to bring the work in-house or change vendors, the code goes with you.
A 30-minute call. We listen to how your operation actually runs, where the system fights you, and what your shop floor team has built workarounds for. If a configured platform or migration to a modern one solves it, we’ll tell you. If custom is the right move, we’ll explain why. Either way, you leave with a written summary, free to keep.