Developer-First Enables Sales-Led Growth
Jeremy Zhang, CEO of Finch, on building a universal API for employment systems
This reveals that developer-first for Finch is mainly a trust and adoption layer, not the main revenue engine. In practice, clean docs, a self-serve dashboard, and fast sandboxing help product and engineering teams validate Finch quickly, then the actual contract is often won through a sales process with a limited set of larger HR, benefits, and B2B fintech buyers. Finch is following the same specialized API playbook Jeremy points to in Plaid.
-
Finch sells into a narrow set of higher value buyers, not millions of developers. Its customers are benefits providers, B2B fintechs, and HR tools that need payroll and employment connectivity across fragmented systems, which makes sales assisted buying more natural than pure self serve.
-
Developer-first still matters because it shortens the proof step inside a sales cycle. A buyer can read the docs, test the API, inspect the schema, and see the employer auth flow before legal, security, and pricing discussions, which makes an infrastructure vendor feel credible faster.
-
The strongest comparison is not Twilio or Stripe at their most viral stage, but specialized API companies that sell deep workflow value. Finch is not just exposing data, it helps customers read payroll data, write deductions, and move employer workflows that were previously handled by CSVs, SFTP, and large ops teams.
Going forward, the winners in universal APIs are likely to combine consumer grade developer experience with enterprise sales and deeper products above the connector layer. For Finch, that means using developer-first tooling to open doors, then expanding revenue through more write workflows, more employment data models, and more value added products on top of the integration base.