Choosing a build path on Unit
How to think about ownership in your embedded finance program across technical, operational, and economic dimensions
Most platforms evaluating embedded finance face the same decision: how much do we own, and when?
A team validating a new revenue stream has different needs than a team making financial products central to their product. Both are legitimate starting points. Both need a path forward that doesn't lock them in.
Unit offers two implementation paths: Ready-to-Launch, where Unit manages the implementation and ongoing program operations under your brand, and Custom, where your team builds on Unit's API and owns the experience end to end. What makes this worth paying attention to is that both run on the same underlying infrastructure: ledger, bank integrations, and payment rails. That means your starting point doesn't determine your ceiling, and you don’t need to commit to a single operating model at launch. You can begin with the managed solution and take on more ownership over time. You can build custom for your core products and let Unit manage a module you don't have the bandwidth to build yet. You're not choosing a permanent model; you’re choosing the right starting point for ownership.
Both paths involve three dimensions of ownership: Technical (what you build), Operational (what you run), and Economic (what you earn and what you're responsible for). The spectrum runs from low control and low effort to high control and high effort.
- Ready-to-Launch sits at the low-control, low-effort end. Unit handles the product build, the operational processes, and takes on substantially more of the program’s financial risk. You earn a share of the revenue.
- Custom sits at the other end. You build the product, run the operations, and assume greater operational and economic responsibility for the program. In exchange, the economics are more favorable.
Ready-to-Launch: Unit owns all three dimensions
1. Technical. With one line of code, you can embed a full financial dashboard for your customers that gives them visibility and solutions for cash flow. You can embed the entire dashboard, or choose one or more of the layers to start: Banking, Bill Pay, and Capital. Adding a second product requires no additional technical work on your end. Unit builds and maintains the product interface your customers see. The product continues to get better over time, with no investment from you.
Webhooks let you connect financial events to your own platform's logic. A payment received can trigger an action in your system. An account created can kick off a workflow. Platforms use this to link accounts payable transactions directly to jobs in their product. The financial layer and the core product stay in sync without your team building or maintaining the financial experience itself.
2. Operational. Unit supports and manages a broader range of operational functions under your brand: end-customer support, escalations, bank-led compliance programs, and outbound communications from your domain. Unit provides you with branded enablement and tooling to drive adoption of the new product within your user base.
3. Economic. You assume substantially less operational and economic responsibility than in a Custom implementation. You earn a share of transaction revenue and deposit revenue.
Ready-to-Launch is the right starting point when:
- You want to validate demand before investing engineering and operational resources
- Your team doesn't have the bandwidth to build and run a financial product right now
Custom: you own all three dimensions
1. Technical. You build any money product for your customers, using enterprise-grade financial infrastructure as your foundation. You own the front-end and the back-end money flows.
2. Operational. Your team is the front line for customer issues. You use Unit's dashboard to investigate and resolve most cases. For complex escalations, fraud reviews, and card disputes, Unit may provide support through defined escalation and operational processes. You configure your help center, set SLAs, and train your support team. Read more about these responsibilities here
3. Economic. You bear the risk, as specified in your agreement. The variable economics on transaction revenue and deposit revenue are more favorable to you than under Ready-to-Launch. You can work with Unit and Unit’s bank partners to customize certain program terms for segments of your customer base.
Custom is the right starting point when:
- Financial products are central to your value proposition today
- Your team has the capacity to build and operate the product
- You want full control over the customer experience and the economics
Where you start isn't where you have to stay
Most platforms don't land permanently in one path. Because Ready-to-Launch and Custom run on the same infrastructure, moving between them or combining them doesn't require a new integration. There’s no migration to a different ledger, no new bank partnership to establish, and typically no full re-onboarding of your users, although bank policies and regulatory requirements may still apply.
A Ready-to-Launch customer who wants more control can migrate to Custom. The underlying infrastructure doesn't change: same ledger, same underlying bank integrations, same rails. What changes is operational ownership: your team takes on the work of building the customer experience, managing risk, and aligning the product to your customers’ specific needs.
A Custom customer who doesn't have the bandwidth to build a particular product from scratch can layer on Ready-to-Launch for that module. You keep full ownership of the products you've built, and let Unit manage the ones you haven't.
This also means you don't have to forecast perfectly. If you start on Ready-to-Launch because you're validating demand, and that demand turns out to be real, you haven't painted yourself into a corner. If you start on Custom because financial products are central to your platform today, you can still move faster on adjacent products by letting Unit manage them.
Find your starting point
How central are financial products to your value proposition today? If you're testing the thesis, Ready-to-Launch lets you validate with minimal overhead. If financial products are already how your customers think about your platform, Custom gives you the control to make them exceptional.
Do you need to control your own program terms? Under Ready-to-Launch, certain program terms are set by Unit in coordination with the bank partner and aren't adjustable by the platform (e.g., interest rates on deposit accounts, identity verification rules for onboarding, the specific criteria used to approve or decline users). If your business requires more flexibility over those parameters, Custom may provide additional options, subject to bank and regulatory approval. If the default terms work for your customers, Ready-to-Launch removes the overhead of managing them.
What can your team take on right now? Ready-to-Launch means Unit builds the product and runs the operations. Custom means your team owns those layers. That lift is real, and it should match your current capacity.
What risk profile works for your business? Ready-to-Launch generally involves substantially less operational and economic responsibility than a Custom implementation. Custom means more favorable economics in exchange for owning that risk.
If you're still working through those questions, talk to our team.
For engineers evaluating the paths
The infrastructure underneath Ready-to-Launch and Custom is the same. Same ledger. Same bank integrations. Same payment rails.
Under Ready-to-Launch, your integration is a single line of code. Under Custom, your team builds on the API.
Migrating from Ready-to-Launch to Custom isn't a new integration against a different platform. The work is operational: taking on the product build, support ownership, and risk management. Explore the sandbox to see what building on Unit looks like.
Frequently asked questions
Can I combine build paths: Custom for some products, Ready-to-Launch for others?
Yes. A Custom customer can layer on Ready-to-Launch for a product module they don't have the bandwidth to build. Both run on the same infrastructure.
Can I move from Ready-to-Launch to Custom later?
Yes. The transition is a change in operational ownership, not a technical migration.
What do I own versus what does Unit handle?
It depends on your path. Ready-to-Launch is designed for customers who want Unit to take on the operational work that comes with managing a fintech program. Custom is designed for customers who want more control, with the option to use Unit's capabilities or own more of the operating model directly. The specific allocation of responsibilities depends on the implementation and applicable Roles & Responsibilities framework.
Can I pick just one Ready-to-Launch module?
Yes. Banking, Bill Pay, and Capital are independently configurable. You can start with one and add others without any additional integration work.
How long does it take to launch on each path?
Ready-to-Launch is designed to get you to market in three weeks or less. Custom timelines depend on what you're building - a team launching a single deposit account use case will move faster than one building a multi-product financial workflow. Talk to our team to get a realistic estimate for your scope.
