Skip to content
§
§ · build vs buy

Build vs Buy: Metallurgical Accounting and Mass Balance Software

Fix the sampling and calibration before you buy or build anything, because either will reconcile confidently around bad inputs. If your flowsheet is stable, licence a modelled plant product.

BI dashboard architecture and database illustration for Metallurgical Accounting Software Build vs Buy Guide.
The short answer

Fix the sampling and calibration before you buy or build anything, because either will reconcile confidently around bad inputs. If your flowsheet is stable, licence a modelled plant product. Build when circuit changes outpace a vendor maintained model, or when joining historian, laboratory and weightometer data is the real problem. A first circuit build runs $70,000 to $150,000.

Fix the measurement regime first, or nothing else counts

This category has a precondition that most buyer guides skip. Metal accounting software does not measure anything. It reads what your instruments and your laboratory report, and reconciles them. If the feed weightometer has not been calibrated this year, if the tails sampler has been reading low since the launder was modified, or if the concentrate moisture result routinely arrives days after the truck has gone, then any system you install will produce a precise wrong answer with a closed balance and a small unaccounted line, which is worse than an open argument because it looks settled.

So the first spend is not software. Get calibration current, verify the sample cutters, document the sampling protocol and confirm that composite samples are identified by the shift they describe rather than the day the laboratory looked at them. We have delayed projects a full quarter over exactly this and would do it again, because a reconciled balance built on a biased sampler simply moves the error somewhere harder to see.

Once that regime is credible, the software question becomes real, and it is a narrower question than vendors present. You are not buying accuracy. You are buying speed, traceability and the ability to attribute a discrepancy to an instrument while the circuit is still in the state that caused it. A monthly balance closed on the fifth is a post mortem. The same balance closed daily is a process control tool, and that difference is the entire business case.

When a purchased platform is genuinely the right call

Buy when your flowsheet is stable and your problem is presentation rather than reconciliation. Metallurgical Systems Metallurgical Intelligence is a serious product built precisely for modelled plant data with reconciliation on top, and for an operation whose circuit has not changed materially in years it will do the job well. Hexagon MineMarket earns its place from the other direction: if the pressing issue is stockpile accounting, shipment quality tracking and commercial contract management for a bulk commodity, MineMarket is stronger there than anything you would commission.

Buy, too, if you have nothing at all. A plant with no structured metal accounting will reach a defensible baseline faster with a commercial product than with a bespoke programme, because the product arrives with a modelling discipline your team would otherwise have to invent while also learning it.

And there is a scale below which none of this is worth the money. A small single stream plant where the superintendent closes a credible weekly balance in a workbook that he understands and could hand over does not need a platform. The workbook is not a failure, it is proportionate. What makes it a problem is not its format but its bus factor, and the cheaper fix there is documentation and a second trained person, not a procurement exercise.

The conditions that justify building your own balance

Three conditions push operations toward a custom build, and they compound.

  • Your circuit changes faster than a vendor maintained model. A modelled plant has to be built for your flowsheet, and that build is a services engagement. Add a scavenger row, move a sample point or change a reclaim arrangement and the change goes back through the same channel. Plants that modify circuits regularly find the model trails the actual plant by months, and a balance computed against a stale flowsheet is a balance nobody defends in a meeting.
  • The hard part is the join, not the arithmetic. The historian, the laboratory system and the belt scales each hold a piece of the truth, the pieces disagree, and no product ships knowing how your circuit resolves that disagreement. What weight you give a well calibrated weightometer against a tails sample everyone privately distrusts is a metallurgical judgement, and it should be yours to tune.
  • Your numbers leave the plant. Recovery feeds public production reporting, concentrate grade and moisture feed offtake settlement with the smelter or trader, and stockpile balances sit on the balance sheet. Once metal accounting is audited and disputed, you need reproducibility: which measurements, which adjustments, which version of the flowsheet model, approved by whom, with locked periods and restatement carrying a reason code. Aligning that governance to the AMIRA P754 code of practice costs very little at design time and is close to impossible to retrofit.

