Qarz Hasana: social finance SaaS platform

Qarz Hasana is a multi-tenant operations platform for interest-free community loan organizations. It combines branch workflows, role-based controls, donation tracking, and a structured loan lifecycle from application intake to funding and disbursement. I built it from a live pilot model and adapted it for independent organizations with configurable policies and branding.

Story

I built Qarz Hasana to replace fragile manual operations in community loan organizations. Many teams still depend on spreadsheets, chat threads, and informal records. That makes donor tracking, due diligence, and loan visibility unreliable.

The product model came from a real pilot organization in Bangladesh with nine branches and a shared treasury pattern. I translated that operating model into reusable product primitives, not one-off custom code. The core decisions were organization tenancy, branch-local workflows, configurable policy settings, and clear role boundaries.

The result is a SaaS foundation for multiple independent organizations. Each organization can manage its own branding, members, branch network, donation options, and loan limits inside one consistent model. Organizations make lending decisions, while the platform provides workflow and records. I shipped a full production pipeline from manager or public application intake through manager review, admin funding, and disbursement, with activity logging on key transitions.

Organization settings for loan policy limits and due-diligence checklist defaults.

Loan application detail view showing applicant profile and status progression through the review workflow.

Donation entry flow with fund source details and records that feed organization-level treasury visibility.

Impacts

Built a multi-tenant model where each organization runs with separate members, branches, branding, and policy settings.
Shipped core workflows from a live nine-branch pilot for branches, role-based access controls, donation tracking, and loan applications through funding and disbursement.
Added a public no-login loan intake flow with strict server-side validation, automated abuse protections, and submission limits.
Implemented per-organization login branding and installable app identity for each organization.

Challenges & Solutions

Challenges

The pilot required multi-branch operations and shared treasury controls, but the product still had to work for other organizations.
Loan processing needed strict role boundaries between branch managers and organization admins.
Staff needed a workflow simple enough for non-technical teams but strict enough to enforce real loan operations.
Financial records had to stay reliable across donations and loan lifecycle events in multi-branch operations.

Solutions

Used organization-level tenancy and configurable policy settings so pilot defaults can scale without one-off hardcoding.
Enforced a clear status model with server-side transition guards for manager review, admin funding decisions, and disbursement.
Designed role-specific forms and status-driven actions so branch teams can operate daily workflows without losing process discipline.
Standardized server-side validation, auditable activity logs, and status-driven workflows so records stay traceable across branches and roles.