Skip to content
§
§ · build vs buy

Steel Mill Production Software: Custom Build Versus Off the Shelf

Most mills should buy. A single line re-roller working to stock, or a mill under roughly 300 open orders at a time, gets further with SAP lot tracking plus PSI Metals than with anything custom.

Custom Software Development code editor and API illustration for Steel Mill Production Software Build vs Buy Guide.
The short answer

Most mills should buy. A single line re-roller working to stock, or a mill under roughly 300 open orders at a time, gets further with SAP lot tracking plus PSI Metals than with anything custom. Build when you cast, hot roll and cold roll in house, when level 2 systems come from three different suppliers, and when downgrades force re-application every shift.

What the off-the-shelf products actually do well

Coil 44821 is the whole argument, so start with who already solves part of it.

PSI Metals is the reference planning and production suite in this market and it deserves that position. It genuinely models order to material matching, applied inventory pools and re-application, which is the thing every generic system misses. If your mill has the appetite for a long implementation and a configuration model rather than a code model, PSI is the serious answer and we say that to mills regularly.

SAP, usually S/4HANA, is excellent at purchasing, finance, sales order administration and the batch level lot tracking that satisfies most auditors. It is blind between the caster and the shipping bay, which is not a defect, it is scope. Nobody should rebuild SAP.

Your level 2 systems from Primetals Technologies, SMS group and Danieli Automation are better at their own lines than anything you would write. They hold setup models, pass schedules, thermal history and process data at a resolution nobody else can match, and each supplier offers a layer above its own equipment that works well as far as that equipment reaches. AVEVA and Siemens sit in the manufacturing execution layer with an ISA-95, that is IEC 62264, model that is a reasonable starting shape for a plant.

If your operation is a single line re-roller buying hot band and shipping to stock, stop reading. An enterprise resource planning (ERP) system with lot tracking, one good spreadsheet and a disciplined planner will hold you for years, and a build is capital better spent on a leveller or a slitter.

Where they stop: material that changes identity on the way through

Steel is a divergent process with continuous re-identification. One heat becomes several slabs. One slab becomes a coil. One coil becomes child coils and then cut lengths. At every step the material can change grade, owner, destination and value. Standard manufacturing software models convergence and treats material as fungible against a part number. In your mill nothing is fungible, and that single mismatch is where generic products come apart.

The concrete case: a coil comes off the temper mill with an edge defect over the last eight tonnes. Quality downgrades it from an exposed automotive grade to commercial quality. It was applied to an order closing Thursday. Four questions now need answering inside an hour. Is there another coil in the applied pool that meets the specification. If not, does a slab exist that can be rolled in time. Can the downgraded coil serve another open order inside tolerance, or does it join secondary inventory ageing in the yard. And what do you tell the customer.

SAP will allocate a batch to a sales order. It will not tell you that the downgraded coil satisfies four other open lines inside thickness and width tolerance, one of which is late, and that applying it there beats a discount in secondary.

The second thing that stops them is genealogy across splits. Your customers want a mill test certificate under EN 10204 3.1 tying actual chemistry and mechanical results to the specific piece they received, and automotive and pressure vessel customers audit that chain without gentleness. A coil slit into four inherits from one heat, which is easy. A coil rolled from a transition slab in a mixed grade cast sequence inherits from two, which is not. Level 2 systems track the piece on their own line, and the joins between lines get reconstructed later from timestamps by somebody with database access and a free afternoon.

The arithmetic: named seats against a one-time build

Metals planning suites are licensed by module and by named user, with implementation quoted separately and measured in quarters. Put your own quote into this rather than ours.

Suppose the figure is $300 a named user a month. Forty seats across planning, scheduling, quality, metallurgy and shipping is $144,000 a year. Metals implementations are long enough that five years is the honest horizon, so that is $720,000 in licence alone, before implementation, before the annual maintenance percentage, and before the change requests that follow every practice change.

