1 MIN READ
Product
Put the switch where your users already are
InstaSwitch now deploys as individual modules: funding, income platforms, payroll, bills and subscriptions, vendors, and customers. Put each one where that work already happens in your product, so the switch is available at the moment a business is ready to move.
Daniel West
After completing thousands of business switches, we know account opening is the highest intent moment to turn a new account into the primary operating one. Some businesses do it right there, in one sitting. The rest do it on their own schedule: when the next payroll runs, when an invoice goes out at month end, when a vendor bill arrives. Every one of those moments is another chance at the switch, but only if the switch component is there when the moment arrives.
The complete switch at account opening is still what to build for. A business that starts the Instaswitch flow moves income, payroll, bills and subscriptions, vendors, and customers in one session, median under 15 minutes. Accounts where income moves in the first 7 days carry 95% higher lifetime value, and income moving first is what pulls everything else across.
Without that, about three in five accounts never get there. They never fund or they complete the opening transfer and then sit, with payroll still landing at the old bank and the merchant processor settling where it always has. You hold an open account with a balance and no operating activity behind it, and the business that opened it moved on weeks ago.
Those accounts are not coming back on your timeline. They return on their own clock, and each switch runs on the business' timeline. A merchant processor settles daily, so income can move the moment someone decides to move it. Payroll waits for the next run, and vendors need to be updated and customers wait on the counterparty to act. Each of those moments can arrive inside a different part of your product, and a flow that only lives in onboarding reaches some of them.
That's why we built Instaswitch modularly. You know your customers and you built the experience they move through, so you decide where each module goes - income, payroll, spend, vendors, and customers.
Every switch deploys as its own module
Instaswitch is the account activation infrastructure underneath all of this. The full flow maps a business's transaction history, identifies what needs to move, and suggests the funding amount that gets your new account primary. From there it updates income, spend, and payroll online, and guides the business through the vendor and client updates that run over ACH or Wire. That flow has been live with customers across hosted and embedded deployments since last year.
Now, income platforms, payroll, spend vendors, and customers each deploy as an individual module, alongside a funding module that calculates the opening deposit. Take one or take all six, and put each where the matching work already happens in your product. Every module renders under your brand.
We spend a lot of time with banks and fintechs thinking about the right entry points of our modules. Most of these modules live at account opening, but now can also live across the experiences below:
Funding Recommendation, at account opening and on the operating account with $0 in it. The Funding Module that helps get funds deposited at the point of entry.
Income platforms, at account opening and on the accounts built to receive income. Include the Income module in the opening flow and on any account a business opens to receive income. When a business opens a sub-account for rental income or uses a model that routes operating income to an account, they’ve told you that there’s income to move. The module can surface that switch directly in those accounts.
Payroll, at account opening and in dedicated payroll accounts. A separate payroll account is a smart practice for many growing businesses. When a business opens one or adds this account through the treasury team, put the Payroll module in this account so payroll gets paid from this account the moment the account is opened.
Spend, wherever expenses live. Many fintechs and banks give spend its own surface: a vendors page, expenses views, or card activity. The Spend module moves a business’s subscriptions and ex penses and it belongs wherever that spend shows up.
Vendors, wherever your users create payees. These are the vendors a business pay over ACH or Wire, and each one needs a payee created in the new bank account. The Vendors module imports vendor data through CSV or accounting integrations, then passes it back to your ACH or Wire templates or API to create the payees..
Customers, at account opening, on accounts built to receive income, and wherever invoices go out. Customers control where the payment goes, so they need new remittance instructions. The Customers module helps businesses send its clients their new account and routing details, so the next payment lands in the new account.
Any module, behind a re-engagement trigger. An incomplete switch is a signal, and Instaswitch knows which piece is missing. A business that came through onboarding without moving payroll is a specific account with a specific gap, and your lifecycle or banking team can act on it. Put the module behind that outreach, or in your dashboard, and the follow up ends in the switch instead of a phone call.
You also control which switches appear at all. For a bank built around short term rental hosts, or one running a real estate segment where rental income drives the primary relationship, surface the Airbnb, VRBO, and Booking.com income switches by default, whether or not a business connects an account.
What sits behind every module
Every module draws on the same catalog: 380+ tools across income sources, payroll, bills and subscriptions, vendors, and customers. We built the slow way. Every guide came from running the switch by hand, over 3,000 hours of it, because switching instructions found online are wrong 90 to 95% of the time. 35+ of those updates now run as automations that finish in under 30 seconds reliably.
This is also the first step toward full control. The modules shipping today are the building blocks of the API and white-label components later this year, when the execution layer runs entirely behind your own interface.
If account opening is outpacing activation on your side, book a discovery session and we'll map which modules move your number first, let’s talk.
