For advisors, FSPs and lending businesses in South Africa.
Fixing onboarding only when you get an inspection notice, isn’t compliance.
A compliance step that depends on someone remembering to perform it will eventually be missed. A step built into the workflow is evidenced automatically, at the time it happens.
Read how FICA document collection can move from manual filing to an automated registry,
live on our blog.
We start with a discovery: a structured look at how documents, records and onboarding move through your practice right now, not how the process is supposed to work on paper.
We look at what is happening in your practice, not the org chart version. Deep discovery of the client process with security in mind is part of what makes us so effective.
We work out what each gap in the process, the manual re-entry, the untracked follow-up, the person-dependent step, is costing you in time.
What comes out is a written, prioritised set of findings, and a scoped plan for what changes. No system is proposed before the discovery is complete.
One introductory call, twenty minutes, no obligation. We will tell you plainly what we find.
Most practices do not need another piece of software to manage. What they need is their own process, the one already in daily use, built so that document requests, receipts and expiry tracking happen without anyone having to remember to do it. That is a different question from which software to buy, and it is the one we start with.
Off-the-shelf tools are built for every practice at once, which means every practice adapts to fit the tool. A Lumino build starts with a discovery of your specific practice and is scoped around what you do, not around a generic workflow you have to bend your business into.
No. Judgement calls, client risk profiling and due diligence decisions stay with the people qualified to make them. What changes is the administrative load around those decisions: the requests, the receipts, the tracking, the record.
Discovery is a paid, fixed-scope look at your current process. It ends with a roadmap: a written set of findings that you own. There is no obligation to build anything afterwards.
Every discovery starts with what is already in place in your practice: the product provider portals, the CRM, the spreadsheets currently holding things together. What gets built is scoped around that, not around replacing it .
Illuminate, the discovery, comes first. Blueprint maps the detailed solution. Build is where the system is delivered and tested under real conditions. The timeline depends on what the discovery finds, and we will not give you a number before we know that.
The parts of document collection that need no judgement: the request, the reminder, the receipt, the expiry date, and the tracking of when each of those happened. Risk decisions, client assessment and anything else requiring professional judgement stay with the people qualified to make them.
You do. Every tool account sits in your practice’s name from the start, so the system stays yours whether or not we are involved later.
Nothing prepared in advance. We work from how the process runs on an ordinary week, so what helps is access to the people who do the work rather than a tidied version of it.
The people who do the work daily, and whoever can decide what changes. A discovery built only from a manager’s account of the process misses where the real steps are.
