01 The situation
Distribution for consumer lending increasingly happens where people already are — inside the apps they open every day, not on a lender’s own site. So the same personal loan journey needed to run inside two large consumer platforms.
That turns a product build into a three-way program: the lender who owns the loan, the platform that owns the user, and the team building the journey in between.
02 What made it hard
Almost none of the difficulty was in the journey itself.
- Each platform has its own constraints on how an embedded journey can look and behave
- Consent and data-sharing have to be right between three organisations, not two
- Partner reviews and release windows run on their calendars, not yours
- The borrower must always know which regulated lender they’re actually dealing with
03 What I did
Kept one core journey, adapted only at the edges. Rather than building a separate flow per partner, the core lending journey stayed the same and only the entry point, presentation and hand-offs changed for each platform. One thing to test, one thing to fix.
Ran it as a program across three organisations. A shared sequence everyone could see, clear owners on each side, and an escalation route agreed before anything went wrong rather than improvised after.
Planned around partner timelines from day one. Review queues and release windows outside our control were treated as fixed dependencies in the plan, not surprises discovered near the end.
In partner integrations, the critical path usually runs through someone else’s organisation. The most useful thing a program manager can do is find that path early and keep the conversations on it moving — long before anyone is waiting on it.
04 What happened
- The personal loan journey went live inside both consumer apps
- One core journey served the lender’s own channel and both platforms
- The same approach carried over to the business loan journey on a loan marketplace
05 What I’d take into the next one
Map every organisation’s approval path in week one. Engineering estimates are rarely what decides a launch date in embedded lending — the review cycle you don’t control is.