A first release build at $180,000 with $30,000 a year of support is $300,000 across the same five years. The crossover sits near 17 named seats at $300 a month, and near 34 seats if your quote lands closer to $150. Almost every integrated mill is well past that.

Transactions matter more than seats in one place. If a vendor prices by tonne shipped or by piece tracked, work out the fee at your annual tonnage and then at the tonnage in your five year plan. A fee that scales with output scales with the thing the mill exists to increase.

The number that does not appear on either side of that comparison is the one that usually decides it. Material sitting in secondary inventory for six months is capital you already spent, and continuous re-application is what releases it. One mill's answer to how many tonnes are ageing in the yard right now is a better business case than any licence comparison.

What a custom build actually costs

A first release runs $120,000 to $250,000 over 16 to 24 weeks. That covers the plant wide piece and event model, level 2 acquisition for the lines that matter most, order to material matching with continuous re-application, and genealogy with certificate generation.

A full platform adding caster and rolling campaign scheduling, the remaining lines, yield costing, secondary inventory and customer portal access runs $350,000 to $900,000 phased over 12 to 24 months.

Data migration is 10 to 25 percent of the build figure, and steel sits high in that band. You are not moving rows, you are reconstructing a genealogy graph from three level 2 databases whose piece identifiers disagree, and identifier reconciliation is the line item that surprises every mill. Year two costs 15 to 20 percent of the build annually, covering practice rule changes, new customer specifications, a level 2 upgrade you did not schedule, and the certificate format a new automotive customer insists on.

What drives the number up specifically here: the count of production lines and how many different level 2 suppliers are represented, because each acquisition integration is separate work. Whether piece identifiers are consistent across lines or need reconciling. Whether chemistry and mechanical test results arrive from a laboratory information system or from a spreadsheet. And whether customer specific tolerance envelopes exist as data anywhere, or only in a metallurgist's head.

The four situations where building wins

Regulatory and certification fit. If you certify under EN 10204 3.1 and 3.2, ship into automotive under IATF 16949 with production part approval evidence, or supply pressure vessel grades where the chain from heat to piece is audited, a genealogy graph you own is a compliance asset rather than a convenience. Append only event logs matter here, because a genealogy record that can be silently edited is worth nothing in an audit.

Scale economics. Past roughly 17 named seats on a per-user product, or past 300 open orders at a time, the licence arithmetic has already turned and the operational case is separate and larger.

A workflow that is your advantage. Practice rules are yours alone: which grades follow which on the caster without a tundish change, how wide a width jump the hot strip mill accepts in a campaign, which coating line campaigns run weekly. Hundreds of these rules exist as the knowledge of two or three schedulers. Encoding them as data that schedulers edit without a release is the feature operations directors underestimate at kickoff and value most a year later, because when a scheduler retires the mill keeps its sequencing logic.

Integration sprawl across three or more systems. Caster from one supplier, hot strip mill from another, galvanising line from a third means three data models, three timestamp conventions and three opinions about what a production event is. An acquisition layer per line normalising into one plant wide piece and event model is where a large share of the effort goes, and it is what makes everything else possible.

How to decide in a week

Do not run a vendor demonstration. Run this instead, using last month's real data.

Take every downgrade event from the last thirty days. For each one, reconstruct on paper what the best available re-application was at the moment quality made the call, and compare it to what actually happened. Then price the difference: tonnes that went to secondary at a discount when an open order inside tolerance existed, plus tonnes still ageing in the yard.

  • If the gap over thirty days is under the cost of two planner seats, buy the package and configure it properly.
  • If the reconstruction itself takes more than a day because the data lives in three level 2 systems, your first project is the acquisition layer, not the planner.
  • If you cannot produce a certificate for a coil rolled from a transition slab without a metallurgist rebuilding it, build the genealogy graph first.
  • If your schedulers cannot write down the practice rules in an afternoon, that knowledge is a single point of failure and it belongs in a system.

Then buy a paid discovery phase rather than accepting a proposal. At Digital Heroes that is two to three weeks producing a signed product requirements document covering the piece and event model, the level 2 interfaces line by line, the certificate templates and the acceptance criteria. You own that document either way, and you can tender it against three firms.

