Skip to content Skip to sidebar Skip to footer

Fintech Product Strategy: What Real Lending Journeys Reveal

PRODUCT INTELLIGENCE

Fintech product strategy starts where the public product tour ends

Digital lending products are built from hundreds of decisions about borrower effort, loan conditions, repayment and the path back to a second loan. We study those decisions through controlled journeys and turn observed behavior into product questions leaders can actually investigate.

The lending product is more than the application form

A product team can redesign its landing page without changing the borrowing experience. Once an applicant enters a lending app, the decisive product architecture becomes visible: which data is required, how identity is checked, which offer is presented, where the true cost appears, and what happens after repayment. Treating these as separate departmental problems hides how they interact.

At FintechProduct, our product intelligence work follows the borrower beyond the first approval. Loan 1 reveals acquisition design. The interval after repayment reveals retention signals. Loan 2 reveals whether the lender uses the information it already has to improve access, pricing or workflow. This full-cycle view is particularly useful to product managers making trade-offs among conversion, risk controls and customer lifetime value.

Product decisions behind first-loan friction

Friction is not one metric. An additional document, a duplicated field, an unclear OTP error and a long disbursement wait impose different costs and belong to different owners. A friction review needs field counts, action screens, elapsed time, identity-verification events and observed interruptions. A smooth document-verification service cannot compensate for a form that repeatedly demands information the borrower does not have.

In a documented Doctor Peso journey in Colombia, the borrower completed 35 fields across 12 screens in 16 minutes. Biometric verification took about 90 seconds without leaving the app, but another field required a company telephone number, forcing the applicant to exit and look it up. The evidence points to a form-design question, not necessarily a biometric-vendor problem.

The product should recognize a returning borrower

Loan 2 is an opportunity to see whether customer history changes the product. Is previously submitted information retained? Does the application repeat biometric verification? Can the borrower review a second offer without completing a new application? Does a successful repayment unlock more credit, different terms or a new product tier?

In the observed Doctor Peso repeat-loan journey, application time fell from 16 minutes to 3 minutes 41 seconds, with no new fields or repeat identity verification. In a separate ALVOS journey in Mexico, the observed application fell from 12 minutes 42 seconds to about two minutes. These are distinct lender studies, not controlled causal tests of retention rates. What they do establish is that returning-borrower workflows can be materially different from first-time workflows.

Conditions evolution is product design, not just pricing

Credit amount, term, interest, fees, extension availability and minimum loan barriers form a combined offer. A lender can increase the approved limit but make the minimum loan unaffordable. It can simplify Loan 2 without changing financial incentives. It can introduce a visible locked product to signal progression before eligibility is reached.

In our Doctor Peso research, a locked installment-loan option was visible as a product progression cue. Yet the two observed loans retained the same core pricing structure; the lower second-loan limit occurred after a period of late payment and cannot be generalized to borrowers who always pay on time. That distinction matters when a product team interprets competitive findings.

Pricing disclosure is part of the product architecture

A pricing screen answers more than ‘how much?’ A well-designed credit journey clarifies the amount disbursed, total repayment, fees, penalties, dates, available extensions and contract access before the borrower commits. A useful audit records the precise screen where each component becomes visible and whether any condition changes without an explicit alert.

Cost architecture and cost visibility are different analyses. A lender may calculate total charges accurately but explain them late. Product teams should examine both the economic mechanism and the decision context offered to the borrower, including access to the signed contract after disbursement.

Questions a product leader can take into the next sprint

Can we identify the specific input requests that drive app exits? Are identity-verification errors visible as separate funnel events rather than a single KYC failure? What percentage of known borrowers must re-enter existing information? Do borrowers understand extension costs before they are late? Is the next-loan proposition visible to someone who has just repaid?

The best competitive intelligence does not automatically prescribe changes. It gives the team an external observation to compare with its own completion rates, risk policy, underwriting criteria and customer research. Internal outcomes must be measured before assigning revenue or conversion impact.

Explore the evidence and its commercial applications

Our fintech UX research looks closely at borrower effort and identity verification. The Borrower Journey Intelligence Report follows a single lender through two loans; the Competitive Benchmark compares several lenders under standardized conditions.