Softknack Verticals · Chauffeur Fleet

Every job accounted for.
From the quote to the cash in the driver’s hand.

An operations console for chauffeur-driven vehicle rental. Tariffs that price a job the same way twice, dispatch that records why each driver was chosen, vehicle custody with odometer and fuel at both ends, and driver cash reconciled before a shift can close. Built on SK Calendar, SK CRM, SK Billing, SK People and SK Company Cash.

Quoted price is the invoiced price · Auditable allocation · Odometer-verified custody · Cash reconciled before close
Quoted = invoicedpriced from a published tariff
Auditable dispatchevery fact stamped with its age
Custody closedodometer + cash before shift end
Core IntegratedCalendar · CRM · Billing · People
Where the money goes

The job ran. Whether it made money is a different question.

A busy board is not the same as a profitable one. Between the price you quoted and the cash that reaches the office, four things quietly take money out of a chauffeur operation — and none of them appear as a line anyone can point at.

Quote

The price moved on the way to the invoice

A fare agreed on the phone, a waiting charge nobody wrote down, an airport surcharge applied by memory. The invoice argues with the quote and the customer wins.

Why?

Nobody can say why that driver got the job

The allocation happened in someone’s head at 6am. A week later, when a driver asks why he was skipped, there is nothing to show him.

Km

The kilometres between two shifts

A car goes out with one odometer reading and comes back with another. Without a reading at both ends, private mileage and fuel are simply absorbed.

Cash

Cash that settles days late, or never

Fares collected in cash sit in a driver’s pocket across shifts. By the time anyone counts, the shortfall has no owner.

None of this is a discipline problem. It is a record problem — the price, the reason, the reading and the count all existed for a moment and then stopped existing. Software that asks people to remember cannot fix it. The record has to be made at the moment the thing happens, by the person doing it.

Friday night · a car comes back short

The shift cannot close until the money and the car both add up.

23:40

Rafiq ends his last duty in the driver app

Fare AED 118.75, collected in cash. The app records it against the duty, not against his memory.

23:52

He hands the car back

Odometer in, fuel level in, four photos. The reading must move forward from the one he took at the start — the app refuses a lower number.

23:55

The count comes up AED 40 short

Cash collected across the shift versus cash declared. The gap is named, attached to the shift, and routed to the office — not absorbed.

00:04

The office approves; custody closes

Until someone with the authority to accept a variance does so, the session stays open. A shift cannot quietly end on an unexplained shortfall.

How the suite holds the record →

The four records that decide the month

A published tariff, an allocation with its reasons, an odometer reading at both ends, and a cash count that has to balance. Every figure in an SK Fleet report traces back to one of them — there is no number in the system that nobody can explain.

Send us a month of jobs →
The chauffeur-operations workflow

A price you can defend.
A car you can account for.

SK Fleet owns what is genuinely specific to chauffeur-driven rental — tariffs, duties, ordered stops, custody, settlement — and reads everything generic from the suite. Customers live in SK CRM, invoices in SK Billing, drivers in SK People, cash in SK Company Cash. Nothing is duplicated, so nothing drifts.

A tariff that prices the same job the same way twice

Four fare models — distance, hourly package, day rate and transfer — with the surcharges, waiting rules and excess-kilometre allowances written down as rates rather than remembered. The quote is stamped at the moment it is issued and held; if the price should change, the old quote is superseded, never edited.

  • Night, airport and peak windows derived from the clock, not applied by hand
  • A shown price cannot be altered after the fact — the ledger records who decided and when
  • A regulated floor per emirate, so a discount cannot go below what the law allows

Dispatch that can say why it chose that driver

Every candidate arrives with its facts already gathered — on shift, holds custody of a vehicle, distance, trips already taken today — and each fact carries the time it was true. Hard guards disqualify before scoring, so an off-shift driver is never merely ranked lower.

  • Offer or direct allocation; the calendar hold is the authoritative clock
  • A refusal names its reason, so the board can show why a driver was skipped
  • “Nothing could be allocated” is a recorded outcome, not a silent failure

