Revenue Architecture for Mining Tech Software — The Complete Operator Guide in 2027

What a mining tech revenue engine actually is, and why the shape is unusual

Most B2B software revenue architecture assumes a long tail. You segment by employee count or revenue band, you assume thousands of addressable logos in each tier, and you staff a funnel that converts strangers into pipeline at some predictable rate. Mining technology violates that assumption at the first step. The global mining industry concentrates capital spending into a very small number of operators — the majors like BHP, Rio Tinto, Glencore, Vale, Anglo American, Freeport-McMoRan, Newmont, and Barrick each run multi-billion-dollar capital programs, and roughly the top 35 producers account for the large majority of global mining capex. That single fact reshapes every downstream decision: how you segment, how you comp, how you forecast, and what "coverage" even means.

The practical consequence is that a mining tech vendor is not really running a funnel at the top tier. It is running a small number of multi-year enterprise relationships, each of which behaves more like an account-based program than a sales pipeline. A Strategic Enterprise AE covering one to three named majors is not prospecting; they are mapping a buying committee across corporate, regional, and site levels, and they are timing their proposals to capex approval windows they do not control. Meanwhile the mid-tier — producers roughly in the $500M to $10B revenue range, of which there are several hundred globally — behaves more like conventional enterprise software, with territory AEs carrying 15–25 accounts. Below that, junior miners and single-asset operators number in the thousands and can be covered by inside sellers running shorter, more transactional motions.

The buying committee is also unusual. In most software categories you sell to a functional executive and a finance approver. In mining you are typically working a Chief Mining Officer or VP of Operations, a COO, a Chief Mine Planner or head of technical services, a maintenance or asset management leader, and increasingly an ESG or sustainability director whose sign-off has become non-optional after the industry's high-profile tailings and heritage-site failures. Add a technical services group that will run its own evaluation of geological modeling accuracy, and you have five to seven distinct veto holders. Each one has a different definition of proof. The mine planner wants block model fidelity; the maintenance leader wants mean-time-between-failure improvement; the ESG director wants auditability against frameworks like the ICMM Global Industry Standard on Tailings Management.

Two adjacent realities are worth holding in view because they shape the same architecture. First, the OEMs are not just competitors — they are the installed base. Caterpillar's MineStar, Komatsu's Modular Mining, Sandvik's digital mining portfolio, Hexagon's mining division, and Epiroc's technology business all sell software attached to the iron already on site. Second, the specialist planning and geoscience vendors — Deswik, Datamine, Maptek, and Seequent (now part of Bentley Systems) — prove that best-of-breed depth in a single workflow can sustain a substantial standalone business. Your architecture has to pick a lane between "bundled with the fleet" and "deep enough that the mine planner refuses to give it up," because those two lanes require different comp plans, different technical staffing, and different renewal defenses.

The step-by-step process from first contact to multi-mine rollout

The sequence below is what a disciplined mining tech deal looks like end to end. Skipping steps does not accelerate the cycle; it just moves the failure later, usually into implementation.

Step one — tier routing at the lead level. Every inbound or outbound contact gets routed by producer size and asset count before an AE touches it. A junior explorer with two drill programs and a mid-tier producer with eleven operating pits require different first calls. Route to Strategic AE, territory AE, or inside AE within one business day; misrouting a major into an inside queue is the most common self-inflicted wound in this category.

Step two — operations scoping, not discovery. Standard SaaS discovery questions land badly here. The productive version is a site-level operations assessment run jointly by the AE and a solutions architect who has actual mining engineering background. You are documenting pit design workflow, current block model tooling, fleet dispatch system, dispatcher headcount, haul cycle times, and where reconciliation between plan and actual currently breaks. That document becomes the business case and later the implementation scope.

Step three — a scoped pilot on real assets. Mining buyers do not accept sandbox demos as proof. Expect a pilot on one or two operating mines running six to twelve months at enterprise scale, three to six months in mid-market. Define the success metric before the pilot starts and make it operational, not technical: reconciliation variance reduction, haul cycle time improvement, unplanned downtime hours avoided, or planning cycle time cut from weeks to days.

Step four — procurement, legal, and board-level approval. Large mining capital and technology commitments frequently need board or executive committee sign-off, and the contract will carry indemnification language reflecting safety-critical use. Multi-year terms are normal and desirable; they insulate you from the commodity cycle.

Step five — implementation and phased site rollout. This is where mining tech diverges most sharply from horizontal software. A signed enterprise agreement is the beginning of a 12–24 month per-site rollout. Each mine has its own geology, its own fleet mix, its own dispatch conventions, and often its own local regulatory regime. Staffing an implementation manager per major account is not optional overhead; under-resourcing here is the single largest driver of year-two churn.

