Skip to content

01Request a demo

Thirty minutes,
on your own fleet.

Tell us what you run and where. We show the console working on an operation shaped like yours — the map, a fuel authorization resolving against GPS, and what happens when the network drops halfway to Buchanan.

After you submit

  1. 01

    A person replies

    The form writes into the platform’s own leads pipeline rather than a shared inbox, so the request cannot sit unseen in someone’s mail. Someone from the Monrovia team writes back to the address you give to agree a time.

  2. 02

    Thirty minutes, driven live

    We set up an account shaped like your operation — fleet size, sector, country and currency — and drive the console in front of you. No slide deck, and no recorded video pretending to be live.

  3. 03

    Who is on the call

    From us: someone who works the console daily, plus an engineer when the questions turn to trackers, protocols or integration. From you: bring the transport director, whoever reconciles fuel at month end, and whoever owns the devices.

  4. 04

    What follows

    What your setup would actually involve — which modules you need, the roles they map to, whether your existing trackers are supported, and the cost for your vehicle count.

Worth having to hand

  • Roughly how many vehicles, and the corridors or counties they run1–10 … 200+
  • Which trackers are already fitted, if any — make and modelTeltonika · Concox · Queclink
  • Whether fuel is in scope, and the stations your drivers useOptional module
  • The policy you work to: after-hours window, speed limit, idle cap18:00–06:00 · 80 km/h
  • The currency you account inLRD · SLL · GNF · USD

None of it is required to book. It only decides how much of the thirty minutes is spent on your operation instead of on ours.

Request a demo

30 min · no commitment

Primary interest

Sent over TLS to Kappagee Inc. and used only to arrange your demo. Name, organisation and a valid email are required; everything else just shortens the call.

Fleets and station networks · Liberia, Sierra Leone, Guinea

02What the demo covers

Four blocks, and none of them are slides.

A demo should be the product doing the thing, including the parts that decline, flag and fail. This is how the thirty minutes usually runs.

  1. 00–08

    The map

    Live positions on a vector basemap, markers rotated to heading. One click opens the vehicle drawer — plate, driver, speed, fuel level, engine hours, current trip, open work orders. Then yesterday replayed with speed colouring, stops and idles marked, at up to ten times speed.

  2. 08–16

    One fuel authorization

    A card presented at a station, and the six checks it runs in under 200 milliseconds: card and PIN, balance or credit, product and volume, the vehicle’s last GPS fix against the pump, the odometer reading, and the pattern of recent transactions. We run one that declines, so you can read the reason it gives.

  3. 16–24

    The exceptions

    The three the platform raises on its own: movement outside your own after-hours window, a tank level dropping while the vehicle is parked, and a card presented while the vehicle is not at the station. Each one on the map, with the trip or transaction attached.

  4. 24–30

    Your questions

    Hardware you already own, who can see what across the eleven roles, the twenty-one standard reports and the builder that needs no SQL, offline behaviour on your worst route, and what onboarding looks like.

Live telemetryRoute replayA declined transactionA siphon alertOffline sync

Fuel is a module, so the agenda bends. If you are not running fuel cards, that block goes to maintenance scheduling and driver safety scoring instead. If fuel is the only thing in scope, we spend the whole session on the authorization engine and the station side of it.

03Talk to us first

Three offices, one clock.

Liberia, Sierra Leone and Guinea all keep Africa/Monrovia time — UTC+0 — so there is no time-zone gap between the three, and none between you and the team that answers.

Monrovia

06°18′N 10°48′W

Liberia

Head office · Mamba Point

Freetown

08°29′N 13°14′W

Sierra Leone

Regional

Conakry

09°38′N 13°34′W

Guinea

Regional · French

Email
info@kappagee.com

Reaches the same team as the form. Use it for anything that is not a demo request.

Already a customer

Sign in at fleet.kappagee.com, or on your own subdomain if your account has one. The support desk, live chat and your ticket history are inside the portal, where they can see your fleet — which is faster than describing it to us here.

Sign in
Station partners

Partner stations already on the network sign in at partners.fleet.kappagee.com for transactions, settlement summaries, payout details and disputes.

04Work with us

If you sell fuel or fit trackers, there is a second door.

The platform only works because of the forecourts that accept the card and the devices already bolted into the vehicles. Both are partnerships, and both start with an email rather than the form above.

Fuel stations

Fleets on Kappagee Fleet can only fuel where the platform can authorise. Joining the network puts your forecourt on that list, and gives you a back office for it.

  1. 01

    Register the station: brand, address, GPS coordinates, the fuel types you carry, and a payout account — bank or mobile money.

  2. 02

    The platform draws a 200 m approved-fuelling zone around your pumps automatically, so fleets can authorise there and nowhere else.

  3. 03

    POS credentials go to the station manager. The app scans a card or QR, authorises, records the litres dispensed and prints a receipt — and holds transactions in local storage when the line drops.

  4. 04

    Settlement runs daily against completed transactions. Kappagee takes a commission per transaction; you keep the forecourt.

The brands actually operating here — Aminata, Petro Trade, Conex, NP — are all in scope, and so is an unbranded independent forecourt.

Hardware suppliers and installers

We do not sell trackers, and we do not lock a fleet to one. If you supply or fit devices in Liberia, Sierra Leone or Guinea, the models you carry belong on the compatibility list.

  • Devices bind to a vehicle by IMEI, one at a time, and every swap stays on the record.

  • Teltonika, Concox and Queclink are supported through a pluggable adapter layer, with a generic path for NMEA and binary protocols. Dual-SIM units are normal here, not an edge case.

  • Carrying a model we do not yet speak? Send the model name, the protocol it reports on, and a sample of raw frames. That is what writing an adapter takes.

  • The registry tracks SIM, firmware, warranty and RMA state per unit, so a fleet can tell a dead device from a dead vehicle.

Fleets that ask us to recommend an installer are pointed at partners who have already done the work in the region.

Neither of those, and still want to talk?

Press, procurement, donor reporting requirements, or a question the site does not answer — write to us. It reaches the same people.