Operational intelligence software for fleet-heavy operations in Ghana
Money leaks between the field and the office.
ERP shows the invoice. Trackers show the truck moved. Excel shows what someone typed after the shift.
Darikoda gives Ghana's fleet-heavy operators the operating record underneath it all. Fuel, materials, machine hours, downtime, approvals, and certificate evidence. Captured at source.
Keep the leakage map regardless of next steps.
Darikoda is operational intelligence software for Ghanaian fleet-heavy operators. It creates a time-stamped operating record for fuel, machine hours, downtime, approvals and certificate evidence, so contractors can defend margin instead of reconstructing events from WhatsApp, trackers and spreadsheets.
The path from leak to defendable record.
Audit
Free 30-minute map of where your operation is leaking. One-page leakage report you keep regardless of next steps.
Build & Activation
4 weeks · fixed fee
Configure the operating record to your operation. Field test on real devices. Sign-off only when readiness criteria are met.
Pilot, then standard rollout
Three-month pilot proves operational value in your live contracts. Then standard tier per environment.
Start with the audit. The first 30 minutes is free.
Founding-customer engagements active across Ghana fleet operations. First Build & Activation phase now underway. First published case results targeted Q3 2026.
01 / The Gap
What your ERP can't see.
Every fleet operator I sit with tells me the same thing. Something is leaking. Fuel numbers don't add up. Certs run three weeks late. A dozer sat two months and no one can say why. You feel the money walking out. You can't point at it.
You've done the sensible things. A good GM. Trackers on the trucks. An ERP at GHS 150K a year, sold to you as total visibility. Two years in, you're still asking finance to pull a spreadsheet.
Your ERP was built for accounts. Invoices, assets, depreciation. Your question is different.
- Which machine earns? Which bleeds?
- When fuel goes missing, where?
- When a cert delays, which chainage is stuck?
No tool you own was built to answer that.
What you see
Your tracker shows the truck moved.
What you don't
Not that it left full and came back empty.
What you see
Your ERP shows GHS 240,000 on parts last quarter.
What you don't
Not that 40% went to two machines you should have retired two years ago.
What you see
Your spreadsheet shows the dozer came back to site.
What you don't
Not that it sat six weeks waiting for a job no one assigned.
What you see
Your supervisor says no downtime.
What you don't
Your workshop has four machines waiting for parts.
What you see
Your cert takes three people a week.
What you don't
The data was ready two weeks earlier.
Every card above is real. Anonymised.
That's what Darikoda was built to fix.
Where the leaks live.
Fuel
Dispensed at the bowser, consumed by the machine, reconciled at head office. Three handovers. Three places the number can drift.
Machine
Assigned to a project, worked through a shift, stood down for parts or weather, repaired and returned. Four states. Most operations only track the first.
Downtime
Diagnosed, waiting parts, repairing, testing. Most operations track downtime as one number, so they cannot see whether the real problem is procurement, scheduling, workshop capacity, or repair time.
Certificate
Measured (joint with consultant), evidenced (BoQ), submitted (IPC), defended (when the consultant cuts). Cert speed is cash flow. Cert defensibility is margin protection.
Approval
Requested (WhatsApp), approved (GM), delayed, costed. Most operations cannot see the cost of an approval delay until it has already lost them money.
Cross-hire
Your machine. Your fuel. Their operator. On subcontracted work, a weak month-end tally turns machine hours and fuel deductions into a dispute, and you swallow the cost of your own equipment.
Materials
Bought. Delivered. Issued. Consumed. By month-end the variance has already stopped a crew, started a supplier dispute, or shown up in the wrong number.
It works at this size. It stops working at the next one.
The informal system runs on trust, memory, and everyone knowing each other. Then you win a second contract, the fleet grows, or a new site opens. Here are six places where the informal system quietly fails.
Manual entry becomes one tap.
Paperwork search becomes instant query.
Payment cert PRJ-TEMA Ch. 12+400 to 14+200
Phone-chase approvals become one tap.
Fuel top-up 420L M-04 Kwame
GHS 3,108 within limit
The supervisor on the tablet.
The fitter in the workshop.
The operator at the bowser.
Six moments on their shift where paper dies and margin comes back.
Three are how the day grinds for one person on shift.
Three are how the month falls apart between people at the office.
Month-end scramble becomes live dashboard.
"Who did what" becomes an immutable trail.
A 17-day dispute becomes a 2-minute sign-off.
Evidence: 47 work orders, 12 dispense logs, GPS-confirmed.
This is what you get back.
Six small shifts. One compound effect. What a mid-size fleet typically reclaims in the first six months on Darikoda.
Times compound. Supervisors stop chasing paper. Approvers stop dodging calls. Finance stops begging for data. The business starts running like a system.
See where your fleet is leaking before reading another section.
30-minute audit on WhatsApp. You keep the one-page leakage map regardless of next steps.
02 / The Platform
Three questions your dashboards can't answer.
Not because the information doesn't exist. Because it's scattered across people, paper, and days.
Production Profitability
Which machines earn. Which bleed.
Your revenue comes in one machine at a time. Your cost walks out one machine at a time. Averaging both to fleet level hides where the money is actually made and lost.
Darikoda joins fuel, parts, labour and work orders against what each asset actually produces (tonnes, kilometres, bank cubic metres) resolved against the specific rate that asset is earning against.
Cost per tonne, per kilometre, per machine. By month two it lives on a dashboard.
Downtime Intelligence
Not how long. Why.
Every workshop tracks downtime as a single number: hours the machine didn't run. That number hides three different problems.
Down 20 hours waiting for parts is a procurement problem. Down 20 hours diagnosing is a capability problem. Down 20 hours because no fitter was free is a scheduling problem. Three completely different fixes. One number hiding all of them.
Darikoda splits every work order into four timestamped stages: diagnosing, waiting parts, repairing, testing. Stop arguing about downtime. Start fixing it.
68% waiting parts, that's a procurement conversation, not a workshop one.
Built for the site you actually operate.
Fuel Integrity
Dispensed vs consumed. Reconciled daily.
Every fleet operator suspects a 5%+ gap between the bowser and the tank. Most can't prove it.
Darikoda logs every dispense against asset, operator, quantity, GPS and time. It reconciles against shift consumption. Variance over your threshold opens an issue automatically. Where CAN enrichment is in place, we use real engine data. Where it isn't, disciplined manual entry works.
Five percent recovery on GHS 20M fuel is GHS 1M to margin. One line item. (Illustrative model, your number from the audit.)
Issue auto-flagged to reconciliation queue.
Built so the record survives the site.
- Every field write saves locally first, syncs when signal returns. Your operators don't wait for 4G.
- Every transaction has a sync state: saved, queued, synced or failed. No more "did it go through?"
- Every action is attributed to a person, role, device, and time. No silent edits to history.
- Shared tablets use PIN-level worker attribution. No one is logged in as someone else.
- Failed syncs create visible issues, not silent gaps.
- Finance and operations see the same record. Your existing accounting or ERP gets fed the per-machine truth it cannot produce on its own.
For engineers: how it's built →
Who this is for. And who it isn't.
Who Darikoda is for
- Mining contractors with 3–50 heavy assets, where day-works rates, fuel exposure, or contract reporting justify the Build & Activation cost
- Construction main contractors with 50–2,000 assets across multiple projects
- Civils and roadworks contractors on FIDIC red or yellow book contracts
- Plant and equipment hire firms with 20–200 assets
- Main contractors who rent fleet internally to subcontractors on road and civils projects
- Real estate developers with active fleet exposure across their projects
Who Darikoda isn't for, yet
- Multinationals already running Pitram, MineWare, or fully-integrated OEM telematics
- Operators with fewer than 10 assets unless the contract economics are strong enough to justify implementation. Small mining contractors with day-works billing can qualify.
- Operators who want only GPS tracking. Sky Ledge, VisionLink and Introma already do that
- Operators looking for a turn-key plug-in to existing ERP without configuration
What it returns.
In similar operations, the first changes usually show up in:
- Cert preparation becoming faster because field evidence is already structured.
- How much fuel variance becomes visible at source rather than absorbed into operational noise.
- Which component of downtime is the largest, once visible (often parts-waiting, not repair time).
- How hire-versus-own decisions and renewal negotiations get made (with per-asset evidence, not memory).
- How disputed deductions from subcontractors get defended (with immutable digital evidence, not paper tallies).
Your specific number depends on your fleet, your contracts, and your current baseline. The Operational Audit produces it.
Ready to see your own leakage map?
30 minutes. WhatsApp. You walk away with the map either way.
What's already real.
Darikoda Core v2.4.4 is live on owned infrastructure. Sentinel V4 predictive layer deployed. Pilots running across fleet operations in Accra.
Platform live. Pilots running. Case results when partners sign off.
The Flutter app is in active build. Three pilots underway across fleet and hospitality operations. Four-week Build & Activation phase before any pilot clock starts.
No case studies printed yet. Those come from the current pilots, with permission, when they're ready.
If yours is next, you get founding-customer pricing and my direct line for two years.
Talk to me
The fastest way is WhatsApp.
+44 7984 845440
theo@iloristreamline.com
Typical reply within the hour during UK and Ghana business hours.
Patterns described here are drawn from extensive field audits and industry research across Ghana's mining, construction, roadworks, and quarry sectors. No specific operator is named or identifiable.
Frequently asked questions.
What exactly does Darikoda do?
Darikoda is the operating record between what your fleet did and what your office can defend at month-end. Fuel events, hour-meter attribution, mechanical availability, materials variance, approvals, certificate evidence. Captured at source.
Does it work in low-connectivity environments?
Yes. Every field write saves locally first and syncs when signal returns. Operators do not wait for 4G. Sites with Starlink plus patchy 3G/4G are well within the operating envelope.
Is this just for mining?
No. Mining is one of five verticals. Darikoda also serves construction (developers, main contractors, subcontractors), civils and roadworks (government contractors under FIDIC), and plant and equipment hire firms. The operating record architecture is the same across all of them.
Why start with an audit?
Because most operators already know money is walking out. The audit is 30 minutes that produce a one-page leakage map. You keep it regardless of next steps. It pre-qualifies whether Darikoda is the right next move or whether something simpler fixes the issue first.
How fast can someone speak to us?
Usually within the hour during UK and Ghana business hours. WhatsApp is the fastest channel. Email works for asynchronous follow-up.