How to Hire a Mine Haul Fleet Dispatch Software Development Company
Make every candidate whiteboard the cycle model first. The right answer separates load, haul, dump, return and queue as distinct states with their own timestamps and sources, and has an opinion about clock drift.
On this page
Make every candidate whiteboard the cycle model first. The right answer separates load, haul, dump, return and queue as distinct states with their own timestamps and sources, and has an opinion about clock drift. Expect $70,000 to $160,000 and 12 to 18 weeks for a dispatch intelligence layer over your existing fleet system, and do not commission a replacement for a working tier one dispatch.
At 02:10 nothing looks wrong. The trucks are moving, the radio is quiet, and the shovel in the north pit has been waiting eleven minutes because four trucks are stacked at the tip. Buying dispatch software has the same character. The proposal moves, the demo is quiet, and the problem, a trip modelled as a start time and an end time, or a plan that assumes connectivity in a cutback, does not surface until the morning report four months later shows a number nobody can attribute.
This category is hard to buy because the mature products are genuinely good and the honest answer for many operations is not to replace them. Modular Mining DISPATCH, Wenco, Hexagon and Caterpillar MineStar have decades of operating data behind their optimisers. What they will not readily do is hand back your raw data, or model the specific downstream constraint that governs your revenue this shift. So the real hiring decision is usually not who builds a better optimiser. It is who can build the layer around one, and that is a different skill set than most software firms are selling.
What a dispatch software partner actually builds
They build a canonical cycle model before anything else. Load, haul, dump, return and queue as separate measured states, each with its own timestamps and its own source, because queue time at the shovel and the tip is the number the whole business case rests on and a single trip duration hides it completely.
They own the ingestion layer deliberately. You run mixed iron: Caterpillar and Komatsu trucks, a Hitachi excavator, hired water carts, plus third party payload scales and tyre pressure monitoring that arrived as separate safety projects. The AEMP telematics standard, ISO 15143-3, gives a common route to hours, fuel and location across OEMs and covers the easy half. Payload distribution, pass counts, tyre exposure and delay codes are per source work.
They get timestamps right, which sounds trivial and is not. Onboard clocks drift, OEM portals report in UTC, your shift boundary is local across a daylight saving change, and getting that wrong makes the entire reconciliation quietly nonsense.
They design for the dispatcher rather than around him. An override path where he can force an assignment and the system records why, because a dispatcher who cannot override will defeat the system by lunchtime, and the override reasons are the training data for everything that follows.
What it really costs in 2026
These bands reflect Digital Heroes delivery experience on mining and heavy earthworks builds.
| Scope | Cost | Timeline |
|---|---|---|
| Reconciliation and reporting only: ingestion, canonical cycle model, daily variance | $45,000 to $90,000 | 8 to 12 weeks |
| Dispatch intelligence layer: mixed OEM ingestion, cycle model, reconciliation, short interval control alerting | $70,000 to $160,000 | 12 to 18 weeks |
| Full dispatch build: in cab tablets, live assignment, offline tolerance, delay capture | $250,000 to $700,000 | 9 to 18 months |
| Each additional site with its own delay taxonomy | $30,000 to $80,000 | 4 to 10 weeks each |
Two lines are routinely absent. The first is in cab hardware. Device selection, mounting, power, sunlight readability and glove usability are not software questions, and the field trial has to run across a full weather cycle before you commit the fleet. Vendors quote the tablet count and not the trial.
The second is getting raw data out of your incumbent fleet system. That is a commercial negotiation, not an engineering task, and it moves at the pace of your licence renewal. Raw data access is often the single most valuable term in that contract, and a project plan that assumes the export already exists will stall at the exact moment the developers are ready.
Signals of a strong partner
- They will tell you not to replace a working optimiser. A firm that argues you out of the larger project has read your operation rather than your budget.
- Queue is a first class state in their model. Load, haul, dump, return and queue, with sources and timestamps for each, not a trip duration.
- They have an opinion about clock drift and shift boundaries. Including what happens across a daylight saving change with UTC OEM feeds.
- They name the feeds they have pulled. ISO 15143-3, a specific OEM portal, a named payload scale vendor, a plant historian over OPC UA, and what broke on each.
- The alert targets the constraint, not the trucks. Which shovel starves in the next fifteen minutes, and which reassignment recovers tonnes before the break.
- They plan an in cab trial before a fleet rollout. One pit, one shift pattern, read only reconciliation first, live assignment second.
- The dispatcher override is designed in, with reason capture. Adoption is decided by this and almost nothing else.
Red flags
- A trip modelled as a start and an end time. The queue disappears, and queue time is where the diesel and the paid hours go with no tonnes attached.
- Offline treated as caching. Coverage drops in cutbacks and behind walls, which is precisely where the interesting events happen. You need local write, queued sync and an explicit duplicate policy.
- An AI dispatcher pitched without queueing mathematics underneath. Ask what the model optimises and how the assignment is computed. If the answer is a nearest available truck rule with a marketing wrapper, move on.
- A proposal to replace tier one dispatch as a first project. On a large homogeneous fleet that is a multi year risk with unclear upside, and an experienced firm says so unprompted.
- They accept vendor lock on your data again. Since data lock is usually why operators start this conversation, repeating it with your development partner defeats the point.
Questions to ask on the first call
- Whiteboard the cycle model. Where does queue time live, and what is its source?
- Onboard clocks drift and the OEM portal reports UTC. How do you assign a load to the correct shift across a daylight saving change?
- Which OEM telematics feeds have you actually pulled, and which fields did ISO 15143-3 fail to give you?
- Which payload scale or tyre monitoring vendor have you integrated, and what broke?
- A tablet loses signal for ten minutes and then syncs the same events twice. What happens?
- How would you tie fleet state to our crusher throughput or blend constraint rather than to truck counts?
- What in cab hardware have you deployed, and how long was the field trial?
- What do you need from our incumbent fleet vendor, and what do we ask for at licence renewal?
- Who owns the repository, the cloud accounts and every row of cycle data from day one?
A simple way to decide
Buy discovery, not a proposal. Two to four weeks, priced separately, producing a written specification: the canonical cycle and equipment model, the ingestion design per source with the fields each one can and cannot supply, the timestamp and shift boundary policy, the reconciliation and short interval alerting design, the in cab hardware shortlist with a trial plan if you are going that far, the data access you need from your incumbent vendor, and a fixed price for the first release on one pit.
Make the specification yours regardless of who builds. It also strengthens your hand at the next licence renewal, because a written list of the exact fields and frequencies you need from your fleet vendor turns a vague request for data access into a negotiable term. Take the same document to the rest of your shortlist.
Digital Heroes works PRD first and hands over the repository and cloud accounts from the first commit, contracting through India LLP, US LLC and UK LTD entities so intellectual property assigns under the buyer's own law. Given that vendor lock on data is usually why this conversation starts, accepting it from your development partner would be an expensive irony.
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.
- 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) →
- Technology 'Leaders' grow revenue at more than twice the rate of 'Laggards'; laggards surrendered 15% in foregone annual revenue in 2018 and stood to miss out on as much as 46% in revenue gains by 2023 if they did not change their enterprise technology approach. Based on a survey of more than 8,300 organizations across 20 industries and 20 countries. Source: Accenture (2019) →
- In a McKinsey global survey of 1,259 respondents, only about 20% said their organizations excel at decision making, and just 37% said their organizations' decisions were both high quality and high in velocity. Source: McKinsey & Company (2019) →
- In an RCT, text-message reminders (11.7% missed) were non-inferior to telephone reminders (10.2% missed; difference not significant, within the 2% non-inferiority margin) but far cheaper - total cost EUR 230 for SMS versus EUR 8,910 for telephone over 6 months - making SMS more cost-effective. Source: BMC Health Services Research / PubMed Central (Junod Perron et al.) (2013) →
Frequently asked questions
How much does custom haul truck dispatch software cost?
A dispatch intelligence layer over an existing fleet system, covering mixed OEM telematics ingestion, a canonical cycle model, daily reconciliation and short interval alerting, runs $70,000 to $160,000 over 12 to 18 weeks. A full dispatch build with in cab tablets, live assignment and offline sync runs $250,000 to $700,000 across 9 to 18 months. Fleet size, number of sites and in cab hardware selection drive most of the variation.
Should we replace Modular Mining DISPATCH or Wenco?
Usually not. Those optimisers are mature and rebuilding one is a multi year risk with unclear upside for a large homogeneous fleet. The stronger move is building the intelligence layer around the existing system and negotiating raw data access at your next licence renewal. Full replacement makes sense mainly for contractors, quarry groups and mid tier operations where per machine licensing and vendor onboard hardware outweigh the optimisation benefit.
What single question exposes a developer who has not worked with fleet data?
Ask them to whiteboard the cycle model. The right answer separates load, haul, dump, return and queue as distinct states with their own timestamps and sources, and comes with an opinion about clock drift and shift boundary handling. A developer who models a trip as a start time and an end time has erased queue time, which is exactly the number the business case depends on.
What gets left out of dispatch software quotes?
In cab hardware and incumbent data access. Device selection, mounting, power, sunlight readability and a field trial across a full weather cycle are real work that vendors rarely price, and a build that is elegant in the office and unusable in a haul truck has failed. Getting raw data out of your existing fleet system is also a commercial negotiation rather than an engineering task, and it moves at licence renewal pace.
Does the in cab application really need to work offline?
Yes. Coverage drops in cutbacks and behind walls, which is precisely where the interesting events happen, so any design assuming connectivity loses data exactly where you need it. The right answer involves local write, a queued sync on reconnect and an explicit policy for reconciling a device that syncs the same events twice. Ruggedised, glove usable hardware matters as much as the software itself.
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.
Should I ask for a fixed price or pay the agency hourly?
Fixed price for the first version, hourly or retainer for what comes after launch. A fixed-scope, fixed-price V1 puts the estimation risk on the agency, which is exactly where you want it while trust is unproven; hourly billing on an unscoped greenfield build is a blank check. After launch, flip it, because maintenance and small features arrive unpredictably and fixed-pricing every ticket wastes everyone's time.
Is a solo freelancer enough for my project, or do I really need an agency?
A solo freelancer is a fine choice for a well-defined build under roughly $15,000 to $20,000 with a limited lifespan: an internal calculator, a scripted integration, a prototype. Above $50,000, or for any system your business will depend on for years, you are buying continuity as much as code: enforced code review, cover when someone is ill, and support that outlasts one person's career plans. Price the risk of a single point of failure, not just the hourly rate.
How do I work out whether custom software will pay for itself?
Do the arithmetic on hours before anything else: if the system saves three staff eight hours a week at a $35 loaded hourly cost, that is about $43,700 a year against, say, a $70,000 build plus 15 to 20% annual maintenance, a payback around two years. Add revenue effects only if you can name them specifically, like faster quotes or fewer abandoned orders, not as vague growth. In our delivery experience the businesses that see payback inside 24 months are the ones automating a process they already measure.
Can I build my product on a no-code tool like Bubble instead of hiring developers?
For testing whether anyone wants the product, yes, and Bubble's paid plans start at $29 a month, which is the cheapest validation you will ever buy. The ceiling arrives with complex data relationships, heavy integrations, performance at a few thousand users, and the fact that you cannot export a Bubble app to servers you control. A path many Digital Heroes clients take: prove demand on no-code, then rebuild custom once revenue justifies it, treating the no-code version as a paid prototype rather than a foundation.
What does a $50,000 custom software budget actually buy?
One core workflow done properly: 10 to 15 screens, two or three user roles, a couple of integrations, an admin panel, and automated tests, delivered in roughly 12 to 14 weeks. What it does not buy is that workflow plus a mobile app plus AI features plus five more integrations. The discipline of picking the one workflow that matters is what separates $50,000 projects that ship from $50,000 projects that stall at 70% complete.
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.
How do we get years of data out of our old system and into the new one?
Treat migration as a planned sub-project: a field-mapping document, at least one dry run on a copy of your data, then a cutover with the old system kept read-only for 30 days as a safety net. On Digital Heroes projects it consumes 10 to 15% of the budget when the old system has an export, and more when data must be pulled out screen by screen. Ask any vendor to walk you through their last migration before you sign.
What is the biggest mistake first-time software buyers make?
Choosing the lowest quote without asking why it is the lowest. A bid 40% under the field usually gets there by skipping tests, documentation, and code review, which are invisible in a demo and brutal to pay for later; every stalled project Digital Heroes has been asked to rescue tells some version of that story. The second mistake is signing without a written scope, which reliably turns the winning cheap quote into 1.5x to 2x the price by launch.
Our developer disappeared mid-project. Can another team pick up the code?
Yes, this is a routine engagement, provided the code exists somewhere you can access, so your first move is securing the repository, hosting, and domain credentials today. A takeover starts with a one to two week paid code audit that ends in one of three verdicts: continue the build, keep the design but rebuild the weak parts, or start over. Digital Heroes has inherited enough projects to say plainly that sometimes the rebuild is cheaper than the rescue, and an honest agency will tell you which one you have before taking your money.
What is a discovery phase, and is it worth paying for separately?
Pay for it, and treat the output as yours. A discovery phase runs two to three weeks, typically 5 to 10% of the eventual build budget, and produces a written scope, wireframes, and a fixed quote you can take to any vendor, including a competitor of the agency that wrote it. Skipping it is how projects end up quoted from a two-paragraph email and delivered at twice the price.
How many people should be working on my software project?
A typical $40,000 to $150,000 build runs on three to five people: a technical lead, one or two developers, a designer, and someone owning QA and project communication, often as overlapping part-time roles. More bodies do not make software arrive faster; past a point they slow it down with coordination overhead. The question that matters more than headcount is whether one named senior engineer is accountable for the outcome.
What happens if I stop paying for maintenance after launch?
Nothing breaks on day one, which is what makes it dangerous. Within 6 to 18 months, unpatched dependencies accumulate known vulnerabilities, an integrated API like Stripe ships a breaking change, and the first fix requires a developer to relearn a stale codebase at full price. Budget 15 to 20% of the build cost per year for upkeep; it is the difference between a $500 patch and a $15,000 emergency.
If an agency builds my software, who actually owns the code?
You should own everything, assigned in writing: the contract transfers full IP to you on final payment, the code lives in your GitHub organization, and hosting runs in cloud accounts you control. The red flag is a proposal that mentions the agency's proprietary platform or framework, which usually means you are renting, not buying. Digital Heroes structures every build this way precisely so a client can fire us and lose nothing but the relationship.
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.
Who can build a custom software system?
Digital Heroes builds custom software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
More from Shaurya.
Senior React Native Engineer · Delhi · 1 post on the site
Published · Last updated .