Costs, timelines, and the pricing bands that hold up

Pricing in mining technology has converged on a per-mine base plus per-asset metering plus module add-ons. The per-mine base reflects that a mine site is the natural unit of deployment. Per-asset metering — per haul truck, per drill, per shovel — reflects that fleet-oriented modules scale with equipment count, not headcount. Module add-ons cover geological modeling, planning and scheduling, fleet dispatch, predictive maintenance, ESG and tailings monitoring, and safety systems.

Realistic annual contract value bands look roughly like this. Exploration and geological modeling tooling for a junior or single-asset operator lands in the low-to-mid six figures per site. A mid-market suite combining planning, scheduling, and basic fleet management runs materially higher per site, typically several hundred thousand annually. Full enterprise deployments spanning mine-to-mill optimization, fleet dispatch, IoT and condition monitoring, and ESG reporting reach seven figures per site at large copper, gold, and iron ore operations. Multi-site enterprise agreements at a major stack to several million in annual contract value once four or five mines are live.

Timelines are the harder number to internalize. Budget 9–24 months from first qualified conversation to signature at a major. Mid-market runs 6–12 months. Junior and single-asset deals close in 3–6 months. Two structural forces drive the enterprise end: capital approval cycles are annual or semiannual and rarely flexible, and commodity price movements can freeze a decision that was otherwise ready. A copper or iron ore price drawdown of a third does not merely delay a deal — it can cause the entire technology line item to be deferred to the following capital cycle.

Coverage ratios should reflect that timing. Strategic accounts need roughly 5x pipeline coverage measured on a rolling eight-quarter basis, because a four-quarter view simply cannot see a deal that started eighteen months ago and will close six months from now. Mid-market can run 4x on a rolling six quarters. Inside can run 3.5x on rolling three. Win rates settle around 20–25% at the top tier, 30% in mid-market, and 40% for junior deals, and the top-tier number is lower not because the product loses but because a meaningful share of evaluations end in "no decision this capital cycle."

Compensation follows the cycle length. Strategic Enterprise AEs in this category typically carry OTE in the high three hundreds to mid four hundreds of thousands with a 50/50 split and a $1.5–2.2M quota; the aggressive base weighting is necessary because a rep can go three quarters without a close through no fault of their own. Mid-market territory AEs sit around $235–275K OTE at 60/40 against roughly $775K–$1.0M. Inside AEs run $155–185K at 65/35 against $500–650K. Solutions architects with genuine mining engineering credentials command $285–325K at 80/20 — they are frequently the most decisive hire in the entire org and should be comped like it. Commodity specialists covering copper, gold, iron ore, coal, lithium, nickel, or uranium sit around $245–285K at 65/35. Ramp is long: 18–24 months to full productivity at the enterprise tier, roughly 12 months mid-market, 8 months inside.

Accelerators should be generous above plan — 1.5x to quota and 3x above 125% is a reasonable structure — but the more important design choice is *not* decelerating below 75%. Cycle drag in this category is largely outside rep control, and punishing a rep for a deferred capital cycle drives your best mining-literate sellers out the door. Where a clawback does belong is on year-one implementation failure, because it aligns the AE with honest scoping rather than optimistic scoping.

Where mining tech revenue teams get it wrong

Treating OEM bundling as a pricing problem. When Caterpillar or Komatsu or Sandvik packages software with equipment, the instinct is to discount. That is usually the wrong response, because you cannot win a bundle war against a company whose software is a rounding error on a fleet purchase. The durable responses are architectural: be genuinely OEM-agnostic so a mixed fleet of Komatsu, Caterpillar, Hitachi, and Liebherr equipment can run on one orchestration layer, or be so deep in a specific workflow — geological modeling, mine planning, scheduling — that the technical services team treats you as non-substitutable. Deswik and Seequent built substantial businesses on exactly that depth.

Forecasting on a four-quarter view. A rolling four-quarter pipeline model structurally cannot see an eighteen-month enterprise cycle. Teams that keep the standard SaaS forecast cadence end up with a top tier that appears to have no pipeline for the first year and then produces "surprise" deals. Move to rolling eight quarters at the enterprise tier and instrument the leading indicators that actually predict movement: announced capital programs, new mine commissioning schedules, executive turnover in operations, and regulatory deadlines around tailings and disclosure.

