Unified APIs Too Shallow For Enterprises
Ayan Barua, CEO of Ampersand, on going upmarket with deep native product integrations
The pricing backlash shows that unified APIs win the first integration demo, but often lose once customers need enterprise depth. A common model and hosted auth are valuable for pulling a few standard fields fast. But when a customer needs custom objects, tenant specific mappings, bulk writes, and field level debugging, the buyer still owns the hard part while continuing to pay infrastructure like it solved the whole problem.
-
The practical complaint is not that auth and token vaulting are useless. It is that they become a small slice of the integration workload in enterprise accounts. Ampersand describes the expensive work as configuration per tenant, rate limit handling, permissions debugging, and object and field level observability across customer environments.
-
This is why connection based pricing feels wrong in trial heavy or PLG motions. A vendor can rack up paid connections from users who connect a CRM or ads account but never convert, so the software company pays real integration costs before it earns real revenue from that account.
-
Unified APIs still make strong sense in categories where the job is mostly standardized data access. Finch shows the appeal in HR and payroll, where buyers want one way to read employee and payroll data across a highly fragmented market. The tradeoff is that standardization works best when the use case can live inside a narrower common model.
The market is moving toward a split. Breadth first APIs will keep owning fast, low customization use cases, while deeper infrastructure products will take the enterprise workflows where integration quality directly affects revenue. Over time, pricing will follow that divide, with shallow products priced more like access layers and deep products priced more like production infrastructure.