Where we are the wrong choice: if you want a configured metals suite with a vendor consultant on site for a year, PSI Metals is the better fit and we will say so on the call. We are a team of more than fifty specialists with over 2,000 projects delivered, verifiable on Clutch, Trustpilot, Fiverr Vetted Pro and by D-U-N-S number. Our own products, ShopScore, HeroCheckout and Section Vault, are commerce software, so judge us on delivered client work rather than on a metals product we do not sell. We hold India LLP, US LLC and UK LTD entities, so the intellectual property assigns under your own law. You meet the engineers who will do the work before you sign anything.

Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.

Research & sources

The evidence behind this guide

Independent findings on why this investment pays off. Every link goes to the primary source.

  1. Standish's 2015 CHAOS research found roughly a third of software projects (about 36% by the Modern definition) fully succeed on time, on budget, and on scope, with top success drivers including executive support, user involvement, and clear requirements/business objectives. Source: Standish Group (CHAOS Report) (2015) →
  2. McKinsey found that tech debt can amount to 20-40% of the value of a company's entire technology estate before depreciation, and CIOs report that 10-20% of the budget for new products is diverted to resolving tech-debt issues. Source: McKinsey & Company (2020) →
  3. 73% of surveyed businesses now use a headless architecture (up nearly 40% since 2019), and 98% of those not yet using it are evaluating or planning to evaluate headless within 12 months, with 82% saying it makes delivering consistent content easier. Source: WP Engine (2024) →
  4. An analysis of enrollment and completion data for 221 MOOCs (Katy Jordan, published in the International Review of Research in Open and Distributed Learning, IRRODL, 16(3), 2015 - not the Journal of Distance Education) found completion rates ranging from 0.7% to 52.1%, with a median completion rate of 12.6%, and completion negatively correlated with course length (longer courses had lower completion rates) - underscoring how unsupported self-paced online courses struggle to finish learners. Source: Journal of Distance Education (via ERIC / Katharina Jordan) (2015) →
FAQ

Frequently asked questions

How much does custom steel mill production software cost?

A first release covering the plant wide piece and event model, level 2 acquisition for your main lines, order to material matching with re-application, and genealogy with certificate generation runs $120,000 to $250,000 over 16 to 24 weeks. A full platform adding campaign scheduling, yield costing and secondary inventory runs $350,000 to $900,000 across 12 to 24 months. Add 10 to 25 percent for data migration.

How long before a build starts paying for itself in a mill?

Usually inside the first two quarters after the re-application loop goes live, because the saving is tonnage released from secondary inventory rather than headcount. The slower payback is on scheduling and yield costing, which need a year of clean data before the margin by grade and width band report tells you anything you did not already suspect. Sequence the re-application work first for that reason.

Who owns the code, and what happens to our level 2 interfaces?

You should own the repository, the cloud accounts and the interface code from the first commit, and it belongs in the contract. Level 2 interfaces deserve specific attention, because each one encodes an equipment supplier's message formats and identifier conventions. If a supplier upgrades a line, you want the right to change that adapter without asking anyone, and without a per-connector fee.

What happens if our level 2 supplier changes its data format?

You rewrite one adapter, which is a matter of days rather than a project, provided the build normalised readings into your own piece and event model rather than passing supplier structures through to the rest of the system. This is the main architectural reason to insist on an acquisition layer. Mills that let supplier formats reach the planning layer pay for the same upgrade three times.

Can we keep SAP and build only the production layer on top?

Yes, and that is the arrangement most integrated mills should aim for. SAP keeps purchasing, finance, sales orders and the batch record that satisfies your auditors. The build owns everything between the caster and the shipping bay: the piece graph, applied inventory, re-application, campaign sequencing and certificates. The interface is narrower than people expect, mostly order lines in and shipped pieces out.

Should a mini mill with one line build its own system?

