Cash leakage
COD is reconciled days late against paper. Shortfalls surface too late to trace to a rider, a shift, or a parcel — so they are written off as the cost of doing business.
Run dispatch. Move money. Scale operations. Deespatcha unifies dispatch, driver execution, merchant management, tracking, COD reconciliation and settlement on one event stream and one double-entry ledger.
of COD value lost to reconciliation leakage in cash-heavy operations
typical wait before a merchant sees their own COD money today
settlement cycle Deespatcha is engineered to hold, platform-wide
target unexplained cash variance, per tenant, per month
The parcels mostly arrive. The money mostly does. Nobody can prove either — and every gap is absorbed by the operator, untraceable and unpriced.
COD is reconciled days late against paper. Shortfalls surface too late to trace to a rider, a shift, or a parcel — so they are written off as the cost of doing business.
Merchants wait up to two weeks for their own money. Their working capital sits in your process, and the operator who pays in two days takes the account.
"Where is my parcel" needs an agent to call a rider who may not answer. When a dispute escalates there is no evidence — only competing recollections.
Success rate, rider productivity and true cost per delivery are unknown — so unprofitable merchants are served at a loss and rates are set by instinct.
No record of who held what, when, or where. Losses are settled by argument, and absorbed by whoever argues least well.
They are one: there is no system of record. Fix that and the rest resolve as consequences — which is exactly how the platform is built.
Every material action becomes an immutable event with an actor, a server time, a device time and a location. Status is derived from that stream — never asserted, never edited. Cash entries reference the event that caused them.
Dispatch board, live map, exception queue, hub scanning, shipment detail, cash and reconciliation. One screen per question, no tab-switching.
Five screens, deliberately: tasks, custody scan, delivery with proof, cash, shift close. A full ten-hour shift with no connectivity, syncing with zero loss and zero duplication.
Merchants book single or bulk shipments, print labels, track without calling you, raise queries as tickets, and watch their COD wallet settle on a schedule they can see.
A link and a WhatsApp message. The recipient sees the window, the cash to prepare, and can drop a pin or correct a landmark before the rider wastes the trip.
No balance is ever mutated. Money moves between accounts — cash-on-hand per rider, cash-in-hub per hub, a payable per merchant, revenue, and a variance account that cannot be quietly emptied.
For any rider, on any past shift, the platform reproduces exactly what was collected, from whom, what was handed over, to whom, and any variance with its resolution — without a single document outside the system.
Hub-and-spoke or direct-from-merchant pickup, high COD share, real attempts and returns. Not bike-hailing, not interstate haulage, not freight forwarding — those are different products and we say so.
Knows cash is leaking, cannot quantify it. Gets leakage exposure, margin per merchant, and a number that proves ROI in month one.
Eight hours in the console. One screen showing what is going wrong right now, and the tools to fix it without a second tab.
25–40 parcels a day, entry-level Android, cash in his pocket. The app must beat a paper waybill and protect him in a dispute.
40–150 parcels a week, cash flow tied to your settlement speed. Pay in two days with a statement that reconciles and they stop shopping.
We are not selling a finished platform yet. We are looking for a small number of operators willing to have their real operation documented — hubs, zones, rate card, cash process, exception taxonomy — and built against.
Customer zero signed. Their operation documented in full, and the segment assumption validated or corrected.
All four surfaces, offline driver loop, double-entry ledger, settlement statements. One operator live in production, paper retired.
Partners two and three onboarded. Multi-tenant provisioning proven. Merchant API, electronic COD, inbound WhatsApp ticketing.
Self-serve onboarding, iOS, route intelligence, warehouse module, embedded payments, and expansion across the continent.
Customer zero must run one full month with zero paper waybills and cash variance under 0.5% before we sell to anyone else. If it is not met, we fix rather than sell.
Design partners get the platform built around their real operation, founder-led onboarding, and preferential commercial terms for the life of the account. In exchange we need access to how you actually run — including the cash process you would rather not show anyone.
We read every application ourselves. If your operation fits the current cohort you will hear from a founder within two working days — on WhatsApp, not email.
Something not covered? Email hello@deespatcha.com and a founder replies.
No, and we do not pretend to be. We partner with licensed rails for disbursement. Deespatcha is the ledger and the system of record — the layer that knows what is owed to whom and why. Fund-holding structure is being settled with counsel before general availability.
This is the single biggest risk in the product and it is designed around. Five screens. A COD delivery with proof takes no more than six taps and one photo, in under 45 seconds, on an entry-level Android with no network. It also gives the rider what paper never did: a record that protects him when he is blamed for a loss he did not cause.
Offline is the assumption, not the error case. No workflow requires connectivity to complete. Every event carries a client-generated idempotency key, syncs in causal order, and survives app kill, restart and update. A full shift in airplane mode reconciles with zero loss and zero duplication.
No. We will not build a marketplace matching merchants to carriers — you would correctly see that as competing with you. Merchant-facing and recipient-facing surfaces carry your branding, not ours.
Each operation gets an isolated database — no shared tables, no query path that can reach another operator's data. Complete export on request and on termination. Rider location traces default to a 90-day retention window, configurable downward only, in line with the Nigeria Data Protection Act.
That is exactly how we start. We run reconciliation in parallel with your existing process for a month and show you the gap between what you think you collected and what actually landed. That number is the whole conversation.
Route optimisation, automated dispatch, fleet maintenance, rider payroll, warehousing, customs, interstate multi-leg, and an iOS driver app. We would rather do parcels and cash completely than eight things partially.
The leakage is already happening. Deespatcha makes it visible, then makes it stop.