Start with a fleet leakage audit, prove where operational control can recover value, then license Tanka annually based on your operating scope, workflow complexity, integrations, and support needs.
Commercial model
A standard annual license gives your team access to the Tanka operating system. Implementation is scoped separately based on data, integrations, and rollout complexity.
For fuel logistics fleets, the real cost is not the software subscription. It is fuel variance, undocumented trips, delayed POD, manual reconciliation, compliance exposure, idle assets, and decisions made too late.
Tanka gives operations and finance one shared view of the workflow before the month-end cleanup starts.
Example fleet
This is an illustration, not a guarantee. The audit helps confirm what is recoverable in your operation.
Tanka is sold as an annual platform license. Your implementation fee is scoped separately because every fleet has different data readiness, workflows, integrations, locations, and training needs.
Primary commercial model
One annual platform license for the Tanka control layer, with unlimited users for the teams that need shared operating visibility.
Scoped after audit
A separate one-time implementation fee is scoped around master data, migration, workflow setup, integrations, reports, and training.
Scoped after audit
The fleet leakage audit confirms the workflow gaps, rollout scope, and business case before we finalize commercial terms.
Map loading, delivery proof, fuel variance, compliance, and reconciliation before committing to rollout.
Add dispatch, finance, drivers, fleet managers, compliance teams, and executives without per-seat charges.
Vehicles drive trips, fuel spend, maintenance events, compliance records, and financial exposure.
How does Tanka pricing work?
Tanka is sold as an annual platform license, with implementation scoped separately. The final proposal follows the audit so pricing reflects your fleet workflow, rollout scope, integrations, and support needs.
How quickly can we go live?
A focused first workflow can usually go live in about 5 days after kickoff, depending on data readiness and rollout scope.
Is this built for African operators?
Yes. Tanka is purpose-built around transport and fuel logistics realities across African markets: loading records, vehicle control, fuel variance, compliance, documents, and finance reconciliation.
Can we track compliance and inspections?
Yes. You can manage inspection workflows, renewal alerts, and supporting documents in one place.
Do you publish the annual license fee online?
No. Tanka uses a standard annual license model, but we do not publish public package prices because each proposal needs to reflect operational scope, data readiness, integrations, reports, and support requirements.
How do we know Tanka will pay for itself?
We start by looking at your current fleet data and identifying where losses are likely occurring: fuel variance, trip cost leakage, compliance gaps, maintenance delays, and reporting blind spots.
Do you charge for implementation?
Yes. Implementation is a separate fee based on data migration, workflow setup, integrations, custom reports, training, and rollout complexity.
Can we start with an audit before a full rollout?
Yes. The audit is designed to show whether there is enough recoverable value to justify implementation.
What affects the proposal?
Fleet size, number of depots or operating sites, workflow complexity, integrations, data quality, reporting needs, onboarding effort, and support expectations all shape the final proposal.
Do we pay extra for users?
No. Tanka is built for cross-functional accountability, so authorized dispatch, finance, driver, fleet, compliance, and executive users can work from the same system under the annual license model.