Finch becoming a software benefits broker
Jeremy Zhang, CEO of Finch, on building a universal API for employment systems
This points to Finch trying to move from plumbing to distribution. Today Finch mainly helps benefits and HR apps connect to payroll systems and write deductions, but if enough apps run through Finch, it can start shaping which benefits get surfaced to employers, much like a broker that helps an employer pick plans, enroll workers, and push payroll deductions into the right system. That is a much higher leverage position than charging only for API access.
-
Finch already sits on the key workflow a broker touches, employer onboarding, eligibility data, enrollment, and deductions. Its Deductions product lets apps create benefits, set employer contributions and employee deductions, and enroll workers directly in payroll systems, which is the operational core of benefits administration.
-
The marketplace logic is similar to Plaid and Pinwheel. A universal API first aggregates fragmented systems, then gains power as more builders depend on it. Finch has described itself as a two sided network between apps and payroll providers, and Pinwheel describes the same pattern as a value add marketplace on top of core payroll data.
-
A traditional benefits broker wins by owning employer relationships and steering demand to carriers and point solutions. Finch could do a software native version of that. Instead of a human broker recommending plans over email and spreadsheets, Finch could route employers inside connected apps toward specific benefits products that can be activated instantly through its payroll rails.
If Finch keeps expanding from read access into write access and employer facing workflows, the company can become the default channel for launching new benefits products. At that point the biggest prize is not the integration fee, it is controlling discovery, activation, and ongoing payroll level administration for a large share of the employment software ecosystem.