Market Insight
Platforms should select embedded lending partners for lifetime customer coverage, not Day 1 approval rates.
A financing product can be easy to launch, approve a broad initial population and generate attractive economics — and still become the wrong product as those customers mature.
That creates an embedded lending paradox: the better your customers perform, the more likely they are to outgrow a single-product financing program.
For platforms, the implication is straightforward. Optimize financing around the lifetime of the customer, not the first loan.
Three factors determine whether a program can do that.
1. As businesses mature, their financing options expand — and embedded products have to compete
Younger businesses and companies with limited credit histories operate in a constrained credit market. Their alternatives are limited.
Merchant cash advances and similar products can fit this segment well. Embedded distribution can improve that proposition further: a platform may have transaction data and repayment mechanisms that reduce friction and support access to capital.
But successful businesses do not remain in a constrained credit market forever.
Operating history grows. Revenue becomes more established. Credit profiles develop. More financing providers become willing to compete for the business.
The relevant alternatives can expand to term loans, accounts-receivable financing, accounts-payable financing, inventory financing and other forms of commercial credit.
That changes the competitive equation.
Approval is most valuable when alternatives are scarce. Product fit and competitiveness become more important as alternatives expand.
A platform can therefore have a financing program that performs well today while creating a retention problem tomorrow.
The customers most likely to encounter that problem are often precisely the ones the platform should want to retain: established, growing businesses with larger capital requirements.
The uncomfortable implication: a single-product program can become least competitive for a platform’s most valuable customers.
2. Different cash-flow problems require different financing products
“Working capital” is not one problem.
A distributor purchasing inventory before it can sell it, a carrier waiting for an invoice to clear, and a supplier funding a confirmed purchase order may all need capital.
Economically, however, they are financing different things.
| Customer need | Underlying cash-flow gap | Financing structure to evaluate |
|---|---|---|
| Inventory | Cash leaves before inventory sells | AP / inventory financing |
| Receivables | Revenue is earned before cash arrives | AR / invoice financing |
| Purchase order | Fulfillment costs precede customer payment | PO-linked financing |
| General growth | Capital is needed across the business | Term / working-capital loan |
The distinction matters because platforms often possess something outside lenders do not: context.
They may already see orders, invoices, payments and transaction history. They may know the buyer and seller. In some cases, they can observe the underlying economic event creating the need for capital.
That context should inform the financing structure.
Kanmon’s existing model reflects this principle: multiple white-labeled financing products can be delivered through one integration, with Kanmon handling the lending infrastructure while the platform retains the customer relationship.
The strategic advantage is not embedding a loan. It is embedding the right capital against the right need.
A platform that offers only one financing structure risks forcing fundamentally different customer problems through the same product.
3. The economics improve when financing becomes a relationship, not a transaction
Most embedded lending evaluations naturally emphasize launch metrics:
- Integration time
- Approval rate
- Initial conversion
- Customer pricing
- Platform revenue share
Those metrics matter. But they disproportionately measure the beginning of the relationship.
The more important economic question is what happens afterward.
A customer that successfully accesses capital once may need it again. Its financing requirement may increase. Its use case may change. Its available alternatives may expand.
The platform has an advantage if that customer can return to the same environment, access an appropriate product and build on an existing financing relationship.
That changes the objective from borrower acquisition to borrower retention.
It also changes the meaning of convenience.
Convenience is not simply a shorter application. It is the accumulated advantage of not having to start over.
The platform already has the customer. The workflow already exists. Relevant operating data may already exist. The financing relationship can develop history.
The strategic value of embedded lending is not the first financing transaction. It is the second, fifth and tenth.
That is where a broad financing capability can outperform a narrow product over the customer lifecycle.
Near-term conversion can still beat breadth — but that is the wrong optimization if customers mature
There is a legitimate counterargument.
A single financing product can be easier to implement and operate. It may approve customers that have limited alternatives. It can create attractive platform economics without requiring a broader financing architecture.
For some customer populations, that may be exactly the right solution.
The mistake is extrapolating that success across the entire customer lifecycle.
The single-product model remains strongest if three conditions hold:
1. The customer population remains relatively homogeneous.
Financing needs do not materially diverge as customers grow.
2. Customers remain credit-constrained.
They do not gain materially better alternatives outside the platform.
3. Initial conversion matters more than long-term financing retention.
The economics of the first transaction outweigh the value of maintaining the financing relationship.
For many B2B platforms, those are restrictive assumptions.
If customers mature, capital needs diverge and outside financing alternatives increase, product breadth becomes a retention capability rather than a feature checklist.
Platforms should benchmark lending partners on five measures, not one
The decision framework should therefore move beyond “Who can launch this fastest?”
Evaluate an embedded lending partner across five dimensions:
- Coverage: How much of the customer lifecycle can the program appropriately serve?
- Fit: Can the financing structure match materially different uses of capital?
- Competitiveness: Does the proposition remain viable once customers have outside alternatives?
- Convenience: Can customers repeatedly access capital without rebuilding the financing relationship elsewhere?
- Durability: Can the relationship expand as qualified customers grow and their financing requirements change?
Approval rate belongs inside that framework. It should not substitute for it.
The winning embedded lending program should become more valuable as the customer becomes more valuable
Kanmon is built around this lifecycle view.
Platforms can offer multiple white-labeled financing products through one integration. Kanmon manages underwriting, funding, compliance and servicing. The platform maintains the customer relationship.
That architecture matters because customers do not remain static.
A carrier waiting on receivables should not necessarily receive the same financing structure as a distributor buying inventory.
A mature business should not be limited to a product optimized for businesses with constrained access to credit.
And a growing customer should not need to leave the platform because its financing needs have outgrown the product originally integrated there.
The objective is not maximum lending volume at any cost.
It is a financing capability that remains relevant as the underlying businesses become larger, more sophisticated and more valuable.
Do not optimize embedded lending for the first loan. Optimize it for the lifetime of the customer.
Maarten van der Putten serves as VP of Partnerships at Kanmon, where he works with vertical software platforms, marketplaces, and other technology companies to build embedded capital programs around how their customers actually operate.