How to Hire a Custom Manufacturing ERP Development Company for a Job Shop
Make every candidate whiteboard a lot split at operation 30 where four pieces enter a rework loop and eighteen continue. The right answer is a routing graph with lot genealogy.
On this page
Make every candidate whiteboard a lot split at operation 30 where four pieces enter a rework loop and eighteen continue. The right answer is a routing graph with lot genealogy. A focused first release covering routing, shop floor data collection and live job costing runs $60,000 to $130,000 over 12 to 16 weeks. Hire on the data model, never on the screens.
Commissioning an enterprise resource planning system is like ordering a fixture from a print with no tolerances on it. Something will be made. You just will not learn what until the first article comes back, and by then the tooling is cut and the money is spent.
The reason this category is hard to buy is that what decides success is invisible during selection. Every firm can show you a work order screen. The thing that determines whether your shop lives inside the system or keeps a highlighted dispatch list next to it is the schema, and a schema does not demo. Job shop work loops back after a failed inspection, splits into lots, merges again, and leaves the building for heat treat or plating. If routing is modelled as a numbered sequence, your team will create fake jobs and hand journal costs across them thirty times a month, and your work in progress number becomes fiction. That distinction is decided in week one by someone you have not yet met, so you have to interview for it.
What a manufacturing ERP team actually does
The dispatch screen is what you see. Four things underneath it carry the project.
Routing as a directed graph rather than a list, so a failed inspection spawns a rework path with its own operations and costs that roll back into the parent job, lot splits carry genealogy, and outside operations appear as routing steps with a linked purchase order, expected turn days and live vendor status instead of a disconnected order somebody chases by phone. Shop floor data collection treated as the product, not a screen: a barcode scan or a mounted tablet, clock on under ten seconds, no login gymnastics, because a ten click flow at a shared terminal across the aisle means operators batch entries from memory at shift end and your costing becomes an average of guesses. Costing that accrues per operation in real time, with burden rates living at the work centre level so a five axis machining centre stops subsidising the manual deburr bench in your margin reports. And traceability as the data spine, heat lot through every split, merge, rework and shipment, with certificates attached to the routing step that produced them, because an aerospace audit package should be an export rather than four days of digging.
What it really costs in 2026
These bands reflect Digital Heroes delivery experience across manufacturing and operations platforms.
| Project tier | Cost | Timeline |
|---|---|---|
| Paid discovery with a floor walk and a written specification | $8,000 to $20,000 | 3 to 4 weeks |
| Focused first release: routing graph, shop floor data collection, live job costing | $60,000 to $130,000 | 12 to 16 weeks |
| Full platform: quoting feedback loop, finite scheduling, purchasing, multi plant inventory, compliance | $150,000 to $400,000 | 6 to 12 months |
| Each additional plant rolled out after the first | $25,000 to $60,000 | 4 to 10 weeks |
| Care, changes and hosting per year | 15 to 20 percent of build | Ongoing |
Two costs are almost never in the quote. The first is the floor itself. Shop floor data collection assumes wireless coverage inside a steel building full of machines with variable frequency drives, and that coverage frequently does not exist. A site survey, access points, cabling, mounted enclosures and scanners is real money and real lead time, and it is not the software firm's line item unless you ask for it. Get it surveyed before you sign anything, because a costing engine nobody can clock into is worse than the spreadsheet it replaced.
The second is keeping the incumbent alive. You will want the old system read only for about a year so closed jobs, old quotes and historical routers stay searchable while the new system builds its own history. That means another maintenance renewal you had mentally cancelled. Budget it, and put the migration scope in writing: which tables come across, which stay behind as an archive, and who signs off that the mapping is right.
Signals of a strong partner
- They draw the routing graph unprompted. Rework paths, lot genealogy, and a question about whether your outside processes are per lot or per piece.
- They time a clock on flow from a previous project. Under ten seconds at the machine, and they know what share of transactions needed office correction.
- Burden is a question, not an assumption. They ask whether your rates should live at work centre level and what that does to your quoting history.
- Compliance comes up in week one. Aerospace quality system documentation and export controlled data segregation are architecture decisions, not modules.
- They ask what your estimator knows that nobody wrote down. A quoting engine that reaches back into actuals is the difference between a calculator and a feedback loop.
- They name your constraints. Operator skills matrix, fixture availability, real outside process lead times by vendor, rather than generic capacity.
- They phase the plants. One plant live and earning before the second starts.
Red flags
- They offer to add a status field for rework. That is a list pretending to be a graph and the interview should end there.
- They propose rebuilding your general ledger. The money belongs in routing, floor data and costing. Keep accounting where it is and sync to it.
- Compliance is a phase two module. Traceability and access control designed in month nine means rebuilding the data model you already paid for.
- Nobody asks to walk the floor. A firm that scopes a shop system from a conference room will design a shop system for a conference room.
- A big bang cutover across every plant. Big replacements fail far more often than phased builds, and a job shop cannot stop shipping while it happens.
Questions to ask on the first call
- Whiteboard a lot split at operation 30 where four pieces enter a rework loop and eighteen continue to final.
- Show me a clock on flow you shipped and let me time it on a phone.
- How does heat treat appear on the router, and what does the buyer see when the vendor is late.
- Where do burden rates live, and what happens to a quote written against a plant wide rate last year.
- Which finite capacity constraints have you actually modelled. Skills matrix, fixtures, vendor lead times.
- Show me an audit export and an export controlled access model from prior work.
- What comes out of our current system, what stays behind, and how long do we keep it read only.
- Who is surveying the shop floor for wireless coverage, and is it inside your number.
- Who owns the source, the repository and the cloud accounts, and is there any per seat or per plant licensing on our own system.
A simple way to decide
Do not choose from proposals and do not start with the whole suite. Buy a paid discovery phase from your two strongest candidates, three to four weeks each, including a walk of your floor at shift change. Require the same deliverable from both: a written specification covering the routing model with a worked rework example, the floor data capture design with a measured clock on target, the costing and burden approach, the migration scope, the compliance architecture and a phased plant sequence. You own that document whichever firm you pick, or neither.
Digital Heroes runs this way by default, with the client owning the source, the repository and the cloud accounts from the first commit and no per seat or per plant licensing on your own system. Contracting runs through India LLP, US LLC and UK LTD entities so the intellectual property assignment sits under law your own advisers already read. Then build for your two worst problems first, keep accounting where it is, and expand from something the floor already trusts.
Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- 48% of private companies cite integration with legacy systems or technical debt as a top obstacle to realizing the full value of their digital and AI investments (behind data quality/availability at 72% and gaps in AI fluency or technology talent/leadership at 53%). Source: Deloitte (2026) →
- Large companies globally have captured, on average, only 31% of the expected revenue lift and 25% of the expected cost savings from their digital and AI transformations - a significant gap between expected and realized value. Source: McKinsey & Company (2023) →
- Only 22% of firms are 'future ready' having significantly transformed digitally; these companies show average revenue growth 17.3 percentage points and net margins 14.0 percentage points above their industry average. Source: MIT Center for Information Systems Research (MIT Sloan) (2022) →
- The median annual wage for U.S. software developers was $133,080 in May 2024, and employment is projected to grow 15% from 2024 to 2034 - a core input to any in-house build-vs-buy TCO model. Source: U.S. Bureau of Labor Statistics (2024) →
Frequently asked questions
How much does it cost to hire a custom manufacturing ERP developer?
A focused first release covering the routing graph, shop floor data collection and live job costing runs $60,000 to $130,000 over 12 to 16 weeks. A full platform adding quoting, finite scheduling, purchasing, multi plant inventory and compliance runs $150,000 to $400,000 over 6 to 12 months. Each additional plant after the first adds $25,000 to $60,000, and yearly care runs 15 to 20 percent of the build.
What is the best test of whether a firm has built for job shops?
Ask them to whiteboard a lot split at operation 30 where four pieces enter a rework loop and eighteen continue. The right answer involves a routing graph and lot genealogy, with rework costs rolling back into the parent job. If you hear that they will add a status field, the interview is over, because a numbered sequence forces your team to create fake jobs and hand move costs.
What hidden cost do buyers miss on a shop floor system?
Wireless coverage. Shop floor data collection assumes a signal inside a steel building full of machines with variable frequency drives, and that coverage often does not exist. A survey, access points, cabling, mounted enclosures and scanners cost real money and carry lead time, and no software firm quotes it unless asked. A costing engine nobody can clock into is worse than the spreadsheet it was meant to replace.
Should the new system replace our accounting as well?
No. Keep the general ledger where it is and sync to it. The money belongs in the routing graph, the floor data capture and the costing engine, because that is where your shop is genuinely different from every other shop. Any firm proposing to rebuild accounting is proposing to spend your budget on the one part of the business that packaged software already handles well.
How long should we keep the old system running?
About a year, read only, so closed jobs, old quotes and historical routers stay searchable while the new system builds its own history. That means one more maintenance renewal you had probably planned to cancel, so budget it. Put the migration scope in writing too: which records come across, which stay behind as an archive, and who signs off that the mapping is correct before cutover.
We run everything on spreadsheets and Airtable. How do we know it's time for custom software?
The reliable signals are re-typing the same data into multiple tools, one employee acting as human middleware between systems, and errors appearing in handoffs between teams. Hard limits force the issue too: Airtable's Team plan caps at 50,000 records per base, and Business costs $45 per seat per month, so a 20-person team pays about $10,800 a year for a tool it has already outgrown. When workarounds consume more hours than the tools save, the spreadsheet era is over.
Should I pick Microsoft Dynamics 365 Business Central or build a custom ERP?
Pick Business Central if you already live in the Microsoft stack, your processes are close to standard, and around $80 per user per month for Business Central Essentials stays affordable at your headcount. Build custom when your revenue-driving workflow, such as custom manufacturing steps or unusual pricing logic, would need heavy extension work anyway. In our experience, once Dynamics customization quotes pass about $100,000 the custom option deserves a serious side-by-side.
Can custom software connect to the tools we already use, like QuickBooks, Stripe, and Google Workspace?
Yes, and connecting your existing tools is one of the main reasons to build custom: mainstream platforms like QuickBooks, Stripe, Shopify, and Google Workspace all publish documented APIs. Budget 1 to 3 weeks of work per integration depending on API quality and how much data flows in both directions. Ask any vendor whether they have integrated with your specific tools before, because quirks like QuickBooks' OAuth token handling and API rate limits get learned on someone's project, and it should not be yours.
What should I prepare before contacting an ERP development agency?
Bring a list of your current tools and spreadsheets, a rough map of how an order or job moves through the company today, your user count by role, and the three problems costing you the most hours. You do not need a formal specification; a good agency writes that with you during discovery. Companies that arrive with those four things typically cut two to three weeks off scoping in our experience.
How long does it take to build a custom web or mobile app from scratch?
Plan on 8 to 16 weeks for a focused first version and 4 to 9 months for a larger platform, which is the typical spread across Digital Heroes builds. The first 2 to 3 weeks go to discovery and design before any production code ships. The two things that stretch timelines most are integrations with legacy systems and slow feedback from your side, not developer speed.
How small can the first version of my software be and still be worth building?
One workflow, end to end, for one type of user: the single process that currently burns the most hours or loses the most money. In Digital Heroes delivery experience, first versions scoped to 6 to 10 weeks of build time ship, get used, and generate the feedback that makes version two obviously right, while 9-month first versions routinely launch with features nobody touches. Everything you cut from v1 gets cheaper to build later, because real usage reorders the roadmap for you.
How long does custom ERP development take?
Plan on 3 to 4 months for the first working module and 6 to 12 months for a full multi-module rollout. In Digital Heroes delivery experience the schedule risk is data migration and integration testing, not feature coding, so we stage go-lives module by module instead of one big-bang launch.
How many developers does it take to build an ERP?
A typical Digital Heroes ERP pod is five to seven people: two or three backend engineers, one frontend engineer, a QA engineer, a project manager, and a part-time architect and designer. Bigger teams rarely go faster on ERP because the bottleneck is decisions about your business rules, not typing speed. What you need on your side is one empowered internal owner who can answer process questions within a day.
Why do companies replace NetSuite with custom software?
The three reasons we hear most at Digital Heroes are per-user license growth, SuiteScript customizations that became fragile, and workflows the platform cannot model without workarounds. A company adding 50 users to NetSuite takes on roughly $59,000 per year in extra licenses at the commonly quoted $99 per user rate, which is often the moment the custom math starts winning. Replacements usually keep the accounting structure intact and migrate module by module.
What mistakes kill ERP projects most often?
The three we see most in rescue work at Digital Heroes: recreating the old system's broken process in new software, launching everything at once instead of module by module, and having no single internal owner with authority to decide. A fourth is skipping the parallel run on data migration to save two weeks, which trades a short delay for months of distrust in the numbers. None of these are technical failures, which is why vendor selection should weigh process discipline over demo polish.
Who can build a custom ERP software system?
Digital Heroes builds custom ERP software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other ERP software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
More from Harper.
Senior Account Director · APAC · Sydney · 2 posts on the site
Published · Last updated .