A build also gives you something a purchased balance rarely surfaces: the size of the adjustment applied to each instrument becomes a maintenance signal. When the tails sampler needs three times its usual correction for a fortnight, the system has told you the launder modification broke the sample before anyone loses an argument about it.

What each path costs, and the drivers that move it

A first release for one circuit runs $70,000 to $150,000 and ships in twelve to eighteen weeks. That covers ingestion from the historian, the laboratory system and the weightometers, a node based balance around your real flowsheet, weighted reconciliation with per instrument error bounds, moisture and stockpile adjustment handling, and a daily reconciled recovery number with the unaccounted line broken down rather than lumped.

The full build across multiple circuits, adding settlement reporting, restatement workflow, measurement quality monitoring and audit ready sign off, runs $180,000 to $400,000 across six to twelve months. Maintenance sits near fifteen to twenty percent of build cost, and much of that is model upkeep as the circuit evolves.

The costs that surprise people are not in the software. Historian work is the first: a shift tonnage is not a totaliser difference when the belt ran empty for forty minutes, so running status logic, interpolation behaviour and instrument health tags all need explicit handling, and the tag structure conversation is longer than anyone budgets. The second is the laboratory join, because results have to be placed by sample time rather than result time, and a laboratory database never designed to be read by another system adds weeks. The third is in circuit inventory, which in precious metal plants means mills, thickeners, leach tanks and load on carbon or resin, routinely ignored between surveys and routinely the largest source of apparent unaccounted metal. The fourth is your own metallurgists' time during error weighting workshops, which can consume a month if you let the debate run rather than accepting a first version and tuning it against real data.

Reconcile one quarter twice: the test that decides

Take a completed quarter where the unaccounted line moved sharply between months, because that is the quarter with something to learn from. Freeze the source data as it stood, including the assays that arrived late.

Then have three parties reproduce the balance. Your own team, timed honestly, in the current workbook. The vendor you are evaluating, using your flowsheet rather than their demonstration plant. And a development partner asked to build a node model for that one circuit and reconcile it. Compare four outputs: the closed balance itself, the per instrument adjustments each approach applied, how each handled the assays that landed after the month was reported, and how long the whole exercise took.

The most useful result is usually the adjustment profile, because it tells you which of your instruments the maths distrusts. Two things then become visible at once: whether the software can express your circuit, and which piece of hardware is quietly costing you recovery. Insist the exercise runs on your flowsheet. A vendor who asks you to simplify the circuit for the trial has already answered the build question for you.

Sequencing the work, and how to choose a partner

Sequence in this order. Calibration and sampling first. Then the node model for your single most important circuit, drawn on paper by your metallurgists before any developer sees it. Then ingestion, then reconciliation, then governance and reporting. Settlement views and multi circuit consolidation come last, because they are only defensible once the underlying balance is trusted.

When you interview developers, three questions separate the field. Ask how they handle disagreement between measurements: if the answer is that the system uses the most reliable source, they have not done metal accounting, and what you want to hear is error weighting and adjustment. Ask how a late assay is placed in time and how the already published day gets restated with an audit trail. Ask what they have actually pulled from a historian, naming the plant, the historian and the tag count, because aggregation over downtime is where accuracy is won or lost.

Digital Heroes works PRD first on this kind of build, so the node structure, the error weightings and the restatement policy are written and agreed with your metallurgical team before code exists. We are a fifty plus person team with 2,000 plus projects delivered, hold Fiverr Vetted Pro status, and publish our engineering work to 2.5 million subscribers on YouTube. Contracting through our India LLP, US LLC or UK LTD means the agreement sits in your jurisdiction, and you own the repository, the cloud accounts and the flowsheet model itself from the first commit, which matters because that model is your plant's accumulated judgement written down.

