
Implementation
Move to Ustawi without disrupting your operation.
- Process
- 8-step journey
- Data migration
- Validated before go-live
- Go-live
- Phased, starting with a pilot
What implementation includes
Configuration
Your products, branches, users, approval rules, accounting and reports set up around how you work.
Data migration
Your clients, active loans, balances and schedules moved across and validated before go-live.
Integration
Payments/mobile money, SMS, CRB and fiscalization connected where you need them.
Training
Role-based training for every team that uses the system, in Kiswahili or English.
Go-live & support
A controlled, phased launch and ongoing support at your plan's tier.
The 8-step journey
- 1Discovery
We map how your institution works today — products, branches, roles, approval levels, interest and fee structures, and the reports you must file. Nothing is configured blind.
- 2Configuration
Your tenant is set up: loan products, branches, users and capability-based roles, approval ladders by amount band, fees and interest methods, chart of accounts and report templates.
- 3Data migration
Your existing book is moved across — from Excel/CSV or an existing loan/core system — and validated before it goes live (see below for exactly what we migrate and how).
- 4Integration
Where needed, connect the external services you use (payments / mobile money, SMS, CRB, fiscalization) via the Integration Hub, configured per tenant.
- 5Training
Role-based training for the people who use the system daily — administrators, loan officers, accountants, branch managers and field agents.
- 6User acceptance testing (UAT)
Your team validates real workflows on your own configured tenant — origination, approvals, collections, accounting and reporting — before anything goes live.
- 7Go-live
A controlled production launch, typically starting with a branch or product and expanding — a managed transition rather than a big-bang switch.
- 8Support & review
Post-launch support at your plan's tier, with a review of how the first cycles ran and adjustments where they help.
Bring your existing book with you.
Your loan book is your business — so migration is validated before it ever reaches production, and you approve it before go-live.
Customer data
- ✓Names & contact details
- ✓Identification details
- ✓Customer groups
Loan data
- ✓Active loans & products
- ✓Principal & outstanding balances
- ✓Interest & repayment schedules
- ✓Arrears / days past due
Institution data
- ✓Branches
- ✓Users & roles
- ✓Loan products
- ✓Chart of accounts
We configure Ustawi around your institution.
Organization
- Branches
- Departments
- Users
- Roles
Lending
- Loan products
- Interest methods
- Fees
- Approval limits by amount band
Finance
- Chart of accounts
- Accounting rules
- Financial reports
Controls
- Approval workflows
- Permissions
- Maker-checker rules
Training for every role.
Delivered in Kiswahili or English.
System administrators
Configuration, users, permissions and system management.
Loan officers
Customer registration, applications, assessment and loan servicing.
Accountants
Transactions, reconciliation, general ledger and financial reports.
Branch managers
Portfolio monitoring, approvals, branch performance and controls.
Field agents
Collections, receipts, offline workflows and synchronization.
Who does what
| Ustawi | Your institution |
|---|---|
| Configure the platform | Provide your business requirements |
| Support the data migration | Validate your source data |
| Set up integrations | Provide third-party credentials |
| Deliver role-based training | Nominate the users to train |
| Support UAT | Test the workflows |
| Support go-live | Approve the production launch |
| Post-launch review | Share feedback from the first cycles |
Go live with control.
Pilot
Start with one branch, product or a controlled group.
Validate
Confirm transactions, reports, balances and workflows.
Expand
Roll out to additional branches and users.
Monitor
Review the first operational cycles together.
What we'll need from you
To scope and start implementation, it helps to have these ready:
- ✓Existing customer & loan data (Excel/CSV or an export)
- ✓Branch information
- ✓User list & roles
- ✓Loan product details
- ✓Interest & fee structures
- ✓Approval rules
- ✓Accounting structure (chart of accounts)
- ✓Reports you must produce
- ✓Integration requirements & credentials
- ✓Key implementation contacts
Implementation FAQ
Can you migrate our existing data from Excel or another system?
Yes. We migrate clients, active loans, balances and repayment schedules from Excel/CSV or an existing loan/core system, mapped and validated before go-live.
What happens if something is wrong with our existing loan book?
Migration is validated before it reaches production — source data is reviewed, fields are mapped, data-quality issues are surfaced, a test migration is run, and totals are reconciled. You review and approve the migrated data before the production migration and go-live.
How long does implementation take, and can we start with one branch?
It depends on your size, branches, apps and data quality — we scope a realistic timeline during discovery rather than quoting a fixed number. A phased go-live (starting with one branch or product) is the norm, so the change stays controlled.
Do you provide staff training?
Yes — role-based training for administrators, loan officers, accountants, managers and field agents, in Kiswahili or English. Guided onboarding is included on the Priority and Dedicated support tiers; the Standard tier includes self-guided setup with documentation and the Help Center — see the Support plans page.
How much does implementation cost?
Implementation scope is arranged per institution — see the Pricing page for what drives it, and request a consultation for a tailored scope and quote.
Let's plan your move to Ustawi.
Tell us about your institution, current system and lending operation — we'll define the implementation scope, migration approach and rollout plan with you.