Underweighting the ESG and safety veto. A decade of catastrophic industry failures — tailings dam collapses, heritage-site destruction — has permanently elevated ESG governance in mining decision-making. If your ESG, tailings monitoring, and community engagement capabilities are a bolt-on afterthought, you will lose deals in a late-stage review you did not know was happening. Treat auditability and reporting alignment as a core platform requirement, not a module you sell later.

Hiring generalist sellers and generalist SEs. Copper, gold, iron ore, coal, lithium, nickel, and uranium operations differ in process flow, regulatory regime, capital profile, and buyer psychology. A seller who cannot distinguish a heap leach operation from a flotation circuit will be politely dismissed by a technical services group. The fix is commodity specialization on the overlay side and ex-mining-engineer solutions architects on the technical side. This is the single highest-leverage staffing decision in the model.

Selling the enterprise agreement and under-resourcing the rollout. The contract is signed and the rollout takes two years across eleven sites. If you have one implementation manager spread across three majors, sites three through eleven get a degraded experience, the internal champion loses credibility, and your renewal conversation starts from a defensive position. Gross retention in this category should sit at 96% or better precisely because switching is so painful — if yours is lower, the cause is almost always implementation capacity, not product gaps.

Missing the renewal risk signals. Operations leadership turnover within eighteen months of signature is the strongest churn predictor in the category. A major safety incident at a customer site should trigger immediate executive engagement, not a scheduled QBR. A sustained commodity price collapse compresses the customer's entire discretionary spend and should move the account to watch status well before the renewal date.

Decision framework: which architecture to build, and when

The choice that determines everything else is positioning relative to the OEMs. There are three viable postures, and they are not equally available to every vendor.

Best-of-breed depth. Pick one workflow — geological modeling, mine planning and scheduling, reconciliation — and be measurably better at it than anything bundled. This works when you can demonstrate a technical result that a mine planner or chief geologist can verify on their own data. Comp accordingly: solutions architects matter more than SDRs, pilots matter more than demos, and your win rate at the top tier will be higher than category average even though your ACV per site is lower.

OEM-agnostic orchestration. Sell the layer that works across mixed fleets. Autonomous haulage adoption has grown substantially over the past several years, led by Komatsu's FrontRunner and Caterpillar's MineStar Command, and most large operators run heterogeneous fleets they do not want to homogenize. This posture requires heavy integration engineering and a longer technical sale, but it produces the stickiest enterprise relationships and the highest expansion ceiling.

OEM channel partnership. Rather than fighting the bundle, become part of it. This trades margin and control for distribution and shortens the enterprise cycle considerably. It suits vendors whose capability is complementary rather than competitive, and it changes your revenue architecture substantially: fewer strategic AEs, a real alliances function, and comp weighted toward partner-sourced deals.

The second decision is where to concentrate coverage. If your ACV at a major exceeds roughly ten times your mid-market ACV, concentrating senior talent on the top 35 is correct even though the cycle is brutal. If the gap is smaller, the mid-tier's several hundred producers offer better revenue per seller because the cycle is half as long and the buying committee is half as wide. Run that math annually, not once at founding.

Adjacent categories that borrow the same playbook

Mining tech is not alone in this shape, and the comparison is useful when you are hiring leaders from outside the category. Oil and gas upstream software, utility grid management, heavy construction technology, and rail operations software all share the defining traits: extreme buyer concentration, capital-cycle-gated purchasing, safety-critical deployment, and OEM incumbents with bundled offerings. A revenue leader who has run any of those categories will adapt faster than a leader from a horizontal SaaS background, regardless of how impressive the horizontal numbers were.

The upstream effect worth tracking is commodity demand shifting toward battery and energy transition minerals. Lithium, nickel, cobalt, and copper are on different capital trajectories than thermal coal, and a vendor whose commodity specialist coverage mirrors 2015 production mix will be underweight where the capital is actually moving. Refresh commodity coverage annually against announced capital programs, not against your existing customer base — your customer base tells you where the money *was*.

The downstream effect is the processing and metallurgy layer. Mine-to-mill optimization only pays off when the plant side is instrumented too, which means your expansion path frequently runs through a different buyer — the metallurgical manager or plant superintendent — who was not in your original committee. Vendors that map that second committee early expand faster, because the mill-side business case is often easier to quantify than the pit-side one.

Net revenue retention in the category should target 108–115% with gross retention at 96% or better. The expansion math is straightforward: new mines commissioned into an existing agreement, fleet and autonomy module attach, IoT and predictive maintenance attach, and ESG and tailings module attach. Pay for each explicitly. A per-new-mine SPIFF shared between the CSM and the AE is the cleanest mechanism, because it rewards the two people who actually influence whether a new site adopts the platform or runs a competing evaluation.

