Profit recovery pricing

Pricing builtaround fleet ROI.

Start with a fleet leakage audit, prove where operational control can recover value, then license Tanka annually on your operating scope, workflow complexity, integrations and support needs.

Tanka — commercial termsTK-COMRev CSheet 01 of 01
ItemBasis
Annual platform licenseAnnual · scoped
ImplementationOne-time, scoped
Fleet leakage auditBefore proposal
Per-seat feesNone

NoteValues hold for the current printing. The proposal that follows the audit is the binding document.

ROI first

What does one month of leakage cost you?

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 scenario · illustration only
Vehicles
100
Monthly fuel spend
KSh 25M
Preventable leakage
2%
Potential recovery
KSh 500,000

Illustrative figures only — not a Tanka average, benchmark, or guarantee. The audit confirms what is actually recoverable in your operation.

The commercial model

Audit. License. Implement.

Three steps, in that order. The audit decides what the license is for and how big the implementation needs to be — which is why we do not publish tiers.

  1. 01

    Audit

    Start with the records, not a demo.

    • Eight to twelve weeks of trip, fuel and reconciliation records
    • Control gaps with evidence, frequency and owner
    • ROI hypothesis in KES with every input labelled
    • Enough to decide with, or to walk away from
  2. 02

    License

    One annual license for the control layer.

    • All eight modules included
    • Unlimited users across every team
    • Priced on operating scope and complexity
    • No public tiers, no per-vehicle games
  3. 03

    Implement

    Scoped once, from what the audit found.

    • Master data and migration
    • Workflow setup and integrations
    • Reports and training
    • The first workflow sequenced so value lands early

Every proposal is shaped by fleet size, depots, workflow complexity, integrations, data quality, reporting needs and support expectations. That is the whole list.

Pricing FAQs

Common buying questions.

01

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.

02

How quickly can we go live?

We confirm a phased implementation timeline after discovery. Go-live depends on data readiness, workflow scope, and rollout complexity, and we sequence the first workflow so you see value early.

03

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.

04

Can we track compliance and inspections?

Yes. You can manage inspection workflows, renewal tracking, and supporting documents in one place.

05

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.

06

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.

07

Do you charge for implementation?

Yes. Implementation is a separate fee based on data migration, workflow setup, integrations, custom reports, training, and rollout complexity.

08

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.

09

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.

10

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.

Still have questions?Start with the audit.

Bring eight weeks of records. We will tell you what is recoverable, what is not, and what it would take.

Book a fleet leakage audit