How to Hire a Metallurgical Accounting Software Company
Judge candidates on one answer: what they do when the weightometer, the lab and the tails sampler disagree. A firm that says it will use the most reliable source has never closed a mass balance.
On this page
Judge candidates on one answer: what they do when the weightometer, the lab and the tails sampler disagree. A firm that says it will use the most reliable source has never closed a mass balance. Expect $70,000 to $150,000 and 12 to 18 weeks for a first release covering one circuit, and fix your sampling and calibration before you spend anything, because software reconciles confidently around bad inputs.
Choosing a metal accounting partner is itself a sampling problem. You take a small cut of a large stream, a proposal, a demo, two reference calls chosen by the vendor, and you assume the cut represents the whole. It rarely does. The part of the work that decides your recovery number, how a late assay is placed in time and how a drifting instrument is weighted, is not visible in any demo, and by the time it shows up in your balance the circuit has been through a grind change and two liner changes.
This category is hard to buy because the deliverable is a number that gets audited, disputed and paid against. Recovery drives production disclosure. Concentrate grade and moisture drive offtake settlement with the smelter. Stockpile balances sit on the balance sheet. A vendor who builds a competent dashboard has built you a reporting chore. What you need is an engine that reconciles measurements which all carry error, and produces the same figure again next year when someone asks you to reproduce it.
What a metal accounting build actually involves
The flowsheet has to become data rather than a picture on the wall. Nodes, streams and measurement points defined explicitly, so a balance is computed around real nodes instead of assembled by hand in columns each month.
Every measured value carries a source, a timestamp and an assumed error. That last field is what makes reconciliation possible: around any node, mass in should equal mass out and metal in should equal metal out, and in a real plant neither does. The correct treatment adjusts each measurement inside its own error bounds until the balance closes, weighting a freshly calibrated belt scale far above a tails sampler everyone privately distrusts. The size of the adjustment on each instrument is then the most useful maintenance signal your metallurgy team gets all year.
Then the parts that make it your plant rather than a textbook. Moisture handling with the real delay between shipping a wet tonne and receiving the oven dry result. Stockpile accounting that separates surveyed volume from calculated balance and carries the difference explicitly. Provisional versus final assays with an audit trail of every rerun. In circuit inventory for mills, thickeners, leach tanks and load on carbon or resin, which is the largest single source of apparent unaccounted metal in gold plants and is routinely ignored between surveys.
And governance, because these numbers get audited. Locked periods, restatement with reason codes, no silent edits, and a published figure that can be reproduced from the measurements, adjustments and model version behind it.
What it really costs in 2026
These bands reflect Digital Heroes delivery experience on plant data and reconciliation systems.
| Scope | Cost | Timeline |
|---|---|---|
| Reporting layer over an existing balance: ingestion, daily view, variance tracking | $40,000 to $80,000 | 8 to 12 weeks |
| First release, one circuit: historian, laboratory and weightometer ingestion, node model, weighted reconciliation, daily recovery | $70,000 to $150,000 | 12 to 18 weeks |
| Full build: multiple circuits, settlement reporting, restatement workflow, measurement quality monitoring, audit ready sign off | $180,000 to $400,000 | 6 to 12 months |
| Each additional circuit or commodity stream | $25,000 to $60,000 | 4 to 8 weeks each |
Two items disappear from most quotes. The first is historian work. Proposals price it as one integration line, but the accuracy is won or lost in running status logic and aggregation, because a shift tonnage is not a totaliser difference when the belt ran empty for forty minutes. Tag mapping, interpolation behaviour and instrument health handling are the bulk of that effort and they are rarely itemised.
The second is the sign off and lock down workflow. Most operations align to the AMIRA P754 code of practice, and building period locking, approval and restatement to match it costs very little at design time. Retrofitting it after the engine exists is close to a rewrite, so a quote that leaves it to phase two is quietly deferring the expensive half.
Signals of a strong partner
- They talk about error before they talk about screens. The first real design conversation should be which instruments you trust and by how much, not dashboard layout.
- They place results by sample time, not result time. A composite assayed on Thursday describes Tuesday's feed, and any system that files by result date is quietly wrong every time the lab falls behind.
- They name the historian and the tag structures they have handled. AVEVA PI or a Wonderware system, with a real tag count and a story about downtime aggregation.
- They ask about in circuit inventory unprompted. Load on carbon, mill and thickener contents, and how often you survey them. A partner who skips this will hand you an unaccounted line you still cannot explain.
- They will tell you to fix sampling first. A firm willing to delay its own project over an uncalibrated feed scale is telling you something useful about how it works.
- They design restatement as a normal event. Provisional then final is the standard path, and it needs reason codes and an audit trail, not a manual overwrite.
- They connect the balance to settlement. The tonnes and assays that close your plant balance are the same ones that decide payable metal, so commercial and plant should not quote different numbers.
Red flags
- They plan to pick the most reliable measurement. That is subtraction with extra steps. Reconciliation means adjusting every input within its error bounds until the balance closes.
- The model definition would live in their system. Your node structure and error weightings are your metallurgical team's judgement written down, and every circuit change becomes a change request if you cannot open them.
- No mention of locked periods or restatement. It means the design assumes numbers never change, which is not how a plant with a laboratory works.
- Moisture treated as a single field. Wet tonnes ship days before the oven dry result lands. If that delay is not modelled, every shipment restates the wrong way.
- A promise to close the balance without touching your instruments. Software can expose measurement quality. It cannot make a drifting weightometer honest, and anyone implying otherwise is selling precision, not accuracy.
Questions to ask on the first call
- Around a flotation node, mass in does not equal mass out. What does your system do next, in specific terms?
- How do you assign and maintain an assumed error for each measurement, and who is allowed to change it?
- A fire assay result lands four days late. Where does it get placed, and what happens to the balance already published?
- Which historian have you pulled from, how many tags, and how do you compute a shift tonnage when the belt ran empty?
- How do you model in circuit inventory between surveys, including load on carbon or resin?
- How does the system handle a stockpile where the survey volume and the calculated balance disagree?
- What does your sign off and period lock workflow look like, and how does it align with AMIRA P754?
- Show me how a published recovery figure from eighteen months ago is reproduced, including the model version used.
- Who owns the code, the flowsheet model definition and the cloud accounts from day one?
A simple way to decide
Do not pick from proposals. Buy a paid discovery phase, two to four weeks, priced separately, and require one deliverable: a written specification covering the node model for your flowsheet, the measurement inventory with initial error weightings, the ingestion design for historian, laboratory and weightometer sources, the restatement and sign off workflow, and a fixed price for the first release on one circuit.
Make the specification yours regardless of who builds. It is also useful on its own, because the exercise of writing down every measurement point and how much you trust it usually surfaces two or three instruments nobody had defended in years. Some operations take that document, fix the sampling it exposes, and start a quarter later.
Digital Heroes runs PRD first for this reason and hands over the repository and infrastructure accounts from the first commit, contracting through India LLP, US LLC and UK LTD entities so the intellectual property assigns under the buyer's own law. The record is checkable through D-U-N-S, Clutch and Trustpilot.
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.
- 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) →
- An independent Forrester Total Economic Impact study of OutSystems found a 363% three-year ROI with payback in under 6 months, illustrating that faster, lower-labor build approaches can materially shift the payback math. Source: Forrester Consulting (commissioned by OutSystems) (2024) →
- 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) →
- McKinsey emphasizes that most L&D functions still fail to tie training to business outcomes, recommending organizations track 2-3 business-relevant indicators (such as time-to-proficiency, redeployment into priority roles, or frontline productivity) rather than participation metrics to demonstrate training effectiveness. Source: McKinsey & Company (2025) →
Frequently asked questions
How much does custom metallurgical accounting software cost?
A first release for one circuit runs $70,000 to $150,000 over 12 to 18 weeks, 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, settlement reporting, restatement workflow and audit ready sign off runs $180,000 to $400,000 over 6 to 12 months. Each additional circuit adds $25,000 to $60,000.
What question exposes a vendor who has never done metal accounting?
Ask what happens when the weightometer, the lab and the tails sampler disagree around a node. If the answer is that the system uses the most reliable source, they are describing subtraction. The correct answer involves weighted reconciliation, adjusting each measurement within its own assumed error until the balance closes, and treating the size of each adjustment as a maintenance signal about which instrument is drifting.
Should we fix our sampling before commissioning the software?
Usually yes. 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 that is harder to argue with than the spreadsheet was. Get calibration current, verify the sample cutters and document the protocol first. A partner willing to delay the project for that reason is worth keeping.
What does most quotes leave out of a metal accounting build?
Historian work and governance. Proposals price historian access as one integration line, but running status logic, aggregation over downtime, interpolation and instrument health handling are where the accuracy lives. Sign off, period locking and restatement aligned to AMIRA P754 also get deferred to phase two, which is a problem because retrofitting an audit trail and immutable published figures onto a finished engine is close to a rewrite.
Who should own the flowsheet model and the code?
You should own the repository, the cloud accounts and the model definition itself, agreed in writing before kickoff. The node structure and the error weightings are your metallurgical team's accumulated judgement in machine readable form, and if they sit inside a vendor system every circuit modification becomes a change request rather than an afternoon of configuration. Confirm you can hire a different firm to continue the work.
How much does a custom BI dashboard cost for a small business?
For a small business, a focused first dashboard typically runs $25,000 to $60,000 when it covers 2 or 3 data sources, daily refresh, and 5 to 7 core metrics. Across 2,000+ Digital Heroes projects, budgets climb past that only when real-time data, complex permissions, or customer-facing access enters the scope. If a quote for a simple internal dashboard exceeds $75,000, ask exactly which of those three is pushing it there.
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.
When does Looker make more sense than a custom dashboard?
Looker earns its place when multiple teams keep producing conflicting numbers and you need one governed definition of every metric, because LookML enforces definitions centrally. Its pricing is quote-based, and the quotes clients bring to Digital Heroes typically start in the tens of thousands of dollars per year. Under roughly 50 users with straightforward reporting needs, that spend is hard to justify against Power BI or a scoped custom build.
We already pay for Microsoft 365. When does building custom actually beat Power BI?
Keep Power BI for internal reporting; at $14 per user per month for Pro it is hard to beat for employee-facing analytics. Custom wins in three cases: you are showing dashboards to customers, since embedded Power BI is priced on capacity and gets expensive fast, you need a fully white-labeled experience inside your own product, or your team keeps fighting the tool to support a specific workflow. Most companies we build for keep Power BI internally even after launching a custom customer-facing dashboard.
How do I vet a software development agency before signing a contract?
Ask to speak with two past clients whose projects resemble yours in size and industry, and ask exactly who will write your code, since some agencies sell senior faces and deliver junior or subcontracted hands. Demand a written specification with acceptance criteria before any fixed price, and check that their portfolio links to products that are actually live. An instant quote given without questions about your workflows is the clearest warning sign there is.
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 many people does it take to build a custom BI dashboard?
A typical build runs with 3 or 4 people: a data engineer for pipelines and modeling, a full-stack developer for the application and charts, a part-time designer, and a project lead. One strong freelancer can handle a single-source internal dashboard, but in our experience solo builds stall once multiple integrations, permissions, and customer access are added. Team size matters less than having one person explicitly own the data model.
What should the first version of a dashboard include, and what can wait?
Version one should answer 5 to 7 questions your team already asks every week, pull from your 2 or 3 most important data sources, and refresh daily. Real-time data, custom report builders, scheduled email exports, and write-back features can all wait for version two. Across our projects, teams that launch a narrow version one reach a dashboard people actually use roughly twice as fast as teams that try to cover every department at once.
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.
Can we migrate years of data out of our current system into new custom software?
Almost always yes, through CSV exports or the vendor's API, and migration should be scoped as its own workstream with field mapping, a dry run, and a planned cutover window rather than an afterthought. The real time sink is rarely moving the data; it is cleaning it, since years of duplicates, free-text fields, and inconsistent formats surface all at once. Pull a full export from your current vendor before committing to anything new, because some SaaS plans restrict exports on lower tiers.
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.
How do I make sure each client sees only their own data in a shared dashboard?
That is row-level security, and it must be enforced in the database or API layer, never by hiding filters in the interface. Each query carries the logged-in client's identity, and the data layer refuses to return rows outside their account, so a crafted URL or modified request cannot leak another client's numbers. Make any vendor show you exactly where that filter lives, because interface-level filtering is the most common security mistake we find when auditing dashboards built elsewhere.
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 Mahira.
Lead UI/UX Designer · Lucknow · 1 post on the site
Published · Last updated .
