AxleClear
For fleets of 5 to 50 vehicles

You think you are being overcharged. You cannot prove it.

Not because your workshop is crooked. Because the quote came in on WhatsApp, the approval happened on a phone call, and the invoice landed three weeks later with nothing to match it against. Now multiply that by forty vehicles and a year.

Is this you? Engineering evidence

Three people, three different problems

In a small fleet these are sometimes the same person. The problems are still separate.

You sign the cheques

Maintenance is one of your three biggest costs and the only one you cannot interrogate. You have had the suspicion for years. You have never had the paperwork to do anything about it, and you are not going to accuse a workshop on a hunch.

You are the one who says yes at 7pm

The bakkie has to be on the road tomorrow. The workshop wants an answer now. You have no idea what that job costs because you cannot see the last three like it. You approve it. Six weeks later someone asks you why.

You have to reconcile it

Invoices arrive with no quote attached and no name against the approval. You chase people for a week to close a month. In government, the Auditor-General asks the same question and irregular expenditure is the answer nobody wants to write.

And the workshop, who is probably fine

Most of them are honest and tired of being doubted. A quote that was approved in writing is a quote that gets paid without an argument. The good ones want this more than you do.

What changes on Monday

The workshop still WhatsApps you. You still say yes. The difference is that the yes is written down against a number, and when the invoice comes in higher, it does not get paid quietly — it stops and waits for someone to look at it.

01
Quote
Workshop submits over WhatsApp
02
Approval
Checked against a spend cap
03
Work authorised
Scope fixed at approval
04
Invoice
Received against the job
05
Reconciliation
Matched to the approved quote
06
Settlement
Released, or flagged

Now you can query a bill without accusing anyone

This is the part that matters commercially. You are not calling anyone a liar. You are pointing at a record you both agreed to, and the record does not move.

How the audit chain detects tampering Four linked records. Each record's hash is computed from the previous record's hash plus its own payload. Editing record two changes its hash, which breaks every link after it. INTACT — each record seals the one before it Quote approved #a41f… Work authorised #7c03… Invoice received #e5b9… Reconciled #2d81… TAMPERED — record two edited after the fact Quote approved #a41f… Amount changed #9f42… Invoice received expects #7c03… Reconciled chain broken ✕ ✕
event_hash = sha256( previous_hash + canonical_json(payload) ) Each entry is sealed with the fingerprint of the one before it. Change something after the fact and every entry downstream stops lining up, with no backup needed to notice. Your bookkeeper can prove it. So can an auditor, an insurer, or a court.

What it is worth

Here is where a page like this normally tells you it will cut your maintenance bill by some confident-sounding percentage.

We are not going to do that. Nobody selling you software knows what your fleet is losing, and the numbers you see quoted in this industry were not measured on anything. We would be making it up, and you would find out.

What we will do is show you every job where the invoice came in above the approval, with the date, the vehicle, the amount and the name of whoever signed. Then you can count. If that number turns out to be small, you have bought peace of mind cheaply. If it is large, you already knew, and now you can do something about it.

You stop paying for the same fault twice

Every job is attached to a vehicle. When the same repair shows up three months later you can see it, which is a conversation worth having before you pay.

You learn what things cost

After a few months you know what a clutch costs across your fleet, not what one workshop says it costs today. That number is leverage.

Downtime becomes visible

A bakkie off the road is lost revenue, not just a repair bill. The record shows how long each job actually took, per workshop.

Month-end stops being a manhunt

Every invoice arrives already attached to the quote it was approved against. Your bookkeeper stops chasing people for context.

Built for how fleets here work

The workshop needs no software

Your workshop already lives on WhatsApp. They keep doing exactly that. Nobody has to learn a portal, buy a licence, or sit through a training day for this to work.

Your data stays here

Running in Google Cloud africa-south1, Johannesburg. Personal identifiers get hashed on the way in and never reach the logs.

You can say no without it being personal

Set a limit and the system holds the line. Nobody has to be the bad guy at 7pm on a Friday, and the relationship with your workshop survives the conversation.

It works on a phone in a yard

Approvals happen wherever you are, because that is where they actually happen. For the bigger buyers, it also meets the cloud standards procurement asks about.

For whoever has to approve the purchase

If you are a small operator, skip this. If you are in a municipality, an SOE or a corporate, these are the questions your procurement team will ask first.

Data residency

Google Cloud africa-south1, Johannesburg. Your data stays in the country.

POPIA by architecture

Identifiers are hashed at the boundary. Raw personal information never reaches an application log.

Tenant isolation

Every query is scoped to one organisation and one role. The test suite checks it on every build.

Transport and credentials

TLS in transit. bcrypt on passwords. JWT sessions. Every inbound WhatsApp webhook has its signature checked before we read it.

For the people who check

Funders, investors and IT departments want to know something real is behind this. We ran the test suite on 8 September 2026 and these are the numbers it gave back. It takes 71 seconds, so we would rather run it in front of you than describe it.

567tests passing, 0 failures
45database migrations
19,270lines of application code
3.0.0current release

Being straight with you

AxleClear is built and tested. Nobody is paying for it yet. It was engineered for large fleets, and we are now cutting it down for operators running 5 to 50 vehicles: a mobile-first interface, direct workshop integration, and onboarding you can complete without us.

You would have worked that out in the first meeting anyway. The upside of being early is that what gets built next is decided by the handful of operators in the room now.

Tell us we are wrong

If you run a fleet and none of this describes your week, we want to hear that even more than we want to hear the opposite. It is cheaper to find out now.

You run the fleet

Twenty minutes. Tell us how a quote reaches you and what happens when the invoice comes back higher than the yes. No pitch, no demo, no follow-up sequence.
hello@axleclear.com

You are checking us out

Investors, funders, procurement. We will run the tests live and walk you through the chain until you are satisfied it holds.
hello@axleclear.com