Portfolio and branch review
Use delinquency, migration, concentration and early-warning views to identify the next review question.
CBSRM · Microfinance platform
A clearer path from data to risk decisions.
A shared workspace for microfinance risk teams: review portfolio evidence, decide what needs attention, assign actions and prepare management reports. Built to work alongside your CBS and MIS.
Pilot development · Institution service under security review
CBSRMRisk review
Risk reviewBranch review
Actions
Notes & sessions
Calendar
Actions
Notes & sessions
Calendar
August portfolio review
Synthetic demonstration · NPR · 31 August 2026
Portfolio600
Review items7
Missing inputs6
Illustrative portfolio trend
Review branch collection movementReview
Request the missing balance sheetRequest data
Prepare committee evidenceDraft
One institution, its own workspaceMultiple branches and usersEnglish · नेपाली · हिन्दी
The decision layer beside your existing systems
Your CBS records transactions. Your MIS organizes information. CBSRM adds a structured risk-review workflow, with evidence, actions and explanations that people can follow.
Stress and missing-data discipline
Explore defined scenarios and see which inputs are required. Unavailable institution inputs must remain unavailable.
Actions and committee reporting
Keep responsibility, review notes, evidence and draft management material connected to the same snapshot.
From an approved data source to a reviewed decision
The product is being built around a repeatable process, with a human reviewer at the point where an institutional decision is made.
Connect
Approve the source, mapping, institution and branch scope.
Validate
Check dates, currency, completeness and scoped control totals.
Review
Read the risk evidence, assumptions and missing-input requests.
Act
Assign follow-up work and prepare reviewed management material.
A separate institutional workspace, with deliberate access
The SaaS design includes server authentication, institution and branch permissions, audit records and controlled support access. These controls are being implemented and independently checked before production onboarding.
- Strict institution data separation, with branch and role scope.
- Temporary support access only with institution approval, scope, expiry and an audit record.
- Country-specific hosting approved by the institution.
- Production identity and security review before real borrower or financial data.
Keep the human review simple
Calendar, contextual notes and working sessions are being added to the risk workflow. The intention is to keep preparation, decisions and follow-up in one place, with acknowledged saves and explicit sharing.
Your day and calendar
See review sessions, due actions and in-app reminders in context.
Notes and working sessions
Use private-default notes, agendas, reviewed minutes and revision conflict handling.
Future local AI provision
A disabled, provider-neutral extension is planned for future approved local models. The core workflow remains usable without AI.
Retrieve the inputs the analysis actually needs
The integration framework is designed for secure APIs and optional MCP access. Select an analysis, preview its required data and run an approved read. The human interface and approved clients must use the same institutional permissions.
- Versioned vendor adapters and mappings, rather than a promise to support every product automatically.
- Field, purpose, branch and date minimization before data leaves the approved boundary.
- Read-only source access; no loan, disbursement or ledger writes.
- Currency and country-specific analysis packs; no hidden currency conversion.
Institution licences. Partner support. One platform.
Each institution is licensed separately. An agreed partner can receive commission and/or annual maintenance rights, provide first-line support, and escalate to CBSRM for platform updates and specialist support. Commercial rights do not give routine access to institution data.
What you can evaluate today
The public demo demonstrates synthetic risk measurement. The new institution service, calendar/notes interfaces and integration framework are progressing through separate acceptance gates. A public product page is not a production security certification.
Available to explore
Synthetic browser demo and product walkthrough.
Under implementation and review
Authenticated multi-institution service; user/branch administration; calendar, notes and sessions; shared analysis jobs and API/MCP connectors.
Requires institution approval
Production identity, country hosting, source permissions, vendor/version conformance and approved policy settings.
Reproducible synthetic demo dataset · audit chain head
Questions before a pilot
Does CBSRM replace our CBS or MIS?
No. It is intended to work alongside them as a risk analysis and decision-support layer. Transactions and authoritative customer records stay in the source system.
Can any partner sell or maintain the platform?
Partners can work under agreed licensing, commission and AMC terms. Each institution is licensed separately; first-line partner support escalates to CBSRM for platform support and updates.
Can support staff see borrower data?
Commercial or support roles do not confer routine data access. Any temporary access requires institution approval, a defined scope and expiry, revocation and an audit record.
Is every CBS/MIS vendor already connected?
No. The framework is vendor-neutral. Actual compatibility must be verified for the specific product and version with its approved interface or sandbox.
Which languages and countries are supported?
The microfinance experience is being developed in English, Nepali and Hindi. Interface language is independent of country regulation and currency. Each analysis needs a compatible country and policy pack.
Does it make loan decisions automatically?
The current approach is explainable measurement and workflow support. Institutional lending and risk decisions remain with authorized human reviewers.
Is the AI assistant a deployed machine-learning model?
No. Transparent rules are not labelled as machine learning. Future local AI is a disabled extension until separately approved, and prediction models require lawful labelled history and real validation.
How much time will it save?
The pilot will measure manual steps and elapsed time using the institution’s process. We will not promise a percentage before a comparable benchmark is observed.
Plan a controlled institutional pilot.
Start with your process, approved sample data and a clear review objective. Agree the source interface, security requirements, country policy and success measures before onboarding.
Before you commit
Paid pilot available. Pricing on request.
A qualified institution receives the complete pricing schedule privately before accepting a pilot: total pilot cost, likely production subscription, implementation, connectors, training, support/AMC, taxes and conversion credit. The 90-day pilot uses agreed kickoff/readout milestones and starts only after accepted inputs, signed scope/data terms and cleared advance.
Free trial: 14 days, synthetic-only, no card or automatic charge. Real-data uploads and production integrations are disabled. Existing research/Desk access and its separate trial policy do not activate a microfinance institution.
Security and integration features remain under acceptance review. Production access and tested institutional SSO are enabled only after their actual readiness gates pass.