Unit vs. Direct Sponsor Bank
Unit is a well-designed BaaS platform. At the right volume and product stage, a direct sponsor bank relationship generates significantly more economics and product flexibility. Here is exactly what the tradeoff looks like.
| Dimension | Unit (BaaS) | Direct Sponsor Bank |
|---|---|---|
| Interchange capture | 40–60% revenue share → 50–90 bps net | Full capture → 130–160 bps net |
| Annual delta at $5M/mo | $360K–$648K | $936K–$1.15M |
| Annual gap at $5M/mo | $290K–$790K annually that Unit's middleware layer captures | |
| Float economics | Retained by Unit/bank — not passed through | Negotiable — 3–5% yield on customer balances |
| Time to launch | 60–90 days | 6–12 months |
| Compliance ownership | Shared — Unit handles significant layer | Full — you own BSA/AML, KYB/KYC program |
| Product flexibility | Limited to Unit's product surface | Full — limited only by bank appetite |
| Right for | Under $3M/mo, early product, fast launch | $3M+/mo, card issuing, full economics capture |
The Unit decision is not whether Unit is good. It is whether Unit's commercial defaults are the right economic structure for your program at your current and projected volume. Unit is well-built. At $5M+ monthly volume, the economics gap versus a direct bank relationship is typically $400K–$700K annually — enough to fund the compliance infrastructure and bank onboarding investment with significant margin left over.
When Unit is the right choice
Unit is the right starting point when: you are pre-product-market fit and need to launch financial products without infrastructure distraction; your monthly volume is under $2–3M; you need card issuing or deposit accounts but don't yet have the compliance team or operational infrastructure for a direct bank relationship; or you need to move in 60–90 days rather than 9–12 months.
The mistake is not starting on Unit. It is failing to design the migration trigger — the volume, product requirement, or economics threshold — at which you commit to moving to a direct relationship before you are constrained by Unit's contract terms and integration architecture.
When to move off Unit
The economic argument for migration becomes compelling at $3–5M monthly volume. At that level, the annual gap between Unit's revenue share and a direct model typically exceeds $300K — enough to justify the 9–14 month migration investment. The compliance and product flexibility arguments often appear earlier, when your program hits Unit's product ceiling or when your bank is tightening compliance requirements that Unit's infrastructure doesn't fully support.