Embedded finance is one of the few categories where the supply side is genuinely ready. The demand side is not — at least, not the operating side of the demand side.
The reason a wave of embedded-finance launches stall around month nine is not regulation, not partner banks, and not unit economics. It is operating model.
What the Stall Looks Like
A non-financial brand — a retailer, a logistics platform, a SaaS marketplace — partners with a banking-as-a-service provider, runs a strong technical integration, launches a payments or lending product, and hits initial traction faster than the board expected. Month six is celebrated. Month nine is quietly difficult. The product team cannot get clean answers on KYC exceptions. The risk function is uncomfortable with how alerts are routed. Treasury cannot reconcile the float economics. Finance cannot get the cohort-level data they need for the next planning cycle.
The product still works. The organisation around it does not.
The Three Operating Seams That Crack First
The first seam is risk and compliance ownership. When a non-financial brand stands up a financial product, the existing compliance function is usually a contracts and policy team — not an operational risk function. Volume exposes that gap quickly.
The second is reconciliation and treasury. Cash flows in embedded products move in ways line accountants have not seen before — split disbursements, agency relationships, partner bank settlement cycles. Without dedicated treasury capability, month-end close gets ugly. The third is customer operations: disputed payments, fraud claims, and lending escalations need a service capability most non-financial brands have never built.
Designing the Org Before the Launch
The fix is not bigger headcount. It is naming, before launch, the four operating roles that have to exist on day one: a dedicated financial product owner with seniority equal to the brand's commercial leadership; an operational risk lead reporting to the CFO or COO, not buried in legal; a treasury specialist with embedded-product experience; and a customer ops lead for financial complaints, with the right service-level commitments to the partner bank.
Most embedded-finance business cases skip this section. Most stalls trace directly back to it.
What to do next
- Run an operating-model design workshop before — not after — the technical integration
- Name the four day-one operating roles in the business case
- Define the risk function's reporting line explicitly; do not leave it as 'legal'
- Treat reconciliation as a strategic capability, not a finance back-office task
Grant & Graham helps non-financial brands, marketplaces, and SaaS platforms launching financial products address exactly this kind of challenge. Our operating-model design and interim leadership for embedded finance launches is built for organisations facing an embedded-finance product that is technically live but operationally fragile. Email Andrew Collins or visit grant-graham.co.uk to discuss.
