Interview with Maya Srinivasan, Former Head of Growth, Lending@Scale


Why do personal-loans companies suddenly care about global supply chain management when scaling?

Most mid-level growth folks see “supply chain” and think widgets. In personal loans, the supply chain is data, capital, onboarding infrastructure, and—oddly—regulatory compliance. The concern surfaces when you try to increase approved loan volume across markets and realize your underlying vendors, risk checks, and decisioning workflows can’t stretch that far. More direct answer: you care when your underwriters and disbursement partners abroad start missing SLAs, or your new KYC vendor creates bottlenecks in one country.


What’s the first thing that breaks at scale?

First breakage is usually at the data handoff points. I’ve seen credit decisioning systems buckle when loan volume spikes by 6x in three months because their data pipeline wasn’t architected for batch reconciliation. For example, Lending@Scale’s 2022 Q4 campaign in Southeast Asia saw loan-approval lag times jump from 15 minutes to over two hours. The team realized they were running daily rather than real-time fraud checks between their core lending platform and their new regional identity provider. Manual workarounds tripled.


Where do automation efforts make the most difference as you expand?

Automate the stuff that slows people down or adds compliance risk. In personal loans, this means onboarding (KYC, AML, PEP checks), bank account verification, and offer delivery. Automated document verification is a big win, but only if your tool is trained on local ID formats. A 2024 Forrester report found that onboarding automation cut drop-offs by 31% for lenders expanding into LatAm, mostly by removing friction from phone-based ID upload. But be careful: automating rejection handling can tank your NPS if you don’t build in an appeals loop.


Which process bottlenecks hurt growth the most?

Vendor onboarding for new data sources is always slower than teams expect, especially if procurement isn’t set up for multiple jurisdictions. Another choke point: loan disbursement partners who don’t support local payout rails. One team I saw spent nine months negotiating with a local payment processor, only to discover their API couldn’t return confirmation in under 20 seconds, leading to 12% of loans flagged as “pending” for hours. The real cost is lost conversion—those users don’t come back.


How do you decide what to outsource vs. build in-house?

Outsource anything where regulatory norms or integration requirements change frequently by market: document verification, KYC, negative lists, translation/localisation. Build in-house if the process directly impacts your core user experience or contains proprietary logic (e.g., credit decisioning, offer personalization). Here’s a simple comparison:

Process Outsource if... Build in-house if...
KYC/AML Checks You’re entering >2 new markets a year You have 1-2 stable markets
Disbursement Integration Local payout rails are inconsistent You own a licensed financial entity
Credit Decisioning Local bureau data isn’t differentiated You have proprietary risk models
Customer Support Languages/localization is a moving target You’re optimizing for CSAT

What mistakes do mid-level growths make when expanding teams to handle scale?

They hire for volume, not for adaptability. You see a rush to add operational staff in new markets but ignore training on escalation paths. Worse, teams onboard staff with narrow expertise—say, just in onboarding fraud—but lack generalists who can rewire a process when a vendor goes down. At Lending@Scale, we onboarded a dozen local support agents for Indonesia, but only one could handle basic product troubleshooting. When the SMS gateway failed, all tickets escalated to HQ, causing a 4-day backlog.


How can growth teams monitor system health across markets?

Set up dashboards for SLA adherence across all critical vendors: onboarding, decisioning, disbursal, repayment. Use survey/feedback tools like Medallia, Zigpoll, or Delighted seeded at key moments—application submit, approval, payout. Track not just NPS but also time-to-resolution on failed or delayed payouts. Something as simple as a real-time counter for “loans pending disbursement >30 min” can save you a week of sifting through logs. Don’t rely on vendors’ native dashboards alone—they’re always rosier than reality.


What’s a non-obvious regulatory snag that can derail scaling?

Document retention laws. Each country interprets KYC retention differently—some require seven years, others prohibit storing ID images at all. In 2023, a major European lender expanding into Vietnam was hit with an injunction after storing over 40,000 national ID images on AWS outside the country. They lost two months remediating data flows and rewriting privacy disclosures. Solution: map your data flows before you launch and consult with a local specialist, no exceptions.


Any advice for mid-level growths on prioritizing supply chain upgrades?

Don’t gold-plate everything. Prioritize fixes based on customer drop-off data and regulatory heat maps. If users are abandoning at the ID upload stage at twice the rate in one region, start there. If regulators are cracking down on payout speed, focus investment on your payments partners. You’ll never have the budget to automate every link. And be ready to backtrack—a solution that scales well in one region may break your SLA elsewhere. Accept that some manual patches are the cost of doing business at scale.


Anything that just doesn’t work, no matter how much you optimize?

Trying to force-fit a global onboarding or document workflow without accounting for local quirks. Some regions require wet signatures. Others ban cloud document storage. The most sophisticated tech stack can’t fix regulatory mismatches. You need both local compliance expertise and a flexible process that lets you swap out vendors or steps as needed. Otherwise, you’ll end up with beautiful automation... and routinely blocked disbursals.


Final tactics for staying ahead of scaling shocks?

Build in redundancy for every critical process—two disbursement partners, two KYC sources—and set up alerts when performance degrades. Create an “expansion playbook” of what broke last time and share it across teams. And don’t trust vendors’ promises on uptime or scalability; demand proof, preferably from a peer in your region.


Summary Table – What Mid-Level Growths Should Watch When Scaling Personal Loans Globally

Area Typical Failure at Scale Fix or Prevention Limitation/Caveat
Data Hand-offs Batch delays, pipeline errors Real-time integration, monitoring Vendor APIs may limit speed
KYC/AML Checks Manual backlogs, compliance Outsource to regionally aware vendors Vendor swap-out is painful
Disbursements Payout lag, local rail gaps Local partners with proven APIs Some rails lack redundancy
Vendor Management Slow onboarding, SLA miss Pre-vet providers, contract agility Procurement slows multi-market
Regulatory Compliance Data storage, retention Local legal review, flow mapping Ongoing, unpredictable changes
Team Building Skill gaps, slow escalations Cross-train, adaptable hiring Churn in new markets
Automation Over-automation, NPS drops Focus on customer-impact stages Manual edge cases persist
Monitoring Blind spots, vendor opacity Independent dashboards, feedback Vendor data may lag

Scaling personal-loans businesses across borders is less about building a mega-platform, more about watching for weak links, patching rapidly, and keeping one eye on local quirks. The best growth operators I’ve seen are part process architect, part firefighter, part diplomat—never just spreadsheet jockeys.

Start surveying for free.

Try our no-code surveys that visitors actually answer.

Questions or Feedback?

We are always ready to hear from you.