When you are ready to turn this into a specification, Digital Heroes contracts through India LLP, US LLC and UK LTD entities, so the agreement and the intellectual property assignment sit under law your own advisers already read. The document is yours whichever way you go.

Research & sources

The evidence behind this guide

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

  1. The right combination of digital transformation actions can unlock as much as US$1.25 trillion in additional market capitalization across Fortune 500 companies, while the wrong combinations put more than US$1.5 trillion at risk; companies with all three core factors (strategy, aligned technology, and change capability) saw a 5% market-value lift relative to peers. Source: Deloitte (2023) →
  2. 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) →
  3. In a February 2026 survey of 517 small-business employers, 82% had adopted at least one AI tool (typical firm uses five), 66% reported revenue increases linked to AI (22% reported gains exceeding 10%), and 74% said digital platforms make it easier to compete with larger firms; owners saved a median of 5 hours per week and businesses saved a median 11.5 employee-hours weekly. Source: Small Business & Entrepreneurship Council (SBE Council) (2026) →
  4. Across ten outpatient clinics the mean no-show rate was 18.8%, and the marginal cost of no-shows reached $14.58 million per year for those clinics, at roughly $196 per missed appointment (2008 figures). Source: BMC Health Services Research / PubMed Central (Kheirkhah et al.) (2015) →
FAQ

Frequently asked questions

How much does metallurgical accounting software cost to build?

A first release for one circuit runs $70,000 to $150,000 across twelve to eighteen weeks, covering historian, laboratory and weightometer ingestion, a node based balance on your flowsheet, weighted reconciliation, moisture and stockpile handling, and a daily reconciled recovery figure. Extending to multiple circuits with settlement reporting, restatement workflow and audit ready sign off runs $180,000 to $400,000 over six to twelve months. Precious metal plants sit at the higher end.

How long before the plant is closing a daily balance?

Twelve to eighteen weeks for one circuit, and the schedule is set by data access rather than development. Historian tag work, laboratory result mapping and agreeing initial error weightings usually consume the first third. Accept a first version of the weightings and tune them against real data instead of debating them in workshops, because that debate can add a month and the data settles the argument better than opinion does.

What happens to years of historical balances when we migrate?

Bring forward the raw measurements rather than the closed balances. Feed tonnages, assays with their sample times, moisture results, shipment records and survey data can all be reconciled again under the new model, which is more valuable than importing numbers whose derivation nobody can reconstruct. Expect gaps where assays were filed by result date, and treat any period predating a major circuit change as reportable but not comparable.

Does it need to integrate with our plant historian and laboratory system?

Yes, and the historian integration carries most of the accuracy risk. Tonnages, densities and flows come from it, but running status matters more than the totaliser, because a shift tonnage is not a simple difference when the belt ran empty. Laboratory results must join on sample identity and sample time so a composite assayed on Thursday lands on the Tuesday feed it actually describes.

Who should own the system inside the plant after go live?

Metallurgy, not information technology. The node model, the error weightings and the sampling protocol are metallurgical judgements that change when the circuit changes, and a system whose model is maintained by someone outside the process drifts away from the plant within a couple of modifications. Budget a named metallurgist with a few hours a week, plus a defined path for updating the flowsheet model when a circuit change is commissioned.

Who builds custom metal accounting systems for processing plants?

Firms comfortable with both industrial data and reconciliation mathematics, which is a narrow field. Digital Heroes is one option: fifty plus people, 2,000 plus projects delivered, working PRD first so the node structure, error weightings and restatement policy are agreed with your metallurgists before development. Contracting through India LLP, US LLC or UK LTD entities keeps the agreement and IP assignment in your own jurisdiction.

What makes Digital Heroes different from a generic development agency?

The first discussion is about which instruments you trust, not which charts you want. Generic teams treat conflicting measurements as a data quality problem to be picked between, rather than as a weighted reconciliation with adjustments that double as maintenance signals. Digital Heroes will also tell you to fix sampling before building, and clients own the repository, the cloud accounts and the flowsheet model definition from the first commit.

