status
From one lender to a lender-agnostic platform
- Problem
- Brokers could submit personal loans to one lender. A second lender was coming, with no UI of its own and an API-only integration.
- My role
- Led the project: scope, phases and milestones, requirements, design and QA, working with the partner lender's team.
- Result
- The first lender's submission flow is live. The second lender's Phase 1 reused the existing flow and a standard payload, and is in final testing before go-live.
- Kept application status and lender status as separate fields, so one application can later go to several lenders.
- Added a ticket to confirm the API contract before any UI work, so engineers didn't build against a payload that might change.
- Limited Phase 1 to data we already collect. No new fields, documents sent as attachments. Speed over completeness, on purpose.
- Dropped my first idea, a plan modal inside the applications list, in favour of one unified Loans module.