Plaid Model Applied to Payroll

Plaid turned bank connectivity into a shared utility, which let fintechs stop being single feature apps and start stacking adjacent products on top of the same linked account. Once a customer had already connected a bank account for one job, like funding a brokerage account, the marginal work to add checking, cards, lending, or crypto got much lower. That is the rebundling Jeremy Zhang is pointing to, infrastructure first broke apart the old bank bundle, then enabled new software bundles to form around the customer relationship.

• Before Plaid, banks kept data locked inside their own products. Plaid made that data programmable for apps like Venmo, Cash App, Chime, and Robinhood, using developer friendly APIs and pricing. That shifted the bottleneck from access to distribution, meaning the winning fintech was the one that could cross sell more products once the account was linked.
  2 sacra 3 sacra
• Rebundling happened because aggregation by itself got more commodity like. Plaid used its install base of 500M linked accounts and 2,600 fintech customers to move up the stack into income verification, deposit switching, identity, fraud, and ACH products. In other words, the connector became a product suite.
  2 sacra 4 sacra
• The same pattern is what Finch sees in payroll. Old suites like ADP bundled payroll, benefits, and insurance because the data stayed inside one system. A universal API lets newer specialists unbundle that stack first, then lets platforms like Gusto, Rippling, and others rebundle around the payroll system of record with a better product mix.
  1 sacra 5 sacra

The next phase is deeper rebundling around whichever company controls the source of truth and the easiest distribution surface. In fintech that means apps that already hold the customer’s money flow. In employment software it means whoever sits on top of payroll data and can turn many fragmented systems into one clean layer for benefits, lending, insurance, and workflow software.