From Connector to Outcome Layer

The real risk for a universal API company is that the connector itself becomes the least valuable part of the stack. Once a customer can get the same raw connection from a rival, from the underlying platform, or by building around the API, pricing gets squeezed. The durable businesses are the ones that turn the connection into a workflow customers keep buying, like direct deposit switching, underwriting data, deductions, fraud tools, or other products that save labor or drive revenue.

• In payroll and HR, the connector is useful because the market is deeply fragmented. Finch has described roughly 6,000 U.S. employment systems, with the top 10 covering only about 55% of the market. That fragmentation creates demand for middleware, but it also means many providers can chase the same basic aggregation layer over time.
  3 sacra 4 sacra
• The way out is to own a high value use case, not just the pipe. Pinwheel started with direct deposit switching, then expanded into income verification, underwriting inputs, and paycheck linked money movement. That makes the product closer to a business outcome, getting a customer funded, approved, or repaid, instead of just an API call.
  1 sacra 2 sacra
• Plaid is the clearest precedent. As bank aggregation matured, coverage and connectivity became more comparable across providers, which limited pricing power. Plaid responded by bundling payroll, identity, ACH risk, and enriched transaction products on top of its network, using distribution from its core install base to sell higher value software.
  2 sacra 4 sacra

The next phase of this market is a shift from universal APIs as connectors to universal APIs as operating layers for specific workflows. The winners will be the companies that sit in the money flow or decision flow, where replacing them would mean lost conversion, more fraud, more manual work, or worse underwriting, not just swapping one connector for another.