The organisation studio is where an administrator at your institution sets up your loan products, opens accounts for your officers, decides who receives which file, and reads the reports on your team's work.
Everything an administrator looks after is here: your institution's settings, your loan products, your officers and the figures on their work.
One screen shows how things stand right now: applications in progress, which officers are working, activity in each module, and whether the system is running normally. Click any figure to see the detail behind it without leaving the page.
The first time you sign in as an administrator, you are taken through the setup in order: your institution's details, your logo and colours, a first practice loan product, your officers' accounts and how you want to be notified. Each step is checked before you move on, so nothing is left out.
The studio comes with four roles: super admin, product manager, officer supervisor and analyst, each with its own detailed permissions. If those do not fit, you can create your own. Permissions follow your organisation chart, so a branch manager sees only their own area.
A bar at the top of every studio page shows the approval rate on practice files, the average time a review takes, how much training is being completed, how busy your officers are and how satisfied the officers in training are. Set the limits you accept, and any figure outside them stands out.
When your officers sign in, they should see your institution. Here you set what they see, from your name and colours to your branches and the wording of messages, so it matches the rest of your institution.
Enter your institution's legal name, trading name, registration number, licence number and contact details. They then appear by themselves on the formal notices your officers see, in your email templates and in the training reports.
Upload your logo, choose your main colour and a second one, pick a typeface and decide where your brand appears. The portal, the emails and every PDF then carry your name and look. You see each change before you publish it.
Replace our standard wording on the welcome screens, the practice application instructions, the reasons a practice application is declined and the sample approval letters, so every screen your officers see sounds like your institution.
Add, change or switch off branches, with their GPS location, opening hours and phone numbers. Practice applications go to the nearest suitable branch by themselves, and new officers see a map of your branches when they first sign in.
You enter the loan products your officers practise on, with every detail from the amounts you lend to the documents each product needs, and you decide what each practice file puts in front of them.
Build a practice product on screen by dragging in the parts of the form: the amount, the term, the interest rate, the instalment schedule and the fees. Change their order, mark each one required or optional, and see the form as your officers will see it while you work.
Set the rules a practice application has to meet: how long the business has been going, its lowest acceptable annual revenue, the sectors you lend to and those you do not, the areas you cover, and past credit history. When an application falls outside them, the officer sees why, with other products that might fit, and learns how screening works.
For each product, choose which documents are checked (a trade licence, financial statements, a collateral valuation and so on). Mark each one required or optional, say how long it stays valid, and set the checks that flag an incomplete upload, so practice files ask for what a real file would.
Add questions of your own (a list to choose from, text, a number, a date or a file upload), with rules for what counts as a valid answer and a line of help for each. Save a set of questions as a template, and every new practice product can start from it.
Open accounts for your officers, give each one their area, and decide how files are shared out among them.
Invite officers one by one by email, or many at once from a CSV file. Give each a role (senior officer, junior officer or trainee) and set what they may do: only view, review, approve up to a limit, or everything. Each officer gets a welcome email in your institution's colours, telling them how to sign in.
Let practice files go to available officers in turn, so the work stays even, or choose by hand who gets a particular file. There is also a mixed setting, in which a supervisor can change an automatic choice before the officer is told.
Mark each officer with their branch, their region and the products they know. Each new practice file then goes to the officer best suited to it, by place, by product and by how much they already have.
LitFin Intelligence reads how your institution uses it: the conversations, the features people use and the way applications move. It tells you what it finds, so you can act on it early.
Each week, or whenever you ask, you get a report on which products are in demand, where applications get stuck and what changes with the seasons. Every point in it names what in your own data led to it, and what acting on it would involve.
The chat conversations inside your institution are read to find what your officers need and do not yet have: questions your material does not cover, things that often confuse people, and features they ask for. These are listed by how often they come up.
See which parts of the studio your team uses most, which hardly at all, and where officers spend most of their time, so you can find where your own way of working slows people down.
From the way your own institution works, specific changes are suggested: a shorter document list for a product, a different eligibility limit, or moving officers between branches. Each suggestion says what in your data it came from, and you decide.
These controls are in place today: each institution's data is kept apart from every other's, sensitive fields are encrypted, access follows each person's role, forged and unsafe requests are blocked, and the audit trail shows any attempt to change it. Three more are planned and not live yet: spotting unusual activity, handling incidents automatically, and a security dashboard. Our data protection page sets out what we hold and what we do not.
Your institution's data is kept apart from every other institution's in the database itself. Sensitive fields are encrypted where they are stored, and everything travelling over the network uses TLS. Access is strictly by role, forged and unsafe requests are blocked, and the audit trail cannot be changed without it showing. What is sent to an AI model is not stripped of personal details first; that is a deliberate choice, and our data protection page explains why.
This would watch for activity that looks wrong: a sign-in from a place the person could not be, many quick attempts to break into an account, someone trying to open what their role does not allow, or an unusually large download.
Once something unusual was confirmed, the security team would be alerted and an incident record opened, with what happened when, the evidence and the steps to put it right.
Audit logs cannot be changed and are kept for as long as you set, so your compliance team has a clear record it can download and check against your own obligations. LitFin Intelligence holds no approval or licence from any authority, and we do not vouch for your compliance.
A page in the studio would show open incidents and which controls are ready, with reports your compliance officer or outside auditors could download.
See every file in progress and how quickly each is moving, and download what you need for your management reports.
A chart shows how many practice applications are at each stage: started, submitted, in review, approved with conditions, approved, declined, and ready for disbursement. Click a stage to see the files in it, and compare how many move on from one stage to the next to see where your officers get stuck.
Follow over time the approval rate, the average loan size, the weighted average interest rate, the loans at risk and the mix of products. Break them down by branch, officer, product or region, and compare this period with your own past figures.
See how files are spread across the team: how many are open on each desk, how long they have been open, and where the queue is growing. It shows the work, not a ranking of people: LitFin Intelligence calculates no overall figure about any individual.
Download data as CSV, Excel or a formatted PDF. Reports follow the layouts your institution gives us, so your team keeps the format it already files in. You can also have exports sent on a schedule, by email or SFTP.
Mwikila, our AI Senior Agriculture & Finance Consultant, reads your own data and writes a brief for management: what changed, where the queue is growing, what to look at next and what he could not read. It contains no forecast, because we could not give one a range.
We go through the organisation studio with you, one part at a time, and set up your institution together. We give you a date before you commit to anything.