Custody with a reading at both ends

A vehicle moves from the yard to a named driver and back, with odometer and fuel captured at handover and hand-back. The reading has to move forward; a lower number is refused at the point of entry rather than discovered in a report.

  • Photographs at both ends, stored in SK Drive, never in the app
  • Custody cannot close while its cash reconciliation is unapproved
  • The kilometres between two duties are attributable, not absorbed

Driver cash that has to balance before a shift ends

Fares collected in cash are recorded against the duty that produced them. At hand-back the count is compared with what was collected, and a shortfall is named and routed for approval — custody of company money is a decision someone makes, not a side effect of taking a fare.

  • Collections, floats and deposits held in SK Company Cash, not a spreadsheet
  • A driver holds read-and-record rights; opening an assignment is a finance action
  • Expenses post to SK People payroll with the period derived from when they happened

One operation, wired to the whole suite.

Fleet owns what only a chauffeur operation has — tariffs, duties, custody, settlement. Everything else is the suite: customers in SK CRM, invoices in SK Billing, drivers in SK People, cash in SK Company Cash, holds in SK Calendar, files in SK Drive. It holds references, never copies, so a customer’s number is right everywhere at once.

See the platform →

Dubai, Abu Dhabi and Sharjah on one board.

Regions carry their own tariffs, regulatory rules and billing branch, so a job is priced and invoiced under the emirate it actually ran in.

How tenancy works →

Priced per vehicle, once we know your shape.

SK Fleet is in active rollout with our first operators, so pricing is quoted against your real fleet size, emirates and job mix rather than published as a table we would have to caveat.

In development · talk to us for a quote
Talk to us →

Common questions.

How does dispatch decide which driver gets the job?
Fleet gathers the facts first — whether a driver is on shift, whether they currently hold custody of a suitable vehicle, how far away they are, how many trips they have already run today — and stamps each with the time it was true. Hard guards disqualify before any scoring happens, so an off-shift driver is never simply ranked lower. Every candidate keeps its reason code, which is what lets the board answer “why not me?” a week later.
Can a price change after the customer has been quoted?
No. A quote is stamped when it is issued and held for its validity window. If the price genuinely needs to change, a new quote supersedes the old one and both remain on the record with who decided and when. The invoice is raised from the same tariff the quote came from, so the number the customer heard is the number they are billed.
Does it hold its own copy of customers or invoices?
No. Fleet stores only what is genuinely specific to chauffeur operations — tariffs, bookings, duties, custody, settlement. Customers live in SK CRM, invoices in SK Billing, drivers in SK People, cash in SK Company Cash. Fleet holds an opaque reference to each and reads it fresh, so there is no second copy to drift out of date.
What happens if a driver’s cash does not add up?
The shortfall is named at hand-back, attached to that shift, and routed to the office for a decision. Custody cannot close while its reconciliation is unapproved, so a shift never quietly ends on an unexplained gap. Approving a variance is a finance action — a driver can record and read, but not resolve.

SK Fleet is in active rollout — first operators are live in the UAE

Starting

Two weeks from now, you’ll know if it works.

We set up one depot first — your vehicles, your tariffs, your drivers — and you run it alongside whatever you use today.

Day 1

We move your data across

Vehicles and classes, your tariff card, drivers, corporate accounts, open bookings.

Day 3

Your team gets an hour of training

Dispatchers need one session. Drivers need the app and about ten minutes.

Day 5

Real jobs run through it

Quote, allocate, drive, hand back, settle — we watch the first day’s duties with you and tune the tariff.

Day 14

We show you the count

Jobs run, quoted-versus-invoiced variance, unexplained kilometres, cash outstanding. If the numbers do not hold up, do not roll it out.

Send us a month of your job sheets.

We'll show you what it would have recovered — with your own numbers, not a benchmark.

Book a demo