Related questions

How many sellers does a $100M mining tech vendor need?

Fewer than a horizontal SaaS company at the same revenue. Concentrated buyers mean roughly 10–15 quota carriers total: 4–6 strategic AEs on named majors, 5–8 mid-market territory AEs, and a small inside team. Overlay roles — solutions architects and commodity specialists — often outnumber closers.

What is the right RevOps ratio in mining tech?

Roughly one RevOps FTE per $15M ARR, denser than typical SaaS, because deal complexity, multi-year contract structures, per-asset billing, and rolling eight-quarter cohort modeling all demand analytical support that a self-serve dashboard cannot provide.

Should mining tech vendors run a PLG motion?

Rarely at the enterprise tier — safety-critical operational software does not get adopted bottom-up. A limited free tier can work for geological modeling and exploration tooling aimed at junior miners and consultants, where individual geologists genuinely evaluate software themselves.

How do you forecast through a commodity downturn?

Shift the value narrative from growth to cost per tonne, extend contract terms to insulate against single-year capex cuts, and reweight coverage toward mid-tier producers whose capital decisions are less board-gated than the majors'.

What is the most common first bad hire?

A VP of Sales from horizontal SaaS who tries to install a four-quarter forecast cadence and a high-velocity SDR motion. Both fail against an 18-month capital cycle and a seven-person technical buying committee.

FAQ

What is a realistic enterprise sales cycle in mining technology?

Nine to twenty-four months from first qualified conversation to signature at a major producer, six to twelve months in the mid-tier, and three to six months for junior and single-asset operators. The enterprise variance is driven almost entirely by capital approval timing rather than by evaluation speed, which is why compressing "the sales process" rarely compresses the actual cycle.

Why is gross retention expected to be so high in this category?

Switching operational mining software is genuinely dangerous. Block models, planning workflows, dispatch logic, and safety systems are woven into daily production, and a migration risks both output and safety performance. That stickiness sets a high bar — gross retention below 96% usually signals an implementation or support failure rather than competitive loss.

How should commodity specialists be organized?

One specialist per major commodity family, covering copper, gold, iron ore, coal, lithium, nickel, and uranium as coverage justifies. They function as overlays supporting both strategic and mid-market AEs, comped around $245–285K at a 65/35 split, with quota credit shared rather than owned so they cooperate with territory reps instead of competing.

Does the autonomous mining transition help or hurt an independent vendor?

Both. It expands the addressable software spend considerably, but the autonomy layer itself is dominated by the equipment OEMs. The independent opportunity sits in orchestration across mixed fleets, in the planning and reconciliation layers that autonomy depends on, and in analytics that OEM systems expose but do not interpret well.

What should trigger executive escalation on an existing account?

Operations leadership turnover within eighteen months of signature, any major safety incident at a customer site, a sustained commodity price decline that compresses the customer's capital program, and any stalled site rollout where a scheduled deployment slips more than two quarters. Each of those predicts renewal risk far earlier than usage metrics do.

How do you build a business case a mining COO will actually sign?

Denominate everything in cost per tonne, tonnes moved, or unplanned downtime hours. Software-flavored metrics — seats activated, reports generated, adoption percentage — carry no weight with an operations executive. The strongest cases come out of the pilot itself, using the customer's own production data rather than a vendor benchmark.

Sources

• https://www.icmm.com/en-gb/our-work/environmental-resilience/tailings-management
• https://www.woodmac.com/industry/metals-and-mining/
• https://www.spglobal.com/market-intelligence/en/solutions/products/metals-mining-research
• https://www.mining-technology.com/
• https://www.hexagon.com/company/investors
• https://www.caterpillar.com/en/investors.html
• https://www.home.sandvik/en/investors/
• https://investors.bentley.com/
• https://www.epirocgroup.com/en/investors
• https://www.globaltailingsreview.org/

Related on PULSE

• [Revenue Architecture for Corrections Tech Software in 2027 — The Complete Operator Guide](/knowledge/ra0090)
• [Revenue Architecture for Recruiting Tech / ATS in 2027 — The Complete Operator Guide](/knowledge/ra0055)
• [Revenue Architecture for HR Tech / HRIS in 2027 — The Complete Operator Guide](/knowledge/ra0054)
• [Revenue Architecture for Funeral Home + Cemetery + Cremation Software in 2027](/knowledge/ra0159)
• [Revenue Architecture for Mortgage Tech + LOS in 2027](/knowledge/ra0154)
• [Revenue Architecture for QSR Tech in 2027](/knowledge/ra0151)