Finch Neutral Data Pipe for Payroll
Jeremy Zhang, CEO of Finch, on building a universal API for employment systems
This reveals Finch is trying to become the neutral data pipe for a market where the same payroll infrastructure company can play three roles at once. A white label payroll vendor can buy Finch to avoid building dozens of HRIS connectors, partner with Finch to make its own product easier to plug into benefits or fintech apps, and invest because more embedded payroll products mean more fragmented back end systems, which makes Finch more valuable.
-
Check and Gusto Embedded sit one layer below Finch. They help a software company launch payroll inside its own product, while Finch helps apps sitting above payroll read employee data, sync records, and write deductions across many underlying providers. That makes the relationship complementary more often than head to head.
-
The economic reason these companies become Finch customers is simple. Building payroll is not the same as building connectivity into every legacy HR and payroll system an employer already uses. Finch said the top 10 providers cover only about 55% of the market, and getting to 75% coverage would require 40 to 50 connectors.
-
This is also why overlap is normal. Gusto markets Embedded Payroll as infrastructure for software platforms, and Check markets embedded payroll for 80 plus platform partners. As more platforms launch payroll, the number of systems an app must connect to rises, which increases demand for a standard API layer above them.
Going forward, the winners in payroll infrastructure are likely to split into system builders and connection builders. More vertical SaaS companies will launch branded payroll through Check, Gusto, and similar vendors, and that should expand the number of fragmented employment systems in market. Finch is positioned to capture the integration layer that makes that sprawl usable.