Portfolio-first framing
The interface is built around book health and recovery stage exposure, which makes the product story feel strategic as well as operational.
Recovery and Collections/admin5 screens
NDB Botswana - Loan Recovery and Portfolio Management
Loan recovery hub for borrower accounts, lending portfolio analysis, repayments, communications, and AI-assisted portfolio oversight.
Screen walkthrough
A fuller gallery for the product story.
This gallery shows progression, not just a single hero frame. Use it to talk through navigation depth, records, analytics, and workflow context during a call.
/admin
Screen 01
Primary interface capture used for the listing card and story lead.
Overview
NDB Botswana presents itself as a broader servicing and portfolio environment than a simple collections queue. The dashboard names borrower accounts, lending portfolio, repayments, communications, and portfolio AI, with exposure and activity metrics oriented around recovery stages.
Strongest story angle
Use this case study to talk about portfolio management tools that sit between lending operations, borrower servicing, and recovery execution.
Observable modules
Portfolio DashboardBorrower AccountsLending PortfolioRepaymentsClient CommunicationsPortfolio AIRepayments by Portfolio SegmentExposure by Recovery Stage
Why this one works
Three angles worth carrying into the final write-up.
Borrower servicing visibility
Borrower accounts, repayments, and communications sit alongside recovery metrics, which gives the platform a fuller banking workflow shape.
Banking-grade positioning
This is a strong reference point for case-study copy aimed at loan servicing, restructuring, or recovery teams inside banks.
Motion outline
This sequence can still become a short teaser.
- 01
Lead with the portfolio recovery title and main dashboard metrics.
- 02
Animate borrower accounts, repayments, and exposure-by-stage callouts.
- 03
Close on a narrative of portfolio control rather than isolated debt chasing.
Next publishing pass
The structure is now cleaner: better screenshots, stronger conversion paths, and shared page chrome that behaves correctly. The next layer is adding repository-backed build notes and verified outcome data.
Still worth adding
- 1. Verified repository context for stack and architecture notes.
- 2. Approved proof points to replace generic performance language.
- 3. Short teaser renders once the repository evidence is in place.