How Much Does Metallurgical Accounting Software Cost in 2026?
$70,000 to $400,000, and the decision that moves the number most is how many circuits the balance has to close around.
On this page
$70,000 to $400,000, and the decision that moves the number most is how many circuits the balance has to close around. One circuit with a single feed, a single concentrate and a single tailings stream is one node network with one error weighting set, and it lands in the lower band. Parallel circuits sharing a tailings system, a reclaim stream or a common regrind change the problem qualitatively, because metal moves between circuits and the balance can no longer be closed independently. One circuit runs $70,000 to $150,000 in 12 to 18 weeks. Multiple circuits with settlement reporting, restatement workflow and audit ready sign off runs $180,000 to $400,000 across 6 to 12 months.
The bands a metal accounting build falls into
The focused first release closes a daily balance for one circuit from data you already generate. Automated ingestion from the plant historian, the laboratory system and the weightometers, a node and stream model of your actual flowsheet, weighted reconciliation that adjusts each measurement inside its own error bounds, moisture and stockpile handling, and a daily reconciled recovery number with the unaccounted line broken down rather than lumped. That runs $70,000 to $150,000 and ships in 12 to 18 weeks in our delivery experience.
The full build adds further circuits, reconciled reporting into offtake settlement and production disclosure, provisional and final restatement with reason codes, locked periods and sign off, and a measurement quality regime that tracks instrument trust over time. That runs $180,000 to $400,000 phased across 6 to 12 months.
Below roughly $70,000 you get a dashboard on top of the same spreadsheet, which moves the closing date and nothing else. The floor exists because historian aggregation, sample time placement and error weighted reconciliation all have to be correct before a single recovery number is defensible, and none of the three is visible in a demo.
What drives a metal accounting build up
Circuit count is the first lever, and it is not linear. Two independent circuits are close to two node networks. Two circuits sharing tailings, reclaim or a regrind are a single larger network with cross flows, and the reconciliation has to solve them together. That distinction is worth settling before anyone quotes.
In circuit inventory is second, and it is why precious metal plants sit at the higher end. Load on carbon or resin, solution inventory in leach tanks and thickener beds, and mill charge are all real metal that moves between surveys, and they are the single largest source of apparent unaccounted loss in gold plants. Modelling them properly means survey events, interpolation between surveys and an explicit adjustment rather than absorbing the difference.
Laboratory data structure is third and is frequently the surprise. If your laboratory information system was never designed to be read by another system, or if it is a database somebody built in house, extracting sample identity and sample time reliably is real work.
Then governance. Locked periods, restatement with reason codes, no silent edits and reproducible published figures aligned to the AMIRA P754 code of practice cost very little at design time and are close to impossible to retrofit.
What keeps the number down
One circuit, one commodity, and a decision to accept the first version of the error weighting and tune it against real data. The temptation is to settle the trust weightings in workshops before anything is built. In our delivery experience four weeks of live adjustment data settles the argument faster and more honestly than four workshops, because the instruments themselves reveal which ones drift.
Fix the measurement regime first rather than budgeting around it. If the feed weightometer is out of calibration and the tails sampler is known to be biased, the software will reconcile confidently around bad inputs and produce a precise wrong answer. We have delayed projects by a quarter for exactly this, and it saved the client money.
Use the existing historian and laboratory system as they are. Nothing here requires replacing either, and the value comes from joining them rather than from consolidating them.
Defer settlement reporting until the plant balance is trusted. The commercial team will want it early, and building it on numbers the metallurgy team has not yet accepted creates two versions of the truth inside one project.
A worked example that adds up
A single circuit copper concentrator, one feed weightometer, composite samplers on feed, concentrate and tails, a fire assay laboratory with a weekend backlog, and a monthly balance closed in a workbook. Here is the focused first release priced line by line.
- Historian ingestion covering tonnages, densities and flows with running status aware aggregation, so a shift tonnage is not a totaliser difference when the belt ran empty: $22,000
- Laboratory ingestion keyed on sample identity and sample time, with provisional and final results and a change trail when a composite is rerun: $18,000
- Weightometer and shipment ingestion with calibration date, check weight results and drift visible on the same screen as the balance: $14,000
- Node and stream model of the flowsheet with mass, moisture and assay by element per stream, each carrying an assumed error: $20,000
- Weighted reconciliation engine producing per measurement adjustments and an attributed unaccounted line rather than a residual: $26,000
- Moisture delay handling, stockpile surveyed against calculated balance, restatement, and the daily reconciled report: $16,000
That totals $116,000, mid band for one circuit. The reconciliation engine is the largest line because it is the only part that turns three disagreeing data sources into a defensible number, and it is also what produces the maintenance signal that pays for the project.
How the spend phases
Discovery and a measurement audit come first, usually two to three weeks and about a tenth of the budget. The output is a flowsheet with named nodes and sample points, a current calibration status per instrument, and an honest error assumption per measurement written down and signed by the metallurgy team. A developer quoting before that document exists is quoting against a plant they have not seen.
Ingestion and the node model take the largest block, close to half the spend. Build them together, because a reconciliation engine cannot be tested without real data placed correctly in time, and correct time placement is the part most likely to be wrong.
The remainder covers reconciliation, moisture, stockpiles and a parallel period. Run the workbook and the system in parallel for one full month and compare closed balances. The disagreements are the point. In our delivery experience they usually trace to assays placed by result date in the spreadsheet rather than by sample time, which means the historical recoveries everyone has been quoting were quietly shifted whenever the laboratory fell behind.
The ongoing costs nobody quotes
Model maintenance is the permanent line and it is a metallurgical task rather than a software one. Circuits change. A scavenger row is added, a sample point moves, a regrind is installed, and the node model has to change with it. Someone in the technical team owns that, and the system should let them do it without a change request.
Plan 15 to 20 percent of the build cost per year across hosting, monitoring, integration maintenance and small enhancements. Historian tag structures get reorganised, laboratory systems get upgraded, and both land on your ingestion.
Error weighting review is an annual habit. Instrument trust should be revisited against a year of adjustment data, because an instrument that has been reliably adjusted downward every month is telling you something that a fixed weighting will hide.
Then audit support. Metal accounting numbers get disputed by offtake counterparties and examined by auditors, so producing the evidence pack for a period is a recurring task even when the system makes it easy. Budget the time rather than assuming automation removes it.
Comparing a build against your current renewal
The comparison here is rarely licence against licence, because what most operations are actually replacing is a workbook and a person. Price it against the delay instead.
Count the days between a shift ending and its recovery being known with confidence, then ask what decisions are made in that window. Grind size changes, reagent trials and blend decisions all happen inside a month, and a balance that closes on the fifth of the following month cannot inform any of them. That is the value: not a cheaper report, but recoveries that can be acted on while the circuit is still in the same condition.
Then price the disputes. Payable metal is settled against concentrate weight, moisture and assays, and the situation where the commercial team and the plant quote different tonnes for the same shipment is common and expensive. A single reconciled source removes that class of argument.
Be honest about the other side. A build takes 12 to 18 weeks, adds a maintenance line, and needs a metallurgist who owns the model. And it will not improve a bad measurement regime, it will only make its faults visible.
When buying beats building
If you run a small single stream plant where the superintendent already closes a credible weekly balance in a workbook he understands and can hand over, do not build. The delay is short, the flowsheet is simple, and the money is better spent on sampling and calibration.
If your problem is commercial rather than metallurgical, meaning stockpile management, shipments, quality tracking and contract management for a bulk commodity, buy Hexagon MineMarket. That is what it is for, and it does the job without you building a sales and logistics system from scratch.
If you want a modelled plant with reconciled data on top and your flowsheet is stable, Metallurgical Systems Metallurgical Intelligence is a serious product in this space and belongs on the shortlist. Test one thing in the evaluation: how a circuit modification, such as adding a scavenger row or moving a sample point, gets reflected, and how long that takes. Plants that modify circuits frequently should price that answer carefully.
The build case is specific. Your balance is closed monthly in a spreadsheet and the causes are gone by the time you see the number. Unaccounted losses are a figure nobody can attribute. Your flowsheet changes often enough that a vendor maintained model would trail the plant. Or metal accounting feeds public production reporting and offtake settlement, so reproducibility and sign off are governance requirements rather than conveniences. Two or more of those and building pays.
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.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- SaaS spend averaged $4,830 per employee (up 21.9% year over year), with large enterprises (10,000+ employees) spending roughly $284M annually and running about 660 apps, while organizations wasted an average of $21M annually on unused licenses. Source: Zylo (2025) →
- Nucleus Research's analysis of published analytics deployment case studies found business intelligence and analytics returned an average of $13.01 in benefits for every dollar spent, up from $10.66 three years earlier. Source: Nucleus Research (2014) →
- Brandon Hall Group research on onboarding reports that done well, structured onboarding drives measurable gains in new-hire productivity, employee engagement, and retention; the page notes 41% of organizations experience greater than 5% turnover among new hires. Source: Brandon Hall Group (2024) →
- WordPress powers 41.5% of all websites and holds 59.2% of the market among sites running a known content management system, making it by far the most-used CMS on the web. Source: W3Techs (2026) →
Frequently asked questions
How much does custom metallurgical accounting software cost in total?
A first release for one circuit runs $70,000 to $150,000 over 12 to 18 weeks in Digital Heroes delivery experience, covering historian, laboratory and weightometer ingestion, a node based balance around your flowsheet, moisture and stockpile handling and a daily reconciled recovery number. Extending to multiple circuits with settlement reporting, restatement workflow and audit ready sign off runs $180,000 to $400,000 over 6 to 12 months.
Precious metal plants sit at the higher end because in circuit inventory on carbon or resin has to be modelled explicitly rather than absorbed.
What does it cost to run each year?
Plan 15 to 20 percent of the build cost annually across hosting, monitoring, integration maintenance and small enhancements. Historian tag structures get reorganised and laboratory systems get upgraded, and both changes land on your ingestion layer.
Two lines are specific to this work. Model maintenance is a metallurgical task, because circuits change and the node model must change with them. And error weightings should be reviewed annually against a year of adjustment data, since an instrument adjusted the same way every month is telling you something a fixed weighting hides.
How long does it take to build a metal accounting system?
Twelve to 18 weeks to a first release for one circuit, then one full month running in parallel with your existing workbook before you rely on it. Compare closed balances line by line during that month, because the disagreements are the most valuable output of the whole project.
Multiple circuits, settlement reporting and audit ready sign off phase over 6 to 12 months. If your sampling and calibration need work, add that time at the front rather than building around it.
Is Metallurgical Intelligence or MineMarket cheaper than building?
Both are real products and either can be the right answer. MineMarket is strong on the commercial side, meaning stockpiles, shipments, quality tracking and contract management, and if that is your problem you should not build a sales and logistics system yourself.
Metallurgical Intelligence gives you a modelled plant with reconciliation on top. Test one thing in evaluation: how a circuit modification such as an added scavenger row or a moved sample point gets reflected in the model, and how long that takes. If your plant modifies circuits regularly, price that answer carefully against a build where your own team owns the model definition.
Why do parallel circuits cost so much more than one?
Because they usually are not independent. Two circuits sharing a tailings system, a reclaim stream or a common regrind form a single larger node network with cross flows, so the balances cannot be closed separately and the reconciliation has to solve them together.
If your circuits genuinely are independent, the cost is closer to additive than multiplicative. Settle which situation you are in before anyone quotes, because it is the difference between the two bands.
What is the cheapest useful version we could build?
Ingestion from the three sources plus a daily balance for one circuit, with assays placed by sample time and the unaccounted line shown against each measurement's adjustment. No settlement reporting, no restatement workflow, no measurement quality dashboards.
Scoped that way it sits near the bottom of the $70,000 to $150,000 band and it delivers the whole point, which is a recovery number available the day after the shift rather than five weeks later when the circuit has changed and there is no experiment left to run.
Should we fix our sampling and calibration before we build?
Usually yes, and we have delayed projects by a quarter over it. If the feed weightometer is out of calibration and the tails sampler is known to be biased, the reconciliation will close confidently around bad inputs and hand you a precise wrong answer with more authority than the spreadsheet had.
Get calibration current, verify the sample cutters and document the sampling protocol first. The system then earns its keep by keeping that regime honest, because instrument trust weightings and adjustment tracking make drift visible instead of arguable.
Does it need to align with AMIRA P754?
Most operations align to it, and building the sign off and lock down workflow to match costs very little at design time. That means locked periods, restatement with reason codes, no silent edits, and every published figure reproducible from the measurements, adjustments and flowsheet version behind it.
Retrofitting that governance onto a finished system is close to impossible, which is why it belongs in the first release even though nobody asks for it in a demo. Auditors and offtake counterparties both eventually will.
How do we justify the cost to the general manager?
Do not lead with a cheaper report. Lead with the delay. Count the days between a shift ending and its recovery being known with confidence, then list the decisions made inside that window: grind size changes, reagent trials, blend calls. A balance closing on the fifth of the following month cannot inform any of them.
Then add the settlement argument. Payable metal is settled against concentrate weight, moisture and assays, and the situation where the commercial team and the plant quote different tonnes for the same shipment is common. One reconciled source removes that class of dispute entirely.
Why do BI dashboard quotes range from $25k to $200k for what sounds like the same project?
Four variables move the price: how many data sources you connect and how messy they are, real-time versus daily refresh, permission complexity, and whether outside customers will log in. A three-source internal dashboard with daily refresh sits near the bottom of that range, while a customer-facing product with row-level security and live data sits near the top. Wildly different quotes are usually pricing different assumptions about those four things, so pin them down in writing before comparing.
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.
How do I vet an agency or developer for a BI dashboard project?
Ask them to walk you through the data model of a past project, not a portfolio of pretty charts, because dashboard failures are almost always data modeling failures. Good answers mention specifics like star schemas, dbt, incremental refresh, and how they handled a source schema change after launch. Then ask for a fixed-scope discovery phase with a written data audit as the deliverable, so you judge their real work for a small spend before committing to the build.
Is Tableau worth $75 per user per month, or should we build our own dashboard?
If you have analysts who explore data visually all day, Tableau Creator at $75 per user per month earns its price, and Viewer seats at $15 keep the total reasonable for a small team. The math flips once you have hundreds of viewers or need dashboards inside a customer-facing product, because per-seat pricing scales with your audience while a custom build does not. Run the 3-year seat cost before deciding; that horizon usually makes the answer obvious.
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.
What happens to my software if the agency shuts down or we stop working together?
Nothing dramatic, if the engagement was set up correctly: the code sits in your repository, hosting runs on your cloud account, and a handover document explains how to deploy and operate the system. Any competent replacement team can then take over in days rather than months. If the agency controls the repo, the servers, or the domain, fix that now, because renegotiating access during a dispute is the most expensive place to discover the problem.
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.
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.
Related guides
More from Ria.
Hydrogen & Headless Lead · Delhi · 3 posts on the site
Published · Last updated .
