12.3 Phase 3 — SaaS / LSP partner portal

Goal

Productise the platform far enough that a partner RE (bank or NBFC) can use it as their digital-lending stack — with the lender as the RE on books and the platform as the LSP earning fees.

Features

• Rich partner portal — origination MIS, policy configuration, branding tweaks, reporting, audit access.
• Tenant-aware data model (light multi-tenancy: tenant_id on every entity).
• Per-partner KFS / agreement templates.
• Per-partner policy + workflow configuration.
• Per-partner fee economics — origination, servicing, SaaS.
• Embedded SDK / iframe for partner UIs.
• DLG-as-LSP arrangement if applicable.
• API / SFTP both supported for daily MIS exchange.

Integrations

• Additional partner integrations.
• One or two embedded distribution partners (CA software, accounting cloud, marketplace).

Team

• Add 2 engineering for multi-tenancy.
• Add 1 – 2 customer success / partner success.
• Add 1 enterprise sales.

Time

3 – 4 months.

Build vs buy

• Multi-tenancy framework: Build (start light; full tenant-isolation by Phase 7).
• Partner portal: Build (rich, role-based).
• SDK for embedded distribution: Build.

Acceptance criteria

• One LSP-style customer live (own NBFC’s book or second NBFC).
• Per-partner reporting works end-to-end.
• Multi-tenant data isolation tested.
• LSP fee flows confirmed in P&L.

Risks

• Customisation requests fragmenting the codebase.
• Multi-tenancy bugs leaking data across tenants (high-risk).
• Sales cycle long; expectations need management.

Go / no-go for Phase 4

• Stable phase 3 operations.
• Underwriting team ready to evaluate ML / advanced features.