Competing on Integration Quality
Zachary Kirby, co-founder of Vessel, on building the Vercel for integrations
Integration quality has moved from a nice to have to a revenue lever. In B2B SaaS, the winner is often the product that connects most cleanly to a customer’s existing system of record, especially Salesforce, HubSpot, and Zendesk. That means fewer setup steps, better field mapping, faster syncs, clearer logs when something breaks, and more control over edge cases, not just a badge that says the app connects.
-
Zapier solved breadth. It let apps claim hundreds or thousands of connections through a generic trigger and action layer. But that model often pushes users off product, into a separate setup flow, and into generic data mapping, which makes it weaker for the handful of workflows customers rely on every day.
-
The shift is from internal automation to customer facing product integrations. Internal tools are built for ops teams dragging blocks in a workflow builder. Customer facing integrations are part of the product itself, so engineers need code level control over auth, permissions, rate limits, custom fields, and tenant specific behavior.
-
This is why newer platforms split into two camps. Unified APIs help teams ship the first 20 to 30% fast with a common schema. Native integration infrastructure goes deeper, handling custom objects, pass through actions, ETL, observability, and enterprise specific variants, which is where vendors can actually win deals.
Over the next few years, integrations will look more like cloud infrastructure and less like one off side projects. Software buyers will increasingly assume the core systems already connect, and vendors that own the deepest, most reliable product integrations will convert faster upmarket, retain more customers, and pull integration work out of the long tail tool layer into the core product.