Availability target
99.9%
Dispatch decisions are time-critical; the platform is engineered to stay reachable.
Pre-launch
Booking for gas logistics, built on live corridor intelligence.
Request a truck, assign a driver, follow the movement and track asset performance from one platform. The GASCORP App brings the corridor's operations into a single, auditable system — for customers, drivers, fleet owners and our own control room.
- Role-based interfaces
- 4 Role-based interfaces
- Trip visibility
- 24/7 Trip visibility
- Fuel streams covered
- 3 Fuel streams covered
- Paper dispatch
- 0 Paper dispatch
GASCORP App
Android · iOS · Web
- Days remaining
- 272
- Hours remaining
- 11
- Minutes remaining
- 35
- Seconds remaining
- 11
Estimated launch window: July 2027
Interface preview
One platform, four surfaces.
Every role opens a different experience, all bound to the same live operational record. These are illustrative layouts of the workflows the app will ship with.
-
01 — Customer Book a movement, confirm price and follow the trip.
-
02 — Driver Receive assignments, update status, upload delivery proof.
-
03 — Investor Utilisation, revenue by asset and owner wallet performance.
-
04 — Admin Fleet readiness, dispatch queue, payouts and compliance.
Why it exists
Gas logistics still runs on phone calls and paper.
Booking is negotiated by call. Dispatch lives in a group chat. Proof of delivery is a photograph on someone's handset. By the time a fleet owner asks how an asset performed last month, the answer is an estimate.
The GASCORP App replaces that with one recorded workflow: every request, assignment, movement and delivery written to the same ledger, visible to whoever is entitled to see it.
Before
Booking by phone call
No record of what was agreed, at what price, for which date.
After
Structured booking request
Route, capacity, cargo and price captured once and reused.
Before
Dispatch by group chat
Assignments are verbal, unverifiable and impossible to audit.
After
Dispatch with assignment trail
Every job carries an owner, a driver and a status history.
Before
Proof by photograph
Delivery evidence sits on a personal device.
After
Proof attached to the trip
Confirmation is stored against the job and the asset.
Before
Performance by estimate
Utilisation and revenue are reconstructed after the fact.
After
Performance from live data
Utilisation, revenue and readiness read from operations.
Role-based access
Everyone sees exactly what they should.
The same job looks different depending on who opens it. Each role gets the fields, actions and reporting that belong to their part of the corridor — nothing more.
01
Customers
Set the route, choose truck type and capacity, confirm the price, then follow the movement through to delivery with the full invoice history attached.
- Booking with route and capacity
- Price confirmation before dispatch
- Live trip visibility
- Invoice and delivery history
02
Drivers
Receive an assignment with route instructions, progress the trip status at each stage and close the job with verified proof of delivery.
- Assignment inbox
- Route and site instructions
- Stage-by-stage status updates
- Proof-of-delivery capture
03
Fleet owners & investors
See how each asset is actually performing: active versus idle time, revenue by asset, route activity, utilisation rate and owner wallet balance.
- Utilisation by asset
- Revenue and route activity
- Readiness and downtime
- Owner wallet performance
04
Operations & admin
Run the corridor: users, fleet readiness, the dispatch queue, booking exceptions, payout logic, disputes and compliance expiry, with analytics on top.
- Dispatch queue control
- Fleet readiness and compliance
- Payout and dispute handling
- Operational analytics
How it runs
From booking to verified delivery in three steps.
One request creates one job. That job carries its own state until the delivery is closed and the payout is settled.
-
01
Book
The customer sets route, truck type, cargo and schedule. The app returns a price and a confirmed slot.
-
02
Dispatch
The dispatch engine assigns the nearest suitable asset and driver, and pushes the assignment to the driver app.
-
03
Deliver & settle
Movement is tracked, delivery is confirmed with proof, the job closes and payouts are reconciled.
Platform characteristics
Built as operations infrastructure, not an app.
Response target
< 2s
Booking and status actions are designed to feel immediate on mobile networks.
Trip visibility
24/7
Every movement is observable end to end, including out-of-hours transfers.
Corridor coverage
774 LGAs
The rollout roadmap follows the national penetration programme.
Audit trail
Every action
Bookings, assignments and confirmations are recorded and attributable.
Access model
Role-based
Data is scoped to the role, so partners only see what concerns them.
Launch programme
Join the first wave.
Early access shapes onboarding priorities, corridor coverage and the sequence of the rollout. Tell us which side of the corridor you are on and we will bring you in as capacity opens.
- Early access ahead of public release
- Input into corridor and route priorities
- Onboarding support for your first bookings
- No cost to join and no obligation
- Days remaining
- 272
- Hours remaining
- 11
- Minutes remaining
- 35
- Seconds remaining
- 11
Estimated launch window: July 2027
Request early access
Four fields. We will confirm your place and let you know as onboarding opens.
Prefer to speak to the team first? Call +234 703 839 2520 or send an enquiry.