How do we check a development partner is legitimate before paying?

Verify the company before the capability. Ask for a D-U-N-S number and confirm the contracting entity is registered in the jurisdiction it claims. Read the Clutch profile for reviews attached to named clients and the Trustpilot profile for how they behave when something goes wrong. Then request a reference in industrial or process data work, and put code, data and infrastructure ownership into the contract before the first payment.

Why do agencies charge for a discovery phase instead of quoting for free?

Because an accurate quote requires real work: mapping your workflows, finding the edge cases, and writing a specification, which typically takes 1 to 3 weeks and costs $2,000 to $10,000 at Digital Heroes depending on system complexity. You leave discovery owning a written spec and a fixed price you can take to any vendor, so the money is not locked into one agency. Free estimates are guesses, and the guess usually becomes your budget overrun six months later.

When is it time to move from Excel reports to an actual dashboard?

The reliable signal is when someone spends more than a few hours a week copying data between spreadsheets, or when two teams arrive at a meeting with different numbers for the same metric. At that point the spreadsheet is acting as an unversioned, single-person database, and a costly error is a matter of time. A first dashboard that automates those recurring reports typically pays for itself in recovered hours within the first year.

Who owns the code when an agency builds my software?

You should, completely, through a written intellectual property assignment that transfers everything on final payment; without that clause, copyright stays with whoever wrote the code by default. Insist that the repository lives in your own GitHub organization from day one and that hosting, domains, and third-party accounts are registered to you. Also check for licenses to the agency's proprietary frameworks buried in the contract, because those can make switching vendors practically impossible even when you own your own code.

Does it matter which tech stack the agency wants to use?

Yes, but not in the way most buyers expect: the goal is boring, popular technology such as React, Node.js or Python, and PostgreSQL, because any future team can maintain it and hiring a replacement developer takes days, not months. The red flag is an agency-proprietary framework or an unusual language, which welds you to that one vendor no matter what your contract says about code ownership. A useful test: could you find three freelancers fluent in this stack within a week? If not, push back.

What are the most common mistakes companies make on dashboard projects?

The four we see most: designing charts before modeling the data, cramming 30 metrics onto one screen so nothing stands out, letting every team define revenue slightly differently, and skipping data quality checks so the dashboard confidently displays wrong numbers. The wrong-numbers failure is the fatal one, because a dashboard loses trust once and never fully earns it back. Spend the first weeks on metric definitions and data quality, not on colors.

How do I work out whether a custom dashboard will pay for itself?

Add up three numbers: hours of manual reporting it removes each month, license seats it replaces or avoids, and the value of one or two decisions it speeds up, like catching margin slippage a month earlier. Across Digital Heroes projects, internal dashboards typically pay back in 8 to 18 months, and customer-facing dashboards pay back faster when analytics is a paid feature or reduces churn. If the honest math does not clear payback within 2 years, buy an off-the-shelf tool instead.

What questions should I ask a development agency on the first call?

Ask who exactly will build it, what happens when scope changes mid-project, what their maintenance terms are after launch, and what they will need from you every week. Then ask them to describe a project that went wrong and what they changed afterward; teams that have shipped at real volume have war stories, and teams claiming a perfect record are hiding something. The scope-change answer matters most: a disciplined shop describes a written change-order process, not a vague promise to be flexible.

How many SaaS seats do we need before building custom becomes cheaper?

The crossover usually shows up between 20 and 50 seats on premium tiers. Salesforce Enterprise lists at $165 per user per month, so 40 users cost about $79,000 a year in subscriptions, which is real money against a custom system you would own outright. Run the comparison over three years: if subscription spend beats the build cost plus 15-20% annual maintenance, custom wins on price before you even count workflow fit.

Who can build a custom business intelligence dashboards system?

Digital Heroes builds custom business intelligence dashboards 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 business intelligence dashboards 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