No. A single line re-roller working to stock is the clearest buy case in this category. Lot tracking in your enterprise resource planning system plus a disciplined planner handles it, and the money is better spent on equipment. The build case starts when you cast, hot roll and cold roll in house, because that is when material changes identity often enough for re-application to matter.

What is the difference between a manufacturing execution system and this?

A manufacturing execution system, built on the ISA-95 model, is organised around work orders, operations and resources moving through a plant. A metals production system is organised around a material piece that splits, downgrades and gets re-applied to different orders. Generic execution systems can be bent toward that shape, but the bending is where the cost goes, and the result usually still treats material as fungible.

How do we keep mill test certificates defensible through splits?

Model every piece as a node with parents and children and record the transformation event between them, rather than copying attributes forward. Test results attach to the piece they were taken from and propagate to descendants with the propagation rule visible. Flag transition material from mixed grade cast sequences explicitly rather than assuming inheritance. Write the whole thing as an append only log so an auditor gets a real answer.

Can we phase this so the first release is affordable?

That is the recommended approach, and it is cheaper in total than scoping everything at once. Start with the piece and event model plus acquisition for the two lines that cause the most argument, then order to material matching, then genealogy and certificates. Campaign scheduling comes later, because good sequencing depends on a settled data model that only exists once production has run on it.

What are the alternatives to building if the budget is not there yet?

Three things help without a project. Get piece identifiers reconciled across your level 2 systems so a coil has one number across the plant, which is a data exercise rather than software. Write down the practice rules your schedulers hold in their heads. And run a manual weekly re-application review over downgraded material. Each of those makes a later build cheaper and improves things now.

What is a discovery phase, and is it worth paying for separately?

Pay for it, and treat the output as yours. A discovery phase runs two to three weeks, typically 5 to 10% of the eventual build budget, and produces a written scope, wireframes, and a fixed quote you can take to any vendor, including a competitor of the agency that wrote it. Skipping it is how projects end up quoted from a two-paragraph email and delivered at twice the price.

How long does it take from first call to software my team can actually use?

Plan for four to six months: two to three weeks of discovery, two to four weeks of design, then a 10 to 16 week build with testing. In Digital Heroes delivery experience the schedule killer is not engineering speed but decision lag; a client who takes two weeks to approve wireframes adds two weeks to launch. Book a weekly 30-minute decision slot before kickoff and most of that risk disappears.

Is it cheaper to customize Salesforce than to build a custom CRM from scratch?

If you use less than a third of what Salesforce does, a custom CRM is often cheaper by year three. Salesforce Enterprise lists at $165 per user per month, so 25 seats cost about $49,500 a year before admin and consultant fees, while a focused custom CRM runs $60,000 to $100,000 once plus 15 to 20% a year in maintenance. If you genuinely need Salesforce's ecosystem, reporting, and app marketplace, customizing it beats rebuilding it; the mistake is paying enterprise prices to use it as a glorified contact list.

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.

How much should a small business budget for its first custom app or website?

For a focused first build, most small businesses land between $8,000 and $60,000: roughly $8,000 to $45,000 for a custom website and $25,000 to $60,000 for an internal tool or simple web app, based on Digital Heroes delivery across 2,000+ projects. Customer-facing products with payments, logins, or a mobile app start around $40,000. Quotes far below these bands usually mean a template with your logo on it, not software shaped around your workflow.

Can I build my product on a no-code tool like Bubble instead of hiring developers?

For testing whether anyone wants the product, yes, and Bubble's paid plans start at $29 a month, which is the cheapest validation you will ever buy. The ceiling arrives with complex data relationships, heavy integrations, performance at a few thousand users, and the fact that you cannot export a Bubble app to servers you control. A path many Digital Heroes clients take: prove demand on no-code, then rebuild custom once revenue justifies it, treating the no-code version as a paid prototype rather than a foundation.

Who can build a custom software system?

Digital Heroes builds custom 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 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.

Keep reading

Published · Last updated .

Online now

Hi there. How can we help you today?

Reply