Platform
Private securityMotor retailB2B lead nurturingB2B quoting & fulfilment
Quoting & SalesOperationsAssets & ComplianceWorkforceRecruitmentBack office
Data & InsightsAutomationsContextual Workspace
PlansResourcesContact
Enterprise & supplier development

You have to spend it. This is where it goes.

South African companies are required to spend part of their profit developing black-owned suppliers. Most of that money buys a receipt. We turn it into a working system that lives inside the supplier’s business and reports back what it changed.

Telematics and tracking
Trips
Fuel and card spend
Every fill
Accounting and ERP
Cost lines per vehicle
Payroll and people
Employees
Maintenance and workshop
Service jobs

The five systems a small operator already runs. We attach to them. Nobody is asked to migrate anything.

Book a walkthroughStart at the beginning →
01The problem

The budget is compulsory. Somewhere worth putting it is not.

Enterprise and supplier development is a legal obligation, not a donation. It is also the part of the scorecard companies handle worst, and have for years.

3%
of net profit after tax, due every year
15
scorecard points riding on it
under half
of the national target actually deployed
Why it gets stuck

A grant produces a receipt and nobody learns what happened to it. A training course ends. Neither makes the supplier better at supplying you, so procurement never cares, and next year starts from nothing.

What is being asked for now

Evidence of outcomes, not evidence of spend. Most of what corporates fund today cannot produce that, because nothing is left running once the money is gone.

02What it is

A working system, placed inside the supplier's business.

Not a course and not a cheque. The supplier keeps it when the programme ends, which is what supplier development was always supposed to mean.

01
It attaches to what they already run

A transport contractor has a tracker because the insurer demands one, and an accounting package because SARS does. Asking them to abandon those is why most programmes are never adopted. We read from them instead.

02
It answers what no single system can

The fuel card knows litres bought. The tracker knows litres burnt. Neither sees the gap between them, and that gap is diesel paid for that never reached an engine. Every useful answer in the platform has this shape.

03
It reports itself, every quarter

Adoption, outcomes, and the source of every figure, generated from the records rather than written up by somebody at year end. That is the part a grant can never do.

The supplier's own view of their five systems, three attached, showing what each connection turns on

The supplier’s own screen. Three of five attached, and the platform is explicit about the two that are not.

03What it connects to

Five systems, and every way we get into them.

27 connectors in the catalogue, 13 of them live today. Open a row to see all of them, and the state each one is actually in.

Bought for recovering a stolen vehicle, and satisfying an insurer who requires a unit fitted. The unit is wired into the vehicle and the contract runs 36 months.

  • CartrackLive APILive
  • MiX by PowerfleetLive APIIn build
  • NetstarLive APIIn build
  • CtrackLive APIIn build
  • Tracker ConnectScheduled filePlanned
  • WebfleetLive APIPlanned

Bought for letting drivers buy diesel, tolls and tyres without carrying cash. The card is issued by their bank and tied to the account the business runs on.

  • Bank fleet cards (4 issuers)Scheduled fileLive
  • Engen Fleet CardScheduled fileLive
  • Shell CardScheduled fileLive
  • Sasol Fleet CardScheduled fileIn build
  • On-site bulk tankCaptured hereLive

Bought for producing annual financial statements and filing VAT. Their accountant works in it, and the year-end depends on it.

  • Sage Business Cloud AccountingLive APILive
  • XeroLive APILive
  • Sage Pastel PartnerScheduled fileLive
  • QuickBooks OnlineLive APIIn build
  • Sage EvolutionScheduled fileIn build
  • Zoho BooksLive APIPlanned
  • SAP Business OneLive APIPlanned

Bought for paying people and filing PAYE, UIF and SDL with SARS. Changing it mid-tax-year is a job nobody volunteers for.

  • SimplePayLive APILive
  • PaySpaceLive APILive
  • Sage VIP PremierScheduled fileLive
  • Sage 300 PeopleLive APIIn build
  • Xero PayrollLive APIIn build

Bought for nothing, usually. This is the fragmented one. Most of it lives in a book, which is why the platform can simply hold it.

  • Workshop spreadsheetScheduled fileLive
  • Captured on the platformCaptured hereLive
  • Cartrack MaintenanceLive APIIn build
  • MiX Fleet MaintenanceLive APIPlanned

Where a vendor publishes nothing usable, the stream is captured on the platform instead and the screens say so. Nothing here implies a feed that does not exist.

04What it collects

Everything held, and the obligation each part answers.

Twenty-three record types across six groups. The supplier can see every field held about them, which is the only reason they keep capturing.

Movement
Trips, positions, distance, load carried, engine and idle hours.
The activity data behind any emissions figure.
Fuel and energy
Every fill, litres, rand, station, odometer, and litres burnt against litres bought.
Scope 1 emissions, and the carbon tax return.
Money
Cost lines per asset, revenue and supplier invoices, reconciled bank lines.
Unit economics, and the financial half of any development claim.
People
Employees, pay runs, hours worked, training, and self-declared demographics.
Skills development, employment equity, and the denominator of every safety rate.
Safety
Incidents by severity, days lost, and the driver and vehicle involved.
OHS reporting, and the client SHEQ questionnaire.
Compliance
Licences, operator cards, insurance, tax clearance, B-BBEE affidavits, with expiry dates.
Proof the supplier is trading legally, on the day you are asked.
The register of every record type held, with field counts, retention and what the customer is allowed to see

Personal information is marked as such and never crosses to you against a name, only as workforce totals. That boundary is enforced in the platform, not promised in a contract.

05What it answers

Answers the supplier's own vendors cannot produce.

Twenty-three of them. Each names the systems it needed, and refuses to estimate the rest.

Is diesel going missing?

