About Causa

Compliance meets purpose.

Causa did not start as compliance software. It started with a simpler question: how can we make giving easier?

Start with your first client

Why we built it

The money is already committed. The paperwork is what slows it down.

Every year B-BBEE moves real budget towards skills, suppliers and communities. That part is not the problem. What holds it up is evidence scattered across inboxes, spend recorded in a spreadsheet nobody quite trusts, and a scramble to prove any of it in the weeks before verification.

So we built the engine first. Causa gives the consultants who carry that work a way to run a whole portfolio without losing a point to a missing document.

The better that machinery works, the more of the spend actually lands where it was meant to. That is the whole reason this exists.

Who is on Causa

One platform, every side of the same transaction.

B-BBEE spend passes through a lot of hands before it reaches anyone. Causa puts those hands on the same system.

Consultants and their clients

The consultant runs the portfolio. Their client uploads into a shared vault and watches the same live scorecard.

NPOs, and SD and ED partners

The organisations the spend is meant to reach, listed free, and matched to the clients whose sector they fit.

Verification agencies

The people who have to sign it all off, receiving a pack organised the way they expect it.

The register

Every beneficiary is checked before anyone can fund them.

An organisation does not appear on the Causa register because it filled in a form. It appears once we have checked it, and the documentation behind that check travels with every contribution into the audit pack.

That matters because the risk runs both ways. A consultant needs to know the organisation qualifies. The organisation needs to be found by the people holding the budget.

Members of a community food garden tending raised vegetable beds

Where your clients' data lives

You are handing us a portfolio. Here is how we hold it.

Not a promise, a description of how it is actually built.

Hosted in South Africa

Causa runs in Google Cloud's Johannesburg region. The application, the database, and every document your clients upload.

Isolated per firm

Each firm's data is separated at the database level, not just in the interface, and that separation is tested on every change we ship.

Built for the audit

Every figure on a scorecard traces back to the document behind it, because that is what a verifier will ask for.

Come and take it apart.

The fastest way to judge Causa is to put a real client into it and generate the pack you would have to defend.