South African consumers deserve to
know their options before they decide.
INSURELOANSA is a South African financial services platform built on a single premise: commission-motivated intermediaries and opaque processes cost South African consumers money, time, and rights they are legally entitled to. The platform eliminates the intermediary from the comparison decision — and eliminates the delay, the confusion, and the rejection from the claims process.
Not by replacing human advisors. By doing the information and processing work that intermediaries and institutions currently do badly or not at all.
The problems INSURELOANSA solves
South African consumers make permanent financial decisions with incomplete information.
The platform exists because three specific failures in the South African financial services market create real harm for real consumers — and because those failures are solvable with the right infrastructure.
The Broker Problem
Commission structures create steering — not always intentionally.
A South African consumer seeking funeral cover calls a broker. The broker shows them one insurer — the one that pays the highest commission that month. The consumer has no way to know what five other insurers would have charged. They sign. They pay more than they needed to, for possibly less cover than they could have had. This is not fraud. It is structural conflict that the current intermediary model does not resolve.
The Claims Problem
Bereaved families navigate insurer processes alone, in distress.
A bereaved South African family submits a funeral claim directly to the insurer. They do not know that Assupol requires a certified copy of the death certificate while Hollard accepts a funeral parlour certificate. Their claim is rejected. They resubmit. They wait six weeks for funds that were payable in days. Nobody told them what was wrong the first time. The platform that assembles, validates, and submits their claim correctly — before it reaches the insurer — does not exist in the South African market.
The Access Problem
Forty percent of South African adults are underserved by traditional financial services channels.
They have WhatsApp. They do not have a broker's number. They cannot navigate insurer websites on a limited data connection. They have never been shown what products they qualify for, at what price. SAM — the AI comparison assistant on WhatsApp and voice — is built specifically for this consumer. The same comparison capability, the same product knowledge, the same lead submission — by WhatsApp, by phone, in plain language.
Platform architecture — two live modules
Two modules. Two South African problems. One platform underneath both.
The modules are architecturally separate — independent backend services, separate database tables, no shared API logic. The shared layer is the frontend, the Supabase project, the SAM AI assistant, and the POPIA compliance infrastructure. A failure in the claims module cannot affect the marketplace. A deployment to the marketplace does not require a claims release.
Financial Marketplace
"Compare every option. Pay for what suits you. Decide for yourself."
The only people who benefit from opacity in financial product comparison are the intermediaries. A broker shows the consumer one insurer — the one that pays the highest commission. The consumer has no idea what five others would have charged.
9 product verticals. 40+ insurers and partners. Real confirmed prices in Rand. Side by side. In under 2 minutes. No login. No personal details required to see prices. Available on web, WhatsApp, and voice.
Key metrics
See the full module
Architecture · data flows · compliance position · tech stack
Funeral Claims Acceleration
"Your claim. Assembled correctly. Submitted within 2 hours."
Funeral insurance claims are rejected not because the claim is wrong — but because the dossier is incomplete. Most policyholders do not know that Assupol's document requirements are different from Hollard's. They find out after rejection.
1–2 hour processing from complete document upload to insurer submission. 94% first-time approval rate. Human advisor reviews every claim before it reaches the insurer. Available to any South African funeral policyholder — regardless of which insurer or how the policy was obtained.
Key metrics
See the full module
Architecture · data flows · compliance position · tech stack
Regulatory position
INSURELOANSA is not a broker. The law says so. The architecture says so. The copy says so.
Every public-facing statement, every AI assistant boundary, and every API endpoint reflects the same legal position. This is not a disclaimer at the bottom of a page — it is a design constraint that shapes every technical decision in the platform.
The Tristar Position — Financial Marketplace
The Financial Marketplace operates as a comparison and lead-generation platform. INSURELOANSA earns introduction fees from insurers and partners — not regulated commission from intermediary services. This distinction is confirmed by the Supreme Court of Appeal in the Tristar case. It does not require an FSP licence in lead-generation mode. FSP Category I Sub-Category A application is in preparation to activate full intermediary services.
SAM's Legal Boundary — Enforced in Code
SAM presents factual product information across web, WhatsApp, and voice. SAM compares prices. SAM explains cover, waiting periods, and exclusions. SAM does not recommend. SAM does not advise. This is enforced architecturally: createApplication() is dormant until FSP is issued. What is live is createLeadFromWebsite() and createReferral(). The legal boundary is a code boundary, not just a copy boundary.
Claims: Processing and Submission — Not Advice
The Funeral Claims Platform processes and submits claims. It does not tell consumers whether their claim is valid. It does not interpret policy terms. It does not advise on legal rights under the policy. The human advisor who reviews every claim before submission is the qualified advisory layer. The platform is the processing infrastructure. FICA, POPIA, and FAIS compliance are built into the pipeline — not added afterwards.
FSP Category I Sub-Category A — Application in Preparation
On FSP issuance, createApplication() activates across four files and the full intermediary model goes live — replacing the current lead-generation model with a fully licensed advice and application pathway. The architecture is already built for this transition. The switch is a four-file activation, not a rebuild.
Platform architecture
One platform. Two isolated modules.
The marketplace and the claims platform share a frontend, a Supabase project, the SAM AI assistant, and the POPIA compliance infrastructure. Beyond that shared layer, they are fully independent — separate FastAPI services, separate Celery queues, separate database schemas, separate Railway deployments.
This isolation is regulatory as much as architectural. FICA-governed claims processing must be independently auditable and independently deployable without marketplace entanglement. A claims pipeline deployment must not require a marketplace release. An insurer reviewing the claims platform sees a discrete, documented service — not a component of a larger consumer platform.
SAM is the single component that crosses both modules — the same WhatsApp number, the same VAPI voice agent, the same plain-language approach. The routing logic determines which module's backend handles the conversation based on intent classification.
SAM — three channels, one assistant
Web
Embedded in QuoteWizard — comparison, qualification, and lead submission
+27 60 014 5992 · Twilio · All 9 products · 24/7
Voice
VAPI · 10 functions active · SA English register · create_application dormant
Shared technology stack
Frontend
Next.js 14 App Router · TypeScript · Tailwind CSS · Vercel
Backend
FastAPI Python 3.11 — two independent services (marketplace + claims)
Database
Supabase PostgreSQL + pgvector · Row-Level Security · South Africa region
Twilio WhatsApp Business API — SAM on +27 60 014 5992
Voice
VAPI — SAM voice agent · 10 functions active · SA English register
Auth
Supabase Auth (consumers) · POPIA consent gate on all data pathways
Storage
Supabase Storage — claim documents · signed URLs · expiry enforced
Payments
PayFast — SA gateway · fee-per-claim model in preparation
POPIA compliance — platform-wide
- Explicit consent captured before any data collection pathway opens
- popia_accepted: true is an API contract requirement — not a UI checkbox
- All personal data stored in South Africa — Supabase SA region
- Channel consent gates: WhatsApp, SMS, email require active opt-in
- Sensitive fields redacted in all audit logs and external communications
- Data minimisation enforced — only fields necessary for the transaction collected
Both modules are live
Compare products.
Submit a claim. Both are live.
Nine product verticals. Forty providers. Confirmed Rand prices. A funeral claims platform with a 94% first-time approval rate. One platform. Two South African problems that have needed this infrastructure for a long time.