Litres bought on the card against litres burnt by the engine. The difference is fuel that never reached a vehicle.

Card + tracker
What does a kilometre cost?

Fuel, maintenance, finance and tyres against real distance, per vehicle.

Card + tracker + accounting
Can the emissions number be defended?

Scope 1 derived from fuel records and checked against what was actually burnt.

Card + tracker
Is anything on the road illegally?

Licences, operator cards and cover, with a warning before anything lapses.

Documents + payroll
Are drivers worked past the record?

Hours spent on the road against the hours they were paid for.

Payroll + tracker
When does an asset stop paying?

Whole-life cost against what it still earns, so replacement is a decision rather than a breakdown.

Four systems

Every answer, and how many systems each needs before it can be produced at all.

Insight catalogue showing what each connection is worthOne vehicle showing cost per kilometre and unaccounted dieselContextual workspace answering questions across the supplier's data
Swipe to read the screen
06Who gains what

Three parties, and each has to get something real.

A programme that only serves the scorecard is abandoned by the supplier inside a year.

The supplier
A business they can finally see.
  • Knows what a job costs before quoting it, rather than after
  • Finds fuel loss that was invisible to every system they owned
  • Produces a compliance record on demand, not reconstructed at year end
  • Keeps the platform when the programme ends
The funder
Spend that can be defended.
  • Fully claimable supplier or enterprise development
  • Adoption and outcome evidence per beneficiary, every quarter
  • Suppliers who quote faster and deliver more reliably
  • A programme still producing value after the financial year closes
The people in it
The part that is easy to forget.
  • Drivers paid for the hours they actually worked
  • Expired licences caught before a roadblock finds them
  • Safety incidents recorded properly rather than absorbed
  • Skills and training tracked against a person, not a spreadsheet
07What you file

At the end of the quarter, the report writes itself.

Built from the same records the supplier reads about their own business, so it cannot disagree with what they see.

Adoption

Active users, logins, records created and transactions processed, per beneficiary.

Outcomes

Response times, admin hours removed, systems retired, revenue movement, jobs created.

Compliance

Access control, audit trail, and how personal information is handled under POPIA.

Provenance

For every figure: which system it came from, and whether it was pulled or declared.

The uncomfortable part

The platform also reports how much of the programme is not yet coming from a connected system. Every ESD report that shows only its successes asks a transformation manager to sign something they cannot defend. Stating the gaps is what makes the rest of it credible at verification.

Every supplier in the programme, with figures derived from their own records.

Programme dashboard showing suppliers with emissions, fuel intensity and capture statusCoverage screen stating what share of data comes from a system of recordEvidence pack screen offering per-quarter per-supplier packs
Swipe to read the screen

The screens on this page are the live platform, captured as it renders. The companies, people, vehicles and figures in them are generated for demonstration. No client of ours appears anywhere on this page.

What transformation teams usually ask.

No, and that is the whole premise. A transport contractor runs a tracker because the insurer requires a unit fitted and an accounting package because SARS requires a return. Asking them to abandon those in exchange for a development programme is why so many programmes are never adopted. The platform attaches to what is there and produces the answers none of those systems can produce alone.
Five system classes: telematics, the fuel or fleet card, accounting, payroll and maintenance. Fourteen connectors are live today, the rest are in build or planned, and the platform states which is which rather than implying a feed that does not exist. A supplier is usually live inside thirty days, because attaching to systems they already run is a far shorter job than migrating them onto a new one.
Because the supplier already owns that system and already reads its reports. Value here is combinatorial. The fuel card knows how many litres were bought; the tracker knows how many were burnt. Neither can see the difference between them, and that difference is diesel that was paid for and never reached an engine. One system attached answers five of the twenty-three questions; two answers fourteen.
A grant produces a receipt and the funder never learns what happened to it. A training course ends. Neither makes the supplier measurably better at supplying you, so procurement has no reason to care and the following year starts from nothing. A deployed platform cannot be misspent, does not stop when the financial year closes, and generates its own evidence as a by-product of being used.
A pack per beneficiary per quarter: adoption, meaning active users, logins, records created and transactions processed; operational outcomes; business outcomes; compliance position; and the provenance of every figure, meaning which system it came from and whether it was pulled or declared. It is generated from the same records the supplier's own screens read, so it cannot disagree with what they see about their business.
Operating and compliance data only, never their pricing, their margins or their other customers. Personal information about their employees crosses only as workforce totals, never against a name. A supplier who discovers otherwise stops capturing, and the programme dies with them, so the boundary is enforced in the platform rather than promised in a contract.
Exempted Micro Enterprises under R10 million turnover and Qualifying Small Enterprises under R50 million, at least 51% black-owned, evidenced by a sworn affidavit or a verification certificate. Enhanced recognition applies where the beneficiary is at least 30% black-woman-owned. Supplier development means businesses that already supply you; enterprise development means ones that do not.
The supplier keeps the platform. It is not licensed back or withdrawn at term, because an asset that leaves when the programme ends is exactly the failure the Codes intend supplier development to avoid. You can renew for a new cohort or extend the existing suppliers.
Yes, and it is the first thing to be clear about. The Codes permit a measured entity to recognise payments to a suitably qualified third party performing ESD initiatives on its behalf. The B-BBEE status that has to qualify is the beneficiary's, not the implementer's, which is the same structure corporates already use to pay training providers, mentorship firms and consultancies out of ESD budget. We are the technology provider; the development happens to the beneficiary. Confirm the structure in writing with your verification agency before signing.
No. The screens are the live platform captured as it renders, but the companies, people, vehicles and every figure in them are generated for demonstration. No client of ours appears anywhere on the page.

See the platform in your business.

We walk through what it does for businesses that look like yours.

Book a discovery callSee the platform